The zaqar::server_instance resource type allows setting up multiple
instances of zaqar-server by creating /etc/zaqar/{name}.conf .
Currently there is no validation about the name and if it can be set to
'zaqar' which results in conflicting management of zaqar.conf .
This change introduces a simple validation logic to make sure that
the resource type uses a config file different from the base
zaqar.conf .
Change-Id: Idb0eaff24e84121e0c78daf659d5b9f861491faa
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
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 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