airship
/
shipyard
Code Issues Proposed changes
A cluster lifecycle orchestrator for Airship.
786 Commits 3 Branches 0 Tags 8.1 MiB
Python 95.7%
Shell 3.1%
Smarty 0.8%
Makefile 0.4%
Go to file
Ruslan Aliev e3e71f7d16 Bump airship dependencies 
Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
Change-Id: I3bc287af7a89410b7e7e248673a854477360f9ac
 		2022-09-28 09:51:39 -05:00
.github Update Airship vulnerability link 2020-05-18 21:27:25 +00:00
charts [shipyard] Postgres upgrade to 14.5 2022-09-23 13:14:12 +00:00
doc Bump airship dependencies 2022-07-07 14:14:51 -05:00
etc/shipyard Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
images Merge "[airflow] Bumping up kubectl version to 1.24.6" 2022-09-26 21:16:03 +00:00
src/bin Bump airship dependencies 2022-09-28 09:51:39 -05:00
tools Merge "[helm-toolkit] Update to latest helm-toolkit" 2022-09-26 21:12:02 +00:00
.dockerignore Use helm 3 in chart build 2021-10-01 11:48:37 -05:00
.editorconfig Fix: various documentation and URL fixes 2018-09-24 12:53:27 +02:00
.gitignore Use helm 3 in chart build 2021-10-01 11:48:37 -05:00
.gitreview OpenDev Migration Patch 2019-04-19 19:52:20 +00:00
.zuul.yaml Gate fixes: remove py35, make xenial non-voting 2021-10-18 12:43:13 -07:00
LICENSE Add Apache 2.0 LICENSE file 2018-05-14 13:46:28 +00:00
Makefile Use helm 3 in chart build 2021-10-01 11:48:37 -05:00
README.rst Fix: various documentation and URL fixes 2018-09-24 12:53:27 +02:00
requirements.readthedocs.txt Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
tox.ini Gate fixes: remove py35, make xenial non-voting 2021-10-18 12:43:13 -07:00

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.