Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-70483

[RFE] rhel_system_roles.ha_cluster - export corosync configuration [rhel-9]

    • rhel-sst-system-roles
    • 0
    • Dev ack
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • Enhancement
    • Hide
      .Support for exporting `corosync` configuration of an existing cluster

      The `ha_cluster` RHEL system role now supports exporting the `corosync` configuration of an existing cluster in a format that can be fed back to the role to recreate the same cluster. If you did not use the `ha_cluster` RHEL system role to create your cluster, or if you have lost the original playbook for the cluster, you can use this feature to build a new playbook for the cluster.

      Show
      .Support for exporting `corosync` configuration of an existing cluster The `ha_cluster` RHEL system role now supports exporting the `corosync` configuration of an existing cluster in a format that can be fed back to the role to recreate the same cluster. If you did not use the `ha_cluster` RHEL system role to create your cluster, or if you have lost the original playbook for the cluster, you can use this feature to build a new playbook for the cluster.
    • Proposed
    • None

      This is a clone of issue RHEL-46219 to use for version rhel-9.6

      Original description:

      Goal

      • As an ha_cluster role user, I want to be able to export corosync configuration and other essential pieces of existing cluster setup so that when running the exported configuration as a ha_cluster role playbook I am able to recreate the same cluster.
      • In this step no pacemaker, sbd, qnetd or other configuration is expected to be exported

      Acceptance Criteria

      A list of verification conditions, successful functional tests, or expected outcomes in order to declare this story/task successfully completed.

      • There is a way to export corosync configuration into a variables / playbook
      • Other necessary parts of configuration are handled as well:
        • ha_cluster_hacluster_password
        • ha_cluster_start_on_boot
        • ha_cluster_corosync_key_src
        • ha_cluster_pacemaker_key_src
        • ha_cluster_fence_virt_key_src
        • ha_cluster_regenerate_keys
      •  
      • The result can be run as a playbook and creates a bare running cluster with no resources. However, the whole corosync configuration is recreated.

              rmeggins@redhat.com Richard Megginson
              watson-automation Watson Automation
              Tomas Jelinek Tomas Jelinek
              Michal Nováček Michal Nováček
              Steven Levine Steven Levine
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: