airship/shipyard
Code Issues Proposed changes
A cluster lifecycle orchestrator for Airship.
822 Commits 3 Branches 0 Tags 8.3 MiB
Python 95.5%
Shell 3.2%
Smarty 0.8%
Makefile 0.5%
2fb62659c5
Go to file
Sergiy Markin 2fb62659c5 Updated base image docker repo url 
Also fixed some code deprecation warnings

Change-Id: I01d924c82677213251547a677c10d5d963765b94
2024-12-19 22:04:37 +00:00
.github Update Airship vulnerability link 2020-05-18 21:27:25 +00:00
charts Airflow and Openstack modules upgrade 2024-12-18 14:37:52 +00:00
doc Bump up docker Pypi module version 2024-10-08 22:24:12 +00:00
etc/shipyard Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
images Updated base image docker repo url 2024-12-19 22:04:37 +00:00
src/bin Updated base image docker repo url 2024-12-19 22:04:37 +00:00
tools Updated base image docker repo url 2024-12-19 22:04:37 +00:00
.dockerignore Use helm 3 in chart build 2021-10-01 11:48:37 -05:00
.editorconfig Fix: various documentation and URL fixes 2018-09-24 12:53:27 +02:00
.gitignore Airflow webserver UI 2023-09-25 22:01:00 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:52:20 +00:00
.readthedocs.yaml Treasuremap references fixes 2024-10-05 17:41:15 +00:00
.zuul.yaml Treasuremap references fixes 2024-10-05 17:41:15 +00:00
bindep.txt Shipyard upgrade for focal 2023-04-28 20:40:50 +00:00
LICENSE Add Apache 2.0 LICENSE file 2018-05-14 13:46:28 +00:00
Makefile Remove ubuntu_focal as image alias 2024-10-15 15:25:15 +00:00
README.rst Fix: various documentation and URL fixes 2018-09-24 12:53:27 +02:00
requirements.readthedocs.txt Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
tox.ini Airflow 2.10.2 + ubuntu_jammy 2024-09-26 18:20:04 +00:00

README.rst

Shipyard

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:

  1. Initial 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 Storyboard issue.