airship
/
shipyard
Code Issues Proposed changes
A cluster lifecycle orchestrator for Airship.
404 Commits 3 Branches 0 Tags 8.1 MiB
Python 95.7%
Shell 3.1%
Smarty 0.8%
Makefile 0.4%
Go to file
Felipe Monteiro 0c9152d62e Update Deckhand commit 
This patchset uplifts Deckhand commit to include fix
for document replacement.

This uplift is the same one used in Promenade [0].

The Shipyard README.md was renamed to README.rst for
2 reasons:

* To fix an issue with [1] breaking.
* To update content for OpenStack migration.

[0] I32d22110749b334d1fbf19f910e41ab0b7ff3a16
[1] http://logs.openstack.org/96/571296/1/check/airship-shipyard-pep8/76f6cb1/job-output.txt.gz#_2018-05-30_20_19_47_616403

Change-Id: Ie15f4234d504223e961c525339c87fca3a883ffc
 		2018-06-01 21:16:08 +01:00
charts/shipyard Update Image Reference 2018-05-22 16:47:57 +08:00
docs Update Deckhand commit 2018-06-01 21:16:08 +01:00
etc/shipyard Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
images Update Deckhand commit 2018-06-01 21:16:08 +01:00
src/bin Update Deckhand commit 2018-06-01 21:16:08 +01:00
tests/unit/plugins Pass Drydock health failure 2018-05-02 15:47:06 +00:00
tools Add tox tests to .zuul.yaml 2018-05-25 10:59:40 +08:00
.dockerignore Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
.editorconfig Cleanup dockerfile and add editorconfig 2018-02-16 13:44:15 -06:00
.gitignore Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
.gitreview Update .gitreview for openstack infra 2018-05-17 19:26:55 +01:00
.zuul.yaml Add tox tests to .zuul.yaml 2018-05-25 10:59:40 +08:00
LICENSE Add Apache 2.0 LICENSE file 2018-05-14 13:46:28 +00:00
Makefile Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
README.rst Update Deckhand commit 2018-06-01 21:16:08 +01:00
requirements.readthedocs.txt Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
tox.ini Add tox tests to .zuul.yaml 2018-05-25 10:59:40 +08: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.

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.