airship
/
shipyard
Code Issues Proposed changes
A cluster lifecycle orchestrator for Airship.
514 Commits 3 Branches 0 Tags 8.1 MiB
Python 95.7%
Shell 3.1%
Smarty 0.8%
Makefile 0.4%
Go to file
Roman Gorshunov 655b1ae3c3 Fix: git commit id labels on images 
1) Use OCI Image Specs for labels instead of custom 'commit-id=xxxxx'
   or legacy "Label Schema"
2) Fix missing git commit id labels on images (.revision)
3) Add human-readable title (.title) of the image, URL (.url), and
   a few other properties (annotations) according to the latest Specs

Change-Id: Iedd64fa70016880d5df241d27d8dad101e10130b
 		2018-09-21 03:31:13 +02:00
charts/shipyard Merge "Update Shipyard's default RBAC policy" 2018-09-04 19:00:39 +00:00
docs Add documentation for safer redeploy_server 2018-09-10 15:27:48 -05:00
etc/shipyard Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
images Fix: git commit id labels on images 2018-09-21 03:31:13 +02:00
src/bin Block site_update if there is no host in MaaS/Drydock 2018-09-12 14:13:28 -05:00
tools Fix: git commit id labels on images 2018-09-21 03:31:13 +02:00
.dockerignore [refactor] logging refactor + redaction filter 2018-06-01 17:14:15 -05:00
.editorconfig Cleanup dockerfile and add editorconfig 2018-02-16 13:44:15 -06:00
.gitignore Workflow to support deployment groups 2018-06-20 09:55:15 -05:00
.gitreview Update .gitreview for openstack infra 2018-05-17 19:26:55 +01:00
.zuul.yaml Consolidate pep8/bandit zuul gating 2018-08-21 20:53:24 +00:00
LICENSE Add Apache 2.0 LICENSE file 2018-05-14 13:46:28 +00:00
Makefile Fix: git commit id labels on images 2018-09-21 03:31:13 +02:00
README.rst Update Deckhand commit 2018-06-01 21:16:08 +01:00
requirements.readthedocs.txt Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
tox.ini Add venv tox environment 2018-08-24 21:34:36 +02: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.

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.