Crank, Daniel (dc6350)
A recent Shipyard change  introduced user-context tracing support in Shipyard, which requires the passing of an additional parameter to the Deckhand and Drydock API clients. The Deckhand  and Drydock  clients were updated to handle the additional parameter, but the versions of those components used by Shipyard was not updated. This change uplifts the versions of Deckhand and Drydock in requirements.txt for the Airflow component of Shipyard to a version that supports the aforementioned, additional, user-context parameter.  https://review.openstack.org/633873  https://review.openstack.org/634068  https://review.openstack.org/638115 Change-Id: I096191f436c5123b6c263fe92c0d69b9e4085c66
|2 years ago|
|charts/shipyard||2 years ago|
|doc||2 years ago|
|etc/shipyard||3 years ago|
|images||2 years ago|
|src/bin||2 years ago|
|tools||2 years ago|
|.dockerignore||3 years ago|
|.editorconfig||3 years ago|
|.gitignore||3 years ago|
|.gitreview||3 years ago|
|.zuul.yaml||2 years ago|
|LICENSE||3 years ago|
|Makefile||2 years ago|
|README.rst||3 years ago|
|requirements.readthedocs.txt||3 years ago|
|tox.ini||3 years ago|
Shipyard adopts the Falcon web framework and uses Apache Airflow as the backend engine to programmatically author, schedule and monitor workflows.
Find more documentation for Shipyard on Read the Docs.
The current workflow is as follows:
Note: This project, along with the tools used within are community-based and open sourced.
The goal for Shipyard is to provide a customizable framework for operators and developers alike. This framework will enable end-users to orchestrate and deploy a fully functional container-based Cloud.
This project is under development at the moment. We encourage anyone who is interested in Shipyard to review our documentation.
If you find a bug, please feel free to create a Storyboard issue.