Changes for page Container management
Last modified by Danniar Firdausy on 2024/09/18 13:01
From version 8.1
edited by Danniar Firdausy
on 2023/09/08 08:53
on 2023/09/08 08:53
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - Containermanagement1 +Managing releases - Best practice - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.eMagiz - Content
-
... ... @@ -6,6 +6,9 @@ 6 6 7 7 Should you have any questions, please contact academy@emagiz.com. 8 8 9 +- Last update: October 13th, 2021 10 +- Required reading time: 5 minutes 11 + 9 9 == 1. Prerequisites == 10 10 - Intermediate knowledge of the eMagiz platform 11 11 ... ... @@ -13,11 +13,11 @@ 13 13 This microlearning centers on containers. Containers in this context are the same as the runtimes of eMagiz that you will see in the runtime dashboard of eMagiz under Deploy - Runtime Dashboard. Each system in the model will create a runtime or container. You have to explain eMagiz what flows will run on what container. Notably important for the process container that holds the onramps and offramps - selection can be made how to spread these across one or more containers 14 14 15 15 **Some basic considerations:** 16 - *Default behavior of new onramps and offramps is that these will be spread over all process containers. In some cases this desirable (2 containers - failover setup), but in some case one has to be specific and ensure the flows are put on the right process container17 - *In case a certain flow is made part of a release, but has not been assigned to any container than that release can't be set to active18 - *Entry and Exit flow are always put on the system specific container19 - *Exit gate flows are always put on the Gateway Container20 - *Event processors are always put on the Event Container19 +- Default behavior of new onramps and offramps is that these will be spread over all process containers. In some cases this desirable (2 containers - failover setup), but in some case one has to be specific and ensure the flows are put on the right process container 20 +- In case a certain flow is made part of a release, but has not been assigned to any container than that release can't be set to active 21 +- Entry and Exit flow are always put on the system specific container 22 +- Exit gate flows are always put on the Gateway Container 23 +- Event processors are always put on the Event Container 21 21 22 22 Please make sure that the maximum number of flows on any container is approx. 60 flows 23 23 ... ... @@ -25,7 +25,7 @@ 25 25 26 26 === 3.1 Container assignments === 27 27 28 -Navigate to Deploy -> Containers. Select the runtime where the flow needs to be added and press Add. Select the flow and press Add once more in the pop-up. 31 +Navigate to Deploy --> Containers. Select the runtime where the flow needs to be added and press Add. Select the flow and press Add once more in the pop-up. 29 29 30 30 [[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container.png]] 31 31 ... ... @@ -35,17 +35,25 @@ 35 35 36 36 [[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container-2.png]] 37 37 38 -== 4. Keytakeaways==41 +== 4. Assignment == 39 39 43 +Check out if the best practices detailed above are applied within your (Academy) project. If not open up a discussion on why those choices are made to learn from that. 44 + 45 +== 5. Key takeaways == 46 + 40 40 The key aspects are: 41 - *Ensure to consider the container assigments when making releases42 - *Considering setting the maximum number of flows on a process container to allow optimal performance of the container48 + - Ensure to consider the container assigments when making releases 49 + - Considering setting the maximum number of flows on a process container to allow optimal performance of the container 43 43 44 44 45 -== 5. Suggested Additional Readings ==52 +== 6. Suggested Additional Readings == 46 46 47 47 If you are interested in this topic please read the help text eMagiz provides you in the container section in the Deploy phase. Try to set the maximum of process flows to a low value to trigger the alert on the release level 48 48 56 +== 7. Silent demonstration video == 57 + 58 +As this is a more theoretical microlearning we have no video for this. 59 + 49 49 ))) 50 50 51 51 ((({{toc/}}))){{/container}}