Whether you want to build the software, run it, grow the community or just learn more about it, there will be content, workshops and design sessions for you to attend at the OpenStack Summit, Oct 15-18 in San Diego. Stick around Friday for the first OpenStack service day, a 1/2 day beach cleanup.
This session will include the following subject(s):
Splitting out compute to it's own service:
There is a lot going on in nova. I feel that nova is the scheduler and orchestration point for compute services and would like to have a discussion about abstracting the "hypervisor" and "container" services into a defined API and making it easier to maintain features, parity, and enhancements there without touching the core nova code base.
Lock the hypervisor guys in a room:
A general discussion between people who work on the different hypervisors, to ensure that:
- code is shared - code is outside the hypervisor when at all possible - different hypervisors have the same behaviours - great ideas propagate
Specific points I'd like to see discussed are injection (it looks like it shouldn't be hypervisor specific but it is; it's hard to add new file injection methods for unsupported filesystems, different config disks or even different network interface file formats), firewalling, proliferating VIF implementations and device mapping.