Skip to Content
Last modified by Erik Bakker on 2024/09/03 08:14
From version 23.1
edited by Carlijn Kokkeler
on 2024/08/29 10:58
Change comment: There is no comment for this version
To version 19.1
edited by Erik Bakker
on 2024/06/25 14:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,5 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In this microlearning, we'll explore the concept of runtime images and their crucial role in deploying and maintaining eMagiz containers. A runtime image serves as the blueprint for creating container images, encompassing everything from the operating system to necessary libraries and configurations. We'll discuss how updates to these images impact your deployments, strategies for managing these updates, and steps for disaster recovery in case issues arise. Understanding this will help ensure your eMagiz environment remains stable and up-to-date.
2 +In this microlearning, we will focus on helping you to assess the impact of upgrading to a new image.
3 3  
4 4  If you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
... ... @@ -13,14 +13,12 @@
13 13  
14 14  == 3. Assessing the impact of runtime images ==
15 15  
16 -As mentioned, the runtime image is a template (i.e., blueprint), meaning all specific eMagiz container images are created from this template. The template holds all the latest software updates and libraries that the integration flows require. eMagiz follows the strategy of updating these required libraries frequently to ensure vulnerabilities can be fixed quickly and new functionality is available on a needed basis. Furthermore, having a single template available allows all eMagiz containers to operate on the same software base across all eMagiz clients. This way, a single mix of libraries can be made available to the community and tested correctly and coherently. There can be no other mix of software components that behave differently (as we had in our legacy runtime architecture).
16 +As mentioned, the runtime image is a template (i.e., blueprint), which effectively means that all specific eMagiz container images are created from this template. The template holds all the latest software updates and libraries that the integration flows require. eMagiz follows the strategy of updating these required libraries frequently to ensure vulnerabilities can be fixed quickly and new functionality is available on a needed basis. Furthermore, having a single template available allows all eMagiz containers to operate on the same software base across all eMagiz clients. This way, a single mix of libraries can be made available to the community and tested correctly and coherently. There can be no other mix of software components that behave differently (as we had in our legacy runtime architecture).
17 17  
18 -In essence, any container image consists of multiple layers. The first (foundational) layer comprises the operating system information (i.e., Linux configuration or Windows configuration) and a Java installation (correct JRE). Building on this in the second layer, we see a wide array of open-source code heavenly rooted in the Spring and Java frameworks combined with our proprietary monitoring stack, allowing us to gather information on your model upon which you can monitor. The third layer consists of your collection of flows that should run on a container (i.e., runtime). This layer is built up by the various flow designer components used in your release's flow versions. The fourth layer is the configuration layer in the form of (application) properties, memory configuration, and other configuration elements (i.e., route, deployment location, volumes, runtime settings). Below, you see a picture that illustrates this concept in an abstract form. In eMagiz, as well as in the image, you see that the layers form one construct that facilitates the purpose of the object. For eMagiz, this purpose is handling data via integrations.
18 +In essence, any container image consists of three layers. The first (foundational) layer comprises a wide array of open-source code heavenly rooted in the Spring and Java frameworks. The secondary layer consists of your collection of flows that should run on a container (i.e., runtime). This layer is built up by the various flow designer components used in your release's flow versions. The third layer is the configuration layer in the form of (application) properties, memory configuration, and other configuration elements (i.e. route, deployment location, volumes, runtime settings). Below, you see a picture that illustrates this concept in an abstract form. In eMagiz, as well as in the image, you see that the layers form one construct that facilitates the purpose of the object. For eMagiz, this purpose is handling data via integrations.
19 19  
20 20  [[image:Main.Images.Microlearning.WebHome@advanced-lifecycle-management-impact-of-runtime-image-upgrades--runtime-layers.png]]
21 21  
22 -This approach allows us to easily provide updates of not only dedicated eMagiz functionality but also of the OS, Java, and open-source frameworks used through a unified approach regardless of whether you deploy in our cloud or on-premises.
23 -
24 24  === 3.1 Overal deployment strategy ===
25 25  
26 26  When the prepare release step is triggered, the runtime image will create specific runtime images to deploy eMagiz containers. When we release a new runtime (base) image, eMagiz will trigger the generation of a new container image for each runtime (i.e., container) captured within the first release created **after** we release our new runtime image. For more information on when eMagiz creates a new container image, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]].
... ... @@ -33,7 +33,7 @@
33 33  
34 34  === 3.3 Approach ===
35 35  
36 -We strongly advise updating your Test and Acceptance environment before moving to Production. This will avoid potential problems appearing in a Production environment before any other environment. We will inform our customer base along the following timelines to better anticipate when a new runtime image will be released.
34 +We strongly advise updating your Test and Acceptance environment first before moving to Production. This will avoid potential problems appearing in a Production environment before any other environment. To better anticipate when a new runtime image will be released, we will inform our customer base along the following timelines.
37 37  
38 38  * High impact
39 39  ** As part of the release notes of **three** releases ahead of us releasing the new runtime image.
... ... @@ -56,6 +56,5 @@
56 56  * Read the release notes for runtime images carefully to assess the impact.
57 57  
58 58  == 5. Suggested Additional Readings ==
59 -* [[Release Information (Menu)>>doc:Main.Release Information.WebHome||target="blank"]]
60 -** [[Runtime Images (Navigation)>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]
61 -)))((({{toc/}}))){{/container}}{{/container}}
57 +
58 +If you are interested in this topic and want more information on it, please read the [[release notes>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] provided by eMagiz.)))((({{toc/}}))){{/container}}{{/container}}