Comment 22 for bug 1468871

Considering the pre-migration checks question from a different perspective, there is already the ability for Nova to potentially attempt migration across nova-compute applications as they are all deployed as hypervisors in the same cell (typically), and we get issues with performing migrations/retries due to ssh key failure quite a bit now when we add new units that have to have a different config for i.e. different paths to the ephemeral-device on newer machines added to a cloud.

We currently already have to employ aggregate/flavor filters to handle i.e. SRIOV vs non SRIOV type nodes.

Ultimately, adding the ssh keys sync doesn't create any new bugs, it simply resolves this ssh key availability bug. James' question, however, does suggest a need for additional Openstack operator documentation when configuring non-homogenous hypervisors as migration peers.

Also, I agree on the spec comment from James, this should be a nova-compute configuration or relation interface that then communicates to n-c-c that ssh keys should be shared across any number of groups of migration-peer nova-compute applications.