Skip to Content
Last modified by Erik Bakker on 2024/09/03 07:58
From version 4.1
edited by Erik Bakker
on 2022/06/13 09:14
Change comment: There is no comment for this version
To version 1.1
edited by eMagiz
on 2022/05/05 09:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,0 @@
1 -Impact of Cloud template upgrades
Parent
... ... @@ -1,1 +1,0 @@
1 -WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.marijn
Content
... ... @@ -1,22 +1,36 @@
1 -{{container}}{{container layoutStyle="columns"}}(((
1 +{{html wiki="true"}}
2 +<div class="ez-academy">
3 + <div class="ez-academy_body">
4 +
5 +
6 + <li class="doc-nav__item"><a href="../../docs/microlearning/advanced-cloudmanagement-index" class="doc-nav__link">Home</a></li>
7 +
8 +
9 +
10 +
11 +
12 +<div class="doc">
13 +
14 +
15 +
16 += Impact of Cloud template upgrades =
17 +
2 2  In this microlearning, we will focus on the helping you to assess the impact of upgrading to a new Cloud template.
3 3  
4 -Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
20 +Should you have any questions, please get in touch with academy@emagiz.com.
5 5  
6 6  * Last update: November 2nd, 2021
7 7  * Required reading time: 5 minutes
8 8  
9 9  == 1. Prerequisites ==
10 -
11 11  * Advanced knowledge of the eMagiz platform
12 12  * Completed the relevant microlearnings around Cloud Management till advanced.
13 13  
14 -== 2. Key concepts ==
15 15  
30 +== 2. Key concepts ==
16 16  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.
17 17  
18 18  Cloud Templates:
19 -
20 20  * Determine what runtime runs where
21 21  * Determine which eMagiz Cloud version will we use
22 22  * Determine which supporting tools are available
... ... @@ -23,16 +23,16 @@
23 23  * Are updateable
24 24  
25 25  
26 -
40 +
27 27  == 3. Assessing the impact of upgrading Cloud templates ==
28 28  
29 29  The following consideration are valid when upgrading to a new Cloud template
30 30  
31 31  1. Service affecting vs. non-service effecting
32 - 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.
46 +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.
33 33  
34 34  2. Other changes pending for an AWS update
35 - 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
49 +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
36 36  
37 37  * Memory changes
38 38  * Runtimes removed
... ... @@ -40,17 +40,19 @@
40 40  * Etc.
41 41  
42 42  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.
57 +
43 43  
44 44  3. Duration of the upgrade
45 - 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.
60 +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.
46 46  
47 47  4. Availability zone
48 - 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.
63 +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.
49 49  
50 50  5. Multiple Cloud template upgrades
51 - 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.
66 +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.
52 52  
53 53  
69 +===== Practice =====
54 54  
55 55  == 4. Assignment ==
56 56  
... ... @@ -70,4 +70,10 @@
70 70  
71 71  == 7. Silent demonstration video ==
72 72  
73 -There is no video available as this is more a theoretical microlearning.)))((({{toc/}}))){{/container}}{{/container}}
89 +There is no video available as this is more a theoretical microlearning.
90 +
91 +</div>
92 +</main>
93 +</div>
94 +</div>
95 +{{/html}}