Container management

(((

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.

6

7

Should you have any questions, please contact academy@emagiz.com.

8

9

== 1. Prerequisites ==

10

- Intermediate knowledge of the eMagiz platform

11

12

== 2. Key concepts ==

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

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 container

17

* 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

18

* Entry and Exit flow are always put on the system specific container

19

* Exit gate flows are always put on the Gateway Container

20

* Event processors are always put on the Event Container

21

22

Please make sure that the maximum number of flows on any container is approx. 60 flows

23

24

== 3. Container management ==

25

26

=== 3.1 Container assignments ===

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.

29

30

[[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container.png]]

31

32

=== 3.2 Setting maximum number of flows per container ===

33

34

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.

35

36

[[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container-2.png]]

37

38

== 4. Key takeaways ==

39

40

The key aspects are:

41

* Ensure to consider the container assigments when making releases

42

* Considering setting the maximum number of flows on a process container to allow optimal performance of the container

43

* Try to set the maximum of process flows to a low value to trigger the alert on the release level

44

45

== 5. Suggested Additional Readings ==

46

47

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:

48

49

* [[Crash Course (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]

50

** [[Crash Course API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]]

51

*** [[Setting up Exit gate (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-setting-up-exit-gate||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"]]

53

)))

54

55

((({{toc/}}))){{/container}}

56

author	version	line-number	content
		1	{{container}}
		2	{{container layoutStyle="columns"}}
		3	(((
		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.
		6
		7	Should you have any questions, please contact academy@emagiz.com.
		8
		9	== 1. Prerequisites ==
		10	- Intermediate knowledge of the eMagiz platform
		11
		12	== 2. Key concepts ==
		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
		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 container
		17	* 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
		18	* Entry and Exit flow are always put on the system specific container
		19	* Exit gate flows are always put on the Gateway Container
		20	* Event processors are always put on the Event Container
		21
		22	Please make sure that the maximum number of flows on any container is approx. 60 flows
		23
		24	== 3. Container management ==
		25
		26	=== 3.1 Container assignments ===
		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.
		29
		30	[[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container.png]]
		31
		32	=== 3.2 Setting maximum number of flows per container ===
		33
		34	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.
		35
		36	[[image:Main.Images.Microlearning.WebHome@intermediate-release-management-assign-flows-container-2.png]]
		37
		38	== 4. Key takeaways ==
		39
		40	The key aspects are:
		41	* Ensure to consider the container assigments when making releases
		42	* Considering setting the maximum number of flows on a process container to allow optimal performance of the container
		43	* Try to set the maximum of process flows to a low value to trigger the alert on the release level
		44
		45	== 5. Suggested Additional Readings ==
		46
		47	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:
		48
		49	* [[Crash Course (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome\|\|target="blank"]]
		50	** [[Crash Course API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome\|\|target="blank"]]
		51	*** [[Setting up Exit gate (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-setting-up-exit-gate\|\|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"]]
		53	)))
		54
		55	((({{toc/}}))){{/container}}
		56	{{/container}}

Wiki source code of Container management