<div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><p>Hi Everyone, </p><p>Thierry asked each PTL to send out a note about project goals in the Grizzly release cycle. I wanted to talk not just about new features being added to the Quantum codebase, but also what I see as helpful directions for the Quantum team as a whole. Since most people just want to read about the features, I put that at the bottom to make you read the team stuff first :) </p>
<p>I'm happy to hear other people's inputs on the topic of project goals as well. Thanks,</p><p>Dan</p><p></p><p>== Quantum Team Direction == </p><p>Broaden Team Leadership: </p><p>As the project grows both in terms of contributors and codebase, we need a more distributed model of team leadership. As discussed at the summit, we'll be experimenting with introducing sub-teams for different aspects of Quantum, with sub-team leads that are charged with helping to drive features, monitor bugs, and ensure consistency within their area of expertise. <br>
</p><p>Rise of the Users: </p><p>Quantum has so far been a project primarily driven by vendors, but with the transition to core project status, we are seeing more Quantum users get involved in the development of the project, and even taking leadership roles. This is a great trend that we want to build on even more in Grizzly, as it helps keep the focus on "enabling use cases for cloud tenants" rather than on "expose vendor capability X". </p>
<p>Focus on Enabling Real-world Deployments: </p><p>Now that Quantum is core, its important that we focus not only on adding new capabilities, but also on recognizing the practical issues (bug fixes, stable releases, documentation, answering deployment questions, improving usability, upgrade, etc.) that help people be successful using Quantum. As a team, we need to make sure that people who focus on these things are respected and rewarded and that we don't always rush to implement the "next big thing". </p>
<p>Growing the Core Developer Team: </p><p>Fundamental to Quantum's success is a core team who spend significant cycles working on community projects and reviewing code contributed by others. Making sure these developers, and their employers, see value in being a core dev and helping this team grow over time without sacrificing developer quality is central to the long-term success of the project. <br>
</p><p>== New Quantum Capabilities ==</p><p>Improved System Test / Gating: </p><p>Our unit tests provide good coverage, but getting this in place is key to handling a growing feature-set and handling interactions across projects. We will work closely with the CI and Tempest teams on this. </p>
<p>Close Feature Gaps compared to Nova network: </p><p>We want to make sure that Quantum can be used in all major use cases supported by nova-network. One key gap here is enabling a deployment model that has similar properties to the nova-network "multi-host" flag, in which DHCP + NAT services run locally on each compute node. Additionally, we want to update features like security groups (see below) and metadata server to support overlapping IPs, which is a key benefit of Quantum. </p>
<p>Improved Security Groups: </p><p>We will deliver security groups as part of the Quantum API, with several benefits over standard nova security groups, including: ability to apply security groups per VM interface (not just per instance), ability to filter both inbound and outbound traffic, ability to filter v4 and v6 traffic, ability to change group membership after VM boot, etc. This not only meets, but exceeds the capabilities of Amazon's newer version of security groups (called VPC security groups). Similar to floating-ips, we will provide a proxy so that nova security group commands can be passed on to Quantum. </p>
<p>Load-Balancing and other advanced network services: </p><p>With Folsom Quantum delivered a base L2/L3 feature-set, so attention is now turning to more advanced network services. We are building a generic framework to enable multiple plugins, each of which offers a service built on top of the core L2/L3 Quantum service. The first higher-layer service we are focusing on is load-balancing, which will support an open source LB solution (e.g., HAproxy) as well as vendor technologies. Once the network services framework has been proven out with load-balancing, we will explore additional services such as VPNs and advanced firewalls. Adding richer advanced network services will be an ongoing effort that extend beyond the Grizzly release. <br>
</p><p>Adding Support for New Backend Technologies: </p><p>New vendors continue to express significant interest in integrating with Quantum. We expect new plugin proposals to add Quantum support for technologies like Brocade, Floodlight, Hyper-V virtual networking and more. We also expect several vendors to contribute drivers for different load balancing backends, including Citrix, F5, Radware, Riverbed. Managing the contributions for these new parties will be a major challenge for the core team. <br>
</p><p>Improve Horizon Integration: </p><p>Folsom saw the initial integration of basic Quantum features into Horizon, but in Grizzly we will add more advanced capabilities, including the management of L3 routers, security groups, floating IPs, and load-balancing. <br>
</p></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">The full list of Grizzly blueprints for Quantum is here: <a href="https://blueprints.launchpad.net/quantum/grizzly" target="_blank" style="color:rgb(17,85,204)">https://blueprints.launchpad.net/quantum/grizzly</a></div>
<div><br></div>-- <br>~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>Dan Wendlandt <div>Nicira, Inc: <a href="http://www.nicira.com" target="_blank">www.nicira.com</a><br><div>twitter: danwendlandt<br>~~~~~~~~~~~~~~~~~~~~~~~~~~~<br></div>
</div><br>