Hi nova and keystone devs,
We have a use case where we want to schedule a bunch of projects to specific compute nodes only. The aggregate_multitenancy_isolation isn’t viable because in some cases we will want thousands of projects to go to some hardware and it isn’t manageable/scaleable to do this in nova and aggregates. (Maybe it is and I’m being silly?)
The best way I can think of doing this is to tag the keystone projects (or possibly set a custom property) and then write a custom nova scheduler filter to use the tag/property. The only issue I have is that tags/properties aren’t available to nova in it’s RequestContext.
Can you think of a better way or a way that would work now?
If this does in fact sound like a good way forward does authtoken middleware send this data downwards so nova could consume?
If it does I assume it would be then as simple as adding these to the nova RequestContext?
Thanks, Sam