What follows is the Airship Community Update for the month of October, 2019, brought to you by the Airship Technical Committee.
As part of the evolution of Airship 1.0, an enduring goal has remained supporting multiple provisioning backends beyond just bare metal. This includes those that can provision to third-party clouds and to other use cases like OpenStack VMs as well as enable you to bring your own infrastructure.
Shipyard provides a frontend API within Airship environments that allow users to push their declared documents into sites and execute pre-defined Directed Acyclic Graphs (DAGs) against those declarations. DAG is a directed graph data structure for topological ordering. From an architectural perspective, this is what Shipyard looks like today and how it interacts with other Airship components:
Welcome to the Airship Community Update, a digest of the latest developments and activities across Airship projects, events, and users! One goal of the Airship Technical Committee is to help build community, and so we hope by keeping you informed of project milestones and news, we will make it easier for you to get involved when the time is right. If you wish to be removed from this distribution, please just respond as such.
You can meet the Airship community at the upcoming Open Infrastructure
In order to achieve the goals of vanishing complexity, as well as broaden the variety of supported use cases for Airship 2.0, we shifted far more of the process to the left. We will accomplish this by introducing airshipctl
The Airship team is excited to announce the completion of its first Technical
Airship 1.0 dramatically improved the way we provision and manage the infrastructure. Navigating through the journey towards Airship 1.0 release, we have learned many lessons.
Did you miss any Airship news or updates at the Open Infrastructure Summit?
We’ve got you covered.
With Airship’s exciting announcement of the availability of its 1.0 release
Two years ago, AT&T Communications CEO John Donovan threw down the gauntlet to his Technology and Operations team – we were going to be first to launch mobile, standards-based 5G in 2018. Never mind that the standards for 5G weren’t even available yet. The team was up for the challenge and went to work. But it meant the infrastructure would have to be built in parallel with the network and radio functions. No silos. No walls. Many teams moving together with a single purpose. It was the only way to make our goal.
The Airship project is taking flight at the the upcoming Open Infrastructure Summit in Denver