Changes for page Volume Mapping (On-premise)

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.etorken

Content

...	...	@@ -47,9 +47,9 @@
47	47
48	48	=== 3.1 Volume ===
49	49
50		-The first Type available to you is Volume. With this option, you create one or more folders on Docker relevant to that runtime to read and write **persistent** data. To configure this Type, you need to link the runtime volume to a machine volume (or network volume) you can create within the same pop-up. This means you can re-use a "Machine volume" or a "Network volume" over multiple runtimes (i.e., containers).
	50	+The first Type available to you is Volume. With this option, you create one or more folders on Docker relevant to that runtime to read and write **persistent** data. To configure this Type, you need to link the runtime volume to a machine volume (or network volume) you can create within the same pop-up. This means you can re-use a "Machine volume" or a "Network volume" over multiple runtimes (i.e., containers). To do so we first need to define a machine (or network) volume. Once we have done that we can learn how to link the volume to the machine or network volume.
51	51
52		-==== 3.1.1 Link to Machine Volume ====
	52	+==== 3.1.1 Define Machine Volume ====
53	53
54	54	So, we first open the tab called "Machine volume." Then, by pressing the "New" button, we can define a new "Machine volume." In the pop-up that follows, we can specify the name of a machine volume and tell whether the Volume already exists on your docker installation or not.
55	55
...	...	@@ -57,33 +57,23 @@
57	57
58	58	Once you have done so, we press "Save" and switch back to the "Runtime volumes" tab.
59	59
60		-In here, we push the "New" button to create a new "Runtime volume." In the following pop-up, we first need to select the Type we want to use. For this example, we use the Type called "Volume."
	60	+==== 3.1.2 Define Network Volume ====
61	61
62		-{{info}}Based on your selection, the relevant input fields will change.{{/info}}
	62	+So, we first open the tab called "Network volume." Then, by pressing the "New" button, we can define a new "Network volume." In the pop-up that follows, we can specify the name of a machine volume and configure the relevant information for a network volume. In most cases a CIFS is used and the only relevant options that need to be filled in are the host, port, username and password.
63	63
64		-[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-volume.png]]
65		-
66		-The first thing we need to select is the "Machine volume." Once we have chosen our "Machine volume," we must set the Target specific for this runtime. This target defines the second part of the path to which the runtime will gain access. For example, when you fill in "/target", we can combine this with the "Machine volume" name to arrive at the correct directory from which eMagiz needs to read data (or write data to). So in our case, this would be "/file-directory/target."
67		-
68		-The last setting we need to configure is to define which rights we will grant our runtime on the Volume we are creating. The default setting is read/write rights for the runtime, which is sufficient in most cases. The result of following these steps will be the following.
69		-
70		-[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-volume-filled-in.png]]
71		-
72		-==== 3.1.2 Link to Network Volume ====
73		-
74		-So, we first open the tab called "Network volume." Then, by pressing the "New" button, we can define a new "Network volume." In the pop-up that follows, we can specify the name of a machine volume and configure the relevant information for a network volume.
75		-
76	76	[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--network-volumes-configuration.png]]
77	77
78	78	Once you have done so, we press "Save" and switch back to the "Runtime volumes" tab.
79	79
80		-In here, we push the "New" button to create a new "Runtime volume." In the following pop-up, we first need to select the Type we want to use. For this example, we use the Type called "Volume."
	68	+==== 3.1.3 Link Volume ====
81	81
	70	+In the "Runtime volumes" tab, we push the "New" button to create a new "Runtime volume." In the following pop-up, we first need to select the Type we want to use. For this example, we use the Type called "Volume."
	71	+
82	82	{{info}}Based on your selection, the relevant input fields will change.{{/info}}
83	83
84	84	[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-volume.png]]
85	85
86		-The first thing we need to select is the "Machine volume." Once we have chosen our "Machine volume," we must set the Target specific for this runtime. This target defines the second part of the path to which the runtime will gain access. For example, when you fill in "/target", we can combine this with the "Machine volume" name to arrive at the correct directory from which eMagiz needs to read data (or write data to). So in our case, this would be "/file-directory/target."
	76	+The first thing we need to select is the "Volume." Once we have chosen our "Volume," we must set the Target specific for this runtime. This target defines the second part of the path to which the runtime will gain access. For example, when you fill in "/target", we can combine this with the "Volume" name to arrive at the correct directory from which eMagiz needs to read data (or write data to). So in our case in which we link the volume to the machine volume we created earlier, this would be "/file-directory/target."
87	87
88	88	The last setting we need to configure is to define which rights we will grant our runtime on the Volume we are creating. The default setting is read/write rights for the runtime, which is sufficient in most cases. The result of following these steps will be the following.
89	89
...	...	@@ -123,13 +123,8 @@
123	123
124	124	The named pipe option can be selected, but we yet have to see a valid use case within the context of eMagiz for using this option. Therefore we won't discuss this option further in this microlearning.
125	125
126		-== 4. Assignment ==
	116	+== 4. Key takeaways ==
127	127
128		-Navigate to Deploy -> Architecture and look at the Volume mapping options, read the help texts, and play around with the settings (if it is not a customer environment).
129		-This assignment can be completed with the help of the (Academy) project you created/used in the previous assignment.
130		-
131		-== 5. Key takeaways ==
132		-
133	133	* File-based communication on-premise changes in the new runtime architecture
134	134	* There are two ways to store **persistent** data
135	135	** Volume
...	...	@@ -137,14 +137,9 @@
137	137	* The Volume option is considered the best alternative because they have better performance, and bind mounts are dependent on the directory structure and OS of the host machine
138	138	* When you want to deal with **non-persistent** data, the Temporary file storage option is the way to go.
139	139
140		-== 6. Suggested Additional Readings ==
	125	+== 5. Suggested Additional Readings ==
141	141
142	142	If you are interested in this topic and want more information, please read the help text provided by eMagiz.
143	143
144		-== 7. Silent demonstration video ==
145	145
146		-This video demonstrates how you could have handled the assignment and gives context to what you have just learned.
147		-
148		-TBA
149		-
150	150	)))((({{toc/}}))){{/container}}{{/container}}