> On 28 Feb 2019, at 1:25 am, Matt Riedemann <mriedemos at gmail.com> wrote: > > On 2/26/2019 11:53 PM, Sam Morrison wrote: >> 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?) > > Is the issue because of this? > > https://bugs.launchpad.net/nova/+bug/1802111 <https://bugs.launchpad.net/nova/+bug/1802111> > Or just in general. Because https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#tenant-isolation-with-placement fixes that problem, but is only available since Rocky. Yeah essentially it is however it would be nice to manage this in keystone where is’t all in one place but this I think would work. Just upgraded to Queens so not far off too! > Also, I can't find it now but there was a public cloud workgroup bug in launchpad at one point where it was asking that the AggregateMultiTenancyIsolation filter work on keystone domains rather than a list of projects, so if those projects were all in the same domain you'd just specify the domain in the aggregate metadata than the thousands of projects which is your scaling issue. Tobias might remember that bug. We actually already have a domain scheduler filter [1] but we have multiple levels of projects that intersects. Eg. We use domains to seperate our Australian and NZ projects. But we also have needs to schedule our projects based on their funding source. Thanks, Sam [1] https://github.com/NeCTAR-RC/nova/blob/nectar/queens/nova/cells/filters/restrict_domain.py <https://github.com/NeCTAR-RC/nova/blob/nectar/queens/nova/cells/filters/restrict_domain.py> > > -- > > Thanks, > > Matt > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190228/cc7b51fa/attachment.html>