Comment 6 for bug 1804125

As an operator, I don't really have a strong opinion one way or the other on whether allocation ratios should be controlled per compute in config files or per aggregate in metadata; in general, I consider the aggregate metadata approach more agile and more in keeping with OpenStack's common pattern of API accessibility to most operations, but I can see an argument on each side.

What's more distressing is that this appears to have produced a schism between the intended, documented functions of Nova scheduler and the actual operation of those functions on several consecutive releases of OpenStack.

If the Aggregate* filters are no longer functional, and are no longer intended to be so, then I would think they should reasonably have been removed from the documentation and from the project so that deployers wouldn't expect to rely on them.