This adds support for running swift as the messaging backend of Zaqar,
and SQLAlchemy as the management backend.
Change-Id: I448d303d01e33a0d89625d7ff442b652838d9c36
This adds defined anchor points for external modules to hook into the
software install, config and service dependency chain. This allows
external modules to manage software installation (virtualenv,
containers, etc) and service management (pacemaker) without needing rely
on resources that may change or be renamed.
Change-Id: If4f585264f5f5a15549855d97b532866d91f5215
Since we are in ocata lets remove all old parameters in api
to configure the keystone_authtoken section
Change-Id: I4950c5dba0eb257412fe2d2d39f1780b431c05d4
Add the option in order to facilitate management.
User can ensure that only the options they hoped
are configured.
Change-Id: Iade2197388b1aa114f2fd9e2ab53a62f1f45c4e9
In zaqar, use keystone::resource::authtoken to configure
keystone_authtoken section in the configuration file,
with all parameters required to configure keystonemiddleware.
This patch will allow to deploy zaqar to use Keystone v3 authentification.
Some deprecations:
- zaqar::identity_uri is deprecated in favor of
zaqar::auth_url
- zaqar::admin_user is deprecated in favor of
zaqar::username
- zaqar::admin_password is deprecated in favor of
zaqar::password
- zaqar::admin_tenant_name is deprecated in favor of
zaqar::project_name
Change-Id: Ie825ce4d88ca4a2a33a7ced6e413ddc59f28ef1c
Related-Bug: #1604463
This patch adds parameters to configure the storage/*_pipeline
parameters for zaqar. These parameters are quite useful is you
wish to recieve notifications for Zaqar. In particular the
message_pipeline would often get set to 'zaqar.notification.notifier'
so that messages that have been subscribed to could be recieved.
Zaqar upstream has these set to nothing upstream so for now
setting the default to $os_service_default seems reasonable.
Change-Id: I14eade5ef0ac64f8856bfa455c4f9aaf51dd6c8d
