When pip is upgraded to 20.3, the pip dependency resolver is much more strict and will no longer install a combination of packages that is mutually inconsistent. These changes account for the fact that Shipyard imports Armada, Drydock, Promenade, and Deckhand. Having said that, with pip 20.3, the pip packages amongst those projects cannot conflict. A follow-up change may be needed if more conflicts are found.  https://pip.pypa.io/en/latest/user_guide/#changes-to-the-pip-dependency-resolver-in-20-2-2020 Change-Id: Id75acea82ddf5d915a8b8805e076dac49cab800f
|8 months ago|
|.github||1 year ago|
|alembic||8 months ago|
|charts/deckhand||8 months ago|
|deckhand||8 months ago|
|doc||8 months ago|
|etc/deckhand||3 years ago|
|images/deckhand||8 months ago|
|releasenotes||3 years ago|
|tools||8 months ago|
|.coveragerc||4 years ago|
|.dockerignore||3 years ago|
|.gitignore||3 years ago|
|.gitreview||2 years ago|
|.stestr.conf||3 years ago|
|.zuul.yaml||1 year ago|
|HACKING.rst||3 years ago|
|LICENSE||3 years ago|
|Makefile||1 year ago|
|README.rst||3 years ago|
|REVIEWING.rst||3 years ago|
|alembic.ini||3 years ago|
|bindep.txt||2 years ago|
|entrypoint.sh||9 months ago|
|requirements.txt||8 months ago|
|setup.cfg||2 years ago|
|setup.py||4 years ago|
|test-requirements.txt||8 months ago|
|tox.ini||8 months ago|
Deckhand provides document revision management, storage and mutation functionality upon which the rest of the Airship components rely for orchestration of infrastructure provisioning. Deckhand understands declarative YAML documents that define, end-to-end, the configuration of sites: from the hardware -- encompassing network topology and hardware and host profile information -- up to the software level that comprises the overcloud.
For more detailed installation and setup information, please refer to the Getting Started guide.
Deckhand has the following integration points:
- Barbican (OpenStack Key Manager) provides secure storage for sensitive data.
- Keystone (OpenStack Identity service) provides authentication and support for role based authorization.
- PostgreSQL is used to persist information to correlate workflows with users and history of workflow commands.
Currently, other database back-ends are not supported.
Though, being a low-level service, has many other Airship services that integrate with it, including: