a02f79a729
We are getting the following errors in [0] when executing the shipyard CLI due to timeout issue. We will be increasing the timeout from 30 seconds to 60 seconds to allow more time for site validations. There is another problem with the deckhand_load_yaml script as the environment variables were defined but not exported. This p.s. is meant to address these 2 issues. [0] Error messages root@genesis:~# shipyard commit configdocs Error: Validations failed Reason: Validation - Error: Drydock unable to validate configdocs - Error: HTTPConnectionPool(host='drydock-api.ucp.svc.cluster.local', port=9000): Read timed out. (read timeout=30) - Error: Armada unable to validate configdocs - Error: HTTPConnectionPool(host='armada-api.ucp.svc.cluster.local', port=8000): Read timed out. (read timeout=30) root@genesis:~# Change-Id: Ia04d244077c9f809e19aca1b47ce178eb5984b0c |
||
|---|---|---|
| alembic | ||
| charts/shipyard | ||
| docs | ||
| etc/shipyard | ||
| generator | ||
| images | ||
| shipyard_airflow | ||
| shipyard_client | ||
| tests | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| Makefile | ||
| README.md | ||
| alembic.ini | ||
| entrypoint.sh | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
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