Anuket Project

Skip to end of metadata
  • Created by Former user , last modified by Former user on Sept 24, 2019
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

Overview

TODO: Bin to add a few words describing overall goal of this document!

Airship

Airship is a collection of loosely coupled but interoperable open source tools that declaratively automate cloud provisioning.

Airship is a robust delivery mechanism for organizations who want to embrace containers as the new unit of infrastructure delivery at scale. Starting from raw bare metal infrastructure, Airship manages the full lifecycle of data center infrastructure to deliver a production-grade Kubernetes cluster with Helm deployed artifacts, including OpenStack-Helm. Airship allows operators to manage their infrastructure deployments and lifecycle through the declarative YAML documents that describe an Airship environment.

See more at https://www.airshipit.org/ .

OpenStack Helm

OpenStack-Helm is a set of Helm charts to enable deployment, maintenance, and upgrading of loosely coupled OpenStack services and their dependencies individually or as part of complex environments.

See more at https://wiki.openstack.org/wiki/Openstack-helm/ .

Treasuremap

Treasuremap is a documentation, deployment reference as well as CI/CD project for Airship.

Airship site deployments are using the treasuremap repository as a global manifest set (YAML configuration documents) that then are overridden with site specific configuration (networking details, disk layout, etc).

See more at https://airship-treasuremap.readthedocs.io/ .

Deployment

The Airship installer is delivered in a form of site and type manifests, as well as deployment script. This helps automating and adjusting the Airship to the OPNFV reference lab Intel POD17.

Manifests

All site configuration is divided in three main  - global, type and site. They are hierarchical and meant as overrides from one layer to another. This means that global is baseline for all sites, type is a subset of common overrides for a number of sites with common configuration patters (e.g. similar hardware, or need of enabled features), and finally the site is the last layer of site specific overrides and configuration (such as specific IP addresses, hostnames, etc). See Deckhand documentation for more details on layering.

The site-definition.yaml ties together site with the specific type and global manifests.

data:
  site_type: cntt

  repositories:
    global:
      revision: v1.4
      url: https://opendev.org/airship/treasuremap.git

Global

Global manifests contain base configuration including version to all the charts and images specified in versions.yaml.

Type

The only type currently provided is cntt. The type will eventually support specifications published by the CNTT community.

Site

See Intel POD17 site manifests for details.

CI/CD

TODO: Describe pipelines and approach

https://build.opnfv.org/ci/view/airship/


OpenStack

Describe how to setup OpenStack CLI

  • No labels