5a9abc73dd
While iterating on the next steps of using notes, it became clear that several changes to the output and access methods for notes needed enhancements. This change introduces a new way to access a note's URL information via a new API/CLI, while removing the resolution of URLs from the existing note output. This supports the concept of "builddata" coming back with sizes of 800kb or more - which really can never work out inline in other data, especially in cases where there is multiplicity of the information across many items. New API: GET /notedetails/{id} CLI: shipyard get notedetails/{id} and/or shipyard get notedetails {id} Returns the resolution of the URL for a note, outputting the raw info as the response (not structured in a JSON response). The CLI will attempt to minimally format the response if it has inline \n characters by replacing them will real newlines in the output (if the output-format is set to either cli or format. Raw format will be returned as-is. The existing notes responses are changed to not include the resolution of the URL information inline, but rather provide the text: Details at notedetails/{id} The CLI will interpret this and present: - Info available with 'describe notedetails/09876543210987654321098765' This is an attempt to inform the user to access the note details that way - luckily the API and CLI align on the term notedetails, as the word details works well enough in the singular form presented by the CLI and the plural form used by the API. The ID returned is the unique id of the note (ULID format). Notes that have no URL will return a 404 response from the API (and an appropriately formatted value from the CLI). This approach solves an issue beyond the large inline values from URLs; providing a means to NOT resolve the URLs except in a one-at-a-time way. Long lists of notes will no longer have the risk of long waits nor needing of parallelization of retrieval of URLs for notes. This change introduces an API-side sorting of notes by timestamp, providing a chronological presentation of the information that may or may not match the ULID or insertion ordering of the notes. Additional feedback from peers about the output of noted indicated that the CLI formatting of notes in general was in need of visual tuning. As such, this change introduces changes to the formatting of the output of notes from the CLI: - Notes for describing an item will be presented with a more specific header, e.g.: Action Notes: or Step Notes: instead of simply Notes. - Tables with notes will change the header from "Notes" to "Footnotes" give the user a better marker that the notes follow the current table. - Table footnotes will be presented in a table format similar to the following, with headings matching the kind of note being produced. Step Footnotes Note (1) > blah blah blah > yakkity yakkity (2) > stuff stuff stuff stuff stuff stuff stuff stuff stuff stuff - Info available with 'describe notedetails/... > things things things Change-Id: I1680505d5c555b2293419179ade995b0e8484e6d |
||
---|---|---|
.. | ||
alembic | ||
etc/shipyard | ||
generator | ||
shipyard_airflow | ||
tests | ||
.coveragerc | ||
README.md | ||
alembic.ini | ||
entrypoint.sh | ||
requirements.txt | ||
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 Airship Undercloud Platform (UCP).
Shipyard provides the entrypoint for the following aspects of the control plane established by the Airship:
- 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 Airship via
Shipyard. Secrets, such as passwords and certificates use the
same mechanism.
The designs and secrets are stored in Airship'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 @ Openstack Gerrit
Helm chart