Updates the definition for queue mirroring to use the same vhost as the queue itself is defined to be. Change-Id: Ibb631d7adb237fa17c5e853a9e9e35297a525782
|3 years ago|
|charts/shipyard||3 years ago|
|doc||3 years ago|
|etc/shipyard||4 years ago|
|images||3 years ago|
|src/bin||3 years ago|
|tools||3 years ago|
|.dockerignore||4 years ago|
|.editorconfig||4 years ago|
|.gitignore||4 years ago|
|.gitreview||4 years ago|
|.zuul.yaml||3 years ago|
|LICENSE||4 years ago|
|Makefile||3 years ago|
|README.rst||4 years ago|
|requirements.readthedocs.txt||4 years ago|
|tox.ini||4 years ago|
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:
- Initial 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.
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.
This project is under development at the moment. We encourage anyone who is interested in Shipyard to review our documentation.
If you find a bug, please feel free to create a Storyboard issue.