Skip to content

Commit 4b05991

Browse files
author
Jonathan Visser
committed
run mdformat
1 parent 64f5156 commit 4b05991

File tree

1 file changed

+18
-12
lines changed

1 file changed

+18
-12
lines changed

docs/about-hypernode/support/how-to-handle-os-and-room-change-upgrade.md

100644100755
Lines changed: 18 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
---
22
myst:
33
html_meta:
4-
description: 'Learn how our Xgrade proces work and how to make sure your Hypernode is ready for the Debian Bookworm upgrade'
4+
description: Learn how our Xgrade proces work and how to make sure your Hypernode
5+
is ready for the Debian Bookworm upgrade
56
title: How does the Xgrade proces work
67
---
78

@@ -14,13 +15,13 @@ An Xgrade is an automated process that allows your server to be upgraded or down
1415
An Xgrade to Debian Bookworm or R405 (which can be performed together) is carried out by our automation. Below are the relevant steps in the process:
1516

1617
1. Ensure a new Hypernode is created.
17-
2. Configure the new Hypernode (Operating system, MySQL, PHP, Varnish, etc.).
18-
3. Synchronize data (everything within the "/" and "/data" partition).
19-
4. Stop all services on the current Hypernode.
20-
5. Synchronize any new data that has been written.
21-
6. Perform checks to ensure all processes are complete.
22-
7. Send a "Hypernode migrated" event.
23-
8. Destroy the old Hypernode.
18+
1. Configure the new Hypernode (Operating system, MySQL, PHP, Varnish, etc.).
19+
1. Synchronize data (everything within the "/" and "/data" partition).
20+
1. Stop all services on the current Hypernode.
21+
1. Synchronize any new data that has been written.
22+
1. Perform checks to ensure all processes are complete.
23+
1. Send a "Hypernode migrated" event.
24+
1. Destroy the old Hypernode.
2425

2526
As you can see, a completely new Hypernode is created with the correct configurations, whether for a Debian Bookworm or an R405 Xgrade. The first synchronization of data will then take place. The duration of this synchronization depends on the amount and type of data. Typically, we calculate about 1 GB per minute, but this may vary.
2627

@@ -29,6 +30,7 @@ At a certain point, all services will be stopped to prevent new orders from bein
2930
## What should be checked or adjusted before the Xgrade? (e.g., Node.js and TLS configuration)
3031

3132
### Nodejs
33+
3234
Before scheduling a Xgrade to Debian Bookworm/R405, you must check which Node.js version you are using. This is necessary because Node.js versions 6 and 10 are no longer supported on the new operating system. Standard Magento 2 does not make use of Nodejs, but if you use another CMS or have custom scripts that require them, you may need to update your setup.
3335

3436
You can check your Node.js version in two ways; withing the Control Panel, or on the CLI:
@@ -47,11 +49,13 @@ Operation was successful and is being processed. Please allow a few minutes for
4749
```
4850

4951
### TLS configuration
52+
5053
With the upgrade to Debian Bookworm, the TLS configurations will also change. We have chosen to phase out outdated TLS versions 1.0 and 1.1. Additionally, the "modern" TLS configuration will now only support TLS 1.3.
5154

5255
Below are the TLS configurations for Debian Buster:
5356

5457
Intermediate TLS configuratie:
58+
5559
```
5660
# intermediate configuration
5761
# nginx 1.16.1 | intermediate profile | OpenSSL 1.1.1d
@@ -104,6 +108,7 @@ ssl_stapling_verify on;
104108
```
105109

106110
modern TLS configuratie:
111+
107112
```
108113
# modern configuration
109114
# nginx 1.22.1 | modern profile | OpenSSL 3.0.11
@@ -135,7 +140,6 @@ app@uaifqk-hnvandijk-magweb-cmbl:~$ hypernode-systemctl settings modern_ssl_conf
135140
false true
136141
```
137142

138-
139143
# What needs to be adjusted after the Xgrade? When can it be performed? (IP changes)
140144

141145
If you choose to Xgrade to R405, you will receive a new IP address from our automation system. You must update this IP address in the DNS settings for both the non-www and www records of your domain. This information will be sent to the email address associated with the Hypernode owner.
@@ -145,11 +149,13 @@ My domain is at Hypernode, can we automate this? Yes, you can enable the "Synchr
145149
We make use of Cloudflare, would we be able to "automate" this proces? Sure! You can enable CNAME Flattening, which ensures that both the non-www and www records point to the Hypernode hostname. For example:
146150

147151
### Non-www Record
152+
148153
```
149154
CNAME hnvandijk.nl ---> hnvandijk.hypernode.io
150155
```
151156

152157
### www Record
158+
153159
```
154160
CNAME www.hnvandijk.nl ---> hnvandijk.hypernode.io
155161
```
@@ -164,14 +170,14 @@ The OS upgrade process itself is the same as for a cloud environment.
164170

165171
# Additional Questions
166172

167-
* An Xgrade to R405 does not incur additional costs, you will not be charged extra.
173+
- An Xgrade to R405 does not incur additional costs, you will not be charged extra.
168174

169-
* An Xgrade from Hetzner to TBBM also incurs no extra costs, you will not be charged extra.
175+
- An Xgrade from Hetzner to TBBM also incurs no extra costs, you will not be charged extra.
170176

171177
# More Information
172178

173179
https://changelog.hypernode.com/release-9961-akeneo-7-0-is-now-available-on-the-platform/
174180

175181
https://changelog.hypernode.com/release-9956-hypernode-on-debian-bookworm/
176182

177-
https://changelog.hypernode.com/sunsetting-node-js-versions-6-and-10/
183+
https://changelog.hypernode.com/sunsetting-node-js-versions-6-and-10/

0 commit comments

Comments
 (0)