OpenStack Summit May 2015 Vancouver

Whether you are a newbie to OpenStack looking at building your first cloud or an experienced operator with years of OpenStack success behind you, you've probably spent some time wondering what to expect from the OpenStack project over the next several releases.  Will it finally support that new capability you've been waiting for?  Should you plan for an upgrade in the next 6 months?

While the development community is always working and planning new features, its takes a lot of time on IRC to get a complete view across the different projects.  The OpenStack Product WG spent time this cycle working with the project teams and PTLs to understand their priorities for the next several OpenStack releases.  Where we have always had an understanding of what's to come in the next release, we're hoping to present a long-term view of the future landscape of OpenStack.  In this session, we'll present our findings across the different projects in an effort to give users a glimpse into the OpenStack roadmap. 

April 9th, 2010. The blue glow of laptop screens illuminates seven developers as they hack out the first few lines of OpenStack Nova. Now, five years later, OpenStack has grown into a behemoth with a hundred times the number of developers. This session will discuss the challenges of rapidly growing OpenStack. It will include humorous stories of some of the biggest debates, insights valuable for future growth, and suggestions for other open source projects attempting to emulate OpenStack's success.

This Committee was formed during the OpenStack Ice House Summit in Hong Kong by Board Resolution on 11/4.

DefCore sets base requirements by defining 1) capabilities, 2) code and 3) must-pass tests for all OpenStack products. This definition uses community resources and involvement to drive interoperability by creating the minimum standards for products labeled "OpenStack."

Our mission is to define "OpenStack Core" as chartered by the by-laws and guided by Governance/CoreDefinition

• What has DefCore done so far?


• Who is involved with DefCore?


• What changes are planned around OpenStack branding in 2015?


• How will DefCore change OpenStack in general?

 

For the last six month we have been running the website OpenstackReactions that has becoming hugely popular within the OpenStack community.

 

The idea of the website is to get a so called ‘reaction’ about the day to day life of the OpenStack users and developers.

 

In this session we are going to just do that, showing you the day to day of an OpenStack developer and an OpenStack operator in animated gifs  which may speaks you better than complicated diagrams and busy slides.

 

For the developer we are going to get from the setup of his OpenStack environment before starting contributing, discussing new features to implement and reviews other people patches.

 

For the OpenStack operator we will get to the part of what it actually take to get that patch to be automated and tested before deployed in production.

 

We hope that this talk will be as much as an introduction to a newcomer to OpenStack and describe in a fun way the life of an existing OpenStack user and developer.

 

OpenStack was previously defined by one thing: “the integrated release”. This single term ended up meaning different things for everyone. It both became too large and too small an artifact to represent what the community does. It was too big for many people to deploy, and too small to fit the features that many people wanted. It was time for a change.


In this talk, we will look at what the proposed changes are, and where we currently stand in implementing them. We’ll explore what the changes mean for the development, testing, and releasing of OpenStack. We’ll explain why we think this will both give us a more solid base infrastructure layer, and allow the creation of numerous add ons that let consumers grow over time. And we’ll leave plenty of time for burning questions.

Join to our panel talk about community status report and meet with the OpenStack Ambassadors. They connect the user groups to the Foundation, and help initialize the groups and guide them to grow.

 

Review of some Ambassadors launched actions during the last release cycle:

- OpenStack community report

- What is the size of the community ?

- Global and regional trends

- Introduce new groups, leaders

- Official group process

     - Officials groups

     - Process

- Examples of User group help

- Groups portal

      - Overview

      - Results

- Welcome pack and OpenStack shop

- Q&A

 

We want to energize an OpenStack user group near you!

To do that, we will be using the community training project. It is happenning at the Tokyo and San Francisco user groups, Coming off the Paris summit, the community training guides project is focusing on the user groups as their main audience. While there are paid OpenStack training programs available, the OpenStack Training Guides project aims to teach the basics of OpenStack through the user groups.

In this talk, we will describe the Training Guides project objectives of OpenStack training cluster, training content mostly by HTML slides, example scenarios and use cases, and quizzes. We will walk through our successes to date delivering training thorugh the user groups.

Join your fellow Women of OpenStack on Tuesday morning before keynotes for a breakfast working session. We’ll hear lightning talks covering various topics including mentorship, leadership, imposter syndrome, etc and then we’ll break into smaller discussion groups to identify actions and goals for the Women of OpenStack to achieve over the next six months. Breakfast and coffee will be provided.

OpenStack is a very active community. Bursts of change happen quite often and it can be difficult to keep up if you are not immersed. We need manage the flow of critical information and decision making just like any other engineering organization. The people that represent the Product Management of OpenStack are a critical group within the community.

The Product Management working group has met a few times starting in Paris. This group has organized itself around three first activities. Gathering the current state of the OpenStack projects, Defining what the Roadmap could look like, and working with the Cross Project team. The User Stories from the Win the Enterprise working group will used alongside the project needs.

Join us to discuss what we have so far and let debate where we the OpenStack community should be going towards.

OpenStack is big and everybody wants to be a part of it. More and more vendor organisations want to ride the OpenStack wave and see getting talks on the summit schedule as a key way to strengthen their position as an OpenStack mover and shaker. The net result is 1500+ talk submissions which the current selection process cannot handle. There has to be a better way, join Mark Baker to discuss problems with the current process and how it might be improved.

In just two amazing years, the Women of Openstack Group grew from a breakfast in Portland to an active working part of the OpenStack Community.  Following an incredible IBM sponsored gathering at the beautiful ESPACE 56 in Paris the group held several productive working sessions on what to do next.  There was agreement all around that it is important to encourage and promote more contributions to the Openstack project from a broad and diverse base of people from around the globe.  This workshop is designed not only for women, but for any member of the OpenStack community who feels they need a bit of coaching in how to gain the confidence to contribute to our amazing and diverse community.  Join this panel of empowered women as we cover some of the tips and tricks for getting heard in an environment filled with many egos and opinions.  Learn how to navigate the differences between:

·          Empowerment, not pushiness

·          Confidence not brashness

·          Technical prowess not just nerdiness

·          Being heard when people are not listening

·          Contributions, not bluster

Large scale corporations are generally reserved and focused on developing proprietary enterprise softwares. Open source software is a fairly new concept that has gained popularity in the field of IT, specifically OpenStack. Here at Symantec, we discovered a need to become of part of OpenStack community. We would like to share various community building strategies we have been following, including :

 

• 
  Why should an Organization invest in Open Source?
  
  

• 
  Shift from Proprietary Software to Open Source Software
  
  




• 
  Our process and approach towards community building
  
  




• 
  How to conduct effective and efficient Meetups and Hackathons
  
  




• 
  Symantec's journey to OpenStack Gold Membership in the short span of a year
  
  

Have you ever wondered how to get a big new feature completed in an open-source project? Getting people in the same company to work together can be a daunting task. Getting people to work together for a common goal when their employers actually compete with one another is quite a bit harder. Despite the challenges, the OpenStack Swift community came together to create the biggest new feature the project has ever seen.

 

Between June of 2013 and June of 2014, the OpenStack Swift community designed, built, and delivered storage policies, a major new feature that enables a ton of new use cases for users. This talk will briefly cover the feature implemented, but we'll mostly talk about how contributors from different companies came together and the lessons learned from that experience.

 

 

If you contribute an open source project, you'll want to hear what we did right, what we did wrong, tools we invented, tools we threw out, and how you can take these lessons we learned to your own project. We'll cover development work, review work, how we did communication, how we tracked tasks, and what we learned through it all.

While the value of co-location for team effectiveness cannot be denied, the nature of the OpenStack community is one of remote work and distributed interactions. Whether you're attending a meeting on IRC, discussing an issue asynchronously via email, or trying to figure out what time it is on the other side of the world, virtual collaboration is a requirement for effective participation in OpenStack. 

 

In this talk, Rainya Mosher will draw from 15 years of personal experience (including 3 years in OpenStack), as well as the latest research on distributed collaboration, to provide practical strategies, best practices, and tools you can use to make your interactions more effective. Regardless of if you are a developer new to OpenStack, an operator running an OpenStack deployment, or a product manager trying to ship a feature, this talk will help make your interactions more productive and effective.

 


Talk Outline

• HD Team Profiles 


• Communication Styles


• Cultural Lenses


• Tools and Best Practices


• Putting it All Together

Talk Takeaways 

• Heightened awareness of the key challenges of distributed collaboration and how to effectively address them


• Insight into the research and theory being done in this field and trends for the next 3 to 5 years of HD work


• Practical guidance on how best to interact with the OpenStack community regardless of your role or your company affliation

 

In its almost five years of existance, OpenStack has grown at an incredible rate into one of the largest open-source projects on the planet. As with any software project - open-source or not - what's ultimately important is the software we produce but yet we must invest much effort into perfecting how we produce it. For a project to scale from dozens of contributors to thousands of contributors, that's especially true.

One aspect of any project's makeup that is fundamental to its identity is its governance model. This talk will describe OpenStack's governance model in the context of other open-source governance models, with particular attention paid to how the project maintains a balance between the commercial interests sponsoring the vast majority of the work done on the project, and the open, transparent and welcoming 'doacracy' which creates the ideal environment for technical collaboration.

This past year has seen a number of fascinating debates within OpenStack - around commercial trademark usage policies, our contributor license agreements, voting methods, cross-project governence, the increase in scope of project, and much more. How these debates were conducted and resolved illustrates the nuances of our governance, so Mark will share his perspective on these debates from his vantage point as a contributor, former technical committee member and director of the foundation.

You've been tasked to host a meetup or organize a community event. What's the first panicked thought that comes to mind? Is it venue, cost, attendees, transportation, entertainment, wifi, food, drinks!? Now imagine you are to host an OpenStack event for the entire Summit audience--in Paris or Tokyo. How do I deal with foreign language and culture? What do I need to know about currency conversion, and cuisine? This is a big deal, and the pressure is on!

In this panel, led by Jeanne Colon-Bonet, Events Extraordinaire and Program Manager of Messaging and Outreach at HP, learn how to:
 

• Select a venue and vendors

• Balance a budget (even if it’s zero)

• Exceed attendee expectations

• Gain knowledge of community event culture

• Best practices of initiation, planning, execution, and closure for a superb event

 
Open source culture encourages us to get up close and personal. In the OpenStack community, you can be a leader by gaining valuable knowledge that gives you an identity. Geared for the seasoned event coordinator or those fresh to event organization, this session will help you discover how a collaborative strategy can ensure unique attendee experiences and make your event memorable. 

We'd like to invite you to participate in defining the future of the Community Apps Catalog. Come to this open working session and contribute your ideas to make this project a game changer for the community.

As OpenStack grows incredibly quickly in popularity there is an increasing and consistent need to have a means to bridge the gap between app developers, operators, and the code itself. In a mainstream business this function is filled by Product Management, whose role it is to understand the needs of customers, work with engineering to build the right product, and then communicate product information back out to product marketers and/or customers using terms they understand.

The issue OpenStack faces today is that virtually any level of exposure to either the technology or the community almost immediately entails deciphering of unfamiliar terms and concepts. This means that product managers must also serve as educators and create products that and value that customers are willing to pay for, while bridging the gap between the community, engineers, customers, and users.

In this panel, join OpenStack veterans as they share perspectives on OpenStack Product Management. They'll discuss:

Strategies for turning trunk into productized solutions and offers 
Pros and Cons of keeping product releases close to trunk 
Creating an effective feedback loop between app developers, operators, contributors, and users 
Monetization strategies in the open source era 
What IT organizations need to know and understand to get the most out of OpenStack 
This is must-attend session for product managers and consumers of OpenStack products. Contributors and users responsible for the creation and success of OpenStack-focused products should also find benefit.