... but test interfaces of that resource type. This helps us avoid
direct breakage caused by any change in puppet-keystone.
Change-Id: I62e146e2736f2702ca7dc82e03c8a26cd1df1a55
... because these were deprecated during Wallaby cycle[1]. Actual
implementation was also removed from Octavia during Xena cycle[2].
[1] 46cffbd1e9229f587f3b6c703f4964aec4bab452
[2] 815a283823121d563562474eb9048673a95f6e1f
Change-Id: Ia516256b9a1acc7790bfaf58c1f17e558fe4a139
This change introduces the new purge_config parameter to the policy
class so that any policy rules not managed by puppet manifests can be
cleared.
Co-Authored-By: Martin Schuppert <mschuppert@redhat.com>
Depends-On: https://review.opendev.org/802305
Change-Id: I3b58daf4d70bd31a3a91a7e631ecc894fb42debe
The authtoken parameters are not managed directly but managed by
the keystone::resource::authtoken class. Thus we should avoid testing
parameters directly otherwise any change in the resource type can
cause test failures.
Change-Id: I1c0d708e710c14ca6214dafb0b15757838cfbb4d
This change adds the 'params' hash in authtoken class, to implement
the same functionality as the one recently introduced into
puppet-nova[1].
[1] 5c38281e1b698f157f03bf1815733277c541c30b
Change-Id: I323d49030db642bc06402306250b177923e02486
This replaces the provider implementation of octavia_config type so
that MultiStrOpt, which is used by several options like
- oslo_messaging_notifications/driver
- oslo_policy/policy_dirs
are handled correctly.
Change-Id: Ic8da2858b4c512d31ebbf78a128367d152cf7616
The following parameters in octavia-controller are defined as ListOpt
which accept comma-separated list.
This change ensures that the corresponding parameters in puppet-octavia
accepts list values and convert these values to strings in the proper
format.
- controller_worker/amp_secgroup_list
- controller_worker/amp_boot_network_list
- health_manager/controller_ip_port_list
- amphora_agent/admin_log_targets
- amphora_agent/tenant_log_targets
Change-Id: I6564e94550ea66f18fd99780a4c990fd18b4da4d
The driver_agent/enabled_provider_agents is not a MultiOpt but ListOpt
so should look like comma-seprated list. We should not pass puppet list
directly which leaves only the first element written in octavia.conf .
Change-Id: I38cb0015fc88079d26cff779b7d9b99c641a9fa1
This change defines manifest_dir and module_path expicitly in unit
tests so that modules installed under fixtures directory is properly
loaded.
Closes-Bug: #1930403
Change-Id: I1645afb89e33cfe03e25b09c446e2d47fc6b9f18
This change ensures that service resources are not declared when
manage_service is false, to fix rspec-puppet 2.7.1 support.
Change-Id: I86e05c5182842b73d413ddc95f797c1da5fd0ac2
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 Octavia API. Therefore, this patch adds a new
octavia_api_uwsgi_config provider as well as a new
octavia::wsgi::uwsgi class.
Change-Id: I89e2bb5bb127020adcaabe26e62f68123fab3990
This patch makes it possible to override the current service default,
which is /etc/<service>/policy.d .
Change-Id: I4a81d4666f52e0305a5ef9880b0f42023cca5f08
Currently we define default values for *_driver parameters in
puppet-octavia but all of the default values are same as the defaults
defined in Octavia itself.
Let's remove the default definition and use service default, to make
it easy to keep consistency with Octavia itself.
Change-Id: I521e8fedf09b25c7a8d6a5f2c67d04f586744bcd
This patch implements a new parameter named pagination_max_limit into
octaiva::api, so that operators can configure that parameter by puppet-octaiva.
Change-Id: Id8c389c136de34fd9d6d9fd762a3bf96f5d02267
This cleans up remaining usage of the idle_timeout parameter which was
removed[1], to fix the failing unit test case asserting the parameter.
[1] 3eb0e709473d53bc9a26c672c10486828d84d50f
Change-Id: Iae57938166d831f4b0b4a449d64181239fe912c7
This change renames parameters of octavia::quota options, so that we
use consistent parameter names with the definitions in Octavia.
Change-Id: I63a585b34eaeb5350dbbd72936b4949ebd96e0f0
As Openstack projects continue to have longer database migration
chains, the Puppet default timeout of 300 seconds for an execution
is becoming too short a duration on some hardware, leading to timeouts.
As projects continue to add more migration scripts without pruning
the base, timeouts will continue to become more frequent unless
this time can be expanded.
Change-Id: Ia1ccd4583f883c3f4efe692043f134ec3991decc
Closes-Bug: #1904962
