From 6c5ebec19f241b5ca67b73f761c750ace6fa037c Mon Sep 17 00:00:00 2001 From: Guillermo Calvino Date: Fri, 19 May 2023 17:39:46 +0200 Subject: [PATCH] Fix bug 1584 - Failure updating the ns state with distributed VCA Signed-off-by: Guillermo Calvino --- 06-osm-platform-configuration.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/06-osm-platform-configuration.md b/06-osm-platform-configuration.md index 69968be..55d2cec 100644 --- a/06-osm-platform-configuration.md +++ b/06-osm-platform-configuration.md @@ -720,6 +720,11 @@ Use the following command to register the installed VCA to your OSM: angelic-iguanodon-vca ``` +### Distributed VCAs and Juju Bundles + +Juju Bundles are composed by Charms, so we can execute day1 and day2 primitives directly in the Charms, without a new Execution Environment for that. For this reason, when we use a distributed VCA with Juju Bundles, there is one constraint that needs to be considered. The K8s cluster used in the dVCA must be the same where the workload is deployed. +That means that we need to add the K8s cluster that we are going to associate with our VIM account (see [this section](#management-of-k8s-clusters) for more details) to the distributed VCA we will use to deploy Juju Bundles. + ### Managing VCAs There are a few commands that will allow us to manage VCAs in OSM: -- GitLab