How did the Kilo summit go?
● Paris felt very productive to me, more productive than Atlanta
● Nova has an increasingly clear vision of where we should go
● There are big architectural improvements to be made, but more on that
later
Specifications
● New specifications process introduced in Juno
● A formal document which defines what is being implemented
● Which is reviewed separately from the code
● Operators encouraged to participate
● Approved: http://specs.openstack.org/openstack/nova-specs/
● Proposed: https://review.openstack.org/#/q/project:openstack/nova-specs,
n,z
How did specifications go in Juno?
● A summary of the specifications implemented in Juno:
● http://www.stillhq.com/openstack/juno/000018.html
● Lessons learned
How did specifications go in Juno?
● Specifications did slow us down
● Some of that was intended, we needed to be more deliberate
● I think we’re seeing higher quality features now
● But there were also lessons to be learned
● Tweaks for Kilo:
● Fast track approvals
● Trivial blueprints
● Backlog blueprints
● Project priorities
Priorities for Kilo
● The idea here is to address the architectural problems we see in Nova
● Wide reaching changes across the entire code base
● So, a single driver is unlikely to ever be listed as a priority
Priorities for Kilo
● Cells v2
● Continued object transition
● Scheduler
● v2.1 API
● Functional testing
● nova-network to neutron migration
● No downtime DB upgrades
● Bugs
● Continuous integration
Other approved specifications
● Enforcing unique instance UUIDs in the SQL database
● API improvements (get instance lock status for example, better result
pagination, tagging for instances)
● Hyper-V and libvirt SMBFS support
● Ironic config drive support
● Continued work on NFV support in libvirt (NUMA, CPU pinning, etc)
● VMWare support for OVA, ephemeral disks, SPBM and vSAN
Other specifications
● There are heaps of other specifications proposed as well
● You can see a recent summary of them here:
http://www.stillhq.com/openstack/kilo/000006.html
Questions?
As always, I’m happy to chat:
● mikal@stillhq.com
● @mikal on twitter
● mikal on freenode IRC
● openstack@lists.openstack.org