4ccb4368ce
Under some circumstances, the payloads retrieved from Barbican do not match what was stored. This primarily affects surrounding whitespace[0], but the implications for passphrases are significant, and even for PEM encoded data, a difference in whitespace in a configmap is enough to trigger a chart upgrade. In general, the effort to align Deckhand document types with Barbican secret types adds complexity without tangible benefit. Barbican does no enforcement of the contents of the data, and if it did, that could lead to further incompatibilities. This change uses the 'opaque' secret type for all secret document types. Before storage (or caching), the payload is serialized using `repr`, and base64 encoded. Upon retrieval, the payload is base64 decoded and parsed back into an object with `ast.literal_eval`. [0]: https://storyboard.openstack.org/#!/story/2007017 Change-Id: I9c2f3427f52a87aad718f95160cf688db35e1b83
Deckhand
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.
- Free software: Apache license
- Documentation: https://airship-deckhand.readthedocs.io/en/latest/
- Source: https://git.openstack.org/cgit/openstack/airship-deckhand
- Bugs: https://storyboard.openstack.org/#!/project/1004
- Release notes: https://airship-deckhand.readthedocs.io/en/latest/releasenotes/index.html
Core Responsibilities
- layering - helps reduce duplication in configuration by applying the notion of inheritance to documents
- substitution - provides separation between secret data and other configuration data for security purposes and reduces data duplication by allowing common data to be defined once and substituted elsewhere dynamically
- revision history - maintains well-defined collections of documents within immutable revisions that are meant to operate together, while providing the ability to rollback to previous revisions
- validation - allows services to implement and register different kinds of validations and report errors
- secret management - leverages existing OpenStack APIs -- namely Barbican -- to reliably and securely store sensitive data
Getting Started
For more detailed installation and setup information, please refer to the Getting Started guide.
Integration Points
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.
Note
Currently, other database back-ends are not supported.
Though, being a low-level service, has many other Airship services that integrate with it, including: