airship/shipyard
Code Issues Proposed changes
A cluster lifecycle orchestrator for Airship.
398 Commits 3 Branches 0 Tags 8.3 MiB
Python 95.5%
Shell 3.2%
Smarty 0.8%
Makefile 0.5%
14d66afb01
Go to file
Anthony Lin 14d66afb01 Update Shipyard API Pod Labels 
As part of ongoing effort to update the "application" and
"component" labels for the UCP components, there is a need
to align with the convention. We will update the label for
the shipyard API pod in this case.

Also updated helm_tk.sh to point to openstack-helm-infra for
reference to helm-toolkit as helm-toolkit has been removed
from the openstack-helm repo [0]

[0] https://review.openstack.org/#/c/558065/

Change-Id: I0b2acda47d87f8dda35fbf054e1c8d906b495061
2018-05-15 14:40:38 +00:00
charts/shipyard Update Shipyard API Pod Labels 2018-05-15 14:40:38 +00:00
docs Promenade validateDesign for Shipyard 2018-05-15 14:39:37 +00:00
etc/shipyard Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
images Add deployment group validation to shipyard 2018-05-09 09:18:16 -05:00
src/bin Promenade validateDesign for Shipyard 2018-05-15 14:39:37 +00:00
tests/unit/plugins Pass Drydock health failure 2018-05-02 15:47:06 +00:00
tools Update Shipyard API Pod Labels 2018-05-15 14:40:38 +00: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 Add gitreview file 2017-08-11 01:20:56 -05: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
requirements.readthedocs.txt Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
tox.ini Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00

docs/README.md

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. Inital 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 GitHub issue