A cluster lifecycle orchestrator for Airship.
Go to file
Anthony Lin 77a9d0ad34 Update update_site Dag
Update the flow for DryDock.  The flow for update site will be
similar to the one for deploy_site as far as DryDock is concenred
as DryDock will only be used for deploying nodes.

A possible use case where we can use drydock with this dag will
be when we are trying to add nodes to an existing site. The flow
for drydock will be the same as that of deploy_site in such scenario.

Change-Id: Icfb0e80ca926fe3a42e88db75e9dec18f073b4c8
2017-09-11 22:08:29 +00:00
docs Merge "Update to make the commitconfigdocs API be sync." 2017-08-30 21:44:26 -04:00
examples/manifests Initial dummy versions 2017-05-22 10:22:05 -04:00
shipyard_airflow Update update_site Dag 2017-09-11 22:08:29 +00:00
tests Add update_site dag, concurrency check 2017-08-23 21:53:50 -05:00
.gitignore Initial commit 2017-05-17 13:20:48 -07:00
.gitreview Add gitreview file 2017-08-11 01:20:56 -05:00
Dockerfile Update Shipyard Dockerfile 2017-08-29 16:32:13 -04:00
README.md Merge branch 'master' into helm_shipyard 2017-06-11 21:55:36 -05:00
entrypoint.sh Shipyard Dockerfiles 2017-08-09 13:44:08 +00:00
requirements.txt Update Shipyard Dockerfile 2017-08-29 16:32:13 -04:00
setup.py Initial testing framework 2017-08-15 06:50:47 -04:00
test-requirements.txt Update Shipyard Dockerfile 2017-08-29 16:32:13 -04:00
tox.ini Add bandit target to shipyard 2017-08-25 04:56:24 -04:00

README.md

shipyard

Directed acyclic graph controller for Kubernetes and OpenStack control plane life cycle management