Skip to content

Commit

Permalink
fix: md formatting
Browse files Browse the repository at this point in the history
  • Loading branch information
alejandrogarza committed Dec 11, 2023
1 parent ede2ab3 commit eb2d803
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 2 deletions.
Original file line number Diff line number Diff line change
@@ -1,7 +1,10 @@
---
myst:
html_meta:
description: Learn how autoscaling dynamically adjusts server resources based on CPU usage metrics, allowing efficient workload management without manual intervention. Configure thresholds, durations, and understand the workflow for seamless autoscaling on Hypernode.
description: Learn how autoscaling dynamically adjusts server resources based
on CPU usage metrics, allowing efficient workload management without manual
intervention. Configure thresholds, durations, and understand the workflow for
seamless autoscaling on Hypernode.
title: How does Autoscaling work? | Hypernode
---

Expand All @@ -18,20 +21,24 @@ Autoscaling is available for Combell Openstack and AWS cloud hosting providers.
## Configuration Parameters

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:

- **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.

## Autoscaling Triggering Process

- **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.

## Autoscaling Workflow

- **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.

## Continued Autoscaling Process:

If the server remains overloaded post-autoscaling, the next autoscaling trigger is determined based on these criteria:

- **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.
Expand All @@ -41,6 +48,7 @@ This approach selects the longer duration between user-defined settings or the f
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.
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
---
myst:
html_meta:
description: Step-by-step instructions on enabling Autoscaling through the Control Panel or command line
description: Step-by-step instructions on enabling Autoscaling through the Control
Panel or command line
title: How to enable Autoscaling? | Hypernode
---

Expand Down Expand Up @@ -45,18 +46,22 @@ To enable autoscaling via the CLI, you can run the following command:
`hypernode-systemctl autoscaling --enable`

### Manage autoscaling tresholds via the CLI

If you have enabled autoscaling, you can configure the thresholds when it is being autoscaled.
This tresholds does have a default value:

- autoscale_trigger_load_percentage **default: 70**
- autoscale_trigger_load_avg_minutes **default: 15**

If you want to change the default settings, you can use the commands below:

```
hypernode-systemctl settings autoscale-trigger-load-percentage 80
hypernode-systemctl settings autoscale-trigger-load-avg-minutes 50
```

### Disable autoscaling via the CLI

If you want to disable autoscaling via the CLI, you can run `hypernode-systemctl autoscaling --disable`.

**Please note:** if you enable autoscaling the next time, the last configured settings will be used.

0 comments on commit eb2d803

Please sign in to comment.