© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
Hi Ihar, the nova scheduler spec you were asking about is this one: https:/
It's very preliminary, and probably inconsistent in many forms yet, but it's up for discussion, I have to re-read jay's resource aggregation spec for the nova scheduler to see if it does (somehow) fit our scheduling purposes.
What Irena is proposing here (I asked her to help with proposing this RFE), is a first step, for a later information feed back to nova.
May be it's too early for this, and we will need to see who feeds the information exactly (compute nodes or neutron-server).
It could be interesting, not only to feed nova, but to provide an API to ask neutron-server, "which hosts can I use to plug this port meeting all it's characteristics" (note: this is not desired by nova because they don't want to do an external API call from the scheduler) but other projects integrating to neutron could benefit from it. From that point of view, centralising the information is a good idea.