OpenStack Mitaka Design Summit

OpenStack is a global community, OpenStack is deployed in many countries. As such, Internationalization (i18n) is essential to the success of OpenStack. The i18n team is a very special team whose contributions, in the form of translations, are of great value to the development and documentation of OpenStack.

In this session we will cover the team structure, how to become part of it, the process to translate OpenStack's different modules and documentation, and the translation tool used to do it (Zanata). The Japanese translation team coordinator will also share his experiences in openstack translation.

Come and join us to learn how to help OpenStack speak your language!

Have you ever had a really interesting idea that you believe could benefit a significant number of OpenStack clouds but you are not a developer so can't contribute code?  Join us in this session to learn about the various ways non-developers can (and need to!) contribute to the OpenStack community. This session not only applies to operators but to any person that has a stake in the future of OpenStack. 

We will cover review and discuss groups that exist inside the OpenStack community that focus on specific market segments and how to get involved with them. We will also introduce the concept of user stories and how to submit them to the newly formed Product Working Group. 

What you will get out of this session:

• An overview of the User Committee and [Working Groups]/teams that exist today


• An understanding of the role that the Product WG plays, how to interact with it, and how its results are used in the community


• Learn how you can submit user stories using the Product WG Repo and Template


• Instructions/demo on how to submit a user story


• Understand the value of work group participation as an OpenStack user

Exciting. Overwhelming. Engaging. Exhausting. How will you transform your first OpenStack Summit into an accelerator for your career and your projects in development? And how will you make it happen without getting lost among thousands of other community members?

This fun and engaging panel presentation, moderated by OpenStack Foundation newbie Heidi Joy Tretheway, features regular contributors to the OpenStack community who have found great ways to maximize the value of the Summit for their professional development and the success of their companies.

We kick off with advice from those who have been to Vancouver, Paris, and other OpenStack Summits, including:

• How to make the most of networking opportunities and social events


• How to use the marketplace trade show to form new business connections and uncover opportunities


• What to look for on the agenda and how to select the best sessions for you


• "Relationship accelerators" - five easy questions you can ask to get conversations rolling past "What's your name?" and "Where are you from?"

We'll open the panel to your questions. Expect some lively and unconventional answers, and a few great icebreakers that will help you better connect with your newbie colleagues.

You'll leave this session Proud to be a Noob, and ready to tackle the rest of the Summit.

In this talk I will share my experience doing upstream OpenStack development using the OpenStack Ansible Deployment (OSAD) distribution instead of DevStack as my development platform.

OSAD is a production OpenStack distribution for private clouds that deploys upstream OpenStack direct from the official git repositories, without any vendor-specific patches or add-ons. But unlike DevStack, services are isolated from each other in LXC containers, providing more flexibility and less dependency headaches.

In this talk I will give you an introduction to the OSAD project and show you how I use it to contribute code upstream. Topics I will cover during the presentation include: 

• What is OSAD?


• Architecture overview


• How to deploy an OSAD all-in-one for upstream development


• OSAD vs. DevStack: How are they similar, and how are they different?


• Development workflow


• Types of upstream work that work well with OSAD.


• Types of upstream work that do not work well with OSAD.


• Live Demonstration

In Vancouver the OpenStack Board chartered a work group to explore and foster a diverse OpenStack Community. The basis for this is the belief that enlisting the broadest set of viewpoints and experience will enable us to create the most innovative and impactful technologies in support of the OpenStack Mission.

A broad set of community members formed the Diversity Work Group that has worked over the Liberty cycle to form a framework for a diverse community through the creation of a Diversity Policy, integrated Diversity expectations into our Code of Conducts and identified initial areas of focus for extending the diversity of our community. Please come join us to discuss the team’s work and shape the future direction.

The “As a…” clause of the classic user story is easily forgotten. To build a feature, we must know what it is and why someone would want it, but as developers we often abstract away the user. Building “the simplest thing that can possibly work” is usually a critical design tool, but without active attention to customer roles and workflows, it can lead to APIs that leak the implementation details of underlying technology or prioritize machine logic over human understanding.

We will use the Unified Job Interface Map feature in the OpenStack Data processing service (sahara)’s Liberty release as a case study in role-aware API design. In addition to demonstrating how this feature can improve communication between data processing developers and cluster operations engineers in your organization, we will examine:

1. Why APIs in the OSS infrastructure and tools space are bound to leak implementation details at some level.


2. Why the ideal of an API flow that is intuitive to any user from any entry point is likely a fool’s errand.


3. Why multi-role customer flows mean that the “simplest thing that can possibly work” usually doesn't at handoff points between users.


4. How domain-specific awareness of user roles allows smart choices about where to go ahead and leak implementation details and where to build a dam.


5. How features to facilitate inter-role communication can quite often be built iteratively, on top of existing APIs.

Data processing users will leave this session with details on a powerful model for easing communication between development and operations in Sahara. OpenStack contributors will leave this session with a refreshed perspective on the importance of understanding not only the use case, or even “the user”, but the many roles within an OpenStack customer organization.

Starting in the Kilo cycle OpenStack underwent a change in governance model where the scope of what we call OpenStack has been redefined. The new model is called the "Big Tent", and is much less exclusionary. Prior to this the QA program had a policy of directly supporting any project that was part of OpenStack, meaning tests in tempest, support in devstack for running them, etc. However in a model where there are far more projects considered part of OpenStack it becomes infeasible to directly support all of them. Even before the "Big Tent" was adopted, we realized that this centralized approach did not scale well with the growing number of OpenStack projects. With the "Big Tent" opening up the doors to more projects, the scale issue has become even more compelling. 

As a result of this change in governance model, we have worked on moving QA in OpenStack to a self-service model, where each new project in OpenStack is responsible for writing and maintaining their deployment scripts and tests, as plugins to the tools for deployment and testing frameworks maintained by the QA team.This will allow both the upstream QA efforts to scale organically with the rest of the OpenStack ecosystem but also allow new projects to control their own testing and deployment stories for gating, which can increase development velocity for newer projects.

This talk will cover the work which was done to add external plugin interfaces to Tempest, Devstack, and grenade as well as go into examples on how to use each project's respective interface. It will also show examples where these plugin interfaces are being leveraged today.

Our panel of APAC-based venture capitalists will discuss the growth of OpenStack across Asia, with a focus on startups developing technology within the OpenStack ecosystem. 

Our panelists will share their personal criteria for evaluating startups to fund, and provide insight to problems not yet addressed within OpenStack today, i.e. opportunities for the next wave of open-source software enthusiasts and entrepreneurs.

Drawing on real-world stories of success (and the occasional stumble), they will answer questions about how OpenStack is being used by industry to reduce cost and time-to-market, as well as about new business opportunities created by OpenStack.

Finally, our panelists will look at the new communities and ecosystems emerging around the OpenStack core.

In the early days of OpenStack—think Diablo and Essex—smart people had a great idea: let’s simplify OpenStack consumption by offering a choice in between the polar opposites of build it yourself (DIY) and a Rackspace account.

And thus, the OpenStack software distribution was born. Startups and legacy IT shops spent the next 4 years trying to convince a skeptical market that distros were the way to go, but it hasn’t worked out. With a couple of exceptions, distros are vanishing from the competitive landscape.

In this session, we’ll look at what happened. We’ll examine the reasons why very few enterprises want to learn or operate OpenStack, but remain hungry to *consume* it. We’ll ask why most enterprise buyers want OpenStack without having to touch OpenStack. We’ll look at the mindset of enterprises that “get” agile and realize their success rests solely on differentiation through application innovation, not through an investment in infrastructure and operations. Finally, we’ll look at some of the places where innovation is happening in the OpenStack ecosystem and how new business models are emerging.

Attend this session if you agree, disagree or simply want to have an honest conversation about what we can learn from the demise of one of the early favorites in OpenStack business models.

OpenStack is like an Orchestra, made up of many different instruments each playing different parts that come together to form an open source masterpiece.  The next wave of OpenStack companies are a set of specialists who are becoming masters at their own instrument.  In this panel, we will have one of the virtuosos of the first wave of OpenStack startups, Boris Renski, Co-founder and CMO of Mirantis, acting as conductor.  He will be directing an all-star ensemble of instrumentalists from companies specializing in projects that harmonize to form the OpenStack symphony.

The first wave of OpenStack startups were generalists delivering a complete OpenStack solutions.  Many of these have now been acquired by larger companies, for example Cisco's acquisition of Metacloud.  Other recent acquisitions include Blue Box, Piston Cloud, and Cloudscaling.  Now there are a number of companies emerging that are focused on specific OpenStack projects. 

In this session, Boris will lead a panel discussion with CxOs of a group of companies from this next wave of OpenStack specialists. The panel will consist of Ken Rugg, CEO of Tesora, Joe Arnold, CPO of SwiftStack, Evan Powell, CEO of StackStorm, Pere Monclus, CTO of PLUMgrid, and John Griffith, Software Engineer at SolidFire and former PTL of Cinder.  They will discuss evolving roles of specialists and generalists in the OpenStack community, how companies should define themselves in a rapidly changing landscape, dissect interactions between specialists and generalists as the market matures, and explore predictions on the future of the OpenStack ecosystem.

Moderator: 

• Boris Renski, Co-founder and CMO at Mirantis

Panelists:

• Ken Rugg, Founder and CEO of Tesora (Trove)




• Joe Arnold, Founder and CPO of SwiftStack (Swift)




• Evan Powell, Co-founder and CEO of StackStorm (Mistral)




• Pere Monclus, Founder and CTO of PLUMgrid (Neutron)




• John Griffith, Software Engineer at SolidFire (Cinder)

The Openstack cookbook project(s) have been growing rapidly and becoming more mature and stable with every release.

These cookbooks provide a way to not only deploy, but also manage the OpenStack service configurations. 

This session will explore the current state of the OpenStack cookbook projects and allow you to better understand the following topics:
- What is Chef and why is it such a great match for OpenStack?
- What is the current state of the OpenStack Chef cookbook community?
- How to I get starting using the cookbooks?
- What are the strengths and weaknesses of the cookbooks?
- Tips and techniques for using the cookbooks

Size your OpenStack environment is not an easy task.

In this session we will cover how to size your controller nodes to host all your OpenStack services as well as Ceph nodes and Overcommit CPU and Memory based on real use cases and experiences.

VMs? Containers? Baremetal? How do I scale? We will cover diferent approaches to do the sizing and we will also talk about the most bottlenecks that you might find while deploying an OpenStack cloud.

Swift and Ceph are both very popular distributed and flexible storage systems providing object storage based on commodity hardware. However, they are very different. This presentation will provide a comprehensive comparison of Swift and Ceph. We will study some real-world object storage requirements and show some test results of both Swift and Ceph based on modeling of real-world scenarios. We will also discuss the pros and cons of building a object storage system with Swift and Ceph, not only the performance and features, but also the cost of constructing and operating such storage systems. We will take the "unified storage" feature of Ceph into account, which may save the cost if the user also want a distributed block storage system and file system.

China cloud market will keep 20% growth in the next 5 years. Public and private cloud total market size is 2.46 billion US$ at 2014. With Goverment support "Open Source" background, the OpenStack ecosystem in China is experiencing healthy growth. It is driving a new generation of innovative businesses that are using the cloud to bring their product and services to market at a rapid pace. Attend this session to get a good understanding of:

• The China cloud market and the opportunity for OpenStack


• OpenStack ecosystem in China – the players, business models, offerings and achievements


• Key milestones


• Community activities and status


• Upcoming China Hackathon


• Summary of a recent big end-user win

OpenStack Ambassadors connect the user groups to the Foundation. They help initialize the groups and guide them to grow. Ambassadors can give feedback about all the OpenStack community.

Ambassadors launch some actions during the last release cycle:

- OpenStack community report
    - What is the size of the community
    - Global and regional trends
    - Introduce new groups, leaders

- Speaker directory

- Recommended practices for starting and running communities

- Official group process
     - Officials groups
     - Process

- Examples of User group help since Vancouver

- Groups portal
      - Overview
      - Results

- Welcome pack and OpenStack shop

- Q&A

Meet with the ambassadors on this session where they will introduce the improvements of the last half year and share their feelings and experience about the community. If you are a user group organizer you must be there, and feel free to share your thoughts and feelings with us!

You are developer, and you have just been told to work with OpenStack. Welcome to the OpenStack community! You have also just been told you need to release your product next month, you have your all the codeyou’re your new feature complete, and a few bug fixes done. Now you just need to get that pushed upstream. Where do you go next?

You have been working for OpenStack for a while; some internal issues meant you had to stop reading the ML for a month or two. How do you get back in the loop?

You are working hard reviewing specs and code, and the work load is getting crazy, and everyone is saying their use case is the most important thing for OpenStack, and they are all really useful things to consider. What is the right thing to do?

Maybe we can use lessons from Harper Lee's To Kill a Mockingbird improves how new and established OpenStack contributors work together?

John has spent time at Citrix packaing OpenStack for public cloud, then pushing a vendor technology upstream (with an element of coopetition). Since early 2013, he has been working on Rackspace’s public cloud. Mostly recently he served as the Nova PTL for the Liberty release. He is distilling what he has learnt during this journey, and looking to share this experience more widely, and hopes this will help create some great conversations about how we can all work together even more efficiently and effectively.

The Liberty cycle has seen some big changes to our release process and tools. As the OpenStack projects have matured, and the OpenStack community has grown, the Release Management team has updated the way we manage releases to support the way projects want to work while continuing to make it easy for users to understand what is included in each release. All of these changes lay the groundwork for more changes to come in Mitaka.

These changes will immediately impact:

• Distribution providers


• Deployers


• Version Numbering


• The future of stable branches


• Release cycles

This is a must-attend session for:

• Those who curate or provide an OpenStack distribution


• Release Managers


• Deployers and architects

The Women of Openstack Working Group continues to go from strength to strength. With a record of over 600 women or 10% of the Vancouver Summit attendees, women are a growing and vocal presence in our extremely diverse community. Join this panel of women and minorities as we discuss the topic of subtle bias in the workplace and the OpenStack community and how to remove barriers to full participation in all aspects and roles. 

From PTL to code reviewer, there is a place for everyone to contribute to the fullest extent possible. Learn how to identify and overcome the subtle biases that can drag down even the most confident person.

• Identifying our own biases and tips for avoiding their influence


• Looking beyond the surface: First impressions and how they can sway even the most seemingly impartial decision


• On an IRC, everyone is equal: Using tools to level the playing field for everyone


• Establishing criteria to ensure fair treatment for all

After figuring out the basics of "How to Contribute to OpenStack" the developer is often faced with a harsh reality. Things can take a long time! Specs and patches can continue for over 50 patch sets, spanning weeks and months. Deadlines due to milestones matter, and getting attention from Core (and non-core) reviewers can be challenging. Scott D'Angelo and Andrea Rosa will provide insight and ideas on 1) what to expect when contributing 2) How the spec process can go 3) Some extreme examples 4) ideas on how to smooth the process In addition, experienced Core/PTL members will give tips and insights into how to contribute and navigate the process.

The OpenStack Tent is big and as an OpenStack Operator, Vendor or Contributor it can be a challenge to know what’s going on in each ring.  Help is on the way! The OpenStack Product Work Group strives to work across our community to create a condensed, simplified set of roadmaps of the capabilities you can expect in the upcoming project releases. 

In this session we'll present our findings across the different projects in an effort to give users a glimpse into OpenStack's upcoming capabilities.  The roadmaps presented will span multiple releases and strive to unify the future direction of the individual projects on a per release basis.  This session had over 800 RSVPs at the last summit so please show up early!  

An OpenStack trivia game featuring multiple choice questions using slides, etc, encouraging audience participation. There will also be audible questions (just shout out the answer). Goofy prizes will be awarded. This theme can be used as an icebreaker/etc at OpenStack meetups (the first one, birthday ones, etc.) This talk would also work as a lightning talk with the slides auto advancing.

Each slide will have a backup slide giving a bit more detail about the topic so also educational.

Would you like to be able to move applications seamlessly between OpenStack Powered clouds?  Sure you would—but today, that’s hard.  One of the trickiest aspects of interoperability today is the network stack: OpenStack has multiple networking API’s available that can’t be deployed together, making it difficult to create an interoperable standard.  Without an interoperable standard, applications become a tangle of if/else loops to account for the different possible networking capabilities of various public clouds, appliances, distributions, and managed offerings--and it’s difficult to determine which products support which networking options at all.  Interoperability by if/else loop isn’t really interoperability at all.

The OpenStack community is responding to the challenge of creating an interoperable standard between OpenStack Powered products via the work of the DefCore Committee.  The DefCore Guidelines seek to define core in such a way that OpenStack Powered products can be verifiably tested for adherence to an interoperability standard and consumers can make informed decisions about what they deploy and how they write their applications.  But the DefCore Committe can't operate in a vacume: solving interoperability in networking requires the help of the technical community, the Board of Directors, the DefCore Committee, vendors, and operators.

In this talk, members of the Nova and Neutron technical communities and the DefCore Committee will discuss the history of networking in OpenStack, take the current temperature of OpenStack's networking stacks, and discuss how the DefCore Committee, technical community, and Board of Directors are working together to solve the interoperability problem.  We’ll explain what’s being proposed for the next DefCore Guideline and how we as a community got there.  Attendees will learn about the impact on operators and vendors and leave with an understanding of what to expect of OpenStack Powered (TM) products that meet interoperable networking standards in the future.  We’ll also discuss the feedback that’s been generated so far from operators, vendors, and developers and discuss the future of interoperable networking in OpenStack.  

The talk will present a quantitative analysis of the projects producing the main free, open source software cloud platforms: OpenStack, Apache CloudStack, OpenNebula and Eucalyptus. The analysis will focus on the communities behind those projects, their main development parameters, and the trends that can be observed.

Understanding the inner life of free / open source software projects is of fundamental importance to developers, users and decision makers. This talk will help to understand what's happening behind the curtains in the most relevant open cloud platforms, by analyzing the rich data obtained from their developing repositories.

The talk will cover, for the four analyzed projects, the following topics:

* How open is their development model, and to which extent they provide access to their development data.
Some parameters related to the overall activity and effort put into the development and maintenance of their products.
* The main characteristics of their development community: size, diversity, engagement, attraction, etc.
* The main parameters characterizing their performance, such as time-to-fix tickets or time-to-review patches.
* Some visualizations of the most relevant aspects.

A bonus track with novel information providing insight on the OpenStack community will have a slot in the presentation.

All the tools used to produce the analysis presented in this talk are free, open source software, based on the Grimoire technology, http://vizgrimoire.github.io. The talk will also provide some hints on how to reproduce the study, on these or other projects.

Illustrative example of the kind of information that will be presented: OpenStack Grimoire Dashboard, http://activity.openstack.org/

This talk will be an update and extension of the one I delivered in Paris OpenStack Summit, http://bit.ly/openstack-opencloud