Pulling aggregates in the compute starting in Rocky might be necessary solely for the provider tree saying if there are shared providers in the tree, like for shared storage. But that's not all teased out yet I don't think, i.e. we haven't really tried testing things out with shared storage modeled like that in placement in a multi-node CI environment like in a ceph job. There was something the other day I was commenting on that won't work with shared storage too, that had to do with move operations, it might have been these types of TODOs:
As for comment 4 and allocations, we have the "nova-manage placement heal_allocations" CLI now to fix up allocations for instances if necessary. That compat code in the compute service can likely be deleted at this point.
Pulling aggregates in the compute starting in Rocky might be necessary solely for the provider tree saying if there are shared providers in the tree, like for shared storage. But that's not all teased out yet I don't think, i.e. we haven't really tried testing things out with shared storage modeled like that in placement in a multi-node CI environment like in a ceph job. There was something the other day I was commenting on that won't work with shared storage too, that had to do with move operations, it might have been these types of TODOs:
https:/ /github. com/openstack/ nova/blob/ c8b93fa2493dce8 2ef4c0b1e7a503b a9b81c2e86/ nova/conductor/ tasks/migrate. py#L56
As for comment 4 and allocations, we have the "nova-manage placement heal_allocations" CLI now to fix up allocations for instances if necessary. That compat code in the compute service can likely be deleted at this point.