airship
/
shipyard
Code Issues Proposed changes
A cluster lifecycle orchestrator for Airship.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
399 Commits
2 Branches
0 Tags
7.9 MiB
 
 
 
 
Tree: 68d4141d1a
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '68d4141d1a'
${ noResults }
Felipe Monteiro 68d4141d1a
Update .gitreview for openstack infra 		4 years ago
charts/shipyard Update Shipyard API Pod Labels 4 years ago
docs Promenade validateDesign for Shipyard 4 years ago
etc/shipyard Refactor shipyard to UCP target layout 4 years ago
images Add deployment group validation to shipyard 4 years ago
src/bin Promenade validateDesign for Shipyard 4 years ago
tests/unit/plugins Pass Drydock health failure 4 years ago
tools Update Shipyard API Pod Labels 4 years ago
.dockerignore Refactor shipyard to UCP target layout 4 years ago
.editorconfig Cleanup dockerfile and add editorconfig 4 years ago
.gitignore Refactor shipyard to UCP target layout 4 years ago
.gitreview Update .gitreview for openstack infra 4 years ago
LICENSE Add Apache 2.0 LICENSE file 4 years ago
Makefile Refactor shipyard to UCP target layout 4 years ago
requirements.readthedocs.txt Refactor shipyard to UCP target layout 4 years ago
tox.ini Refactor shipyard to UCP target layout 4 years ago

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