Tuskar is not maintained anymore.
Further maintenance should be done in stable branches, but master is no
longer supported.
Change-Id: I957ef8dc587086f32c918676a66dd8e247e50280
Rely on packaging dependencies to avoid issues caused by different
package names between Fedora and RHEL (python-PyMySQL vs python2-PyMySQL).
https://review.openstack.org/#/c/245229/4/spec/classes/neutron_db_spec.rb
includes all the discussion that led to this.
Change-Id: Ic8ec00e47b01bc2963018af7accc4a8a1eff8060
https://review.openstack.org/#/c/228744/ has been merged, we need to
drop the 'tenant' parameter to Keystone_user resource.
Change-Id: Idaed260a9c1ad0c0e8400dd9ad4360ed0b39fbc6
This patch introduce the same design than mysql for postgresql
by requiring dedicated lib::python class instead of declaring
a new resource package within tuskar module.
Change-Id: I374ee4ae7b3f6affc17f440e471d147414f4605a
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: I154e5ab5623b932fc3c550f7969a39993f38a3cf
Currently logging configuration is splitted in two distinct classes,
the api.pp and the logging.pp classes. This review aims to centralize
all logging related parameters in a single class, the logging.pp one.
The impacted parameters are :
* use_syslog
* use_stderr
* log_facility
* verbose
* debug
* log_dir
* log_file
This change remains backward compatible with what is currently in place.
Change-Id: I6e56123217a38c384734d31e60699f7b76f7dc4a
With the creation of the new openstack_config provider, some processing
that was done in tuskar_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 :
tuskar_config { 'DEFAULT/foo' : value => 'bar' } # will work as usual
tuskar_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>' } # will mean absent
That means that all the current :
if $myvar {
tuskar_config { 'DEFAULT/foo' : value => $myvar }
} else {
tuskar_config { 'DEFAULT/foo' : ensure => absent }
}
can be removed in favor of :
tuskar_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 :
tuskar_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>',
ensure_absent_val => 'foo' }
Change-Id: I177eee770243749d0c63b90e1d8581c7c92f8b4b
Depends-On: I0eeebde3aac2662cc7e69bfad7f8d2481463a218
This patch is the initial modulesync run, it impacts:
* gitignore: just a sync between projects
* gemfile:
- update and allow to setup facter version and gem source
- split beaker gems with a dedicated group
- switch to rspec-puppet 2.2.0
* rakefile:
- use the new syntax for lint configuration
- add a acceptance target
* acceptance:
- sync nodesets
- update tests in order to use zuul-cloner
* spec: added rspec coverage report
Change-Id: I8721d7649dca32e67f25e59665075a3ca2a5afb0
Currently we specify the ordering of config resources wherever it is
necessary based on the presence of the file it will write to, or the
presence of the package in charge of providing the file it will write
to.
Those kind of ordering can be specified directly at the resource level
using the autorequire mechanism. With this patch, any config resource
will make sure the package in charge of providing the file will be
installed first.
Change-Id: If90d097129bad922511465345d577df37d84e78b
When running the tests, rspec will download the modules speficied in
.fixtures.yml and put them in spec/fixtures/modules.
Some of those modules still point to stackforge/ namespace when they
should be pointing to openstack/ namespace.
Change-Id: I0c61b1b879b78787fe8158977d8cc7ceffea3df7
In order to be able to take an action after all the packages of the
module have been installed/updated or all the services have been
started/restarted, we set a 'tuskar-package' and 'tuskar-service'
tag for each package and service of this module.
At the moment, there is a generic openstack tag that is not specific
enough if one wants to take action upon a single module change.
Use case :
If an action needs to be taken after all the packages have been
installed or updated : Package <| tag == 'tuskar-package' |> -> X
Change-Id: Ie80cdb04a7b9d5adb87bf13ab1adee963adae6af
Other modules provide an X::config class to be able to specify
parameters that are not yet part of the module. Tuskar was missing this
feature. This commit aims to add it for puppet-tuskar.
Change-Id: I651657170d10b31c8280581adea2e19a8419eadd
The gem 'puppet-lint-param-docs' was bumped to 1.2.0 and now handle
class and define type. This patch fix lint issues (missing documentation).
Change-Id: I4c4445b9d0a73bb555d04601d07fd34d2f61a480
This commit adds the service description as a class parameter in order to allow
users to update from a previous version if the service description is changed
(incorrectly spelled or wrong description)
Change-Id: I490dfdc96254967aff0acd64bf4cb2648820fe49
Closes-Bug: #1468407
Puppet Labs is in the process of releasing a 2.0.0 version of
puppetlabs-concat, which will have many breaking changes that affect
many dependent modules. Changes have been merged to master, but not yet
released. While we figure out what changes we need to make in our own
modules and wait for updates in dependent modules, we should just pin
to a stable version.
Change-Id: I66a152787e64ef780fd16311aebbb6c22ba0968b
Let migrate to the new openstacklib::db::postgresql helper for
postgresql backend. This commit also unpin postgresql fixture
(openstacklib support now the latest version of postgre module).
Change-Id: Ibf9bf074f1fb1712c0c5d70faa7d29a3b72bce29
Implements: blueprint commmon-openstack-database-resource
Implement tuskar::ui with:
* tuskar UI package
* optionaly and disabled by default, tuskar UI extras package
* allow to not manage the package
This patch also brings consistency with other modules/classes
in renaming ensure_package to package_ensure.
Change-Id: I8dd03dffbb2c36c7cdfc82681444cecb6e87021c
This changes the puppet-lint requirement to 1.1.x, so that we can
puppet-lint plugins. Most of these plugins are for 4.x compat, but
just catch common errors.
Change-Id: Ic7e3e5f2200c61760436d2c3b2f504e18248a15a
This patch aim to update our specs test in order to work with the
rspec-puppet release 2.0.0, in the mean time, we update rspec syntax
order to be prepared for rspec 3.x move.
In details:
* Convert 'should' keyword to 'is_expected.to' (prepare rspec 3.x)
* Upgrade and pin rspec-puppet from 1.0.1 to 2.0.0
Change-Id: Ic9ac859be612f2afc5486340e5aa8eaf83473ab4
Add puppet parameters lint (with puppet-lint-param-docs gem) and fix
missing documentations, this commit also fix manifest lint issues
(due to puppet-lint upgrade) and metadata.json file (SPDX license,
and open dependencies).
Change-Id: I52d00d76c42a51bcc632c856754fa930ba18bcc1