A cluster lifecycle orchestrator for Airship.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Zuul 30f3a989c7 Merge "Adding default apparmor profile to shipyard components" преди 1 седмица
charts/shipyard Adding default apparmor profile to shipyard components преди 1 седмица
doc Add support for Ubuntu bionic base image преди 3 седмици
etc/shipyard Refactor shipyard to UCP target layout преди 1 година
images Add support for Ubuntu bionic base image преди 3 седмици
src/bin Locked Werkzeug package release to 0.16.1 преди 2 седмици
tools Adding default apparmor profile to shipyard components преди 1 седмица
.dockerignore Minor: docs location fix преди 1 година
.editorconfig Fix: various documentation and URL fixes преди 1 година
.gitignore Minor: docs location fix преди 1 година
.gitreview OpenDev Migration Patch преди 10 месеца
.zuul.yaml Add support for Ubuntu bionic base image преди 3 седмици
LICENSE Add Apache 2.0 LICENSE file преди 1 година
Makefile Add support for Ubuntu bionic base image преди 3 седмици
README.rst Fix: various documentation and URL fixes преди 1 година
requirements.readthedocs.txt Refactor shipyard to UCP target layout преди 1 година
tox.ini Set up publishing of docs преди 1 година

README.rst

Shipyard

Shipyard adopts the Falcon web framework and uses Apache Airflow as the backend engine to programmatically author, schedule and monitor workflows.

Find more documentation for Shipyard on Read the Docs.

The current workflow is as follows:

  1. Initial region/site data will be passed to Shipyard from either a human operator or Jenkins
  2. The data (in YAML format) will be sent to Deckhand for validation and storage
  3. Shipyard will make use of the post-processed data from DeckHand to interact with Drydock.
  4. Drydock will interact with Promenade to provision and deploy bare metal nodes using Ubuntu MAAS and a resilient Kubernetes cluster will be created at the end of the process
  5. Once the Kubernetes clusters are up and validated to be working properly, Shipyard will interact with Armada to deploy OpenStack using OpenStack Helm
  6. Once the OpenStack cluster is deployed, Shipyard will trigger a workflow to perform basic sanity health checks on the cluster

Note: This project, along with the tools used within are community-based and open sourced.

Mission

The goal for Shipyard is to provide a customizable framework for operators and developers alike. This framework will enable end-users to orchestrate and deploy a fully functional container-based Cloud.

Getting Started

This project is under development at the moment. We encourage anyone who is interested in Shipyard to review our documentation.

Bugs

If you find a bug, please feel free to create a Storyboard issue.