6b0100ab00
The current 'trigger_rule' is set to 'all_done' which means that this task will run even if one of the upstream tasks, e.g. 'drydock_build' failed (see [0] on how task is triggered). This is an incorrect behavior as task should only run if all upstream tasks have succeeded. This patch set is meant to correct this behavior. [0] https://airflow.incubator.apache.org/concepts.html#trigger-rules all_success: (default) all parents have succeeded all_failed: all parents are in a failed or upstream_failed state all_done: all parents are done with their execution one_failed: fires as soon as at least one parent has failed, it does not wait for all parents to be done one_success: fires as soon as at least one parent succeeds, it does not wait for all parents to be done dummy: dependencies are just for show, trigger at will Change-Id: I571271b79cece268ae039420e12327f187e8f35c
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.
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