Bug 2056 - _on_update_k8s_db and _on_update_n2vc_db take too much time on large models

Change-Id: Ifb8fff0b5a3f03821fea4863d6d8e6a51e0a3da0
Signed-off-by: Guillermo Calvino <guillermo.calvino@canonical.com>

diff --git a/osm_lcm/ns.py b/osm_lcm/ns.py
index 6aed304..9e2ac43 100644 (file)
--- a/osm_lcm/ns.py
+++ b/osm_lcm/ns.py
@@ -291,7 +291,6 @@ class NsLcm(LcmBase):
             # vcaStatus
             db_dict = dict()
             db_dict["vcaStatus"] = status_dict
-            await self.n2vc.update_vca_status(db_dict["vcaStatus"], vca_id=vca_id)
 
             # update configurationStatus for this VCA
             try:
@@ -399,15 +398,6 @@ class NsLcm(LcmBase):
             db_dict = dict()
             db_dict["vcaStatus"] = {nsr_id: vca_status}
 
-            if cluster_type in ("juju-bundle", "juju"):
-                # TODO -> this should be done in a more uniform way, I think in N2VC, in order to update the K8s VCA
-                #  status in a similar way between Juju Bundles and Helm Charts on this side
-                await self.k8sclusterjuju.update_vca_status(
-                    db_dict["vcaStatus"],
-                    kdu_instance,
-                    vca_id=vca_id,
-                )
-
             self.logger.debug(
                 f"Obtained VCA status for cluster type '{cluster_type}': {vca_status}"
             )