Merge pull request #227 from ByteInternet/autoscaling_documentation_alejandro_version_with_headings

Change existing Autoscaling docs with Alejandro's version

Author: alejandrogarza

docs/hypernode-platform/autoscaling/how-does-autoscaling-work.md

@@ -10,49 +10,36 @@ myst:
 
 # How does Autoscaling work?
 
-## Purpose
+Vertical autoscaling is triggered once the conditions are met from the configured settings in the Control Panel. You can configure the following:
 
-Autoscaling ensures dynamic server resource adjustments based on CPU usage metrics, efficiently managing workload demands without manual intervention. Once triggered, boosted state lasts for a 24-hour period.
+- **CPU Load Threshold:** CPU load that is continuously monitored by the autoscaling agent. The percentage value you see is the actual load divided by the number of CPUs you have. For example, if your actual load is 2, but you have 4 CPUs, your CPU load percentage is 50%. The default setting is 70%.
+- **Minimum Duration in Minutes:** Minimum amount of time the server is overloaded before autoscaling gets triggered. We monitor your CPU load every minute; autoscaling will be triggered once the CPU load condition is met for the minimum amount of time set in the Control Panel. The default setting is 15 minutes.
 
-## Supported providers:
+## Autoscaling workflow
 
-Autoscaling is available for Combell Openstack and AWS cloud hosting providers.
+To minimize downtime during the process, we employ a live volume swapping method. We install a new Hypernode without copying the data over the network to the new hosting environment. Next, we detach the volume using the API and mount it on the new machine before adjusting the DNS.
 
-## Configuration Parameters
+The feature is available on the cloud plans (OpenStack and AWS).
 
-In the control panel or with CLI tool, users can define autoscaling conditions based on CPU load thresholds and minimum duration to tailor actions to their workload demands:
+## Autoscaling process
 
-- **CPU Load Threshold:** Specifies the CPU load percentage that triggers autoscaling using a range slider.
-- **Minimum Duration:** Determines the minimum duration, in minutes, for the CPU load to exceed the threshold to activate autoscaling.
+Once set conditions are met and autoscaling is triggered, you get upgraded to the next available plan for 24 hours. When your Hypernode is in the boosted state, you can still adjust the settings, but you cannot change your plan. If you wish to do so, please contact support@hypernode.com.
 
-## Autoscaling Triggering Process
+If the server remains overloaded post-autoscaling, the next autoscaling trigger is determined based on these criteria.
+The greater of either:
 
-- **Continuous Monitoring:** The autoscaling agent continually monitors your application's CPU load.
-- **Activation Conditions:** Autoscaling is triggered if the CPU load surpasses the defined threshold and duration criteria set by the user or default values that were set when the feature was enabled.
+- User-defined minimum duration for CPU threshold surpassing: Allows time to assess newly allocated resources' impact on CPU performance.
+- A cooldown period of 15 minutes: Ensures a minimum interval for reassessment when the user-defined duration is less than 15 minutes.
 
-## Autoscaling Workflow
+This approach selects the longer duration between user-defined settings or the fallback duration before initiating the next autoscaling event. It ensures adequate time for evaluating resource changes on CPU performance. Autoscaling is capped at the biggest plan available on each cloud provider.
 
-- **Initial Cooldown period:** A 5-minute cooldown period after enabling autoscaling prevents rapid scaling due to sudden spikes.
-- **Scaling Actions:** Autoscaling automatically upgrades the plan to the next available tier within the same provider, catering to increased demand. The upgraded plan remains effective for 24 hours before reverting to the original configuration.
+### How to halt continued Autoscaling
 
-## Continued Autoscaling Process:
+Simply turn off the autoscaling feature in your control panel. This prevents subsequent autoscaling triggers after the initial action.
 
-If the server remains overloaded post-autoscaling, the next autoscaling trigger is determined based on these criteria:
+### Returning to the Initial Plan After 24 Hours
 
-- **The greater of either**:
-  - **User-defined minimum duration for CPU threshold surpassing**: Allows time to assess newly allocated resources' impact on CPU performance.
-  - **A fallback duration of 15 minutes**: Ensures a minimum interval for reassessment when the user-defined duration is less than 15 minutes.
-
-This approach selects the longer duration between user-defined settings or the fallback duration before initiating the next autoscaling event. It ensures adequate time for evaluating resource changes on CPU performance.
-
-To halt continued autoscaling behavior, simply turn off the autoscaling feature in your control panel. This prevents subsequent autoscaling triggers after the initial action.
-
-**Important to know:**
-
-- For the next 24 hours, plan adjustments are restricted. If necessary, please contact support for assistance.
-- If there are still insufficient resources and the conditions are met, the system will initiate another autoscaling process with a cooldown period of 5 minutes.
-- It will scale up to the largest plan available within the same provider.
-- Downscaling takes place within 24 hours from the initial autoscaling event.
+Regardless of the number of times your Hypernode was autoscaled, you will go back to your initial plan after 24 hours from your initial upgrade.
 
 ## Enabling Autoscaling