airship
/
shipyard
Code Issues Proposed changes
A cluster lifecycle orchestrator for Airship.
788 Commits 3 Branches 0 Tags 8.1 MiB
Python 95.7%
Shell 3.1%
Smarty 0.8%
Makefile 0.4%
Go to file
Sergiy Markin b7e7d25308 Rollback apache-airflow back to 1.10.5 
This PS is created to :
- roll back apache-airflow back to 1.10.5
- change default chart values from bionic to ubuntu_focal
- save freshly generated config and policy files samples
- in focal Dockerfile postgres client version is pubped up to v15
- change airflow docker image requirements from limited to fully frozen for shipyard-airflow project
- adjusted requirements-direct.txt for shipyard_airflow
- adjusted requirements-direct.txt for shipyard_client
- regenerated requirements-frozen for both projects
- fixed unit tests after upgrading click module
- gen_all tox profile processing has been moved over to py8 gate because it requires focal zuul node to run
- upgraded airskiff gate playbook to include latest treasuremap patchset with updated airskiff site admada manifests

Change-Id: I47e44f5cfa19b2649697e7cc5a31557a6f4fcfea
 		2023-05-08 21:58:34 +00:00
.github Update Airship vulnerability link 2020-05-18 21:27:25 +00:00
charts Rollback apache-airflow back to 1.10.5 2023-05-08 21:58:34 +00:00
doc Rollback apache-airflow back to 1.10.5 2023-05-08 21:58:34 +00:00
etc/shipyard Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
images Rollback apache-airflow back to 1.10.5 2023-05-08 21:58:34 +00:00
src/bin Rollback apache-airflow back to 1.10.5 2023-05-08 21:58:34 +00:00
tools Rollback apache-airflow back to 1.10.5 2023-05-08 21:58:34 +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 Use helm 3 in chart build 2021-10-01 11:48:37 -05:00
.gitreview OpenDev Migration Patch 2019-04-19 19:52:20 +00:00
.zuul.yaml 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 Shipyard upgrade for focal 2023-04-28 20:40:50 +00:00
README.rst Fix: various documentation and URL fixes 2018-09-24 12:53:27 +02:00
bindep.txt Shipyard upgrade for focal 2023-04-28 20:40:50 +00:00
requirements.readthedocs.txt Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
tox.ini Rollback apache-airflow back to 1.10.5 2023-05-08 21:58:34 +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.