Changes for page Volume Mapping (On-premise)
Last modified by Erik Bakker on 2024/08/26 12:37
From version 57.1
edited by Eva Torken
on 2023/06/20 17:02
on 2023/06/20 17:02
Change comment:
There is no comment for this version
To version 54.1
edited by Erik Bakker
on 2023/04/11 12:31
on 2023/04/11 12:31
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e torken1 +XWiki.ebakker - 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). 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 +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). 51 51 52 -==== 3.1.1 DefineMachine Volume ====52 +==== 3.1.1 Link to 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,23 +57,33 @@ 57 57 58 58 Once you have done so, we press "Save" and switch back to the "Runtime volumes" tab. 59 59 60 - ====3.1.2DefineNetworkVolume====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." 61 61 62 - So, we first openthe tab called"Network volume." Then,bypressing the "New" button, we can define a new "Networkvolume." In the pop-up that follows, wean specifythe name of a machine volume andconfigurethe relevant informationfor a network volume. In mostcases a CIFSis used and the only relevantoptions thatneed to be filled inare the host, port, username and password.62 +{{info}}Based on your selection, the relevant input fields will change.{{/info}} 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 + 64 64 [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--network-volumes-configuration.png]] 65 65 66 66 Once you have done so, we press "Save" and switch back to the "Runtime volumes" tab. 67 67 68 - ====3.1.3LinkVolume====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." 69 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 72 {{info}}Based on your selection, the relevant input fields will change.{{/info}} 73 73 74 74 [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-volume.png]] 75 75 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 casein which we link the volume to the machine volume we created earlier, this would be "/file-directory/target."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." 77 77 78 78 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. 79 79 ... ... @@ -113,8 +113,13 @@ 113 113 114 114 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. 115 115 116 -== 4. Keytakeaways==126 +== 4. Assignment == 117 117 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 + 118 118 * File-based communication on-premise changes in the new runtime architecture 119 119 * There are two ways to store **persistent** data 120 120 ** Volume ... ... @@ -122,9 +122,14 @@ 122 122 * 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 123 123 * When you want to deal with **non-persistent** data, the Temporary file storage option is the way to go. 124 124 125 -== 5. Suggested Additional Readings ==140 +== 6. Suggested Additional Readings == 126 126 127 127 If you are interested in this topic and want more information, please read the help text provided by eMagiz. 128 128 144 +== 7. Silent demonstration video == 129 129 146 +This video demonstrates how you could have handled the assignment and gives context to what you have just learned. 147 + 148 +TBA 149 + 130 130 )))((({{toc/}}))){{/container}}{{/container}}