On 02/16/2015 01:17 AM, Nikola Đipanov wrote:
On 02/14/2015 08:25 AM, Alex Xu wrote:
Agree with Nikola, the claim already checking that. And instance booting
must be failed if there isn't pci device. But I still think it should go
through the filters, because in the future we may move the claim into
the scheduler. And we needn't any new options, I didn't see there is any
behavior changed.
I think that it's not as simple as just re-running all the filters. When
we want to force a host - there are certain things we may want to
disregard (like aggregates? affinity?) that the admin de-facto overrides
by saying they want a specific host, and there are things we definitely
need to re-run to set the limits and for the request to even make sense
(like NUMA, PCI, maybe some others).
So what I am thinking is that we need a subset of filters that we flag
as - "we need to re-run this even for force-host", and then run them on
every request.
Yeah, that makes sense. Also, I think that flag should be an attribute of the
filter itself, so that people adding new filters don't need to also add the
filter to a list somewhere.
Have the default meaning be "can be skipped", then the critical ones can set it
to "can't be skipped".
Chris
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
