Changes for page Impact of Runtime Image Upgrades
Last modified by Erik Bakker on 2024/09/03 08:14
From version 24.1
edited by Carlijn Kokkeler
on 2024/08/29 10:59
on 2024/08/29 10:59
Change comment:
There is no comment for this version
To version 22.1
edited by Carlijn Kokkeler
on 2024/08/27 15:02
on 2024/08/27 15:02
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,5 +1,5 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 -In this microlearning, we 'llexplore theconcept of runtime imagesand their crucial role indeploying and maintaining eMagiz containers. A runtime image serves as theblueprint for creatingcontainer images, encompassing everything fromtheoperatingsystem to necessary librariesand configurations. We'll discusshow updates to theseimages impactyourdeployments, strategies formanaging these updates, and steps fordisasterrecovery incaseissues arise. Understanding thiswillhelp ensure your eMagiz environment remains stableand 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 ... ... @@ -8,6 +8,7 @@ 8 8 * Advanced knowledge of the eMagiz platform 9 9 10 10 == 2. Key concepts == 11 + 11 11 With runtime image, we mean the template used to create runtime-specific (docker) images. That image is used to deploy an eMagiz container and contains all required software components to let the eMagiz container function properly. One of the critical requirements is to load the necessary libraries used by runtime flows. A library in this context is a software component that performs a specific, often technical function in the eMagiz runtime. These libraries are based on Java and many open-source frameworks, such as Spring and Artemis. Given that these frameworks also continuously develop, it means that from time to time, we need to upgrade the versions of these underlying frameworks. 12 12 13 13 == 3. Assessing the impact of runtime images ==