airship
/
shipyard
Code Issues Proposed changes
A cluster lifecycle orchestrator for Airship.
381 Commits 3 Branches 0 Tags 8.1 MiB
Python 95.7%
Shell 3.1%
Smarty 0.8%
Makefile 0.4%
Go to file
Anthony Lin 08e0f2987c [Fix] Update dag name in dag_names dag 
A bug was introduced while trying to rebase and resolve the
merge conflicts in [0]. This led to errors [1] while executing
action workflow with Shipyard.

This patch set will fix the bug

[0] https://review.gerrithub.io/#/c/att-comdev/shipyard/+/408289/
[1] Errors seen in Airflow Web

[2018-04-26 06:50:55,991] {{models.py:288}} ERROR - Failed to import: /usr/local/airflow/dags/deploy_site.py
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/airflow/models.py", line 285, in process_file
    m = imp.load_source(mod_name, filepath)
  File "/usr/lib/python3.5/imp.py", line 172, in load_source
    module = _load(spec)
  File "<frozen importlib._bootstrap>", line 693, in _load
  File "<frozen importlib._bootstrap>", line 673, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 665, in exec_module
  File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed
  File "/usr/local/airflow/dags/deploy_site.py", line 19, in <module>
    from common_step_factory import CommonStepFactory
  File "/usr/local/airflow/dags/common_step_factory.py", line 32, in <module>
    class CommonStepFactory(object):
  File "/usr/local/airflow/dags/common_step_factory.py", line 92, in CommonStepFactory
    def get_get_rendered_doc(self, task_id=dn.GET_RENDERED_DOC):
AttributeError: module 'dag_names' has no attribute 'GET_RENDERED_DOC'

Change-Id: Ib4e26f4acc951bc460ece5d51cea8e0acfdc73d8
 		2018-04-26 07:22:28 +00:00
charts/shipyard Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
docs Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
etc/shipyard Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
images Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
shipyard_airflow/schemas Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
src/bin [Fix] Update dag name in dag_names dag 2018-04-26 07:22:28 +00:00
tests/unit Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
tools Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
.dockerignore Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
.editorconfig Cleanup dockerfile and add editorconfig 2018-02-16 13:44:15 -06:00
.gitignore Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
.gitreview Add gitreview file 2017-08-11 01:20:56 -05:00
Makefile Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
requirements.readthedocs.txt Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
tox.ini Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00

docs/README.md

Shipyard

Shipyard adopts the Falcon web framework and uses Apache Airflow as the backend engine to programmatically author, schedule and monitor workflows.

The current workflow is as follows:

  1. Inital region/site data will be passed to Shipyard from either a human operator or Jenkins
  2. The data (in YAML format) will be sent to DeckHand for validation and storage
  3. Shipyard will make use of the post-processed data from DeckHand to interact with DryDock
  4. DryDock will interact with Promenade to provision and deploy bare metal nodes using Ubuntu MAAS and a resilient Kubernetes cluster will be created at the end of the process
  5. Once the Kubernetes clusters are up and validated to be working properly, Shipyard will interact with Armada to deploy OpenStack using OpenStack Helm
  6. Once the OpenStack cluster is deployed, Shipyard will trigger a workflow to perform basic sanity health checks on the cluster

Note: This project, along with the tools used within are community-based and open sourced.

Mission

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.

Getting Started

This project is under development at the moment. We encourage anyone who is interested in Shipyard to review our documentation

Bugs

If you find a bug, please feel free to create a GitHub issue