Skip to Content

Changes for page Flows Assignment

Last modified by Erik Bakker on 2023/09/05 08:49
From version 1.1
edited by eMagiz
on 2022/06/10 13:21
Change comment: There is no comment for this version
To version 9.4
edited by Danniar Firdausy
on 2023/09/04 09:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -intermediate-release-management-assigning-flows-2-containers
1 +Flows Assignment
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.WebHome
1 +Main.eMagiz Academy.Microlearnings.Intermediate Level.Release Management.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.dfirdausy
Content
... ... @@ -1,65 +1,22 @@
1 -~{~{container}}
2 -~{~{container layoutStyle="columns"}}
3 -~(~(~(
1 +{{container}}{{container layoutStyle="columns"}}(((
2 +This exercise will guide you in managing and assigning flows to containers.
3 +
4 +Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
4 4  
6 +== 1. Prerequisites ==
5 5  
6 -~= Managing releases - Best practice
7 -
8 -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.
8 +* Completed previous exercises and microlearnings
9 +* Access to an eMagiz model with Deploy rights
9 9  
10 -Should you have any questions, please contact academy@emagiz.com.
11 +== 2. Exercise ==
11 11  
12 -- Last update: October 13th, 2021
13 -- Required reading time: 5 minutes
13 +Try to create a new flow that is not yet assigned to any containers in the Deploy phase. Then, navigate to Deploy->Containers, where you can change the advised number of flows that are deployed per container by clicking the "Change advised number of flows" button.
14 14  
15 -~== 1. Prerequisites ==
16 -- Intermediate knowledge of the eMagiz platform
15 +Afterwards, you can try to create a new release. Here, normally, you can select the new flow to be included in the release via the visual interface in Deploy->Release. However, to demonstrate the
17 17  
18 -~== 2. Key concepts ==
19 -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
17 +== 3. Solution ==
18 +In this short movie, you will find the workout of this exercise. Take a moment to review this one and compare it to your solution.
20 20  
21 -~*~*Some basic considerations:~*~*
22 -- 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
23 -- 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
24 -- Entry and Exit flow are always put on the system specific container
25 -- Exit gate flows are always put on the Gateway Container
26 -- Event processors are always put on the Event Container
20 +{{video attachment="intermediate-release-management-container-management.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
27 27  
28 -Please make sure that the maximum number of flows on any container is approx. 60 flows
29 -
30 -~== 3. Container management ==
31 -
32 -~=== 3.1 Container assignments ===
33 -
34 -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.
35 -
36 -~[~[image~:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container.png]]
37 -
38 -~=== 3.2 Setting maxiumum number of flows per container ===
39 -
40 -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.
41 -
42 -~[~[image~:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container-2.png]]
43 -
44 -~== 4. Assignment ==
45 -
46 -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.
47 -
48 -~== 5. Key takeaways ==
49 -
50 -The key aspects are:
51 - - Ensure to consider the container assigments when making releases
52 - - Considering setting the maximum number of flows on a process container to allow optimal performance of the container
53 -
54 -
55 -~== 6. Suggested Additional Readings ==
56 -
57 -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
58 -
59 -~== 7. Silent demonstration video ==
60 -
61 -As this is a more theoretical microlearning we have no video for this.
62 -
63 -
64 -~(~(~(~{~{toc/}}~)~)~)~{~{/container}}~{~{/container}}
65 -
22 +)))((({{toc/}}))){{/container}}{{/container}}