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.
A private cloud in this context is set of compute hosts that a tenant has dedicated access to. The host themselves remain part of the Nova configuration, i.e this is different from bare metal provisioning in that the tenant is not getting access to the Host OS - just a dedicated pool of compute capacity. This gives the tenant guaranteed isolation for their instances, at the premium of paying for a whole host.
The concept was discussed briefly (with a good reception) at the Havana summit, since when it has been evolved into a working prototype based almost exclusively on existing aggregate functionality. (In effect it provides a user facing abstraction to aggregates). Although this looks like a scheduler topic it is mainly about a new layer of aggregate manipulation logic on the API server.
Operations a User can perform: - Create a Pcloud - Allocate hosts to a Pcloud (of a specific host-flavor and AZ) - See hosts and instances in the Pcloud - Schedule instances to a Pcloud - Give access to other tenants to schedule to the plcoud - Change the scheduling parameters (cpu allocation ratio, memory allocation ratio)
Operations an Cloud administrator can perform: - Define a host flavor - Mark specific physical hosts as being available as a host-flavor
I want to use this session to describe the approach and get feedback on both the current design and what additional features are required. I also want to discuss some of the potential race conditions in host allocation, and what might be done to address those, and touch on the performance aspects of using aggregates for scheduling, and what might be done to improve those.
