shipyard

History

Bryan Strassner 295835cf2c Conform expected validation responses to status standard Upon review of standard responses, the validation responses were found to be using valid/invalid instead of success/failure. This change changes the values used to be success/failure for the status field in validations. Additionally, this also cleans up the misuse of api version 'v1', making it v1.0 instead on the status responses. Change-Id: Ia10674158648ef0d0c42badc4bd19e1b48b255d9	2018-01-03 07:37:18 -06:00
..
source	Conform expected validation responses to status standard	2018-01-03 07:37:18 -06:00
README.md	Move most Shipyard docs to .rst	2017-12-04 13:36:26 -06:00

Bryan Strassner 295835cf2c Conform expected validation responses to status standard

Upon review of standard responses, the validation responses
were found to be using valid/invalid instead of success/failure.
This change changes the values used to be success/failure for the
status field in validations. Additionally, this also cleans up the
misuse of api version 'v1', making it v1.0 instead on the status
responses.

Change-Id: Ia10674158648ef0d0c42badc4bd19e1b48b255d9

2018-01-03 07:37:18 -06:00

source

Conform expected validation responses to status standard

2018-01-03 07:37:18 -06:00

README.md

Move most Shipyard docs to .rst

2017-12-04 13:36:26 -06: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:

Inital region/site data will be passed to Shipyard from either a human operator or Jenkins
The data (in YAML format) will be sent to DeckHand for validation and storage
Shipyard will make use of the post-processed data from DeckHand to interact with DryDock
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
Once the Kubernetes clusters are up and validated to be working properly, Shipyard will interact with Armada to deploy OpenStack using OpenStack Helm
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.

Roadmap

The detailed Roadmap can be viewed on the LCOO JIRA

Integrate with DeckHand, DryDock/Promenade, Armada
Expand funcitionality to provide visibility into and options for operation of a UCP installation

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