4.1 Release Review

I have two questions for you today.

What’s in 4.1? Lots of internal architectural changes (we want to speed up

development of new integrations) 20 new features 24 “improvements” 155 bug fixes

Architectural Changes Converted from custom injection framework to Spring Packaging changes Lots of refactoring:

Storage plugin model Network plugin model API implementation refactored (remains compatible)

New Features in 4.1API, UI and Integration Options: AWS style regions Event pub-sub framework (RabbitMQ implementation) Advanced search within the UI API Server request throttling API Discoverer Service Users resetting their own passwords Users directly changing their API keys EC2 query API Cloudmonkey CLI

New Features in 4.1Networking: Nicira integration adds L3 functionality Persistent networks without a running VM Autoscale (Netscaler implementation) Juniper SRX & F5 Big IP inline mode Egress FW rules for guest networks Open vSwitch support for KVM

New Features in 4.1Compute: Support for passing custom VMX settings to vSphere on VM

create Adding and removing Virtual NICs from VMs Reset SSH key within a VM

Storage: Volume resizing S3-backed secondary storage

Schedule

The Plan2012-11-01 through 2013-01-31 – Feature Merge Window

2013-01-31

Feature Freeze

All new feature need to have been merged into master by this date.

Release branch will be cut on this date.

Jenkins updated to include new release branch builds.

2013-02-01 through 2013-02-28

Testing/Bug Fixes (testing against jenkins artifacts)

Documentation Finalization

2013-02-28

Docs Completion Target

Release Branch moves to limited updates only (only commits allowed in would be release blockers fixes, translation updates, etc...)

2013-03-01 through 2013-03-22

Translation Development and Integration (should be ongoing, but focused effort)

Final regression testing / bug fixes / doc fixes

2013-03-22

4.1.0-RC1 is created, and project level VOTE is called

What Happened? Large number of last minute feature merges:

“There are just too many merged happened to master in the last minute, it includes VM snapshot, event framework, region,

Big Switch.”

Final Release Date: June 5 (plan was ~end of May)

Large Changes at the end is bad.

We can’t skip upgrade testing

(Like it or not, we have to deal with users still using 2.x)

Documentation remains last minute

Package name changes killed us

Features developed in isolation are a problem!

(likely review issues, IP clearance problems, etc…)

We had to disable Baremetal provisioning

Thanks!