The resource class has arrived! Except, there are some issues. :(
Ironic users who use Nova, have long been using flavors and additional extra_specs to match baremetal nodes for scheduling. The move to using resource classes impacts this capability. Worse yet, in some cases extra_specs are used to convey things like boot_mode and boot option which can alter the deployment behavior!
We now need to determine and identify traits and the information we collect with Ironic-Inspector. This is different because we have previously been adding attributes about a node, and allow the scheduler to perform magic and choose nodes.
While the Ironic community is still early in to trying to identify possible solutions, we would like to bring up and discuss some of these issues and options.
- What sort of traits would operators be interested in?
- Rules to identify traits? We're thinking an API. Tell us now if we're crazy, oh wait, nevermind!
- Should we also have rules to identify resource classes?
- What other information should we keep around that users/operators find useful?
Registration Opening Soon
Registration will open for you to purchase passes for the OpenStack Summit very soon!
We're excited to see you there!
