A cluster lifecycle orchestrator for Airship.
Você não pode selecionar mais de 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.
Zuul 30f3a989c7 Merge "Adding default apparmor profile to shipyard components" 1 semana atrás
charts/shipyard Adding default apparmor profile to shipyard components 1 semana atrás
doc Add support for Ubuntu bionic base image 3 semanas atrás
etc/shipyard Refactor shipyard to UCP target layout 1 ano atrás
images Add support for Ubuntu bionic base image 3 semanas atrás
src/bin Locked Werkzeug package release to 0.16.1 2 semanas atrás
tools Adding default apparmor profile to shipyard components 1 semana atrás
.dockerignore Minor: docs location fix 1 ano atrás
.editorconfig Fix: various documentation and URL fixes 1 ano atrás
.gitignore Minor: docs location fix 1 ano atrás
.gitreview OpenDev Migration Patch 10 meses atrás
.zuul.yaml Add support for Ubuntu bionic base image 3 semanas atrás
LICENSE Add Apache 2.0 LICENSE file 1 ano atrás
Makefile Add support for Ubuntu bionic base image 3 semanas atrás
README.rst Fix: various documentation and URL fixes 1 ano atrás
requirements.readthedocs.txt Refactor shipyard to UCP target layout 1 ano atrás
tox.ini Set up publishing of docs 1 ano atrás

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.