48f1b09268
Also adds better test coverage for input checks Changes some input checks to be less coupled to invoking action/command. Change-Id: I704b90bf39f4589f78d0253d99d28cf294c40d93
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 processing
- 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
- Create Helm Charts for Airflow
- Create Helm Charts for Shipyard
- Create Falcon API Framework
- Integrate with DeckHand, DryDock/Promenade, Armada
Getting Started
This project is under development at the moment. We encourage anyone who is interested in Shipyard to review our Installation documentation
Bugs
Bugs are traced in LCOO JIRA. If you find a bug, please feel free to create a GitHub issue and it will be synced to JIRA.