Skip to Content
Last modified by Erik Bakker on 2024/09/03 07:58
From version 6.1
edited by Erik Bakker
on 2022/10/03 11:45
Change comment: There is no comment for this version
To version 8.1
edited by Erik Bakker
on 2022/10/03 11:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -23,11 +23,11 @@
23 23  
24 24  The following consideration are valid when upgrading to a new Cloud template
25 25  
26 -1. 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.
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.
28 28  
29 -2. 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
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
31 31  
32 32  * Memory changes
33 33  * Runtimes removed
... ... @@ -34,17 +34,18 @@
34 34  * Runtimes added
35 35  * Etc.
36 36  
37 -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.
37 +{{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}}
38 38  
39 -3. Duration of the upgrade
40 - 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 +* Duration of the upgrade
40 +** 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.
41 41  
42 -4. Availability zone
43 - 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.
44 44  
45 -5. Multiple Cloud template upgrades
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.
43 +* Availability zone
44 +** 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.
47 47  
46 +* Multiple Cloud template upgrades
47 +** 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.
48 +
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.