Skip to Content
Last modified by Erik Bakker on 2024/09/03 07:58
From version 7.1
edited by Erik Bakker
on 2022/10/03 11:46
Change comment: There is no comment for this version
To version 3.2
edited by Erik Bakker
on 2022/06/13 09:13
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Impact of Cloud template upgrades
1 +advanced-cloudmanagement-determine-impact-cloudtemplates
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -1,8 +1,20 @@
1 -{{container}}{{container layoutStyle="columns"}}(((
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 +
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 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
15 +* Last update: November 2nd, 2021
16 +* Required reading time: 5 minutes
17 +
6 6  == 1. Prerequisites ==
7 7  
8 8  * Advanced knowledge of the eMagiz platform
... ... @@ -19,15 +19,17 @@
19 19  * Determine which supporting tools are available
20 20  * Are updateable
21 21  
34 +
35 +
22 22  == 3. Assessing the impact of upgrading Cloud templates ==
23 23  
24 24  The following consideration are valid when upgrading to a new Cloud template
25 25  
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.
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.
28 28  
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
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
31 31  
32 32  * Memory changes
33 33  * Runtimes removed
... ... @@ -45,6 +45,8 @@
45 45  5. Multiple Cloud template upgrades
46 46   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.
47 47  
62 +
63 +
48 48  == 4. Assignment ==
49 49  
50 50  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.
... ... @@ -55,6 +55,8 @@
55 55  * Double lane Cloud template upgrades are non-service affecting.
56 56  * Make sure to keep your Deploy architecture current - less risk of impact of Cloud template upgrade issues.
57 57  
74 +
75 +
58 58  == 6. Suggested Additional Readings ==
59 59  
60 60  If you are interested in this topic and want more information on it, please read the release notes provided by eMagiz