Skip to Content

Changes for page Container management

Last modified by Danniar Firdausy on 2024/09/18 13:01
From version 9.16
edited by Danniar Firdausy
on 2024/09/18 13:01
Change comment: There is no comment for this version
To version 4.1
edited by eMagiz
on 2022/06/10 13:23
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.eMagiz
Content
... ... @@ -1,22 +1,26 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 -In a previous [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]], 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.
4 +
5 +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.
7 7  
9 +- Last update: October 13th, 2021
10 +- Required reading time: 5 minutes
11 +
8 8  == 1. Prerequisites ==
9 -* Intermediate knowledge of the eMagiz platform
13 +- Intermediate knowledge of the eMagiz platform
10 10  
11 11  == 2. Key concepts ==
12 12  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
13 13  
14 14  **Some basic considerations:**
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 -* In case a certain flow is made part of a release, but has not been assigned to any container than that release can not be activated or can not be set to active
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 +- 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
20 20  
21 21  Please make sure that the maximum number of flows on any container is approx. 60 flows
22 22  
... ... @@ -24,32 +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.
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.
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 ===
35 +=== 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.
37 +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 ==
41 +== 4. Assignment ==
38 38  
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 +
39 39  The key aspects are:
40 -* Ensure flows are properly assigned to the correct containers during release management to avoid issues when activating or promoting releases.
41 -* Set and manage the maximum number of flows per process container to maintain optimal container performance.
42 -* Keep the number of flows on process containers as low as possible to trigger alerts when limits are reached, helping you address potential performance bottlenecks early.
48 + - 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 -== 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:
52 +== 6. Suggested Additional Readings ==
47 47  
48 -* [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
49 -** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
50 -*** [[Creating a new Release (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]]
51 -*** [[Runtime Overview (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-runtime-overview||target="blank"]]
52 -* [[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"]]
54 +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
55 +
56 +== 7. Silent demonstration video ==
57 +
58 +As this is a more theoretical microlearning we have no video for this.
59 +
53 53  )))
54 54  
55 55  ((({{toc/}}))){{/container}}