Use flavors for resources in oof csmo deployment

For Casablanca release, flavors have been set up for choosing the "right"
resource requests and limits.

Although the deployment is using the right way for that, oof-csmo-service
charts values.yaml was not. This commit makes values.yaml aligned with
flavors

Change-Id: I38075343b24fc2af85795e9c2a65356d5b776391
Issue-ID: OPTFRA-403
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>

diff --git a/kubernetes/oof/charts/oof-cmso/charts/oof-cmso-service/values.yaml b/kubernetes/oof/charts/oof-cmso/charts/oof-cmso-service/values.yaml
index a970f38..98c6b4a 100644 (file)
--- a/kubernetes/oof/charts/oof-cmso/charts/oof-cmso-service/values.yaml
+++ b/kubernetes/oof/charts/oof-cmso/charts/oof-cmso-service/values.yaml
@@ -65,7 +65,7 @@ service:
   internalPort: 8080
   externalPort: 8080
   #nodePort: 23
-  # as of 20181022 port 23 is reserved for cmso 
+  # as of 20181022 port 23 is reserved for cmso
   # see https://wiki.onap.org/display/DW/OOM+NodePort+List
 
 
@@ -94,9 +94,18 @@ ingress:
   # Minimum memory for development is 2 CPU cores and 4GB memory
   # Minimum memory for production is 4 CPU cores and 8GB memory
 resources:
-  limits:
-    cpu: 1
-    memory: 1.2Gi
-  requests:
-    cpu: 10m
-    memory: 800Mi
+  small:
+    limits:
+      cpu: 1
+      memory: 1.2Gi
+    requests:
+      cpu: 10m
+      memory: 800Mi
+  large:
+    limits:
+      cpu: 1
+      memory: 1.2Gi
+    requests:
+      cpu: 10m
+      memory: 800Mi
+  unlimited: {}