Currently we ssh into compute nodes in at least two places in Adoption:

• "Stop OpenStack services" step, currently puts together controller and compute services as it was developed with the Standalone use case. (For supporting separate compute we'd have to split the compute services out and ssh to computes.)
• OVN adoption step, when redirecting compute node ovn-controller services from the old southbound DB to the new podified southbound DB.

Since there can be many compute nodes in a deployment, it would be very beneficial for Adoption UX to do the necessary compute node actions via EDPM rather than via SSH (using NodeSets and Deployments, regardless if some Adoption-specific Deployment or the "main" data plane Deployment). It would be good if we could push all data plane operations after the control plane has been fully adopted because it would help with rolling back the control plane (OSPRH-1890). Touching the data plane config would be considered a point of no return for the rollback procedure.

Epic definition of done:

• We can still Adopt all services as before but there are no steps which SSH into compute nodes.

Proposed release blocker due to being a hard dependency of OSPRH-1890.