Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:37
From version 19.1
edited by eMagiz
on 2022/05/22 21:30
Change comment: There is no comment for this version
To version 54.1
edited by Erik Bakker
on 2023/04/11 12:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +Volume Mapping (On-premise)
Parent
... ... @@ -1,0 +1,1 @@
1 +WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.marijn
1 +XWiki.ebakker
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Content
... ... @@ -1,97 +1,150 @@
1 -{{html wiki="true"}}
2 -<div class="ez-academy">
3 - <div class="ez-academy_body">
1 +{{container}}{{container layoutStyle="columns"}}(((
4 4  
5 -<div class="doc">
3 +{{warning}}
4 +Please note that this microlearning is for the new monitoring stack only.
5 +{{/warning}}
6 6  
7 +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.
7 7  
9 +Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
8 8  
9 -= Annotations =
11 +== 1. Prerequisites ==
10 10  
11 -In this microlearning, we will focus on using annotations to clarify your thought process. In the annotation, you either describe a best practice everyone should follow when they change that flow (i.e. within the asynchronous routing), describe how the (more complex) parts of the flow work or describe (parts of) of your message definitions (i.e. CDM, API Gateway Data model, system message, etc.). This will help yourself and others every time changes are needed.
13 +* Basic knowledge of the eMagiz platform
12 12  
13 -Should you have any questions, please contact academy@emagiz.com.
15 +== 2. Key concepts ==
14 14  
15 -* Last update: May 9th, 2021
16 -* Required reading time: 5 minutes
17 +This microlearning centers around learning how to set up your volume mapping correctly so you can exchange file-based data on-premise.
17 17  
18 -== 1. Prerequisites ==
19 +By volume mapping, we mean: Creating a configuration through which the docker container can read and write data on a specific path on an on-premise machine.
19 19  
20 -* Basic knowledge of the eMagiz platform
21 +There are several options for volume mapping for your on-premise machine.
22 +* Volume
23 +* Bind mount
24 +* Temporary file system
25 +* Named pipe
21 21  
22 -== 2. Key concepts ==
27 +== 3. Volume Mapping (On-premise) ==
23 23  
24 -This microlearning centers around using annotations.
25 -With annotations, we mean: A piece of text to explain something to yourself and others
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.
26 26  
27 -Annotations can be used for:
31 +There are several options for volume mapping for your on-premise machine.
32 +* Machine volume
33 +* Bind mount
34 +* Network volume
35 +* Temporary file system
36 +* Named pipe
28 28  
29 -* Describing a best practice everyone should follow
30 -* Describing (more complex) parts of the flow
31 -* Describe (parts of) your message definitions
38 +Below we will explain the differences between the various options available for your volume mapping. But before we do, we first explain how to set up this configuration within eMagiz. Then, you must navigate to Deploy -> Architecture on the model level. In this overview, you can access the Volume mapping per runtime deployed on-premise. To do so, you can right-click on the runtime to access the context menu.
32 32  
40 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--volume-option-context-menu.png]]
33 33  
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.
34 34  
35 -== 3. Annotations ==
44 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--volume-mapping-pop-up.png]]
36 36  
37 -In this microlearning, we will focus on using annotations on the flow level to clarify our thought process. In the annotation, you either describe a best practice everyone should follow when they change that flow (i.e. within the asynchronous routing) or describe how the (more complex) parts of the flow work. This will help yourself and others every time changes are needed within the flow.
46 +{{info}}Note that you should be in "Start editing" mode to make any changes to the configuration of your volume mapping.{{/info}}
38 38  
39 -Annotations can be used for:
48 +=== 3.1 Volume ===
40 40  
41 -* Describing a best practice everyone should follow
42 -* Describing (more complex) parts of the flow
43 -* Describe (parts of) your message definitions
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).
44 44  
45 -To clarify the use cases let us take a look at how annotations can be added within the eMagiz platform. In our first example, we will take a look at asynchronous routing. In many eMagiz projects, a best practice is followed on how to add something to the asynchronous routing (or change something within the asynchronous routing). Because the best practice contains multiple steps it makes sense to use the annotation functionality of eMagiz to define all these steps and register them at the place you need them (i.e. the asynchronous routing). Having done so will result in something like this:
52 +==== 3.1.1 Link to Machine Volume ====
46 46  
47 -<p align="center">[[image:novice-devops-perspectives-annotations--annotation-best-practice-async-routing.png||]]</p>
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.
48 48  
49 -The second example is about using annotations on the flow level to describe parts of the flow. In this example, we will use the annotation to describe that we use a filter to determine which messages are picked up from a local directory and how we filter. That way anyway opening the flow has to merely read the annotation to get the context. Having done so will result in something like this:
56 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--machine-volumes-configuration.png]]
50 50  
51 -<p align="center">[[image:novice-devops-perspectives-annotations--describe-parts-of-flow.png||]]</p>
58 +Once you have done so, we press "Save" and switch back to the "Runtime volumes" tab.
52 52  
53 -The third example does not take place on the flow level but the message definition level. Therefore instead of going to Create, we go to Design. In Design when you navigate to the CDM, API Gateway Data model, Event Streaming Data model, message definitions, etc. you have the option to add annotations to the canvas. In this example, we want to make clear to all that make changes that a certain part of our CDM is used by a lot of integrations within eMagiz and therefore everyone should be careful and think twice before adjusting anything related to that part. Having done so will result in something like this:
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."
54 54  
55 -<p align="center">[[image:novice-devops-perspectives-annotations--describe-crucial-part-of-cdm.png||]]</p>
62 +{{info}}Based on your selection, the relevant input fields will change.{{/info}}
56 56  
57 -Now that we saw some examples let us turn our attention to the how. How can I add an annotation and how can I link it. Adding the annotation is simple. You drag the annotation icon from the left context menu onto the canvas. As a result, an empty annotation will be shown on the canvas. By double-clicking on it you can type whatever you want. Note that you need to be in "Start Editing" mode to change anything, including annotations.
64 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-volume.png]]
58 58  
59 -<p align="center">[[image:novice-devops-perspectives-annotations--annotation-icon-context-menu.png||]]</p>
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."
60 60  
61 -When you are satisfied with what you have written down you can press the Save button. After you have done so you can rescale the annotation to ensure that the complete text is visible. To link the annotation to a component (on flow level) or an entity (on message definition level) you hover over the annotation until your mouse indicator changes to a + icon, execute a right-click and drag from the annotation to the component in question.
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.
62 62  
63 -Now you know what annotations are good for and how you can add them within the eMagiz platform.
70 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-volume-filled-in.png]]
64 64  
65 -===== Practice =====
72 +==== 3.1.2 Link to Network Volume ====
66 66  
67 -== 4. Assignment ==
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.
68 68  
69 -Add annotation on the flow level that describes how (a part of) a flow works.
70 -This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
76 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--network-volumes-configuration.png]]
71 71  
72 -== 5. Key takeaways ==
78 +Once you have done so, we press "Save" and switch back to the "Runtime volumes" tab.
73 73  
74 -* Annotations can be used for:
75 - * Describing a best practice everyone should follow
76 - * Describing (more complex) parts of the flow
77 - * Describe (parts of) your message definitions
78 -* You can add annotations by dragging and dropping the annotation icon on the canvas.
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."
79 79  
82 +{{info}}Based on your selection, the relevant input fields will change.{{/info}}
80 80  
84 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-volume.png]]
81 81  
82 -== 6. Suggested Additional Readings ==
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."
83 83  
84 -There are no suggested additional readings on this topic
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.
85 85  
86 -== 7. Silent demonstration video ==
90 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-volume-filled-in.png]]
87 87  
88 -This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
92 +{{warning}}Note that when you use the Volume option, the external system with which you exchange data on-premise via a file-based method needs to be able to write or read the data from the Volume (i.e., directory) you have configured in Docker. Should this be a problem, the Bind mount alternative discussed below should be considered.{{/warning}}
89 89  
90 -<iframe width="1280" height="720" src="../../vid/microlearning/novice-devops-perspectives-annotations.mp4" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
94 +=== 3.2 Bind mount ===
91 91  
92 -</div>
96 +An alternative option to read and write **persistent** data is to use the "Bind mount" option. In general, we advise using the "Volume" option because they have better performance, and bind mounts depend on the host machine's directory structure and OS. However, only some external systems can adapt to this that easily. For example, the "Bind mount" option can interest your use case.
93 93  
94 -</div>
95 -</div>
98 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-bind-mount.png]]
96 96  
97 -{{/html}}
100 +To configure a "Bind mount," you need to define a source and a target directory linked to each other. The source directory represents the directory on your local system (that might already be used currently to exchange files). The target directory defines a directory on your docker installation that the runtime can access.
101 +
102 +{{warning}}Note that when the source directory does not exist, the runtimes cannot be deployed correctly. One of the following two configurations displayed below are needed to find the source directory:
103 +* /mnt/host/{local-directory}
104 +* /run/desktop/mnt/host/{local-directory}{{/warning}}
105 +
106 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-bind-mount-filled-in.png]]
107 +
108 +{{info}}Note that when you use this option, your directory reference in your flow should refer to the "target" directory configured here.{{/info}}
109 +
110 +=== 3.3 Temporary file system ===
111 +
112 +The temporary file system option is for you if you do not want to work with **persistent** data but require **non-persistent** data. This way, you can increase the container's performance by avoiding writing into the container's writable layer.
113 +
114 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage.png]]
115 +
116 +To configure this option, you need a target location. On top of that, you can define the maximum size of the temporary file system.
117 +
118 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage-filled-in.png]]
119 +
120 +{{warning}}We strongly advise you to define this number so that you can limit the potential impact this solution can have on the stability of your machine.{{/warning}}
121 +
122 +=== 3.4 Named pipe ===
123 +
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 +
126 +== 4. Assignment ==
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 +* File-based communication on-premise changes in the new runtime architecture
134 +* There are two ways to store **persistent** data
135 + ** Volume
136 + ** Bind mount
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 +* When you want to deal with **non-persistent** data, the Temporary file storage option is the way to go.
139 +
140 +== 6. Suggested Additional Readings ==
141 +
142 +If you are interested in this topic and want more information, please read the help text provided by eMagiz.
143 +
144 +== 7. Silent demonstration video ==
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 +)))((({{toc/}}))){{/container}}{{/container}}
novice-devops-perspectives-annotations--annotation-best-practice-async-routing.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.marijn
Size
... ... @@ -1,1 +1,0 @@
1 -25.7 KB
Content
novice-devops-perspectives-annotations--annotation-icon-context-menu.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.marijn
Size
... ... @@ -1,1 +1,0 @@
1 -774 bytes
Content
novice-devops-perspectives-annotations--describe-crucial-part-of-cdm.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.marijn
Size
... ... @@ -1,1 +1,0 @@
1 -15.5 KB
Content
novice-devops-perspectives-annotations--describe-parts-of-flow.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.marijn
Size
... ... @@ -1,1 +1,0 @@
1 -18.9 KB
Content