airship
/
shipyard
Code Issues Proposed changes
shipyard/docs
History
Anthony Lin 80fc8095ae Shipyard Documentation for Logs Step 
Documentation for Shipyard API and CLI that is used for retrieval
of logs for a particular Airflow workflow step.

Change-Id: I89c479b164bcbf72e971bb0fc756720b096989e6
 		2018-04-13 09:54:31 -04:00
..
source Shipyard Documentation for Logs Step 2018-04-13 09:54:31 -04:00
README.md Documentation for Shipyard deployment-configuration 2018-03-13 17:54:21 -05:00

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