We have not yet implemented global way to validate bool options in
OpenStack. To keep the implementation simple and consistent across
the modules/parameters, this change removes the current strict
validation for now.
Change-Id: Ida223d6d06d3538b8c2f7b430db233782b3ba500
The purge_config parameters only accept boolean values. This enforces
that using the typed parameters.
Change-Id: Iecf1322669c06feed46bbe02eaeee48b929fc000
These parameters were deprecated in favor of the separate classes for
client options[1].
[1] 0d043d793f
Change-Id: I28b7462f2330409b9dee7debba63ce756a0a74b1
This change introduces support for [clients] parameters and
[clients_<service>] parameters, which determine behavior of service
clients used by heat for communication with the OpenStack services.
- Implementation of heat::clients::<service> are generally same.
Only cinder, heat, keystone and nova provides additional parameters.
- The existing parameters in the base heat class are deprecated in
favor of the new classes.
Change-Id: Icdf4f0201dd1e5f93a450473709851977ec20034
This change introduces the new heat::trustee class to manage
the parameters in the [trustee] options. These options have been set
according to authtoken parameters but it makes maintenance complicated
and the logic doesn't work properly when noauth is used.
This change also removes the [trustee] project_domain_name parameter
because the parameter has never been used actually.
Change-Id: I694a8ea771cc4d4dcfbf8384ece2be10d83ab3f0
... because the max_stacks_per_tenant parameter is used by heat-engine,
and the very similar max_resources_per_stack parameter is implemented
in heat::engine.
Change-Id: I57a8e8b9643d999c8ed379895f998ee1d09fb1a8
The default of 100 is barely useable. Let's add a new parameter
max_stacks_per_tenant to allow increasing this.
Change-Id: I2bd9ce729b5e2b5ff6577951989b93390cb3a6bf
oslo.messaging RabbitMQ driver have now a new option that allow user to
run the RabbitMQ heartbeat over a native python thread.
These change allow user to use this new option.
Change-Id: Ifa7b63cf0e0f276c4bdfc1b840506303355647b1
Closes-Bug: #1840868
So that we can increase it from the default 114688
Useful in case for example the OS-Federation mapping is too large.
If this limit is breached heat will return a 413 Entity Too Large
and not log anything to heat.log.
Change-Id: I90f15091088db67e6d33ef6272e59de69c4fe601
Closes-Bug: #1835161
This changes all the puppet 3 validate_* functions
to use the validate_legacy function.
The validate_legacy function has been available since
about three years but require Puppet >= 4.4.0 and since
there is Puppet 4.10.12 as latest we should assume people
are running a fairly new Puppet 4 version.
This is the first step to then remove all validate function
calls and use proper types for parameter as described in spec [1].
[1] https://review.openstack.org/#/c/568929/
Change-Id: I422be4bfb6fd6f73f0b24ae9464c5c85689594e1
Remove the deprecated rabbit params which has been deprecated for
two years. The default_transport_url has been present for a while
now and should be used.
Change-Id: I9c95be8843e51ac69c95d141507d767aa017afbf
Idb0f408776ef27f16a522e4443531fd97276669b switches to use
www_authenticate_uri but it is not backwards incompatible for folks who
have yet to switch to use www_authenticate_uri. We should still support
auth_uri for the time beaing.
Change-Id: I132fa8ebf91e932cd7fbc610dccd332348d52d49
Closes-Bug: #1764598
By default, the ::heat class configures clients_keystone/auth_uri to the
value of ::heat::keystone::authtoken::auth_url, which is generally the
admin endpoint on port 35357.
However, since this URI can be used by non-admin clients running inside
instances, such as os-collect-config, a better default value would be to
use either the public or internal Keystone endpoint, depending on the
deployment. This commit changes the default to the public Keystone
endpoint defined in ::heat::keystone::authtoken::www_authenticate_uri.
It is still possible to provide a custom value using the
heat_clients_keystone_uri parameter.
Change-Id: Idb0f408776ef27f16a522e4443531fd97276669b
Closes-Bug: #1763700
It is usually the same as auth_url which is defined there
$::heat::keystone::authtoken::auth_url. We can now point this to
another part of the catalog (ie, public vs internal for instance).
Co-Authored-By: Sergii Golovatiuk <sgolovat@redhat.com>
Change-Id: I4429d86d831f49f1bc0fef04379a81ada20b6ab6
Param keystone_ec2_uri was providing default value. It was raising an
engine service error on ifras where ec2 endpoint was not created.
Change-Id: I48c47a2c59ec89212a45125b373844e340731fd9
Param heartbeat_timeout_threshold by default is set to 60 in oslo module.
We shouldn't set hardcoded value, but take default one.
Change-Id: Id572fd98846f640d88cbb46c4a74f9fd43813d8b
Oslo.messaging uses the transport_url to represent the rpc and
notification messaging driver to use and its full configuration. The
rpc_backend configuration option is deprecated for removal and
should not gate oslo.messaging driver configuration options.
This patch:
* deprecate rpc_backend
* remove conditional check
* update spec tests
* add release note
Change-Id: I1537c9e0db956d4271c8334a0aa543cd20c57e67
Now TripleO sets this value, we can use os_service_default for
the default value and we won't have duplicated resource.
Change-Id: I00a47d6dae5be6ea18d93ac8b47c0c0cc58fe43f
Add support for clients/endpoint_type parameter.
Note: Default to False now, because TripleO already sets this resource.
and we don't want duplicated resource.
Once we switch TripleO to use this new option, the default will
become os_service_default.
Change-Id: If707c5623c0e34e9219eeafdafaf0ac42daf5c8d
Closes-Bug: #1675409
The rabbitmq connection parameters have been deprecated in favor of the
transport_url setting.
Change-Id: I7ae5c5a2584eab063b8e647dc34008ac71bd04e0
Related-Bug: #1625198
Since we are in ocata lets remove all old parameters in api
to configure the keystone_authtoken section
Change-Id: I7f18b79b9107baad78129b098246bd9c931420dc
Option "auth_plugin" from group "trustee" is deprecated in Heat.
Use option "auth_type" from group "trustee" instead.
Change-Id: I19024ad7be968c7364dbb8ff94372a168f6f6096
Closes-Bug: #1633282