Go to file

hosingh000 c1bd1203c7 Block site_update if there is no host in MaaS/Drydock

Added the feature in airflow to verify that MaaS list
of BM hosts is not empty for shipyard update_site action.
If the MaaS Machine list is empty, and the
continue-on-fail parameter is not set to true (the default
value is false), it will fail the shipyard steps to
parepare and re-deploy the missing nodes in MaaS through
DD.
Caveat: this US did not have the requirement to compare
the list of nodes in MaaS with the expected site Design.
It simply checks for empty node list, and decide based
on that.

Change-Id: I5ba4a107fe2ae43728e5941570b6c88a436d7b12

2018-09-12 14:13:28 -05: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

Update Dockerfile to allow override of FROM variable

2018-07-17 16:35:42 -05:00

src/bin

Block site_update if there is no host in MaaS/Drydock

2018-09-12 14:13:28 -05:00

tools

Add no_proxy environment variable to CLI script

2018-08-28 13:31:15 +00: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

Remove temp dir deletion statement from make clean

2018-09-04 17:19:57 -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

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:

Initial region/site data will be passed to Shipyard from either a human operator or Jenkins
The data (in YAML format) will be sent to Deckhand for validation and storage
Shipyard will make use of the post-processed data from DeckHand to interact with Drydock.
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
Once the Kubernetes clusters are up and validated to be working properly, Shipyard will interact with Armada to deploy OpenStack using OpenStack Helm
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.