diff --git a/04-day2.md b/04-day2.md index 8cc0fbe1f04ce16d87cf404547351940ee6a5061..9a47a336cd7c9805302a3a097f2c354c8e592076 100644 --- a/04-day2.md +++ b/04-day2.md @@ -133,7 +133,7 @@ vnfd: ### Adding scaling operations -Scaling operations happen at a VDU level and can be added with automatic triggers (_closed-loop_ mode triggered by _monitoring-parameters_ thresholds), or with a manual trigger. At a KDU level, manual scaling operations are available for juju bundle deployments. +Scaling operations happen at a VDU level and can be added with automatic triggers (_closed-loop_ mode triggered by _monitoring-parameters_ thresholds), or with a manual trigger. At a KDU level, manual scaling operations are available for juju bundle and helm chart deployments. In both cases, a `scaling-aspect` section must be added to the VNF Deployment Flavour. The following example enables VDU and KDU scaling based on a manual trigger (OSM API or CLI). @@ -157,7 +157,7 @@ vnfd: name: vdu_manual_scale scaling-type: manual -# KDU level +# KDU level (Juju Bundle) vnfd: df: - ... @@ -180,6 +180,83 @@ vnfd: name: kdu_manual_scale scaling-type: manual +# KDU level (Helm Chart) +vnfd: + df: + - ... + kdu-resource-profile: + - id: openldap-scale + kdu-name: native-kdu + # If replicas or replicaCount iş not located under any section + # in the yaml like here -> https://github.com/helm/charts/blob/master/stable/openldap/values.yaml#L5 + # set resource-name as empty-string ("") like below. + resource-name: "" + scaling-aspect: + - aspect-delta-details: + deltas: + - id: kdu_manualscale-delta + kdu-resource-delta: + - id: openldap-scale + number-of-instances: "1" + id: kdu_manualscale + max-scale-level: 1 + name: kdu_manualscale + scaling-policy: + - cooldown-time: 120 + name: kdu_manual_scale + scaling-type: manual + +# KDU level (Helm Chart) +vnfd: + df: + - ... + kdu-resource-profile: + - id: nginx-lego-scale + kdu-name: native-kdu + # If replicas or replicaCount is located under a section + # in the yaml like here -> https://github.com/helm/charts/blob/7e45e678e39b88590fe877f159516f85f3fd3f38/stable/nginx-lego/values.yaml#L56 + # set resource-name with it's section name. + resource-name: nginx + scaling-aspect: + - aspect-delta-details: + deltas: + - id: kdu_manualscale-delta + kdu-resource-delta: + - id: nginx-lego-scale + number-of-instances: "1" + id: kdu_manualscale + max-scale-level: 1 + name: kdu_manualscale + scaling-policy: + - cooldown-time: 120 + name: kdu_manual_scale + scaling-type: manual + +# KDU level (Helm Chart) +vnfd: + df: + - ... + kdu-resource-profile: + - id: ethereum-scale + kdu-name: native-kdu + # If replicas or replicaCount is located under a section + # in the yaml like here -> https://github.com/helm/charts/blob/7e45e678e39b88590fe877f159516f85f3fd3f38/stable/ethereum/ci/test-values.yaml#L23 + # set resource-name with it's section name seperated with dots(.). + resource-name: geth.tx + scaling-aspect: + - aspect-delta-details: + deltas: + - id: kdu_manualscale-delta + kdu-resource-delta: + - id: ethereum-scale + number-of-instances: "1" + id: kdu_manualscale + max-scale-level: 1 + name: kdu_manualscale + scaling-policy: + - cooldown-time: 120 + name: kdu_manual_scale + scaling-type: manual ``` The following example defines a closed-loop scaling operation based on a specific monitoring parameter threshold.