Skip to Content

Changes for page Container management

Last modified by Danniar Firdausy on 2024/09/18 13:01
From version 9.12
edited by Danniar Firdausy
on 2024/09/04 16:18
Change comment: There is no comment for this version
To version 5.1
edited by Erik Bakker
on 2022/08/29 08:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Container management
1 +Managing releases - Best practice
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Content
... ... @@ -1,6 +1,7 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 +
4 4  In previous microlearnings, we have already explained quite a lot about what releases are and how you should handle releases. In this microlearning, we will take a look at the management part of releases. This microlearning will focus on how to ensure flows are assigned to containers and why that is important.
5 5  
6 6  Should you have any questions, please contact academy@emagiz.com.
... ... @@ -15,8 +15,8 @@
15 15  * 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
16 16  * 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
17 17  * Entry and Exit flow are always put on the system specific container
18 -* Exit gate flows are always put on the gateway container
19 -* Event processors are always put on the streaming container
19 +* Exit gate flows are always put on the Gateway Container
20 +* Event processors are always put on the Event Container
20 20  
21 21  Please make sure that the maximum number of flows on any container is approx. 60 flows
22 22  
... ... @@ -24,29 +24,35 @@
24 24  
25 25  === 3.1 Container assignments ===
26 26  
27 -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.
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.
28 28  
29 29  [[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container.png]]
30 30  
31 -=== 3.2 Setting maximum number of flows per container ===
32 +=== 3.2 Setting maxiumum number of flows per container ===
32 32  
33 -Bus owners have the option to limit the number of flows on a process container. This option will impact the behavior of Release management where a release can't be promoted to a next environment or set as active in case the flows on the process containers exceeds this limit.
34 +Busowners have the option to limit the number of flows on a process container. This option will impact the behavior of Release management where a release can't be promoted to a next environment or set as active in case the flows on the process containers exceeeds this limit.
34 34  
35 35  [[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container-2.png]]
36 36  
37 -== 4. Key takeaways ==
38 +== 4. Assignment ==
38 38  
40 +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.
41 +
42 +== 5. Key takeaways ==
43 +
39 39  The key aspects are:
40 -* Ensure to consider the container assigments when making releases
41 -* Considering setting the maximum number of flows on a process container to allow optimal performance of the container
42 -* Try to set the maximum of process flows to a low value to trigger the alert on the release level
45 + * Ensure to consider the container assigments when making releases
46 + * Considering setting the maximum number of flows on a process container to allow optimal performance of the container
43 43  
44 -== 5. Suggested Additional Readings ==
45 45  
46 -If you are interested in this topic please read the help text eMagiz provides you in the container section in the Deploy phase and see the following link:
49 +== 6. Suggested Additional Readings ==
47 47  
51 +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  
49 -* [[Container management (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&l_space_facet=10&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22container+management%22||target="blank"]]
53 +== 7. Silent demonstration video ==
54 +
55 +As this is a more theoretical microlearning we have no video for this.
56 +
50 50  )))
51 51  
52 52  ((({{toc/}}))){{/container}}