Changes for page R20 Docker - Double Lane

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-R20 Docker - Double Lane
	1	+R8 Docker - Double lane

Content

...	...	@@ -1,52 +1,16 @@
1		-=== Intermediate Template - Release Notes ===
	1	+Non service affecting final template to use the R8 double lane release.
	2	+Process: To use the new R8 release of our cloud template we upgrade in one steps, the update is non service affecting.
2	2
3		-**Non-service affecting** intermediate template to use the R20 double lane release. This is the first of two steps for your upgrade to the new R20 template.
4		-
5		-**Process**
6		-To use the new R20 release of our cloud template we upgrade in two steps, with only the second step being service affecting. Below is the first step.
7		-
8	8	**Overview**
9		-* Security improvements to the eMagiz infrastructure
10		-* Update Ubuntu version
11		-* Update Docker version
12		-* Update control agent version
13		-* Update Authorization Server (if applicable)
	5	+This update improves the security and enhances the auto-healing functionality on our 3rd generation runtimes.
14	14
15		-**Update Steps**
16		-* Use this intermediate R20 template (non-service affecting)(duration: < 15 minutes)
17		-** This step will upgrade the backup machines hosted in the second Availability Zone in your cloudslot.
18		-** The network drive containing the Artemis queue store and your Elastic IPs will remain.
19		-** The runtimes on the machines will be restored using the active release in the eMagiz portal
	7	+**Updates**
	8	+* Improve Locking mitigation in the Artemis server (autohealing).
	9	+* Improve security by disabling SSH access to cloud machines.
20	20
21		-User actions after applying the intermediate template:
22		-Check if all ".02" runtimes are reachable by the runtime dashboard
23		-Check if all flows have been installed according to the active release
24		-Check if messages pass through the bus by verifying a critical message flow in external systems
25		-
26		-**Remarks**
27		-
28		-To allow the user to have more control of the upgrade process we now allow to upgrade to the intermediate template as a seperate step. This gives you the option to wait longer before updating the **service affecting** final template. In this time you can do additional verifications on your model.
29		-
30		-=== Final Template - Release Notes ===
31		-
32		-**Service affecting** final template to use the R20 double lane release.
33		-
34		-**Process**
35		-To use the new R20 release of our cloud template we upgrade in two steps, with only the second step being service affecting. Below is the remaining step.
36		-
37		-**Overview**
38		-* Security improvements to the eMagiz infrastructure
39		-* Update Ubuntu version
40		-* Update Docker version
41		-* Update control agent version
42		-* Update Authorization Server (if applicable)
43		-
44	44	**Update Steps**
45		-* Use the final R20 template (non-service affecting)(duration: < 15 minutes)
46		-** This step will upgrade the primary machines in the first Availability Zone in your cloudslot.
47		-** The runtimes on the machines will be restored using the active release in the eMagiz portal.
48		-
49		-User actions after applying the final template:
50		-Check if all ".01" runtimes are reachable by the runtime dashboard
51		-Check if all flows have been installed according to the active release
52		-Check if messages pass through the bus by verifying a critical message flow in external systems
	12	+* Use the final R8 template (non service affecting) (duration: 4 minutes)
	13	+* User actions after applying the final template:
	14	+** Check if all runtimes are reachable by Deploy Architecture.
	15	+** Check if all images have been installed according to the active release.
	16	+** Check if messages pass through the bus by verifying a critical message flow in external systems.