OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|5 hours ago|
|charts/shipyard||2 days ago|
|doc||2 months ago|
|etc/shipyard||1 year ago|
|images||1 day ago|
|src/bin||1 day ago|
|tools||2 days ago|
|.dockerignore||7 months ago|
|.editorconfig||6 months ago|
|.gitignore||7 months ago|
|.gitreview||5 hours ago|
|.zuul.yaml||2 weeks ago|
|LICENSE||11 months ago|
|Makefile||4 weeks ago|
|README.rst||6 months ago|
|requirements.readthedocs.txt||1 year ago|
|tox.ini||7 months 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.