airship
/
shipyard
Code Issues Proposed changes
A cluster lifecycle orchestrator for Airship.
518 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 d3b282468f zuul: Use zuul templates for unit tests 
This patch set uses zuul templates for python35 and python36
because:

1) python35 template is maintained by project-config; don't need
   to maintain separately in SY
2) python36 is now what SY will be building off in the Dockerfile
   so it is better to also test this actively in CICD

Change-Id: I98230b51db69f1054d11428f48bd09dc2547f8b6
 		2018-10-23 17:58:51 -04:00
charts/shipyard Add release uuid to pods and rc objects (shipyard) 2018-09-14 15:55:04 -05:00
doc Set up publishing of docs 2018-09-14 21:32:41 +02:00
etc/shipyard Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
images Update Dockerfile to allow override of FROM variable 2018-07-17 16:35:42 -05:00
src/bin Corrected the doc URL for shipyard. 2018-09-18 01:03:44 -06:00
tools zuul: Use zuul templates for unit tests 2018-10-23 17:58:51 -04:00
.dockerignore [refactor] logging refactor + redaction filter 2018-06-01 17:14:15 -05:00
.editorconfig Cleanup dockerfile and add editorconfig 2018-02-16 13:44:15 -06:00
.gitignore Workflow to support deployment groups 2018-06-20 09:55:15 -05:00
.gitreview Update .gitreview for openstack infra 2018-05-17 19:26:55 +01:00
.zuul.yaml zuul: Use zuul templates for unit tests 2018-10-23 17:58:51 -04:00
LICENSE Add Apache 2.0 LICENSE file 2018-05-14 13:46:28 +00:00
Makefile Set up publishing of docs 2018-09-14 21:32:41 +02:00
README.rst Set up publishing of docs 2018-09-14 21:32:41 +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.