From f20d9983816d95aeafc624526e3443c65c1a11e3 Mon Sep 17 00:00:00 2001 From: sritharan Date: Mon, 15 May 2023 06:02:41 +0000 Subject: [PATCH 1/4] Feature 10986: Autoheal switch and Autoscale switch --- 05-osm-usage.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/05-osm-usage.md b/05-osm-usage.md index 52353ec..31d0e55 100644 --- a/05-osm-usage.md +++ b/05-osm-usage.md @@ -1195,6 +1195,15 @@ osm ns-list osm ns-show web01 ``` +#### Enabling/Disabling the autoscaling + +1. To enable the autoscaling feature + - change the env `OSMPOL_AUTOSCALE_ENABLED` to `True` in devops dockerfile. + - To enable during runtime, in pol deployment file modify the env `OSMPOL_AUTOSCALE_ENABLED` to `True`. +2. To disable the autoscaling feature + - change the env `OSMPOL_AUTOSCALE_ENABLED` to `False` in devops dockerfile. + - To disable during runtime, in pol deployment file modify the env `OSMPOL_AUTOSCALE_ENABLED` to `False`. + Testing: 1. To ensure the NS is working, visit the Load balancer's IP at the public network using a browser, the page should show an OSM logo and active VDUs. @@ -1276,6 +1285,15 @@ osm ns-list osm ns-show heal ``` +#### Enabling/Disabling the autohealing + +1. To enable the autohealing feature + - change the env `OSMPOL_AUTOHEAL_ENABLED` to `True` in devops dockerfile. + - To enable during runtime, in pol deployment file modify the env `OSMPOL_AUTOHEAL_ENABLED` to `True`. +2. To disable the autohealing feature + - change the env `OSMPOL_AUTOHEAL_ENABLED` to `False` in devops dockerfile. + - To disable during runtime, in pol deployment file modify the env `OSMPOL_AUTOHEAL_ENABLED` to `False`. + #### Testing: 1. To ensure NS is instantiated successfully, check metrics at Prometheus, visit `http://[OSM_IP]:9091` and look for `osm_vm_status`. Metric value should be '1'. -- GitLab From 66c532c8a508d9fb84e0005dddf6f1308a820338 Mon Sep 17 00:00:00 2001 From: sritharan Date: Thu, 22 Jun 2023 05:17:24 +0000 Subject: [PATCH 2/4] Update 05-osm-usage.md --- 05-osm-usage.md | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/05-osm-usage.md b/05-osm-usage.md index 31d0e55..59b202c 100644 --- a/05-osm-usage.md +++ b/05-osm-usage.md @@ -1195,7 +1195,10 @@ osm ns-list osm ns-show web01 ``` -#### Enabling/Disabling the autoscaling +#### How to enable/disable autoscaling +With the previous SA architecture, it is possible to enable/disable autoscaling by patching the POL deployment in kubernetes: + +The steps are given below: 1. To enable the autoscaling feature - change the env `OSMPOL_AUTOSCALE_ENABLED` to `True` in devops dockerfile. @@ -1204,6 +1207,11 @@ osm ns-show web01 - change the env `OSMPOL_AUTOSCALE_ENABLED` to `False` in devops dockerfile. - To disable during runtime, in pol deployment file modify the env `OSMPOL_AUTOSCALE_ENABLED` to `False`. +With the new architecture, Airflow DAGs for scaling can be selectively disabled in Airflow UI by pressing the toggle next to the DAG to pause/unpause it: + + - scalein_vdu, to enable/disable auto-scale-in + - scaleout_vdu, to enable/disable auto-scale-out + Testing: 1. To ensure the NS is working, visit the Load balancer's IP at the public network using a browser, the page should show an OSM logo and active VDUs. @@ -1285,7 +1293,11 @@ osm ns-list osm ns-show heal ``` -#### Enabling/Disabling the autohealing +#### How to enable/disable autohealing + +With the previous SA architecture, it is possible to enable/disable autohealing by patching the POL deployment in kubernetes: + +The steps are given below: 1. To enable the autohealing feature - change the env `OSMPOL_AUTOHEAL_ENABLED` to `True` in devops dockerfile. @@ -1294,6 +1306,10 @@ osm ns-show heal - change the env `OSMPOL_AUTOHEAL_ENABLED` to `False` in devops dockerfile. - To disable during runtime, in pol deployment file modify the env `OSMPOL_AUTOHEAL_ENABLED` to `False`. +With the new architecture, Airflow DAGs for healing can be selectively disabled in Airflow UI by pressing the toggle next to the DAG to pause/unpause it: + + - vdu_down, to enable/disable auto-heal + #### Testing: 1. To ensure NS is instantiated successfully, check metrics at Prometheus, visit `http://[OSM_IP]:9091` and look for `osm_vm_status`. Metric value should be '1'. -- GitLab From 7df996436e12ca228c8544bc62ffbf5b1e4b5ea1 Mon Sep 17 00:00:00 2001 From: sritharan Date: Wed, 28 Jun 2023 04:42:48 +0000 Subject: [PATCH 3/4] Update 05-osm-usage.md --- 05-osm-usage.md | 40 +++++++++++++++++++++++++++++++++++++++- 1 file changed, 39 insertions(+), 1 deletion(-) diff --git a/05-osm-usage.md b/05-osm-usage.md index 59b202c..6478b00 100644 --- a/05-osm-usage.md +++ b/05-osm-usage.md @@ -6,7 +6,7 @@ Before going on, download the required VNF and NS packages from this URL: Date: Thu, 29 Jun 2023 14:46:05 +0000 Subject: [PATCH 4/4] Update 05-osm-usage.md --- 05-osm-usage.md | 67 +++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 36 deletions(-) diff --git a/05-osm-usage.md b/05-osm-usage.md index 6478b00..df97dfd 100644 --- a/05-osm-usage.md +++ b/05-osm-usage.md @@ -1166,6 +1166,37 @@ vdu-profile: max-number-of-intannces: 11 ``` +#### How to enable/disable autoscaling + +With the previous SA architecture based on POL and MON, it is possible to enable/disable autoscaling by patching the POL deployment in kubernetes: + +The steps are given below: + +1. To enable the autoscaling feature, modify the env `OSMPOL_AUTOSCALE_ENABLED` to `True` in `pol` deployment: + + ```bash + kubectl -n osm edit deployment pol + ``` + + ```yaml + OSMPOL_AUTOSCALE_ENABLED: True + ``` + +2. To disable the autoscaling feature, modify the env `OSMPOL_AUTOSCALE_ENABLED` to `False` in `pol` deployment: + + ```bash + kubectl -n osm edit deployment pol + ``` + + ```yaml + OSMPOL_AUTOSCALE_ENABLED: False + ``` + +With the new architecture, Airflow DAGs for scaling can be selectively disabled in Airflow UI by pressing the toggle next to the DAG to pause/unpause it: + +- `scalein_vdu`, to enable/disable auto-scale-in +- `scaleout_vdu`, to enable/disable auto-scale-out + #### Example This will launch a Network Service formed by an HAProxy load balancer and an (autoscalable) Apache web server. Please check: @@ -1195,42 +1226,6 @@ osm ns-list osm ns-show web01 ``` -#### How to enable/disable autoscaling -With the previous SA architecture, it is possible to enable/disable autoscaling by patching the POL deployment in kubernetes: - -The steps are given below: - -1. To enable the autoscaling feature - - change the env `OSMPOL_AUTOSCALE_ENABLED` to `True` in devops dockerfile. - - To enable during runtime, in pol deployment file modify the env `OSMPOL_AUTOSCALE_ENABLED` to `True`. - - ```bash - kubectl -n osm edit deployment pol - ``` - ```yaml - - env: - - name: OSMPOL_AUTOSCALE_ENABLED - value: True - ``` - -2. To disable the autoscaling feature - - change the env `OSMPOL_AUTOSCALE_ENABLED` to `False` in devops dockerfile. - - To disable during runtime, in pol deployment file modify the env `OSMPOL_AUTOSCALE_ENABLED` to `False`. - - ```bash - kubectl -n osm edit deployment pol - ``` - ```yaml - - env: - - name: OSMPOL_AUTOSCALE_ENABLED - value: False - ``` - -With the new architecture, Airflow DAGs for scaling can be selectively disabled in Airflow UI by pressing the toggle next to the DAG to pause/unpause it: - - - scalein_vdu, to enable/disable auto-scale-in - - scaleout_vdu, to enable/disable auto-scale-out - Testing: 1. To ensure the NS is working, visit the Load balancer's IP at the public network using a browser, the page should show an OSM logo and active VDUs. -- GitLab