This replaces the provider implementation of heat_config type so that
MultiStrOpt, which is used by several options like
- oslo_messaging_notifications/driver
- oslo_policy/policy_dirs
is handled correctly.
Change-Id: Ifb3a302e1e15b496761112936c847217ec2116cc
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 Heat API and api-metadata. Therefore, this patch adds
two new heat_api_uwsgi_config and heat_api_cfn_uwsgi_config
providers as well as two new heat::wsgi::uwsgi_api and
heat::wsgi::uwsgi_api_cfn classes.
Change-Id: I0e226046f6e2d69c89681948cee8e8830c186489
... so that correct packages are required according without re-defining
them in resource implementations.
Change-Id: Ia8e6256af44b29b9f3e5aa2ff3c7eeb6e7835a15
With the creation of the new openstack_config provider, some processing
that was done in heat_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 :
heat_config { 'DEFAULT/foo' : value => 'bar' } # will work as usual
heat_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>' } # will mean absent
That means that all the current :
if $myvar {
heat_config { 'DEFAULT/foo' : value => $myvar }
} else {
heat_config { 'DEFAULT/foo' : ensure => absent }
}
can be removed in favor of :
heat_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 :
heat_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>',
ensure_absent_val => 'foo' }
Change-Id: Iaaf2e5755080ef32d7d585465aaea6fd408d0ece
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: I6476060c97d350640b5a254738a60e319ad522e9
In puppet-neutron, keystone_v2_authenticate already exists and is in
colision with the keystone_v2_authenticate in puppet-heat.
While we move the whole method in puppet-openstacklib, let's just rename
the method from keystone_v2_authenticate to keystone_v2_auth.
Closes-bug #1429096
Change-Id: I15b6d0550bb3baef37d7536d264b822768802ad0
There is issue with ipv6 where address has to be in brackets, this causes the
underlying ruby TCPSocket to fail. Net::HTTP.new will fail without brackets on
joining the ipv6 address with :port or passing brackets to TCPSocket. It was
found that if we use Net::HTTP.start with url.hostname the incriminated code
won't be hit.
Change-Id: Ia70e05098b52121d12b035bdab59685b086523db
Closes-Bug: rhbz#1185652
Currently secrets like rabbit_password or admin_password are laked
puppet logs when changed. This commit changes heat_*_config and
heat_*_ini types adding a new parameter that triggers obfuscation
the values in puppet logs.
Change-Id: Ib06a0f967dd5d5f8cc1c4dc7257c0e196786e8ae
Closes-Bug: #1328448
Since we have now an only config file (heat.conf) with this patch:
https://review.openstack.org/#/c/36476/
This patch updates the module and delete old configuration files
support and add a test.
Also, I fixed some tab issues in manifests.
Fix bug #1207858
Change-Id: If3d044e2581156fa5ce4de19f5c740328efa0aa8