... because it is actually required so that zaqar can authenticate with
keystone.
Depends-on: https://review.opendev.org/903852
Change-Id: I8e5ea733f10abfdcc5da0699311222cfbe6cbf4e
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
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
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
Takashi Kajinami