From e55740ee2b4f42dc42660314e566e754a56294e0 Mon Sep 17 00:00:00 2001 From: aktas Date: Sun, 13 Jun 2021 12:26:01 +0300 Subject: [PATCH 1/2] Add KDU level scaling descriptor in the documantation Signed-off-by: aktas --- 04-day2.md | 41 ++++++++++++++++++++++++++++++++++------- 1 file changed, 34 insertions(+), 7 deletions(-) diff --git a/04-day2.md b/04-day2.md index 2952d96..ca78c7b 100644 --- a/04-day2.md +++ b/04-day2.md @@ -133,28 +133,55 @@ 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. +Scaling operations happen at a VDU and KDU level and can be added with automatic triggers (_closed-loop_ mode triggered by _monitoring-parameters_ thresholds), or with a manual trigger. -In both cases, a `scaling-aspect` section must be added to the VNF Deployment Flavour. The following example enables VDU scaling based on a manual trigger (OSM API or CLI). +Note: KDU level scaling is available just for juju bundle deployments at the moment. + +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). ```yaml +# VDU level vnfd: df: - ... scaling-aspect: - aspect-delta-details: deltas: - - id: vdu_autoscale-delta + - id: vdu_manualscale-delta vdu-delta: - - id: hackfest_basic_metrics-VM + - id: basic-VM number-of-instances: "1" - id: vdu_autoscale + id: vdu_manualscale max-scale-level: 1 - name: vdu_autoscale + name: vdu_manualscale scaling-policy: - cooldown-time: 120 - name: cpu_util_above_threshold + name: vdu_manual_scale scaling-type: manual + +# KDU level +vnfd: + df: + - ... + kdu-resource-profile: + - id: nginx-scale + kdu-name: native-kdu + resource-name: nginx # Application name in the KDU instance. This name is stored in the juju bundle's yaml file + scaling-aspect: + - aspect-delta-details: + deltas: + - id: kdu_manualscale-delta + kdu-resource-delta: + - id: nginx-scale # Points the kdu-resource-profile:id which has the resource-name information + 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. -- GitLab From 8c2471d83731dc25b345976cc508cf7e4c3a23c7 Mon Sep 17 00:00:00 2001 From: aktas Date: Wed, 23 Jun 2021 18:32:45 +0300 Subject: [PATCH 2/2] Note removed, kdu level definition added Signed-off-by: aktas --- 04-day2.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/04-day2.md b/04-day2.md index ca78c7b..8cc0fbe 100644 --- a/04-day2.md +++ b/04-day2.md @@ -133,9 +133,7 @@ vnfd: ### Adding scaling operations -Scaling operations happen at a VDU and KDU level and can be added with automatic triggers (_closed-loop_ mode triggered by _monitoring-parameters_ thresholds), or with a manual trigger. - -Note: KDU level scaling is available just for juju bundle deployments at the moment. +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. 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). -- GitLab