Hi Paul, Thanks for your answer, I read the blueprint and am aware of what it will add to the whole resource and scheduling bits of OpenStack.
I guess I'll just continue with what I did and wait for the blueprint to get implemented, unless there's a quick way to add it to Havana without waiting for the next release. Abbass. > Hi Abbass, > I guess you read the blueprint Russell referred to. I think you actually > are saying the same - but please read steps below and tell me if they don't > cover what you want. > This is what it will do: > 1. Add a column to the compute_nodes table for a JSON blob > 2. Add plug-in framework for additional resources in resource_tacker > (just like filters in filter scheduler) > 3. Resource plugin classes will implement things like: > a. Claims test method > b. "add your data here" method (so it can populate the JSON blob) > 4. Additional column is available in host_state at filter scheduler > You will then be able to do any or all of the following: > 1. Add new parameters to requests in extra_specs > 2. Add new filter/weight classes as scheduler plugins > a. Will have access to filter properties (including extra_specs) > b. Will have access to extra resource data (from compute node) > c. Can generate limits > 3. Add new resource classes as scheduler plugins > a. Will have access to filter properties (including extra specs) > b. Will have access to limits (from scheduler) > c. Can generate extra resource data to go to scheduler > Does this match your needs? > There are also plans to change how data goes from compute nodes to > scheduler (i.e. not through the database). This will remove the database > from the equation. But that can be kept as a separate concern. > Paul.
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev