Kumar, Nishant (nk613n)
Policy validation in Deckhand was not implemented completely. Refer link below: https://airshipit.readthedocs.io/projects/deckhand/en/latest/users/validation.html#policy-validations This PS removes some of the code related to the feature which was being used in a code path when a set of documents are uploaded to Deckhand. In standard Airship deployments the number of documents could be quite high and this leads to significant delay (more than 300seconds in some cases). As there are no plans to implement the policy validation feature, it makes sense to remove it from code path which could cause delay and sometimes timeouts while uploading documents. This has been tested on a Baremetal lab: GF and BF. Change-Id: I2ff3f40a7fe37bed5a589fab00d829db726604fe
|7 months ago|
|.github||2 months ago|
|alembic||1 year ago|
|charts/deckhand||3 months ago|
|deckhand||2 weeks ago|
|doc||2 weeks ago|
|etc/deckhand||1 year ago|
|images/deckhand||3 months ago|
|releasenotes||2 years ago|
|tools||3 months ago|
|.coveragerc||2 years ago|
|.dockerignore||2 years ago|
|.gitignore||1 year ago|
|.gitreview||1 year ago|
|.stestr.conf||2 years ago|
|.zuul.yaml||2 months ago|
|HACKING.rst||1 year ago|
|LICENSE||2 years ago|
|Makefile||3 months ago|
|README.rst||1 year ago|
|REVIEWING.rst||1 year ago|
|alembic.ini||2 years ago|
|bindep.txt||1 year ago|
|entrypoint.sh||2 years ago|
|requirements.txt||3 months ago|
|setup.cfg||7 months ago|
|setup.py||2 years ago|
|test-requirements.txt||4 months ago|
|tox.ini||7 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: