A cluster lifecycle orchestrator for Airship.
Go to file
Bryan Strassner 2e780aef5a [fix] add labels to shipyard jobs
Adds the appropriate labels to the ks-user and ks-service jobs
to ensure they can be referenced for deletion.

Change-Id: I56d6f67d37e7293f596193a8bf7311e82cac3e7f
2018-04-11 17:23:28 -05:00
alembic Document staging api 2017-10-18 18:39:24 -05:00
charts/shipyard [fix] add labels to shipyard jobs 2018-04-11 17:23:28 -05:00
docs Documentation for Shipyard deployment-configuration 2018-03-13 17:54:21 -05:00
etc/shipyard Shipyard deployment configuration 2018-03-12 13:31:11 -05:00
generator Add Action API 2017-09-22 21:47:13 -05:00
images Add Airflow Worker Upgrade Workflow 2018-03-16 10:18:43 -04:00
shipyard_airflow Update K8s Preflight Check Operator 2018-04-04 17:36:30 -04:00
shipyard_client [391107] Sorting of commit configdocs results 2018-03-23 14:14:11 -04:00
tests [Fix] Armada Operator/Dag - Task Id and Xcom Key 2018-03-27 05:47:26 +00:00
tools Use Shipyard Docker Container for Tools Scripts 2018-03-20 23:35:18 -05:00
.coveragerc Unit Test for WorkflowResource and WorkflowIdResource 2017-12-05 11:43:26 -06:00
.editorconfig Cleanup dockerfile and add editorconfig 2018-02-16 13:44:15 -06:00
.gitignore Cleanup dockerfile and add editorconfig 2018-02-16 13:44:15 -06:00
.gitreview Add gitreview file 2017-08-11 01:20:56 -05:00
Makefile Removing Whitespace 2018-02-25 12:40:27 -06:00
README.md [docs] Include Read the Docs link in README 2018-03-22 17:00:45 -05:00
alembic.ini Add Action API 2017-09-22 21:47:13 -05:00
entrypoint.sh Make Ingress proxy-read-timeout Configurable 2018-02-07 18:37:12 +00:00
requirements.txt Add CLI formatted responses to Shipyard CLI 2017-11-20 10:38:46 -06:00
setup.cfg Add database upgrade entrypoint 2018-01-25 09:37:00 -05:00
setup.py Add Action API 2017-09-22 21:47:13 -05:00
test-requirements.txt SY/AF Test version pinning 2018-03-28 10:22:58 -04:00
tox.ini Shipyard deployment configuration 2018-03-12 13:31:11 -05:00



Shipyard is the directed acyclic graph controller for Kubernetes and OpenStack control plane life cycle management, and a component of the Undercloud Platform (UCP).

Shipyard provides the entrypoint for the following aspects of the control plane established by the UCP:

Designs and Secrets
Site designs, including the configuration of bare metal host nodes, network design, operating systems, Kubernetes nodes, Armada manifests, Helm charts, and any other descriptors that define the build out of a group of servers enter the UCP via Shipyard. Secrets, such as passwords and certificates use the same mechanism.
The designs and secrets are stored in UCP's Deckhand, providing for version history and secure storage among other document-based conveniences.
Interaction with the site's control plane is done via invocation of actions in Shipyard. Each action is backed by a workflow implemented as a directed acyclic graph (DAG) that runs using Apache Airflow. Shipyard provides a mechanism to monitor and control the execution of the workflow.

Find more documentation for Shipyard on Read the Docs

Integration Points:

OpenStack Identity (Keystone) provides authentication and support for role based authorization
Apache Airflow provides the framework and automation of workflows provided by Shipyard
PostgreSQL is used to persist information to correlate workflows with users and history of workflow commands
Deckhand supplies storage and management of site designs and secrets
Drydock is orchestrated by Shipyard to perform bare metal node provisioning
Promenade is indirectly orchestrated by Shipyard to configure and join Kubernetes nodes
Armada is orchestrated by Shipyard to deploy and test Kubernetes workloads

Getting Started:

Shipyard @ Gerrithub
Helm chart

See also:

Undercloud Platform (UCP)