Wiki source code of V2.1.0 - Reverted

Version 5.1 by Carlijn Kokkeler on 2024/01/18 09:13

Hide last authors
Eva Torken 1.1 1 {{container}}
2 {{container layoutStyle="columns"}}(((
Carlijn Kokkeler 5.1 3 {{warning}}The delivery of failover in release 212 of this morning unfortunately breaks the Deploy/Architecture/Start-stop flows screen in some cases.
4 This is when your active release is created after 05:15 this morning (thus based on the 2.1.0 image), and you try to open the start-stop flows screen for any container that was not deployed yet.{{/warning}}
Eva Torken 1.1 5 These are the release notes for this runtime image. Once a runtime image is released, every new release will utilize this runtime image as base for creating runtime images for docker. For more information on this 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"]].
6
Carlijn Kokkeler 3.1 7 =====New features=====
Eva Torken 1.1 8
Carlijn Kokkeler 3.1 9 New components to support a failover setup:
Eva Torken 1.1 10
Carlijn Kokkeler 4.1 11 * Clustered lock registry: obtain a lock that can be shared over different containers
Carlijn Kokkeler 3.1 12 * Leader initiator: Used to automatically start and stop roles based on whether they can obtain a cluster-wide lock
13 * New & extended operations for controlling integration components
14 ** New: Start & stop all components in a specific role, so you can start and stop multiple components at the same time
15 ** New: List all roles and whether they support leadership
16 ** Extended: List flow components now also shows whether a component is configured to be in a role
17
18 Deploy - Deployment plan: to incorporate failover actions during deployment, two new deployment step types are introduced namely “Group” and “Failover”.
19
Eva Torken 1.1 20 )))((({{toc/}}))){{/container}}
21 {{/container}}