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.
 
 
 
 
Tin Lam 87ae709fb2 fix(gate): fix airship-shipyard-ubuntu job 4 years ago
charts/shipyard Update chart to support TLS for Shipyard 4 years ago
docs Externalize database connection pool parameters 4 years ago
etc/shipyard Refactor shipyard to UCP target layout 4 years ago
images Externalize database connection pool parameters 4 years ago
src/bin Change k8s node status to be a positive check 4 years ago
tools fix(gate): fix airship-shipyard-ubuntu job 4 years ago
.dockerignore [refactor] logging refactor + redaction filter 4 years ago
.editorconfig Cleanup dockerfile and add editorconfig 5 years ago
.gitignore Workflow to support deployment groups 4 years ago
.gitreview Update .gitreview for openstack infra 4 years ago
.zuul.yaml fix(gate): fix airship-shipyard-ubuntu job 4 years ago
LICENSE Add Apache 2.0 LICENSE file 4 years ago
Makefile Update Shipyard Chart - HTK OSH Infra 4 years ago
README.rst Update Deckhand commit 4 years ago
requirements.readthedocs.txt Refactor shipyard to UCP target layout 4 years ago
tox.ini Unifying proxy variables for tox and docker build 4 years ago

README.rst

Shipyard

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

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.