Changes for page Volume Mapping (On-premise)

Summary

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

Details

Page properties

Content

...	...	@@ -29,8 +29,9 @@
29	29	When you need to read and write files from an on-premise disk, you need to know the path in which the data is stored and make sure that the docker container in your runtime(s) running has access to this path. There are several ways of dealing with this challenge. First, this microlearning will discuss the various alternatives and best approaches in these scenarios.
30	30
31	31	There are several options for volume mapping for your on-premise machine.
32		-* Volume
	32	+* Machine volume
33	33	* Bind mount
	34	+* Network volume
34	34	* Temporary file system
35	35	* Named pipe
36	36
...	...	@@ -38,7 +38,7 @@
38	38
39	39	[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--volume-option-context-menu.png]]
40	40
41		-When you click this option, you will see the following pop-up. In this pop-up, you can define the machine-level and runtime-level volumes. More on that later. This is the starting point for configuring your volume mapping. We will walk through each available option and explain how they work and should be configured.
	42	+When you click this option, you will see the following pop-up. In this pop-up, you can define the machine-level, runtime-level volumes and network-level volumes. More on that later. This is the starting point for configuring your volume mapping. We will walk through each available option and explain how they work and should be configured.
42	42
43	43	[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--volume-mapping-pop-up.png]]
44	44
...	...	@@ -46,17 +46,33 @@
46	46
47	47	=== 3.1 Volume ===
48	48
49		-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 you can create within the same pop-up. This means you can re-use a "Machine 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.
50	50
	52	+==== 3.1.1 Define Machine Volume ====
	53	+
51	51	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.
52	52
53	53	[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--machine-volumes-configuration.png]]
54	54
55		-Once you have done so, we press "Save" and switch back to the "Runtime volumes" tab. Then, 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." Based on your selection, the relevant input fields will change.
	58	+Once you have done so, we press "Save" and switch back to the "Runtime volumes" tab.
56	56
	60	+==== 3.1.2 Define Network Volume ====
	61	+
	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	+
	64	+[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--network-volumes-configuration.png]]
	65	+
	66	+Once you have done so, we press "Save" and switch back to the "Runtime volumes" tab.
	67	+
	68	+==== 3.1.3 Link Volume ====
	69	+
	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	+
	72	+{{info}}Based on your selection, the relevant input fields will change.{{/info}}
	73	+
57	57	[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-volume.png]]
58	58
59		-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."
60	60
61	61	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.
62	62