Skip to Content
Last modified by Erik Bakker on 2024/09/03 07:58
From version 10.1
edited by Erik Bakker
on 2023/10/17 12:12
Change comment: There is no comment for this version
To version 11.1
edited by Erik Bakker
on 2023/10/26 10:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In this microlearning, we will focus on the helping you to assess the impact of upgrading to a new Cloud template.
2 +In this microlearning, we will focus on helping you assess the impact of upgrading to a new Cloud template.
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
... ... @@ -10,45 +10,45 @@
10 10  
11 11  == 2. Key concepts ==
12 12  
13 -With cloud template, we mean: A Cloud template is a configuration, specified by eMagiz, how deploy Architecture will run in AWS, and which supporting tools (such as auto-healing, auto-recovery, and improved alerting for instance) are available for your environment.
13 +With cloud template, we mean: A Cloud template is a configuration, specified by eMagiz, how deploy Architecture will run in AWS, and which supporting tools (such as auto-healing, auto-recovery, and improved alerting, for instance) are available for your environment.
14 14  
15 15  Cloud Templates:
16 16  
17 17  * Determine what runtime runs where
18 -* Determine which eMagiz Cloud version will we use
18 +* Determine which eMagiz Cloud version we will use
19 19  * Determine which supporting tools are available
20 20  * Are updateable
21 21  
22 22  == 3. Assessing the impact of upgrading Cloud templates ==
23 23  
24 -The following consideration are valid when upgrading to a new Cloud template
24 +The following considerations are valid when upgrading to a new Cloud template.
25 25  
26 26  * Service affecting vs. non-service effecting
27 -** Non-service affecting templates will not affect your current operation * flows will continue to function as usual. You can safely apply the cloud template. Service affecting means that that the machines will need to be stopped and started to make the cloud template operational. There is short window in which flows are not operational and there will be a delay in message delivery & processing. Messages is not lost.
27 +** Non-service affecting templates will not affect your current operation. * flows will continue to function as usual. You can safely apply the cloud template. Service affecting means that the machines will need to be stopped and started to operationalize the cloud template. There is a short window in which flows are not operational, and there will be a delay in message delivery & processing. Messages are preserved.
28 28  
29 29  * Other changes pending for an AWS update
30 -** The apply to environment button will apply all the changes that are made in Design architecture and Deploy architecture. These can be things such as
30 +** The apply to environment button will apply all the changes made in Design architecture and Deploy architecture. These can be things such as
31 31  *** Memory changes
32 32  *** Runtimes removed
33 33  *** Runtimes added
34 34  
35 -{{info}}It is a good practice to isolate the Cloud template upgrade from these changes to the AWS slot. All changes can be handled in a single push of the button, but when an issue occurs at that moment it may become harder to isolate the root cause. So keep your Deploy Architecture as current as possible.{{/info}}
35 +{{info}}It is a good practice to isolate the Cloud template upgrade from these changes to the AWS slot. All changes can be handled with a single push of a button, but it may become harder to isolate the root cause when an issue occurs. So keep your Deploy Architecture as current as possible.{{/info}}
36 36  
37 37  * Duration of the upgrade
38 -** A Cloud template upgrade will take between 5 and 15 minutes depending on the size of the slot in terms of machines. Take this value into account when making the plan to upgrade or set the automatic upgrade timeslot.
38 +** A Cloud template upgrade will take between 5 and 15 minutes, depending on the size of the slot in terms of machines. Take this value into account when making the plan to upgrade or set the automatic upgrade timeslot.
39 39  
40 40  
41 41  * Availability zone
42 -** For fail-over setups, the Cloud template upgrade will perform the upgrade zone by zone. There are 2 zones (A and B) defined in the failover scenario. Effectively this means that there is no downtime in the entire environment as flows and the JMS server will continue to operate as usual.
42 +** The Cloud template upgrade will perform the upgrade zone by zone for failover setups. Two zones (A and B) are defined in the failover scenario. Effectively, this means there is no downtime in the entire environment as flows, and the JMS server will continue operating as usual.
43 43  
44 44  * Multiple Cloud template upgrades
45 -** In case you have a backlog of upgrades to perform, please take each cloud template step by step. In case you switch to an automatic upgrade, this upgrade will take of making all the upgrades.
45 +** If you have a backlog of upgrades, please take each cloud template step by step. If you switch to an automatic upgrade, this upgrade will take making all the upgrades.
46 46  
47 47  == 4. Key takeaways ==
48 48  
49 -* Cloud templates can be rolled-out automatically via the upgrade options. Regardless of the type of environment (Test, Acceptance or Production)
49 +* Cloud templates can be rolled out automatically via the upgrade options. Regardless of the type of environment (Test, Acceptance, or Production)
50 50  * Double lane Cloud template upgrades are non-service affecting.
51 -* Make sure to keep your Deploy architecture current - less risk of impact of Cloud template upgrade issues.
51 +* Keep your Deploy architecture current - less risk of the impact of Cloud template upgrade issues.
52 52  
53 53  == 5. Suggested Additional Readings ==
54 54