feat: add hor autoscale docs

Author: martijneichelsheim

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

@@ -0,0 +1,148 @@
+---
+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
+      horizontal autoscaling without downtime on Hypernode.
+    title: How does horizontal Autoscaling work? | Hypernode
+---
+
+# How does horizontal Autoscaling work
+
+This article explains how Horizontal autoscaling works, what the requirements are and how you can enable it.
+
+## How does it work
+
+With horizontal autoscaling, additional Hypernodes will be added automatically to your main Hypernode at peak times. The extra Hypernodes will be used as PHP fpm workers. 
+Since there are no configuration or IP changes needed, Horizontal autoscaling is zero-downtime.
+
+For Horizontal autoscaling you can configure some conditions. If the conditions are met from the configured settings in the Control Panel, Horizontal autoscaling will be triggered. 
+You can configure the following conditions:
+
+- **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.
+
+## Horizontal autoscaling process
+
+### Upscaling
+
+Once the configured conditions are met and autoscaling is triggered, we spin up extra Hypernode(s) which meets the extra calculated amount of resources you need.
+We create a snapshot of your main Hypernode and attach that snapshot to the extra provisioned Hypernodes. 
+All the services, such as MySQL, Elasticsearch and Redis, keep running on your original Hypernode. We add the additional Hypernodes as PHP-fpm workers and will handle the incoming requests.
+The load of the different autoscaling nodes will be balanced from your original Hypernode.
+
+
+If the Hypernodes remains overloaded post-autoscaling, the extra needed resources will be added to handle the traffic. The 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 cooldown period 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. Autoscaling is capped at the biggest plan available on each cloud provider.
+
+### Downscaling
+
+If the monitor agent noticed if one Hypernode will be removed, the used resources will stay below the configured thresholds, the downscale operation will be triggered. 
+Downscale will happen by detaching the autoscaling instances from the main Hypernode one by one. 
+After a downscale operation has completed, there will be a cooldown of 15 minutes to monitor the behaviour of the newly available resources before downscale again. 
+If the amount of used resources is still below the configured threshold, another downscale operation will be triggered.
+If there is need for extra resources instead, extra resources will be added again.
+
+## Horizontal autoscaling requirements
+
+Horizontal autoscaling is available on all the Falcon cloud plans (OpenStack).
+Next to the provider, horizontal autoscaling does have a couple of additional requirements.
+
+### Supported CMS
+Horizontal autoscaling is available for Magento2.
+To make use of Horizontal autoscaling, there are a couple of other requirements the Hypernode and the application should met:
+
+**System requirements:**
+### Operating system
+- The operating system of the Hypernode should be Debian Bookworm
+
+### Enable and configure Varnish
+To make use of Horizontal autoscaling, Varnish should be enabled and configured on the Hypernode.
+You can check if Varnish is enabled on your Hypernode by running
+```console
+hypernode-systemctl settings varnish_enabled
+```
+Example output if Varnish is enabled:
+```console
+varnish_enabled is set to value True
+```
+
+If Varnish is not enabled, you can [enable Varnish](../varnish/how-to-enable-varnish-on-hypernode.md) by following the documentation
+If varnish is enabled on your Hypernode, your Magento store should also be configured to make use of varnish.
+You can verify if the Varnish host is configured correctly by running the following command from the Magento root:
+```console
+php bin/magento config:show  system/full_page_cache/varnish/backend_host
+```
+The output should show `varnish` as backend. If it is configured as something else (like `localhost` or `127.0.0.1`), you can update it by running which sets the backend host to `varnish` instead.
+```console
+php bin/magento config:set  system/full_page_cache/varnish/backend_host varnish
+```
+
+Aditionally make sure the IP range `10.0.0.0/24` is set to the `acl_purge` section in the Varnish VCL file. The `acl_purge` section should look something similar:loaded Varnish VCL.
+```console
+acl purge {
+    "localhost";
+    "10.0.0.0/24";
+}
+```
+
+### Enable and configure Redis Persistent
+Redis persistent is another requirement before you can make use of Horizontal autoscaling.
+The persistent instance will be used to store the sessions so we can access the same sessions from the Horizontal autoscale Hypernodes.
+
+You can check if Redis Persistent is enabled on your Hypernode by running
+```console
+hypernode-systemctl settings redis_persistent_instance
+```
+Example output if Redis Persistent is enabled:
+```console
+redis_persistent_instance is set to value True
+```
+
+If Redis Persistent instance is not enabled, you can enable the second Redis instance for sessions you run the command: 
+```console
+hypernode-systemctl settings redis_persistent_instance --value True
+```
+
+Make sure Redis session is configured as [described](../../ecommerce-applications/magento-2/how-to-configure-redis-for-magento-2.md#configure-magento-2-to-use-redis-as-the-session-store) in our docs
+Please notice the Redis host in the setup documentation. The Redis host should be set to `redismaster` instead of `localhost` or `127.0.0.1`.
+
+### Make sure Elasticsearch/Opensearch configured properly
+Please make sure Elasticsearch or Opensearch host is set to `elasticsearchmaster` in the Magento2 configuration file at `<magento_root>/app/etc/env.php`
+More information about [Elasticsearch o Hypernode](../../hypernode-platform/tools/how-to-use-elasticsearch-on-hypernode.md)
+
+### Make sure RabbitMQ configured properly
+
+Please make sure RabbitMQ host is set to `rabbitmqmaster` in the Magento2 configuration file at `<magento_root>/app/etc/env.php`
+More information about [RabbitMQ o Hypernode](../../best-practices/database/how-to-run-rabbitmq-on-hypernode.md)
+
+### Make sure we use MySQL 5.7 or higher
+
+The configured MySQL version should be 5.7 or above. You can check the enabled MySQL version by running the following command.
+
+```console
+hypernode-systemctl settings mysql_version
+```
+
+Example output if MySQL version is 8.0:
+```console
+mysql_version is set to value 8.0
+```
+If your MySQL version is still set to 5.6, you can concider [upgrade](../mysql/how-to-use-mysql-on-hypernode.md) the MySQL version to a supported version for autoscaling.
+
+After the version validation, please verify the MySQL host is set to `mysqlmaster`. You can verify this by running `cat app/etc/env.php | grep -i mysql | grep -i host` from the magento root.
+You should see something similar to `'host' => 'mysqlmaster',`. If this is not the case please make sure the database connection host is set to `mysqlmaster` instead of `localhost` or `127.0.0.1` in the magento configuration file at `<magento_root>/app/etc/env.php`.
+
+### Make sure the Hypernode is a production plan
+Unfortunately we don't support Horizontal autoscaling for development plans.
+
+
+## Enabling Horizontal Autoscaling
+
+For detailed steps on enabling horizontal Autoscaling, please refer to our documentation: [How to enable vertical Autoscaling?](how-to-enable-vertical-autoscaling.md)

…autoscaling/how-does-autoscaling-work.md …ng/how-does-vertical-autoscaling-work.mddocs/hypernode-platform/autoscaling/how-does-autoscaling-work.md renamed to docs/hypernode-platform/autoscaling/how-does-vertical-autoscaling-work.md docs/hypernode-platform/autoscaling/how-does-autoscaling-work.md renamed to docs/hypernode-platform/autoscaling/how-does-vertical-autoscaling-work.md

@@ -5,10 +5,10 @@ myst:
       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
+    title: How does vertical Autoscaling work? | Hypernode
 ---
 
-# How does Autoscaling work?
+# How does vertical Autoscaling work?
 
 Vertical autoscaling is triggered once the conditions are met from the configured settings in the Control Panel. You can configure the following:
 
@@ -41,6 +41,6 @@ Simply turn off the autoscaling feature in your control panel. This prevents sub
 
 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
+## Enabling vertical Autoscaling
 
-For detailed steps on enabling Autoscaling, please refer to our documentation: [How to enable Autoscaling?](how-to-enable-autoscaling.md)
+For detailed steps on enabling Autoscaling, please refer to our documentation: [How to enable vertical Autoscaling?](how-to-enable-vertical-autoscaling.md)

docs/hypernode-platform/autoscaling/how-to-enable-horizontal-autoscaling.md

@@ -0,0 +1,17 @@
+---
+myst:
+  html_meta:
+    description: Step-by-step instructions on enabling horizontal Autoscaling through the Control
+      Panel
+    title: How to enable horizontal Autoscaling? | Hypernode
+---
+
+# How to Enable horizontal Autoscaling?
+
+## What is horizontal Autoscaling?
+
+Horizontal autoscaling in other words means upgrading the amount of resources when your Hypernode needs it, so you don’t need to worry about constant monitoring.
+
+The amount of resources your Hypernode will upgrade with, is calculated by our agent based on the requirements.
+
+The upgrade is effective as long the extra resources are needed and being used. For more technical overview you can check our docs [How Horizontal Autoscaling Works](how-does-horizontal-autoscaling-work.md).

…autoscaling/how-to-enable-autoscaling.md …ng/how-to-enable-vertical-autoscaling.mddocs/hypernode-platform/autoscaling/how-to-enable-autoscaling.md renamed to docs/hypernode-platform/autoscaling/how-to-enable-vertical-autoscaling.md docs/hypernode-platform/autoscaling/how-to-enable-autoscaling.md renamed to docs/hypernode-platform/autoscaling/how-to-enable-vertical-autoscaling.md

@@ -1,24 +1,24 @@
 ---
 myst:
   html_meta:
-    description: Step-by-step instructions on enabling Autoscaling through the Control
+    description: Step-by-step instructions on enabling vertical Autoscaling through the Control
       Panel or command line
-    title: How to enable Autoscaling? | Hypernode
+    title: How to enable vertical Autoscaling? | Hypernode
 ---
 
-# How to Enable Autoscaling?
+# How to Enable vertical Autoscaling?
 
-## What is Autoscaling?
+## What is vertical Autoscaling?
 
 Vertical autoscaling in other words means upgrading your plan automatically when your server needs it, so you don’t need to worry about constant monitoring.
 
 Your plan will be upgraded to the next possible plan within the same provider, increasing your resources while keeping the disk size the same. The upgrade is effective for 24h, after which your Hypernode will return to your regular plan. For more technical overview you can check our docs [How Autoscaling Works](how-does-autoscaling-work.md).
 
-## How to enable Autoscaling?
+## How to enable vertical Autoscaling?
 
 You can enable Autoscaling two ways: in the Control Panel or directly via command line.
 
-### How to enable Autoscaling in the Control Panel?
+### How to enable vertical Autoscaling in the Control Panel?
 
 You can start using autoscaling by:
 
@@ -32,7 +32,7 @@ After enabling Autoscaling feature, expect a 5min grace period before Autoscalin
 
 Now, rest easy knowing that your server will automatically handle overloads.
 
-## How to enable Autoscaling via command line?
+## How to enable vertical Autoscaling via command line?
 
 To allow using autoscaling via the command line, follow the steps below:
 
@@ -41,12 +41,12 @@ To allow using autoscaling via the command line, follow the steps below:
 
 **Please note:** when enabled, **everyone who has SSH access can enable and configure autoscaling from the CLI**, even if they are not the Owner or Admin.
 
-### Enable autoscaling via the CLI
+### Enable vertical autoscaling via the CLI
 
 To enable autoscaling via the CLI, you can run the following command:
 `hypernode-systemctl autoscaling --enable`
 
-### Manage autoscaling tresholds via the CLI
+### Manage vertical 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:
@@ -61,7 +61,7 @@ hypernode-systemctl settings autoscale_trigger_load_percentage 80
 hypernode-systemctl settings autoscale_trigger_load_avg_minutes 50
 ```
 
-### Disable autoscaling via the CLI
+### Disable vertical autoscaling via the CLI
 
 If you want to disable autoscaling via the CLI, you can run `hypernode-systemctl autoscaling --disable`.