Airship Update - May 2020

By Alexander Hughes on 15/05/2020

What follows is the Airship Community Update for the month of May 2020, brought to you by the Airship Technical Committee.


  • Learn how Airship 2.0, targeted for delivery later this year, is solving NFVi challenges on the way to full 5G deployment in this white paper authored by VP of AT&T's Network Cloud: Ryan van Wyk, and Airship architects: Alan Meadows and Rodolfo Pacheco.
  • On 06-May-2020 Airship 2.0's alpha milestone was declared complete. This was a significant step towards getting Airship 2.0 production-ready, and would not have been possible without the hard work from all of our talented developers, the valuable input from all of our community members, and the collaboration across the projects that Airship 2 will leverage. Thank you all for your contributions!


The Airship blog is a great way to keep up with what's going on in the community. The Airship community publishes blog posts regularly, including the recent Airship 2.0 Blog series. These blog posts introduce the changes from Airship 1.0 to Airship 2.0, highlight new features, and detail the evolution of each component. The first six Airship 2.0 Blog posts are already available:

UPDATE 03-August-2020: Airship 2.0 development spans multiple milestones. Upon completing the first major milestone, Alpha, the community took some time to reflect on lessons learned and how they impacted the direction and design of Airship 2.0. We have summarized these lessons learned and how the design has changed over time - including using different technologies and approaches. You can read more about these changes here: Airship 2.0 is Alpha - Lessons Learned. We recommend reviewing these changes before reading blogs marked as "Pre-Alpha."


The OpenStack Foundation is holding a Virtual Project Teams Gathering (PTG) 01-05 June. The event is free with registration here.

The Project Teams Gathering (PTG) is an event organized by the OpenStack Foundation. It provides meeting facilities allowing the various technical community groups working with OpenStack (user workgroups, development teams, operators, SIGs) to meet in-person, exchange and get work done in a productive setting. It lets those various groups discuss their priorities for the upcoming cycle, assign work items, iterate quickly on solutions for complex problems, and make fast progress on critical issues. The co-location of those various meetings, combined with the dynamic scheduling of the event, make it easy to get specific people in the same room to discuss a specific topic, or participate in multiple team meetings. Evenings allow for relationship building and problem sharing.

The list of groups attending and their planned sessions are available on this calendar.

The Airship sessions will be in one-hour increments and will be recorded. The sessions are scheduled for:

Thursday 04-June

  • 13:00-14:00 UTC (08:00-09:00 CDT)
  • 14:00-15:00 UTC (09:00-10:00 CDT)
  • 15:00-16:00 UTC (10:00-11:00 CDT)
  • 16:00-17:00 UTC (11:00-12:00 CDT)

Friday 05-June

  • 13:00-14:00 UTC (08:00-09:00 CDT)
  • 14:00-15:00 UTC (09:00-10:00 CDT)
  • 15:00-16:00 UTC (10:00-11:00 CDT)
  • 16:00-17:00 UTC (11:00-12:00 CDT)

Airship Topics have not yet been assigned to sessions. To propose additional topics you may do so until the 23rd of May on the agenda etherpad. Once the schedule is finalized this blog post will be updated, and the schedule will be shared by e-mail distribution list.

Be sure to subscribe to the airship-discuss distribution list here to get all the latest news in the community.


If you are evaluating or running Airship, share your feedback in the Airship User Survey! This survey provides users an opportunity to provide anonymous feedback to influence the community and software direction. By sharing information about your configuration and requirements, the Airship Working Committee will be able to advocate on your behalf. The 2020 survey results will be presented at the Fall Summit, November, 2020. Take the Airship User Survey to be included in this round of analysis.


The Airship community adopted formal governance in 2019 leading to the creation of two committees responsible for helping to guide Airship projects. Each of these committees is elected by the community to serve for one year at a time.

Next month, in June, the current Technical Committee term will end, and elections to fill all 5 seats for the 2020-2021 Technical Committee term will be held.

Anyone who has demonstrated a commitment to Airship (community building, communications, or had code merged to the Airship project repositories) within the last 12 months is eligible to run for the Technical Committee. Anyone who is a Contributor (someone who has had changes merged within the last 12 months to any Airship project repository) before the election will be eligible to vote for the TC candidates. There are no term limits, but in order to encourage diversity, no more than 2 of the 5 seats can be filled by any one organization. The Technical Committee will meet regularly in an open forum with times and locations published in community channels.

For more details for eligibility, responsibilities, and election processes please see the Airship Governance.


The progress shown below is for airshipctl, the new Airship 2.0 client.

Last month, airshipctl saw the following activity:

  • 20 authors
  • 98 commits
  • 683 files changed
  • 33,374 additions
  • 4,554 deletions
  • 38 closed issues
  • 47 new issues

This activity led to the completion of the alpha milestone, and significant progress towards the beta milestone. Below is the overall status of the beta milestone:

beta status may 2020


This page lists everything you need to know to get involved and start contributing.

Alexander Hughes, on behalf of the Airship Technical Committee