Grounded in the Cloud
Showing results for 
Search instead for 
Did you mean: 

OpenStack Summit Sessions: How to Contribute


As mentioned in a previous post, the OpenStack community is now voting on submitted talks for the upcoming Summit in Paris.  I have broken the submissions down into separate blogs to make it easier to find the available HP Helion submitted talks for your voting consideration.



How to Contribute and effectively communicate with the OpenStack Community  

This session will help the beginners who are interested in contributing to OpenStack and would need mentoring on where to start and how to complete your contribution. 

This session will cover the basics for the audience to get ready for contribution and also will walk through and educate on how to write Blueprint specs, how to contribute code or fix bugs, and how to contribute to documentation and testing. Also a major part in being an OpenStack Technical Contributor is how you communicate with the community. 

This session will provide you the necessary tips with some examples on how to become a good citizen of the OpenStack Community. 


Slaying the Salmon of Doubt  

Working your way upstream is not easy. In this talk, I will explore how a team of software engineers in HP went from being closed-source enterprise developers to being a full house of ATCs and one core team member. I will look at the personal, departmental and institutional waterfalls that had to be flattened to achieve this.

Back in the day, we forked Diablo and worked feverishly behind closed doors to run v1 of our public cloud. Today we work upstream and run weeks behind trunk with only a handful of proprietary patches. We also offer a "Community Edition" release every 6 weeks that uses TripleO technology to encapsulate some of the learnings we got from running trunk at scale.


Contributing a big feature – Experiences with Neutron’s DVR feature in Juno  

OpenStack uses advanced processes to exercise new code changes using automated tests and human review.  The standards are high and getting higher.  When even small features can seem like a chore why would we attempt a larger change such as Neutron’s new distributed virtual router feature?  As a new core member of the Neutron team and the DVR development team, we worked with the community to contribute this new feature in Juno. 

In this talk, we will share our experiences with the community from the blueprint review and approval through the Juno release that carries the implementation.  We will share the good and the bad:  both what went well and what could have been done better.  Our experiences illustrate that working with the community early is best.  They also show the difficulties inherent in developing large features and how to mitigate them.  We will demonstrate strategies for managing many dependent patches with multiple authors.  We will address how to respect reviewers’ time as well as how to be an effective and constructive reviewer. 

If you are looking to contribute even a small or moderate feature to an OpenStack project you will learn from our experience.


Fast Path to Becoming an OpenStack Contributor  

In this talk we provide an overview of tools and processes that enable developers that are new to OpenStack to learn key fundamentals that will accelerate their ability to contribute to OpenStack. Specifically, this presentation will cover how to integrate the Eclipse development environment with Git, the revision control and source code management system used by OpenStack. We also provide an overview of OpenStack's Gerrit review/contribution workflow and show how to do basic operations like commit and rebase. We then describe straightforward approaches for pulling down and executing  in debug mode other developer's patches which will greatly improve your "hands-on" learning experience with OpenStack. Next, for your new cool features that don't quite fit into existing OpenStack projects we show how you can create your own OpenStack incubation project on StackForge to build your own ecosystem and position your project for future OpenStack adoption. Finally, we provide detailed instruction on hints, tips, and strategies for becoming a strong code reviewer as used by experienced core contributors.


OpenStack Hello World !!!  

OpenStack has grown over the last few years and is a result of a global collaboration of developers and cloud computing technologists producing the ubiquitous open source cloud computing platform for public and private clouds.   The aim of delivering all types of clouds with simple to implement, scalable and feature rich has attracted a global collaboration of developers, non-developers and cloud computing technologists.    


This has been possible with the introduction of process, tools and a set of governance.   

This session “OpenStack Hello Word” aims at evangelizing OpenStack and enriching the participants with processes, tools and governance that is being followed and how to be successful as a “Contributor”.    


Authentication and Credentials in Tempest

Until Icehouse Tempest worked in environments running OpenStack Identity v2 API. It's "tenant isolation" mechanism, which provides the ability for test to run in parallel without collisions, relied on Identity V2.

Parallel execution of tests has been key in identifying many bugs and race conditions in OpenStack.

The introduction of OpenStack Identity v3 API, as well and hierarchical multi-tenancy - has generated the need to Tempest to support multiple versions of the Identity API and to have more granularity in its test accounts model,

It has also has opened up the space for new type of tests, related to scope of resources across tenants and domains.


This session describes how Tempest has been refactored and extended in Juno to become domain aware, by introducing the concepts of credentials and authentication provider. A new flavor of "tenant isolation" has been introduced, that may work with both versions of the Identity service, as well as without the need of admin credentials at run time. At the time of writing work is planned to extend the concept of "admin account" in tempest to have more granularity.


The aim is to help contributors to Tempest in the Kilo timeframe to use the new modified framework, and write integration tests and verify cross tenant and cross domain scope of cloud resources.



Senior Manager, Cloud Online Marketing
0 Kudos
About the Author


I manage the HPE Helion social media and website teams promoting the enterprise cloud solutions at HPE for hybrid, public, and private clouds. I was previously at Dell promoting their Cloud solutions and was the open source community manager for OpenStack and at Rackspace and Citrix Systems. While at Citrix Systems, I founded the Citrix Developer Network, developed global alliance and licensing programs, and even once added audio to the DOS ICA client with assembler. Follow me at @SpectorID

Jan 30-31, 2018
Expert Days - 2018
Visit this forum and get the schedules for online HPE Expert Days where you can talk to HPE product experts, R&D and support team members and get answ...
Read more
See posts for dates
HPE Webinars - 2018
Find out about this year's live broadcasts and on-demand webinars.
Read more
View all