2-Node Openshift has two sets of configuration it needs to apply to the OS:

1. the Corosync and Pacemaker binaries (currently being built in via an external image build)
2. a set of file/unit configuration, plus additional password configuration for a non-core user: https://gitlab.cee.redhat.com/clobrano/2no-lab/-/blob/main/HASetupPhase/setup_ha.yaml

The mains asks are:

1. the configuration does not need any user intervention, and can be updated along with the OCP platform
2. this is present during bootstrap time on the master nodes (does not need to be on the bootstrap nodes)
3. this is available for testing latest by early 4.19 cycle so this can be shipped as tech preview in 4.19 (and potentially using 4.18 payloads to do early testing)

As a shorter term solution:

1. the Corosync and Pacemaker binaries will be added to RHEL base, so we can add them as extensions
2. the additional files/units can be added into MCO templates, and we can add additional rendering logic to detect for 2NO architecture

For edge:

1. the sanlock and lvmlockd binaries will be added to the RHEL base
2. the additional files/units can be added into the MCO

Longer term:

1. we would like to supply the packages (and content) as an image build
   1. we would need to build an image on the bootstrap node
   2. the configuration snippet for the packages need to work alongside any additional user image-based customizations, and automatically rebuild with cluster upgrades