The current logic checks for nodes that started the join process (based on the snapshot of the environment that was taken by the operator at that point in time). It will not check the state of nodes that it is not aware of, i.e. those that it did not capture initially will not be checked. Hence there is a need to introduce backoff time as it takes a while before all the nodes start to join the Cluster. This is a short term stop gap approach until the Promenade API is ready for consumption Change-Id: I2bdf9c970ecb509fe833fd353e6648a97118d79b
|5 years ago|
|alembic||5 years ago|
|charts/shipyard||5 years ago|
|docs||5 years ago|
|etc/shipyard||5 years ago|
|generator||5 years ago|
|images||5 years ago|
|shipyard_airflow||5 years ago|
|shipyard_client||5 years ago|
|tests||5 years ago|
|tools||5 years ago|
|.coveragerc||5 years ago|
|.gitignore||5 years ago|
|.gitreview||5 years ago|
|Makefile||5 years ago|
|README.md||5 years ago|
|alembic.ini||5 years ago|
|entrypoint.sh||5 years ago|
|requirements.txt||5 years ago|
|setup.cfg||5 years ago|
|setup.py||5 years ago|
|test-requirements.txt||5 years ago|
|tox.ini||5 years ago|
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
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.
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