Skip to Content
Version 2.1 by eMagiz on 2022/05/05 10:02
Show last authors
1 {{html wiki="true"}}
2 <div class="ez-academy">
3 <div class="ez-academy_body">
4
5 <div class="doc">
6
7
8
9 = Impact of Cloud template upgrades =
10
11 In this microlearning, we will focus on the helping you to assess the impact of upgrading to a new Cloud template.
12
13 Should you have any questions, please get in touch with academy@emagiz.com.
14
15 * Last update: November 2nd, 2021
16 * Required reading time: 5 minutes
17
18 == 1. Prerequisites ==
19
20 * Advanced knowledge of the eMagiz platform
21 * Completed the relevant microlearnings around Cloud Management till advanced.
22
23 == 2. Key concepts ==
24
25 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.
26
27 Cloud Templates:
28
29 * Determine what runtime runs where
30 * Determine which eMagiz Cloud version will we use
31 * Determine which supporting tools are available
32 * Are updateable
33
34
35
36 == 3. Assessing the impact of upgrading Cloud templates ==
37
38 The following consideration are valid when upgrading to a new Cloud template
39
40 1. Service affecting vs. non-service effecting
41 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.
42
43 2. Other changes pending for an AWS update
44 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
45
46 * Memory changes
47 * Runtimes removed
48 * Runtimes added
49 * Etc.
50
51 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.
52
53 3. Duration of the upgrade
54 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.
55
56 4. Availability zone
57 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.
58
59 5. Multiple Cloud template upgrades
60 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.
61
62 ===== Practice =====
63
64 == 4. Assignment ==
65
66 Review the release notes in the Portal, be sure to understand the release notes of each cloud template. And which are service affecting and which ones not.
67
68 == 5. Key takeaways ==
69
70 * Cloud templates can be rolled-out automatically via the upgrade options. Regardless of the type of environment (Test, Acceptance or Production)
71 * Double lane Cloud template upgrades are non-service affecting.
72 * Make sure to keep your Deploy architecture current - less risk of impact of Cloud template upgrade issues.
73
74
75
76 == 6. Suggested Additional Readings ==
77
78 If you are interested in this topic and want more information on it, please read the release notes provided by eMagiz
79
80 == 7. Silent demonstration video ==
81
82 There is no video available as this is more a theoretical microlearning.
83
84 </div>
85 </main>
86 </div>
87 </div>
88
89 {{/html}}