Please note: This schedule is for OpenStack Active Technical Contributors participating in the Icehouse Design Summit sessions in Hong Kong. These are working sessions to determine the roadmap of the Icehouse release and make decisions across the project. To see the full OpenStack Summit schedule, including presentations, panels and workshops, go to http://openstacksummitnovember2013.sched.org.
Context is how to create a mechanism that allows new resource metrics to be added to the scheduler in a flexible way.
User Stories: - I want to be able to define a new filter that tracks network badwidth entitlement - I want to be able to define a new filter that tracks cpu entitilement - I want to be able to schedule based on utilization. - I want to be able to schedule based on power consumption. .... PCI-style metrics in scheduling ('I have a limited number of X per host' versus continuous (CPU) or nearly so (memory) metrics)
* What should the Nova scheduler's relationship be with Celiometer ? Possible answers are: - Provide metrics to Ceilometer (or, at least, offer the same sources to Ceilometer) - Optionally Consume additional metircs from Ceilometer for advanced scheduling - Depend on Ceilometer for metrics - An extensible plugin framework on nova compute node to collect various metrics data to be used by nova schedulers, that kind of data could also be sent to ceilometers for other advanced usages like alarming.
* What needs to be changed in the current Nova data model (flavours / compute_nodes) - See https://docs.google.com/document/d/1m7Uda4lgNOyAUnlJuHi2m1nqjp1Gi4T13RBUNBgDhNM
