airship/shipyard
Code Issues Proposed changes
A cluster lifecycle orchestrator for Airship.
632 Commits 3 Branches 0 Tags 8.3 MiB
Python 95.5%
Shell 3.2%
Smarty 0.8%
Makefile 0.5%
962126ed4c
Go to file
Drew Walters 962126ed4c airflow: Update image reqs to match src reqs 
The airflow image has a requirements file that is separate from the one
located in src/bin/shipyard_airflow, which was missed in a previous
uplift patch [0]. This change updates all versions in the image
requirements file to match the source code requirements.

[0] https://review.openstack.org/652736

Change-Id: I238bba4038e5cd8364711c2c5d1f78f51fc76948
2019-04-15 19:25:28 +00:00
charts/shipyard Merge "Adds HTTP Security Headers" 2019-04-02 18:33:24 +00:00
doc Move Airflow web container into Shipyard pod 2019-01-29 09:41:16 -06:00
etc/shipyard Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
images airflow: Update image reqs to match src reqs 2019-04-15 19:25:28 +00:00
src/bin airflow: Update Armada version 2019-04-15 12:14:45 -05:00
tools (zuul) Fix image publish job 2019-04-03 15:23:27 -05:00
.dockerignore Minor: docs location fix 2018-09-14 23:38:29 +02:00
.editorconfig Fix: various documentation and URL fixes 2018-09-24 12:53:27 +02:00
.gitignore Minor: docs location fix 2018-09-14 23:38:29 +02:00
.gitreview Update .gitreview for openstack infra 2018-05-17 19:26:55 +01:00
.zuul.yaml CI: Add chart build gate 2019-01-28 11:27:26 -06:00
LICENSE Add Apache 2.0 LICENSE file 2018-05-14 13:46:28 +00:00
Makefile images: Update default image tag to latest 2019-03-22 18:42:48 +00: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 Set up publishing of docs 2018-09-14 21:32:41 +02: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.