@Jeff, yeah it's gross, and taken way too long to deal with (granted, I don't think anyone noticed/appreciated this regression until ~queens, about a year after it happened).
There has been discussion about how to make the aggregate filters with the allocation_ratio metadata *work* again, discussed at the Dublin PTG:
Which would essentially mirror the allocation ratio metadata from the compute host aggregates API back to placement. If you have input on that spec please leave comments in the review - it's waylaid at this point.
@Jeff, yeah it's gross, and taken way too long to deal with (granted, I don't think anyone noticed/appreciated this regression until ~queens, about a year after it happened).
There has been discussion about how to make the aggregate filters with the allocation_ratio metadata *work* again, discussed at the Dublin PTG:
https:/ /etherpad. openstack. org/p/nova- ptg-rocky- placement ~L37
That solution never materialized though...
There is also this proposal:
https:/ /review. openstack. org/#/c/ 544683/
Which would essentially mirror the allocation ratio metadata from the compute host aggregates API back to placement. If you have input on that spec please leave comments in the review - it's waylaid at this point.