Comment 8 for bug 1863190

I must correct parts of my earlier comment 7:

> With multiple cells with each cell using their own separate message queue, the late affinity check can't work.

> When running with multiple cells, it presently is not possible to enforce affinity policy properly in a race situation. To support this, affinity support needs to be implemented in the placement service.

This is incorrect. It is possible to enforce affinity policy in a race situation with multiple cells if cell conductors are configured to set [api_database]connection and computes do not set [workarounds]disable_group_policy_check_upcall.

This is not an ideal configuration with multiple cells, however, as cells are meant to be isolated from the upper layers of the deployment. That is where we will need affinity support to be added in the placement service, to be able to fully enforce affinity policies without need to configure cell conductors to access the API database.