airship
/
shipyard
Code Issues Proposed changes
A cluster lifecycle orchestrator for Airship.
482 Commits 3 Branches 0 Tags 8.1 MiB
Python 95.7%
Shell 3.1%
Smarty 0.8%
Makefile 0.4%
Go to file
Bryan Strassner 7d9ca0b69b Remediate failing Bandit gate 
Adds a #nosec exclusion to a known Bandit error that has been evaluated
as low severity, and included comments about how the severity is further
reduced.

Adds a target Python version for Bandit job so that it does not fail to
scan several more files that are not working with a Python 2 run of
Bandit.

Change-Id: I251abd092b3049a663b8758bbec0926f4b4836f7
 		2018-08-17 15:10:30 -05:00
charts/shipyard Merge "Set ULID of action on DAG request" 2018-08-15 16:35:40 +00:00
docs Merge "Set ULID of action on DAG request" 2018-08-15 16:35:40 +00:00
etc/shipyard Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
images Update Dockerfile to allow override of FROM variable 2018-07-17 16:35:42 -05:00
src/bin Remediate failing Bandit gate 2018-08-17 15:10:30 -05:00
tools Add Oslo Policy options for policy file location 2018-08-09 13:55:40 -05: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 fix(gate): fix airship-shipyard-ubuntu job 2018-07-06 04:17:13 +00:00
LICENSE Add Apache 2.0 LICENSE file 2018-05-14 13:46:28 +00:00
Makefile Update Dockerfile to allow override of FROM variable 2018-07-17 16:35:42 -05: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 fix tox python3 overrides 2018-07-27 13:13:02 +07: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.