The document summarizes release notes for version 4.1 of a software. It lists numerous architectural changes, 20 new features, 24 improvements, and 155 bug fixes. Key new features include an event pub-sub framework, advanced search, API throttling, password/API key management by users, and integrations with AWS, RabbitMQ, Nicira, Netscaler, Juniper SRX, F5 Big IP, and Open vSwitch. The release schedule planned feature development from November 2012 to January 2013, testing from February to March 2013, and release on June 5th, later than the original May target date, due to numerous last minute feature additions. Lessons learned include avoiding large last minute changes and developing features in isolation

1. 4.1 Release Review

2. I have two questions for you today.

3. 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

4. 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)

5. New Features in 4.1
API, 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

6. New Features in 4.1
Networking:
 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

7. New Features in 4.1
Compute:
 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

8. Schedule

9. The Plan
2012-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

10. 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)

11. Large Changes at the end is bad.

12. We can’t skip upgrade testing
(Like it or not, we have to deal with users still
using 2.x)

13. Documentation remains last
minute

14. Package name changes killed us

15. Features developed in isolation are
a problem!
(likely review issues, IP clearance problems, etc…)

16. We had to disable Baremetal
provisioning

17. Thanks!