SMO-Install charts - A1 Controller updates

[it/dep.git] / smo-install / helm-override / pythonsdk-tests / oran-override.yaml

diff --git a/smo-install/helm-override/pythonsdk-tests/oran-override.yaml b/smo-install/helm-override/pythonsdk-tests/oran-override.yaml
index 27f9821..f8e608b 100644 (file)
--- a/smo-install/helm-override/pythonsdk-tests/oran-override.yaml
+++ b/smo-install/helm-override/pythonsdk-tests/oran-override.yaml
@@ -24,8 +24,8 @@
 
 ######### NONRTRIC #########
 
-nonrtric: 
-  installPms: false
+nonrtric:
+  installPms: true
   installA1controller: false
   installA1simulator: true
   installControlpanel: true
@@ -34,6 +34,8 @@ nonrtric:
   installNonrtricgateway: true
   installKong: true
   installORUApp: false
+  installODUSMOApp: false
+  installODUICSApp: false
   installTopology: true
   installDmaapadapterservice: true
   installDmaapmediatorservice: true
@@ -42,61 +44,57 @@ nonrtric:
   # referenced by persistent volumes and log files
   persistence:
     mountPath: /dockerdata-nfs
-  volume1: 
-    # Set the size to 0 if you do not need the volume (if you are using Dynamic Volume Provisioning) 
-    size: 2Gi 
-    storageClassName: pms-storage 
-  volume2: 
-     # Set the size to 0 if you do not need the volume (if you are using Dynamic Volume Provisioning) 
-    size: 2Gi 
-    storageClassName: ics-storage 
+  volume1:
+    # Set the size to 0 if you do not need the volume (if you are using Dynamic Volume Provisioning)
+    size: 2Gi
+    storageClassName: pms-storage
+  volume2:
+     # Set the size to 0 if you do not need the volume (if you are using Dynamic Volume Provisioning)
+    size: 2Gi
+    storageClassName: ics-storage
   volume3:
     size: 1Gi
-    storageClassName: helmmanager-storage 
+    storageClassName: helmmanager-storage
 
-common: 
-  releasePrefix: r3-dev-nonrtric 
-  ingressClassName: kong 
+common:
+  releasePrefix: r3-dev-nonrtric
+  ingressClassName: kong
 
 informationservice:
-  informationservice:
-    persistence:
-      # Either refer to a volume created under the nonrtric by storageClassName. Then the claimed size should be the same.
-      # The alternative use a dynamic volume provisioner in the cluster. Storage class can then be for instance 'standard' or 'gluster-fs' (depeneds on which classes that are available)
-      size: 2Gi
-      storageClassName: ics-storage
-    ingress:
-      enabled: true
-
- 
-# Need to check the external port Availability 
-policymanagementservice: 
-  policymanagementservice: 
-    persistence: 
-      # Either refer to a volume created under the nonrtric by storageClassName. Then the claimed size should be the same. 
-      # The alternative use a dynamic volume provisioner in the cluster. Storage class can then be fon instance 'standard' or 'gluster-fs' (depeneds on which classes that are available) 
-      size: 2Gi 
-      storageClassName: pms-storage 
+  persistence:
+    # Either refer to a volume created under the nonrtric by storageClassName. Then the claimed size should be the same.
+    # The alternative use a dynamic volume provisioner in the cluster. Storage class can then be for instance 'standard' or 'gluster-fs' (depeneds on which classes that are available)
+    size: 2Gi
+    storageClassName: ics-storage
+  ingress:
+    enabled: true
+
+
+# Need to check the external port Availability
+policymanagementservice:
+  persistence:
+    # Either refer to a volume created under the nonrtric by storageClassName. Then the claimed size should be the same.
+    # The alternative use a dynamic volume provisioner in the cluster. Storage class can then be fon instance 'standard' or 'gluster-fs' (depeneds on which classes that are available)
+    size: 2Gi
+    storageClassName: pms-storage
   ingress:
     enabled: true
 
 kong:
   ingressController:
-    installCRDs: false 
+    installCRDs: false
   admin:
     enabled: true
 
 helmmanager:
-  helmmanager:
-    persistence:
-      # Either refer to a volume created under the nonrtric by storageClassName. Then the claimed si>
-      # The alternative use a dynamic volume provisioner in the cluster. Storage class can then be f>
-      storageClassName: helmmanager-storage
+  persistence:
+    # Either refer to a volume created under the nonrtric by storageClassName. Then the claimed si>
+    # The alternative use a dynamic volume provisioner in the cluster. Storage class can then be f>
+    storageClassName: helmmanager-storage
 
 controlpanel:
-  controlpanel:
-    ingress:
-      enabled: false
+  ingress:
+    enabled: false
 
 oru-app:
   simulators: