airship
/
shipyard
Code Issues Proposed changes
A cluster lifecycle orchestrator for Airship.
280 Commits 3 Branches 0 Tags 8.1 MiB
Python 95.7%
Shell 3.1%
Smarty 0.8%
Makefile 0.4%
Go to file
Anthony Lin a29d62fb43 Improve Ingress Controller handling in deckhand_load_yaml script 
This Patch Set is meant to address Shipyard issue #18 [0]

Issues Identified:

1) The deckhand_load_yaml.sh script does not check if the
   ingress_controller_ip returned a null value. This may
   result in invalid entries written to /etc/hosts.

2) The subsequent DNS entries written to /etc/hosts are not
   idempotent, so script re-runs (e.g., after discovering and
   resolving YAML validation errors) will result in duplicate
   (and possibly disagreeing) DNS entries written to /etc/hosts.

3) The '--replace' flag should also be used in the "shipyard create configdocs"
   command, to allow for iterative YAML corrections and re-execution
   of this script to get past validation errors.

[0] https://github.com/att-comdev/shipyard/issues/18

Change-Id: I33531d07a5d6c425071af99c8824c12d3e177e69
 		2018-01-25 08:36:32 +00:00
alembic Document staging api 2017-10-18 18:39:24 -05:00
charts/shipyard Merge "Redeploy Server - Dags & Operators" 2018-01-24 22:16:10 -05:00
docs Shipyard Documentation for Dryrun Option/Query 2018-01-12 16:07:20 -05:00
etc/shipyard Redeploy Server - Dags & Operators 2018-01-24 17:34:51 +00:00
generator Add Action API 2017-09-22 21:47:13 -05:00
images Bump Airflow Version to 1.9.0 2018-01-18 08:28:59 +00:00
shipyard_airflow Merge "Redeploy Server - Dags & Operators" 2018-01-24 22:16:10 -05:00
shipyard_client Fix shipyard encoding of status response 2018-01-22 18:52:16 -06:00
tests Merge "Redeploy Server - Dags & Operators" 2018-01-24 22:16:10 -05:00
tools Improve Ingress Controller handling in deckhand_load_yaml script 2018-01-25 08:36:32 +00:00
.coveragerc Unit Test for WorkflowResource and WorkflowIdResource 2017-12-05 11:43:26 -06:00
.gitignore ActionsValidationsResource and VersionsResource Unit Tests 2017-12-06 13:27:18 -06:00
.gitreview Add gitreview file 2017-08-11 01:20:56 -05:00
Makefile Update makefile with run commands 2017-12-11 12:07:44 -06:00
README.md Enhance the README for Shipyard 2017-10-13 21:30:01 -05:00
alembic.ini Add Action API 2017-09-22 21:47:13 -05:00
entrypoint.sh Update Shipyard Dockerfile 2018-01-07 23:31:38 -05:00
requirements.txt Add CLI formatted responses to Shipyard CLI 2017-11-20 10:38:46 -06:00
setup.cfg CLI for Shipyard API 2017-11-08 14:28:08 -06:00
setup.py Add Action API 2017-09-22 21:47:13 -05:00
test-requirements.txt Adds keystonemiddleware and falcon to test-requirements 2017-12-06 09:54:37 -06:00
tox.ini Unit Test for WorkflowResource and WorkflowIdResource 2017-12-05 11:43:26 -06:00

README.md

Shipyard

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.
Actions
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.

Intgration 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 mangement 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)