Like we do in other modules, include zaqar::policy class in
zaqar::server so users can define policies without taking care of the
class.
Change-Id: I9f549f11bd4e939ad41ff77c51dd2f32338621c8
To be able to use the swift backend, we may need to configure Zaqar to
have the proper role to access Swift. This exposes the roles parameter
to allow that.
Change-Id: I9ce1bbc18d02383a5cdd3edbcf8c65c90165fb53
This adds support for running swift as the messaging backend of Zaqar,
and SQLAlchemy as the management backend.
Change-Id: I448d303d01e33a0d89625d7ff442b652838d9c36
All db settings should be applied and all releated packages should
be installed before dbsync starts.
Change-Id: If5d4076315df5d4d5c9672a8265c126bf4d06ab8
The python-memcache package is required if using memcached. By
default the package is not installed and the define has it set to
false. This change allows managing the python-memcache package
install from the authtoken class.
Change-Id: Id0d980618cd3816172e491b20058d540d6d1ed41
The signing_dir is deprecated for removel because of PKI token format
is no longer supported.
Update warning message and release note.
Change-Id: If82b345969da11d2187a7919fd213275f1cf8339
Closes-Bug: #1652700
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
We can add suport for Debian system due to have the
zaqar package in Debian system.
The Debian system does not support the use of services to run
a second instance, because there is no zaqar-server@.service
in zaqar package, so do not test it. I will Re-test it after
the zaqar package solve the problem.
Change-Id: I026b7d8f2b5994114d5a319200ed7c7d099b4fb5
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
If db sync fails, it is never retried leading to errors. So, this
patch adds retries for db_sync to avoid sync fails.
Change-Id: Id89665099079ab5e4c468f7f30953762a248af01
Closes-Bug: #1628580
User[zaqar] is not in the catalog, don't try to require it, it doesn't
exit!
The dbsync is run after package management so we're good.
Change-Id: Ie642f9ec6e6acc0765bc88ec4438a01a5618563b
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
Adds a new zaqar::keystone::auth_websocket class to help
create a 'messaging-websocket' Keystone endpoint. Users of
zaqar websockets currently have to do substring replacement on the
Zaqar HTTP URLs... having a dedicated endpoint for websockets will
be much better.
Change-Id: Idd3ca1765604d9a461f68fc7b4a18b23a3c19d5b
This change updates the zaqar::keystone::auth class to include a default
service_name of 'zaqar' so that if a user changes the auth_name, the
service is still created as being related to 'zaqar'. This improves the
user experiance when they want to customize the usernames for services.
Change-Id: I2977790c3558732c2a1773aa3ede834c1d62ca16
Closes-Bug: #1590040
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
This change updates the tests to use rspec-puppet-facts. Additionally
this change fixes the relationship in zaqar::server_instance for Debian
based systems.
Change-Id: I03ce4ee17feec1f0ea7012ea116c9c12cf3bde5f
This class manages N instances of zaqar-server each using an
alternate /etc/zaqar/n.conf file to control select service
settings which take priority over settings in /etc/zaqar/zaqar.conf.
The primary use case for this class would be to enable websockets
alongside of wsgi. The only way to do this with Zaqar today is
to run multiple processes.
Change-Id: Ib730206ece73efe57aca7df4a65c906e95cdd606
Update the defaults for keystone::auth so that they are
consistent with the project (python-zaqarclient, etc.)
Change-Id: I317fb47a1326eb577dd0fa8ec5eb2d7ac842c4af