Change Details

The main goal of the Pacemaker 3 release is to remove support for deprecated legacy syntax, in order to improve code maintainability. The Pacemaker 3.0.0 release is expected in late 2024. == Release compatibility == * Rolling upgrades from Pacemaker versions earlier than 2.0.0 are not supported. (Rolling upgrades from version 2.0.0 and greater should be possible with little to no change. Clusters with earlier versions can do a rolling upgrade to any Pacemaker 2 release and then another rolling upgrade to 3.0.0 or later.) * Cluster nodes running Pacemaker 3.0.0 or later will be unable to connect to Pacemaker Remote nodes running Pacemaker 1.1.14 or earlier. * Cluster nodes running a Pacemaker 1 release will be unable to connect to bundles or Pacemaker Remote nodes running Pacemaker 3.0.0 or later. == Proposed changes == * [[/w/projects/pacemaker/pacemaker_3.0_changes/pacemaker_3.0_build_changes/ | Pacemaker 3.0 Build Changes]] * [[/w/projects/pacemaker/pacemaker_3.0_changes/pacemaker_3.0_configuration_changes/ | Pacemaker 3.0 Configuration Changes]] * [[/w/projects/pacemaker/pacemaker_3.0_changes/pacemaker_3.0_behavioral_changes/ | Pacemaker 3.0 Behavioral Changes]] * [[/w/projects/pacemaker/pacemaker_3.0_changes/pacemaker_3.0_api_changes/ | Pacemaker 3.0 API Changes]]

The main goal of the Pacemaker 3 release is to remove support for deprecated legacy syntax, in order to improve code maintainability. The Pacemaker 3.0.0 release is expected in late 2024. == Release compatibility == * Rolling upgrades from Pacemaker versions earlier than 2.0.0 are not supported. (Rolling upgrades from version 2.0.0 and greater should be possible with little to no change. Clusters with earlier versions can do a rolling upgrade to any Pacemaker 2 release and then another rolling upgrade to 3.0.0 or later.) * Cluster nodes running Pacemaker 3.0.0 or later will be unable to connect to Pacemaker Remote nodes running Pacemaker 1.1.14 or earlier. * Cluster nodes running a Pacemaker 1 release will be unable to connect to bundles or Pacemaker Remote nodes running Pacemaker 3.0.0 or later. == Changes == * [[/w/projects/pacemaker/pacemaker_3.0_changes/pacemaker_3.0_build_changes/ | Pacemaker 3.0 Build Changes]] * [[/w/projects/pacemaker/pacemaker_3.0_changes/pacemaker_3.0_configuration_changes/ | Pacemaker 3.0 Configuration Changes]] * [[/w/projects/pacemaker/pacemaker_3.0_changes/pacemaker_3.0_behavioral_changes/ | Pacemaker 3.0 Behavioral Changes]] * [[/w/projects/pacemaker/pacemaker_3.0_changes/pacemaker_3.0_api_changes/ | Pacemaker 3.0 API Changes]]

The main goal of the Pacemaker 3 release is to remove support for deprecated legacy syntax, in order to improve code maintainability. The Pacemaker 3.0.0 release is expected in late 2024. == Release compatibility == * Rolling upgrades from Pacemaker versions earlier than 2.0.0 are not supported. (Rolling upgrades from version 2.0.0 and greater should be possible with little to no change. Clusters with earlier versions can do a rolling upgrade to any Pacemaker 2 release and then another rolling upgrade to 3.0.0 or later.) * Cluster nodes running Pacemaker 3.0.0 or later will be unable to connect to Pacemaker Remote nodes running Pacemaker 1.1.14 or earlier. * Cluster nodes running a Pacemaker 1 release will be unable to connect to bundles or Pacemaker Remote nodes running Pacemaker 3.0.0 or later. == Proposed c== Changes == * [[/w/projects/pacemaker/pacemaker_3.0_changes/pacemaker_3.0_build_changes/ | Pacemaker 3.0 Build Changes]] * [[/w/projects/pacemaker/pacemaker_3.0_changes/pacemaker_3.0_configuration_changes/ | Pacemaker 3.0 Configuration Changes]] * [[/w/projects/pacemaker/pacemaker_3.0_changes/pacemaker_3.0_behavioral_changes/ | Pacemaker 3.0 Behavioral Changes]] * [[/w/projects/pacemaker/pacemaker_3.0_changes/pacemaker_3.0_api_changes/ | Pacemaker 3.0 API Changes]]