Project Update Shanghai Open Infrastructure Summit Airship Overview - PowerPoint PPT Presentation

Project Update Shanghai Open Infrastructure Summit

Airship Overview “ Airship is a collection of loosely coupled, but interoperable, open source tools that declaratively automate cloud provisioning.” Motivations Orchestration: Batteries included • Singular Deployment Method • Predictable Upgrades • Repeatable Multi-site Deployments • Resiliency • Enterprise-Grade Security •

Strategic Focus – 1.x Enhancement Highlights • Platform security enhancements • Limit privileges: Secure operational access via porthole utility containers • Kubernetes security best practices • End to end encryption on the wire and at rest • Implemented seamless rotation of secrets • Platform, deployment and tooling • Per patchset virtualized deployment • Armada workflow: Wait and test management • Initial multi-OS support • Redfish OOB driver • Rev’d Kubernetes, Docker, Helm • Added support for Openstack Stein deployment via Airship • Resiliency • Full resiliency against control plane node failure • Hardened services by restricting container use of root • Added resiliency for MaaS services and networking • High availability processes

Airship 2.0

Why Airship 2.0? • Building Airship YAML is hard • Supporting smaller deployments • Changing the tires while the car is moving is hard • Workflows should be fully declarative • Adoption of entrenched upstream project

Airship 2.0 – Components Involved • AirshipCTL • Kustomize • Leverage Kubernetes Cluster API • MetalKube / Ironic integration • KubeADM integration • Leverage cloud-native workflow management • Service layers • Containerized Network Function (CNF) support • Multus integration • Multi-tenancy • Helm v3 and Armada Operator • Cloud Harbor • Edge use cases

Airship 2.0 – Evolution of the front door

Airship 2.0 – Document Changes

Airship 2.0 – Baremetal provisioning

Technical Best Practices

Technical Best Practices: Documentation Documentation includes: Overview, Architecture, Getting Started • Site Authoring and Deployment Guides • Contributor / Review Guide • Component and Integration Testing Docs • Dev and Ops-focused Guides • More on the way… •

Technical Best Practices: Code Review Code Review Follows Established OSF Community Norms Core Reviewer teams per Airship project, • nominated/ratified by those core teams Two +2s, WF +1, and Zuul gating required • for merge +1s from non-cores (and cores) strongly • encouraged Documentation and CICD are reviewed as • code

Technical Best Practices: Testing & CICD Airship has multi-faceted testing: Linting and unit testing, via Zuul • Lightweight integration testing per change, via • Zuul Voting and non-voting checks • VM-based 3 rd -party integration run per • Treasuremap change Nightly 3 rd -party bare metal deployment testing • Developer documentation for local testing •

Community Growth

Expanding Contributor Base and Growth of Community 103 All Time Metrics 90 4,063 commits in 2 5 repos • 203 authors representing 20+ • companies 46 38 26 Pike Queens Rocky Stein Train Contribution Metrics Available at https://www.stackalytics.com/?project_type=openstack-others&module=airship-group&metric=commits

Airship Contributor Growth (cumulative) 2017 2018 2019

Airship Contributor & User Announcements June 2019 May 2018 February 2019 April 2019 August 2019 November 2018 2019 2018

“More than 20 Network Cloud regions deployed and managed by Airship to date, and 5G Core deployments inflight.” “Airship is becoming the foundation of SKT’s cloud infrastructure deployment efforts.” “Aside from contributing to Airship upstream and collaborating with AT&T on key roadmap features, Mirantis is integrating much of the code into Mirantis Cloud Airship Contributors Platform (MCP), Mirantis’s core product that empowers telcos and enterprises to efficiently run Kubernetes on- premises.” “ Ericsson is positive of an alignment between Airship and CNCF. We are increasing our upstream investments to the related opensource projects, and will work closely with AT&T and the Airship and CNCF communities to align and evolve capabilities in both communities.” “StarlingX uses Airship Armada for orchestrating the deployment of multiple Helm charts.” “Airship is core to realizing high -availability cloud services optimized for edge computing systems and applications.”

Governance

Developer Roles Contributor Core Reviewer • Has had changes merged within • Nominated and approved by the the last 12 months established Core, following established OpenStack processes • Eligible to vote in the election of Technical Committee • Can be Cores of multiple Airship components • Able to propose changes and give +1/-1 reviews on changes from • Able to merge changes and give +2/-2 other contributors reviews on changes from other contributors

Technical Committee Responsible for the road map, vision and use cases for Airship • Ensures Airship projects are adhering to the projects core principles, promote standardization, • define and organizes the Airship versioning and release process 5 Members elected by Contributors • Elections take place once per year • Anyone who has demonstrated commitment to the Airship project in the last 12 months is • eligible to run No term limits for TC seats • No more than 2 of the 5 seats can be filled by any one organization •

Working Committee The WC committee cares for day to day functioning of Airship community • WC intends to: • Help influence the project strategy • Help arbitrate when there is a disagreement between Core Reviewers within a single project or • between Airship projects Perform marketing and communications • Help provide product management as well as ecosystem support • 5 Members elected by Core Reviewers • Elections take place once per year • Any Contributor is eligible to run • No term limits for WC seats • No more than 2 of the 5 seats can be filled by any one organization •

Current Committee Members Technical Committee Working Committee • James Gu, *independent • Nishant Kumar, Ericsson • Alexander Hughes, Accenture • Matt McEuen, AT&T • Jan-Erik Mångs, Ericsson • Kaspars Skels, Ericsson • Alexey Odinokov, Mirantis • Drew Walters, AT&T • Ryan van Wyk, AT&T • Stas Egorov, Mirantis

Future Plans December 2019 March 2020 May 2020 ● Bootstrap first host ● Demonstrate at least one ● Full feature set ● Ephemeral cluster alternative to baremetal ● Target cluster ● Workflows for software LCM ● Baremetal ● MVPs for most other features provisioning ● Kubernetes provisioning

Community Channels Mailing Lists: lists.airshipit.org t Freenode IRC: #airshipit Website: www.airshipit.org OpenDev: https://opendev.org/airship YouTube: https://www.youtube.com/user/OpenStackFoundation/ AT&T and Mirantis Airship Webinar: Elevate Your Infrastructure Using Airship

Elevate Your Infrastructure Questions?