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
Bindep is a binary automation tool used in openstack-infra. With it,
projects can better control the default packages installed into the
OS. Because we are using puppet, we actually don't want any packages
installed by default as to better test our manifests.
Change-Id: Icc52372a90946e1874b42b52f677d29039e952c2
Co-Authored-By: Paul Belanger <pabelanger@redhat.com>
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
* Update CHANGELOG with release notes URL.
* Update README with new release number & name.
* Update metadata.json with new tag & dependencies.
* Add release note prelude for Mitaka.
* Update Reno release note to drop prelude.
* Improve release note landing page.
Change-Id: I55cb70b74940eeed95e911b4df24f8320f57fe6d
* drop reno note, because it's a new module
* add a note that explains it's a new module and the features
that are supported.
Change-Id: I52b2baf73ae5f06e7c852eeca0b745341913b02e
ReNo [1] is the release management tool in OpenStack.
This patch adds the basic structure to start using it.
* Update .gitignore
* Add a basic note "use-reno"
* Add releasenotes/ dir and basic files
* Add python files: setup.cfg, setup.py, test-requirements.txt and
tox.ini.
[1] http://docs.openstack.org/developer/reno
Change-Id: I10824be2c27e1476031fa4d591b666ddf1587e55
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
With the creation of the new openstack_config provider, some
essing
that was done in zaqar_config has been centralized in
openstack_config.
Impacted methods are :
* section
* setting
* separator
Also, this commit adds the fact that, when passing a specific string
(ensure_absent_val) the provider will behave as if ensure => absent
was
specified. '<SERVICE DEFAULT>' is the default value for
ensure_absent_val.
The use case is the following :
zaqar_config { 'DEFAULT/foo' : value => 'bar' } # will work as
l
zaqar_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>' } #
mean absent
That means that all the current :
if $myvar {
zaqar_config { 'DEFAULT/foo' : value => $myvar }
} else {
zaqar_config { 'DEFAULT/foo' : ensure => absent }
}
can be removed in favor of :
zaqar_config { 'DEFAULT/foo' : value => $myvar }
If for any reason '<SERVICE DEFAULT>' turns out to be a valid value
for a specific parameter. One could by pass that doing the following
zaqar_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>',
ensure_absent_val => 'foo' }
Change-Id: Iaaf2e5755080ef32d7d585465aaea6fd408d0ece
Update the defaults for keystone::auth so that they are
consistent with the project (python-zaqarclient, etc.)
Change-Id: I317fb47a1326eb577dd0fa8ec5eb2d7ac842c4af
mock is not used anywhere in the module, let's drop it.
This patch will help to hit this bug:
https://launchpad.net/bugs/1492636
Change-Id: I5e02370b5ab269eea88c6b29a21e4b6eaf7f5ac8
This change adds the rspec-puppet-facts gem to the spec helper so that
we can centralize the management of the base operating systems that we
support. rspec-puppet-facts allows us to simplify our unit tests and
provides a more complete list of Operating Systems and their associated
facts for the unit tests. With this change we can now loop over and
test CentOS, Debian, Fedora, RedHat, and Ubuntu by simply providing a
list of supported os to rspec-puppet-facts.
Additionally this change includes a central object for managing our
supported os list for rspec-puppet-facts and providing our default facts
like os_service_default. This central object should replace the usage of
@default_facts within the unit tests for each module.
Change-Id: Ib61c316e965662ee66c0c0a1f14759c3b7c888bb
This patch fixes the puppet forge namespace, and bump min dependency to Kilo
https://wiki.openstack.org/wiki/Puppet/releases.
Change-Id: I2640446d5dfd6bea6e43a52e016a813ef78a105f
Signed-off-by: Gael Chamoulaud <gchamoul@redhat.com>
https://review.openstack.org/#/c/228744/ has been merged, we need to
drop the 'tenant' parameter to Keystone_user resource.
Change-Id: I44064f0d8fab71cfccc1dda5b49b04200d5a66a2
In OpenStack Infra, we would like to run Puppet unit tests that
sometimes depends on other Puppet OpenStack modules.
Example: a patch in puppet-openstacklib that needs to be tested in puppet-nova.
This patch modifies the Rakefile to:
* clean spec_prep and spec_clean Rake tasks
* use openstack/puppet-openstack-integration/install_modules_unit.sh script
to clone modules.
* do not use .fixtures.yaml file to clone modules and rely on
zuul-cloner or git.
* Add openstack/ in gitignore so we never commit the
puppet-openstack-integration repository (can happen when spec_clean
did not run but you want to submit the patch anyway)
* Allow to run a custom Puppetfile if PUPPETFILE env is exported. It
will allow people to test the module with the dependencies they like,
feature we had with .fixtures.yaml.
Also add 'r10k' to Gemfile.
That way, we will be able to use zuul dependencies and run tests accross
modules like we do with functional testing.
Change-Id: Ie3476db0bcc7f4ab08d64dd63e71958e8b3f5ab2
