Skip to content

Commit daf071d

Browse files
add Redirect_from
1 parent 68e543b commit daf071d

File tree

3 files changed

+28
-5
lines changed

3 files changed

+28
-5
lines changed

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

Lines changed: 19 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,6 @@ We create a snapshot of your main Hypernode and attach that snapshot to the extr
3232
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.
3333
The load of the different autoscaling nodes will be balanced from your original Hypernode.
3434

35-
3635
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.
3736
The greater of either:
3837

@@ -55,36 +54,45 @@ Horizontal autoscaling is available on all the Falcon cloud plans (OpenStack).
5554
Next to the provider, horizontal autoscaling does have a couple of additional requirements.
5655

5756
### Supported CMS
57+
5858
Horizontal autoscaling is available for Magento2.
5959
To make use of Horizontal autoscaling, there are a couple of other requirements the Hypernode and the application should met:
6060

61-
**System requirements:**
6261
### Operating system
62+
6363
- The operating system of the Hypernode should be Debian Bookworm
6464

6565
### Enable and configure Varnish
66+
6667
To make use of Horizontal autoscaling, Varnish should be enabled and configured on the Hypernode.
6768
You can check if Varnish is enabled on your Hypernode by running
69+
6870
```console
6971
hypernode-systemctl settings varnish_enabled
7072
```
73+
7174
Example output if Varnish is enabled:
75+
7276
```console
7377
varnish_enabled is set to value True
7478
```
7579

7680
If Varnish is not enabled, you can [enable Varnish](../varnish/how-to-enable-varnish-on-hypernode.md) by following the documentation
7781
If varnish is enabled on your Hypernode, your Magento store should also be configured to make use of varnish.
7882
You can verify if the Varnish host is configured correctly by running the following command from the Magento root:
83+
7984
```console
8085
php bin/magento config:show system/full_page_cache/varnish/backend_host
8186
```
87+
8288
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.
89+
8390
```console
8491
php bin/magento config:set system/full_page_cache/varnish/backend_host varnish
8592
```
8693

8794
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.
95+
8896
```console
8997
acl purge {
9098
"localhost";
@@ -93,19 +101,24 @@ acl purge {
93101
```
94102

95103
### Enable and configure Redis Persistent
104+
96105
Redis persistent is another requirement before you can make use of Horizontal autoscaling.
97106
The persistent instance will be used to store the sessions so we can access the same sessions from the Horizontal autoscale Hypernodes.
98107

99108
You can check if Redis Persistent is enabled on your Hypernode by running
109+
100110
```console
101111
hypernode-systemctl settings redis_persistent_instance
102112
```
113+
103114
Example output if Redis Persistent is enabled:
115+
104116
```console
105117
redis_persistent_instance is set to value True
106118
```
107119

108120
If Redis Persistent instance is not enabled, you can enable the second Redis instance for sessions you run the command:
121+
109122
```console
110123
hypernode-systemctl settings redis_persistent_instance --value True
111124
```
@@ -114,6 +127,7 @@ Make sure Redis session is configured as [described](../../ecommerce-application
114127
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`.
115128

116129
### Make sure Elasticsearch/Opensearch configured properly
130+
117131
Please make sure Elasticsearch or Opensearch host is set to `elasticsearchmaster` in the Magento2 configuration file at `<magento_root>/app/etc/env.php`
118132
More information about [Elasticsearch o Hypernode](../../hypernode-platform/tools/how-to-use-elasticsearch-on-hypernode.md)
119133

@@ -131,17 +145,19 @@ hypernode-systemctl settings mysql_version
131145
```
132146

133147
Example output if MySQL version is 8.0:
148+
134149
```console
135150
mysql_version is set to value 8.0
136151
```
152+
137153
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.
138154

139155
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.
140156
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`.
141157

142158
### Make sure the Hypernode is a production plan
143-
Unfortunately we don't support Horizontal autoscaling for development plans.
144159

160+
Unfortunately we don't support Horizontal autoscaling for development plans.
145161

146162
## Enabling Horizontal Autoscaling
147163

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@ myst:
66
intervention. Configure thresholds, durations, and understand the workflow for
77
seamless autoscaling on Hypernode.
88
title: How does vertical Autoscaling work? | Hypernode
9+
redirect_from:
10+
- hypernode-platform/autoscaling/how-does-autoscaling-work
911
---
1012

1113
# How does vertical Autoscaling work?

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

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@ myst:
44
description: Step-by-step instructions on enabling vertical Autoscaling through the Control
55
Panel or command line
66
title: How to enable vertical Autoscaling? | Hypernode
7+
redirect_from:
8+
- hypernode-platform/autoscaling/how-to-enable-autoscaling
79
---
810

911
# How to Enable vertical Autoscaling?
@@ -44,7 +46,10 @@ To allow using autoscaling via the command line, follow the steps below:
4446
### Enable vertical autoscaling via the CLI
4547

4648
To enable autoscaling via the CLI, you can run the following command:
47-
`hypernode-systemctl autoscaling --enable`
49+
50+
```console
51+
hypernode-systemctl autoscaling --enable
52+
```
4853

4954
### Manage vertical autoscaling tresholds via the CLI
5055

@@ -56,7 +61,7 @@ This tresholds does have a default value:
5661

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

59-
```
64+
```console
6065
hypernode-systemctl settings autoscale_trigger_load_percentage 80
6166
hypernode-systemctl settings autoscale_trigger_load_avg_minutes 50
6267
```

0 commit comments

Comments
 (0)