Airship Update - October 2019
What follows is the Airship Community Update for the month of October, 2019, brought to you by the Airship Technical Committee.
SPOTLIGHT ON ....
- Breaking News: Airship has exited the pilot phase and has been confirmed by the OpenStack Foundation as an official project. Thank you to all community members for your efforts over the last 2 years that have led to this significant milestone.
- The Software research team within Standards &Technology at Ericsson kicked off a collaboration with Airship community to leverage Airship as a container platform enabling their beyond 5G testbed R&D efforts. It is expected that this collaboration will result in the introduction of Multus and other new integrations with Airship.
- Congratulations to the Airship community for making significant progress in Airship 2.0. 17% of planned work was completed, another 18% is in progress and/or in review. The community is looking for more developers to contribute code.
-
Tip of the month: A Quick and Dirty Guide to Airship in a Bottle
Airship is designed to enable you to reliably deploy OpenStack on Kubernetes, but with both of those systems being complicated to deploy, a system that combines them can be downright confusing. Fortunately, the community has created Airship in a Bottle, a simple way to create a deployment so you can get an idea of what's going on. Read more: https://www.mirantis.com/blog/airship-in-a-bottle-quick-dirty-guide.
THE GROWTH OF COMMUNITY
- 5 consecutive OpenStack releases of contributor growth
- Achieved 4,000 all-time commits
- Reached 200 unique all-time authors
- Over 100 contributors during the OpenStack Train release
AIRSHIP BLOG
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."
- Pre-Alpha Airship Blog Series 1 - Evolution Towards 2.0
- Pre-Alpha Airship Blog Series 2 - An Educated Evolution
- Pre-Alpha Airship Blog Series 3 - Airship 2.0 Architecture High Level
- Pre-Alpha Airship Blog Series 4 - Shipyard - an Evolution of the Front Door
- Pre-Alpha Airship Blog Series 5 - Drydock and Its Relationship to Cluster API
- Pre-Alpha Airship Blog Series 6 - Armada Growing Pains
AIRSHIP PROJECT STATUS
If you are looking for more detailed information on the status of specific components or features, you can now check the initial Airship Project Status Report. For changes, we use the Airship Jira as our single source of truth, and the Airship Project Status Report will be updated automatically when Jira is updated.
These are initial reports, and the community is working on more. Let us know what reports you'd find helpful! Your involvement and contribution helps the Airship community go further.
GET INVOLVED
Want to get involved? This page lists everything you need to know.
Get involved and start contributing!
HOW TO SUBSCRIBE/UNSUBSCRIBE TO THIS NEWSLETTER
Please email rv6848@att.com if you want to opt in, opt out, or change the point of contact for your organization.
If you have any news related to Airship, for example, if your organization has started to use it or contribute to it, please share that with rv6848@att.com as well.
We want to hear from you!