The OpenStack Blog

Category: Development

Call for Proposals Open Source @ OpenStack Summit

UPDATE: Friday, April 18 is the deadline for submissions. 

At this year’s OpenStack Summit we’re going to be offering space to Open Source projects that are important to the OpenStack community. We’re calling it Open Source @ OpenStack, and it’s an opportunity for these projects to hold small design summits with their community members. We’re impressed by the number of projects that have grown in the OpenStack ecosystem, and want to continue the practice we started with StackForge of fostering these projects.

We have space and time available for half day sessions on Tuesday and Wednesday, both morning and afternoon. The purpose of the space is to get developers in the same room so they can plan their development for the Juno release cycle. Rather than being a time to market a particular company or technology, it should be an opportunity communication and goal setting. To achieve these goals, we would like participating projects to use the following guidelines:

  • The project needs to be directly related to OpenStack in some way.
  • The project must be open source, with source code available and actively developed.
  • The work needs to be non-commercial and vendor neutral, although a vendor that sponsors a project can organize the meeting.
  • Sessions must be open to anyone who wants to attend. This should be not just an opportunity for core developers to meet, but to also give a venue for people interested in your project to get more information.
  • Meeting notes from the design session should be made publicly available.
  • The group organizers and participants must adhere to the OpenStack Summit Code of Conduct.

If you have a project that you think qualifies for this space, we invite you to submit a proposal for Open Source @ OpenStack. Update: Friday, April 18 is the deadline for submissions. 

Please include:

  • The name of your project.
  • A description of the project and how it relates to OpenStack.
  • The names and contact information for the organizers commiting to hosting the session.
  • Relevant links to project sites such as repositories, bug trackers, and documentation.
  • An estimate of the number of developers you expect to attend your design meeting.
  • A plan for how you intend to use the time and space.

We want to thank everyone for the time and effort they put into supporting OpenStack.

OpenStack Upstream Training in Atlanta

The OpenStack Foundation is delivering a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project.  If you’re a new OpenStack contributor or plan on becoming one soon, you should sign up for the next OpenStack Upstream Training in Atlanta, May 10-11. Participation is strongly advised also for first time participants to OpenStack Design Summit.

With over 1000 developers from 80 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in social norms and technical conventions. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.

OpenStack Foundation partnered with Upstream University to train new OpenStack developers and documentation writers to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project’s technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have. Get all the details on the wiki.

Enrolment for the training session in Atlanta is now open: register and reserve your free seat for OpenStack Upstream Training in Atlanta, May 10-11.

Eventbrite - OpenStack Upstream Training

OpenStack at the Chicago Mercantile Exchange Group: Chicago-land Meetup

The Chicago Mercantile Exchange (CME) Group hosted the Chicagoland OpenStack Meetup last night, February 20, 2014.  The night kicked off with some quick introductions from OpenStack Meetup Organizer Erik Martensen and CME Host and Senior Director Vinod Kutty. Then the crowd settled in to listen to OpenStack Cinder Core Developer Mike Perez discuss what’s new with the block storage project. It was a lively discussion with thirty plus minutes of enthusiastic Q&A. Most of the audience had a general to advanced concept of Cinder and some even gave Mike an idea or two about what users want in future releases. A very special thank you to Mike for coming out from Los Angeles to address the growing OpenStack interest in the Chicago community. And, thank you as well to the CME and Vinod for the wonderful meeting space.

Outside of the CME GroupCrowd ShotMike & Vinod quiz the audienceMike that might be in the next releaseMike Talking - Interesting

OpenStack Project Update Webinars

Each OpenStack Summit we’ve hosted a Project Update track, where the Project Technical Leads (PTLs) share the state of the project and what’s on the roadmap for the next release. Rather than host the Project Update track during the Hong Kong Summit, we are breaking the sessions out into post-Summit webinars, to allow for broader community participation and give the PTLs a chance to regroup from their Design Summit sessions before presenting.

Join us for the remaining OpenStack projects the week of January 6th and maybe a few additional sessions. The current schedule is below along with registration links that will provide meeting instructions. If you are unable to make the scheduled webinars, please note they will be recorded and available to view after the scheduled date below. Thanks.

Completed Sessions

Thursday, January 16, 2013

9 a.m. Pacific/12 Noon Eastern
Project team leads: Sergey Lukjanov, Data Processing (Savanna) and Michael Basnight, Database Service (Trove)
Data Processing Slides: http://slidesha.re/1duJaxP
Database Service Slides:
Recording: http://bit.ly/1g61ulH

Tuesday, December 17, 2013

7 a.m. Pacific/10 a.m. Eastern
Project team leads: Mark McClain, Networking (Neutron) and Dolph Mathews, Identity (Keystone)
Networking slides: http://bit.ly/JLiu39
Identity slides: http://bit.ly/1bVlcwQ

Thursday, December 19, 2013
7 a.m. Pacific/10 a.m. Eastern
Project team leads: Russell Bryant, Compute (Nova) and John Dickinson, Object Storage (Swift)
Compute slides: http://bit.ly/JPQ8FE
Object Storage slides: http://bit.ly/1l1CNoP
Recording: http://bit.ly/1c7IOiH

Tuesday, January 7, 2013
7 a.m. Pacific/10 a.m. Eastern
Project team leads: Mark Washenberger, Image Service (Glance); Julien Danjou, Telemetry (Ceilometer); John Griffith, Block Storage (Cinder)
Image Service slides: http://bit.ly/1enOuG3
Ceilometer slides: http://bit.ly/KQhDzu
Block Storage slides: http://bit.ly/1ewskiN
Recording: http://bit.ly/1iYl8BF

Thursday, January 9, 2013
Noon Pacific/3 p.m. Eastern
Project team leads: Steve Baker, Orchestration (Heat) and David Lyle, Dashboard (Horizon)
Orchestration slides: http://bit.ly/1gYXj9U
Dashboard slides: http://bit.ly/1dkFi6R
Recording: http://bit.ly/1cVbYO2

Reviewing how Blueprints are handled

OpenStack Compute Tech Lead Russell Bryant has triggered an important discussion on the OpenStack Development mailing list about the process to review blueprints. The Blueprints wiki page currently assigns to Project Tech Leads the task of assigning priority to the blueprints and Russell is suggesting that a wider group of people in the community shares such responsibility..

Blueprints are used by project leaders to track development of significant features in all OpenStack programs: a blueprint is made of a title and a brief description, plus a URL to a wider description of architecture and specifications (usually a wiki or etherpad page).  Given the growing size of OpenStack code base, scaling development operations is increasingly hard and one person cannot handle reviewing all the proposed blueprints and set priorities in a way that guarantees finalization.

This brings us to the second issue that needs to be addressed: managing expectations of new contributors. With so many blueprints being proposed it’s hard for a PTL to be accountable for developers to deliver the code based on blueprint’s priorities. Since the PTL used to set the priority for the blueprint, it is hard to held him/her accountable when the code is not delivered accordingly. There is clearly a separation of powers between the person evaluating the blueprints, the developers that will implement them and the reviewers that will review the code submitted.

Russell’s proposal is to assign the responsibility to review the blueprints to the same team of people that will be responsible for reviewing and approving the code during the implementation phase, the core reviewers. The role of the PTL will still be to set the deadlines for the blueprints and to make sure that the roadmap for the program is sound. The core reviewers will then be sharing with the PTL the responsibility and accountability for the deliverables at each release milestone

In the discussion that’s following on the mailing list there are also proposals to include user input while setting the priorities for blueprints. There are risks also associated with this setup. So far, the process has been discussed only taking into account the needs of OpenStack Compute. The project is the largest OpenStack project by number of blueprints, making it the first to need reviewing the existing process. However, the expectation is that several other OpenStack projects may evolve to this point in the future and this is an important test for that time. As such, we welcome holistic feedback: join the discussion on the development mailing list and in Hong Kong.

The Growing Diversity inside OpenStack Object Storage

Of all OpenStack projects, Object Storage (also known as Swift) has always been considered mature or, in other words, a place where new things rarely happen. I’ve always been looking at the Object Storage project closely and I’m happy to report a lot of exciting things are happening in Swift, specifically around the community participation and growing ecosystem.

The total number of contributors to OpenStack Object Storage reached 136 with as many as 16 different people committing code in a single week of July 2013. Of those, 64 have participated in the Havana cycle, 30 of whom are new contributors to Swift. The charts show a very good upward trending curve for the total authors per week, different people filing new bugs (the Closers/Openers chart) and variety of people filing, triaging, setting priority and fixing bugs (the Changers chart). The top contributors (by patch count) are from 6 different companies: SwiftStack, Red Hat, Rackspace, United Stack, IBM, and eNovance.

Features are also growing: in Havana we’ll get global clusters. This allows deployers to build a single Swift storage system that spans a wide geographic area. For example, a deployer can build a Swift storage cluster that keeps different replicas in different regions for either DR or for low-latency regional access. SwiftStack, SoftLayer, and Mirantis all contributed into the global clusters feature. More details on what’s coming are on the CHANGELOG. Get to the Summit in Hong Kong to hear how Concur set up their global Swift cluster.

More new and cool features are also coming: SwiftStack, Box, and Intel are working on an erasure coding storage policy. Rackspace is working on improving replication. Red Hat is working on making Swift’s interface to storage volumes more dynamic. Work has started on this functionality and will be a major topic of discussion in Hong Kong.

Because of this broad base of contributors, the major feature development addressing real-world use cases, and the proven performance at scale, OpenStack Object Storage is being widely deployed and is powering some of the world’s largest storage clouds. I’m tremendously excited about Swift’s progress and its future trajectory.

OpenStack Launches Training Marketplace

Screen Shot 2013-09-16 at 10.37.09 AM

Today the OpenStack Foundation has launched a new Training Marketplace, making it easier to discover and participate in training courses offered by technology providers in the OpenStack ecosystem. Aptira, hastexo, The Linux Foundation, Mirantis, Morphlabs, Piston, Rackspace, Red Hat, SUSE and SwiftStack are the first companies to have courses available in the Marketplace, with the goal of growing the OpenStack talent pool and accelerating the availability of OpenStack training courses worldwide.

To find an OpenStack training course from the ecosystem of providers, visit http://www.openstack.org/marketplace/training.
OpenStack expertise continues to pay off, with OpenStack jobs consistently paying higher wages and employers doubling the number of job postings over the past year.  The ecosystem has quickly responded to help developers and operators gain these valuable skills, with dozens of courses across 10 countries and 25 cities included in the Marketplace at launch. Future demand for OpenStack skills is only expected to grow, with the BSA Global Cloud Scorecard predicting that 14 million cloud jobs will be created by 2015.

OpenStack Jobs Pay

OpenStack Jobs Pay

“The goal of the Foundation is to eliminate barriers to OpenStack adoption, create more OpenStack experts and ensure that OpenStack has a positive impact on the careers of our community members,” said Jonathan Bryce, executive director of the OpenStack Foundation. “We want to grow the community, accelerate the availability of training programs worldwide and help close the OpenStack job gap.”

In order to offer courses in the Training Marketplace, companies must meet requirements set by the Foundation, with the primary purpose of the course being to contribute to, operate or build applications for an OpenStack cloud. The training curriculum should provide a strong understanding of the OpenStack core projects based on a current version of the software, as well as cover community governance and contribution processes.

In addition to paid and free training courses by companies in the OpenStack ecosystem, there are many community efforts to produce helpful documentation, how-to information and new Operations and Security guide books. There are also many educational sessions and hands-on workshops scheduled for the next OpenStack Summit, November 5-8, in Hong Kong. Workshops from previous Summits are available to view online.

Does your company offer training for OpenStack?  Contact us with details: Ecosystem@openstack.org.

Infrastructure Bootcamp

Recently the Project Infrastructure team hosted a two-day “bootcamp”
for people who are interested in contributing to the Project
Infrastructure.  The OpenStack project is so large, and continuing to
grow, that creating and operating the developer infrastructure for the
project itself is a unique challenge.  Because OpenStack receives code
contributions from more than 600 developers in a release cycle, and
merges as many as 200 changes per day, we are at the cutting edge of
distributed development and testing.

The project infrastructure covers a wide range of tools and services
used by the project, including code review, testing, and
collaboration.  The design and operation of these systems is managed
under the Infrastructure Program which is overseen by the TC just like
the rest of the OpenStack project.  And like any other OpenStack
program, our team is open and we welcome contributions from anyone.

Managing the infrastructure for a project of this scale is a lot of
work, but it is uniquely rewarding because it affects every OpenStack
project and affords interactions with all of the developers.  We heard
a lot of interest from persons and companies who wanted to contribute,
so we held the bootcamp to get anyone who was interested in
contributing together in a room with the current core team of
infrastructure developers.

OpenStack Infrastructure Bootcamp kicks off

OpenStack Infrastructure Bootcamp kicks off
Photo: Elizabeth Krumbach, CC-BY 2.0

Day one saw us all together and discussing how contributions are
accepted, how the team operates, and how new members can expect to
become core members in the future.  We discussed each major system at
a high level, and worked out how all of the systems interact with each
other.

In the evening, we all got together for dinner and spent several
enjoyable hours talking about how we could improve the system, and
generally getting to know each other.

On day two, we dove deeper into some topics of particular interest to
attendees, and generally had a less structured approach where people
who shared interest in an area got together and discussed it in depth.

I think everyone who attended got a lot out of the event, and we’re
already seeing significant new contributions as a result.  I hope that
in several months more time we will have new core members on our
team.  I also think this is a good model for other programs in
OpenStack who want to quickly bring new contributors up to speed.

I’d like to thank Monty Taylor for organizing the event, the rest of
the core contributors (or “coremudgeons”) for talking about what we do
for two days straight, and Hewlett-Packard and the OpenStack
Foundation for sponsoring the event.

Some reactions from others who attended:
http://dague.net/2013/06/29/openstack-infrastructure-bootcamp/
http://princessleia.com/journal/?p=8229

Lessons, Learning, and Long Views for Internship Programs

In January 2013 the OpenStack project welcomed aboard three interns and excitedly assigned them to work on fairly complex projects in our first attempt at an organized project-level internship program. The OpenStack Foundation participated as one of the organizations with the GNOME Outreach Program for Women and learned quite a few lessons during the six months internship period.

By February, two of the interns had learned the tough lesson of what happens when coordinated work efforts move at a fast pace. For example, Laura Alves, an API documentation intern had a patch with a manually created WADL for the Networking project nearly completed. She started requesting reviews from the core developers. We soon discovered that the devs were working on an automated method for creating the WADL. It certainly took some quick communication and coordination to make sure her work wasn’t wasted. Her efforts certainly weren’t wasted but it also hasn’t landed quite yet either. Lesson learned: internship projects are difficult to scope and it’s nearly impossible to set aside tasks in a reserve area just for interns.

Still more lessons learned were that the timing of code freeze dates landing prior to the internship’s completion made for a steep on ramp for new interns with early deadlines. We also found that interns can contribute so much right away with their fresh perspective — and they created such valuable blog entries for newcomers, like Logging and debugging in OpenStack by Victoria Martínez de la Cruz,  so they’ll be helping more newcomers for months.  We pulled all our lessons learned together for a “What Everyone Should Know About OpenStack Internships” panel session at the Summit in Portland.

One of the takeaways from the Summit was to learn more about mentoring from Katy Dickinson, and the blog at MentorCloud where she is Vice President has been very valuable to learn from as we continue to shape our plans for interns wanting to learn and contribute to OpenStack. Katy attended our brainstorming session at the Summit and gave us very useful suggestions. We surveyed outgoing interns and are working on a plan to coordinate early and often to identify and promote natural mentors in the OpenStack community.

The more you look for internships and mentors in OpenStack, the more you’ll find. Cisco has interns working on OpenStack projects each summer. One OpenStack intern, Emilien Macchi, at StackOps went on to do a graduate part-time internship at eNovance. Rackspace has interns working on multiple OpenStack projects.

The Foundation is continuing the involvement in the Outreach Program for Women also in the northern hemisphere’s summer edition: Terri Yu started working on the Ceilometer project with Juilan Danjou at the end of May: be sure to welcome her! Look for more opportunities to connect the dots with interns and mentors in the coming months. If you have funds for travel so interns and mentors can meet each other in person, let Stefano Maffuli know. If you have a great intern story to tell, please let us all know.

New Foundation Gold Members & Corporate Sponsors

The OpenStack Foundation was thrilled to add two new Gold Members and 13 corporate sponsors so far this year to the already impressive list of companies who are supporting the Foundation and driving innovation on the platform.    Ericsson and Juniper Networks won the OpenStack Board’s approval at the April board meeting and joined the Foundation as Gold members.  To learn more about these companies and their OpenStack initiatives please visit www.ericsson.com and www.juniper.net

We’ve also seen amazing support in Corporate Sponsorship and we want to share the impressive list of recent additions.

The diversity in technologies and geographic location of these new additions to the ecosystem reflects the growth of OpenStack and its footprint worldwide.  We are looking forward to enjoying each these companies’ unique contributions going forward!

Back to top