Wiki source code of Container management
Last modified by Danniar Firdausy on 2024/09/18 13:01
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
2.1 | 1 | {{container}} |
| 2 | {{container layoutStyle="columns"}} | ||
| 3 | ((( | ||
| |
9.13 | 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. |
| |
1.1 | 5 | |
| 6 | Should you have any questions, please contact academy@emagiz.com. | ||
| 7 | |||
| |
2.1 | 8 | == 1. Prerequisites == |
| |
9.14 | 9 | * Intermediate knowledge of the eMagiz platform |
| |
1.1 | 10 | |
| |
2.1 | 11 | == 2. Key concepts == |
| |
1.1 | 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 | |||
| |
2.1 | 14 | **Some basic considerations:** |
| |
5.1 | 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 |
| |
9.13 | 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 |
| |
5.1 | 17 | * Entry and Exit flow are always put on the system specific container |
| |
9.10 | 18 | * Exit gate flows are always put on the gateway container |
| 19 | * Event processors are always put on the streaming container | ||
| |
1.1 | 20 | |
| 21 | Please make sure that the maximum number of flows on any container is approx. 60 flows | ||
| 22 | |||
| |
2.1 | 23 | == 3. Container management == |
| |
1.1 | 24 | |
| |
2.1 | 25 | === 3.1 Container assignments === |
| |
1.1 | 26 | |
| |
7.1 | 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. |
| |
1.1 | 28 | |
| |
2.1 | 29 | [[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container.png]] |
| |
1.1 | 30 | |
| |
9.2 | 31 | === 3.2 Setting maximum number of flows per container === |
| |
1.1 | 32 | |
| |
9.4 | 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. |
| |
1.1 | 34 | |
| |
2.1 | 35 | [[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container-2.png]] |
| |
1.1 | 36 | |
| |
8.1 | 37 | == 4. Key takeaways == |
| |
1.1 | 38 | |
| 39 | The key aspects are: | ||
| |
9.16 | 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. | ||
| |
1.1 | 43 | |
| |
8.1 | 44 | == 5. Suggested Additional Readings == |
| |
1.1 | 45 | |
| |
9.7 | 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: |
| 47 | |||
| |
9.13 | 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"]] | ||
| |
9.15 | 51 | *** [[Runtime Overview (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-runtime-overview||target="blank"]] |
| |
9.8 | 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"]] |
| |
3.1 | 53 | ))) |
| |
1.1 | 54 | |
| |
3.1 | 55 | ((({{toc/}}))){{/container}} |
| 56 | {{/container}} |