... so that we users can use '<SERVICE DEFAULT>' similarly to
the resource types to manage the <service>.conf files.
Closes-Bug: #1981118
Change-Id: Iefc9b16662603fd8fc410c9080cb13b603bd4cf5
The api-paste.ini accepts not only "=" but also ":" and some services
like Barbican have been using ":" for their default api-paste.ini
files.
[composite:main]
use = egg:Paste#urlmap
/: barbican_version
/v1: barbican-api-keystone
This change allows users to use ":" so that they can update the ini
files with keeping it consistent with the default fules
Depends-on: https://review.opendev.org/813614
Change-Id: Ibde258e605c827ef042ae7f4c32db15c816fd038
This replaces the provider implementation of gnocchi_config type so
that MultiStrOpt, which is used by several options like
- oslo_policy/policy_dirs
are handled correctly.
Change-Id: I6a99bd57ad8e3713e824e4394b6fc2125167a768
On each puppet run, I'm seeing:
value changed ['12'] to '12' (corrective)
Therefore, this patch switches from :openstackconfig to :ini_setting
to make the 2nd run not changing anything.
Change-Id: Ib674673edec143841aa88d754ea2e9b0cb13be1a
This patch is adding the configuration of the number of workers,
threads, and the size of the listen queue in Debian, which uses
uwsgi to run Gnocchi API. Therefore, this patch adds a new
gnocchi_api_uwsgi_config providers as well as a new
gnocchi::wsgi::uwsgi_api class.
Change-Id: Iea9a674be86902be46fdc124e6d0ecf0c1ec8961
When reading credentials from the configuration's keystone_authtoken
section www_authenticate_uri was used as URL for Keystone.
As www_authenticate_uri is a public endpoint that is not necessarily
reachable for the Puppet agent, this change uses the more appropriate
auth_url as Keystone URL.
Change-Id: I9b2e85842fb9a6ec75158bc612b47a4b64f169f9
Option auth_uri from group keystone_authtoken is deprecated[1].
Use option www_authenticate_uri from group keystone_authtoken.
[1]https://review.openstack.org/#/c/508522/
Change-Id: Ie5ea4578879fc8aa21bb27e228b1eea52200cdb7
Depends-On: I4c82a63baabd6b9304b302c97cd751a0103d8316
Closes-Bug: #1759098
Create a new class to handle the keystone authtoken configuration
utilizing the keystone::resource::authtoken resource.
Some deprecations:
- gnocchi::api::keystone_user is deprecated in favor of
gnocchi::keystone::authtoken::username.
- gnocchi::api::keystone_password is deprecated in favor of
gnocchi::keystone::authtoken::password.
- gnocchi::api::keystone_tenant is deprecated in favor of
gnocchi::keystone::authtoken::project_name
- gnocchi::api::keystone_identity_uri is deprecated in favor of
gnocchi::keystone::authtoken::auth_url.
- gnocchi::api::keystone_auth_uri is deprecated in favor of
gnocchi::keystone::authtoken::auth_uri
Change-Id: I7be1c8f471472e74642e25508c6871d0f948d75b
Related-Bug: #1604463
Add gnocchi_api_paste_ini type/provider for Gnocchi.
Also add the capability to configure api-paste.ini with config.pp.
Closes-bug: #1483371
Change-Id: Iae097c5cee3f43c5fb801550c9d038ccb652a1b5
With the creation of the new openstack_config provider, some processing
that was done in gnocchi_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 :
gnocchi_config { 'DEFAULT/foo' : value => 'bar' } # will work as usual
gnocchi_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>' } # will mean absent
That means that all the current :
if $myvar {
gnocchi_config { 'DEFAULT/foo' : value => $myvar }
} else {
gnocchi_config { 'DEFAULT/foo' : ensure => absent }
}
can be removed in favor of :
gnocchi_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 :
gnocchi_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>',
ensure_absent_val => 'foo' }
Change-Id: Ie8dce6e9d4c1027bd1f7d8653a4fa6fe28b696d9
Depends-On: I0eeebde3aac2662cc7e69bfad7f8d2481463a218
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: I3b0df55fa4d827934185f8e213ad89d360fb56a0
Takashi Kajinami