Changes for page V2.1.1
Last modified by Carlijn Kokkeler on 2024/07/17 14:41
From version 15.1
edited by Carlijn Kokkeler
on 2024/07/17 14:41
on 2024/07/17 14:41
Change comment:
There is no comment for this version
To version 9.1
edited by Carlijn Kokkeler
on 2024/02/12 14:35
on 2024/02/12 14:35
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -V2.1. 11 +V2.1.0 - Content
-
... ... @@ -3,9 +3,18 @@ 3 3 4 4 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"]]. 5 5 6 -====New features==== 6 +=====New features===== 7 7 8 - * Whenusing a failovermanager, the runtimewill nowindicate itsleadershipstatustaking intoaccount whetherit isconnected to other containers.8 +New components to support a failover setup: 9 9 10 +* Clustered lock registry: obtain a lock that can be shared over different containers 11 +* Leader initiator: Used to automatically start and stop roles based on whether they can obtain a cluster-wide lock 12 +* New & extended operations for controlling integration components 13 +** New: Start & stop all components in a specific role, so you can start and stop multiple components at the same time 14 +** New: List all roles and whether they support leadership 15 +** Extended: List flow components now also shows whether a component is configured to be in a role 16 + 17 +Deploy - Deployment plan: to incorporate failover actions during deployment, two new deployment step types are introduced namely “Group” and “Failover”. 18 + 10 10 )))((({{toc/}}))){{/container}} 11 11 {{/container}}