This adds a few more parameters so that we spawn less processes from
each service, to reduce resource footprint in our CI.
Change-Id: I30f32b6414960c341d64282d91b8f958c8996772
This enables usage of service user token for interaction with nova and
barbican to avoid failure caused by token expiration during operations.
This also enables service_token_roles_required option in authtoken
middleware to allow only users with the service role to use this
feature.
Change-Id: Id6b0aad7aa24af2b6d03d484ada23357828c4325
Currently we always use IPv4 for MySQL even in the test cases which are
supposed to use IPv6. This fixes that and ensures the expected ip
version is used.
Change-Id: I483f04376f29b75dcca20061ae381c7e71f26caf
Previously EC2 API is always deployed with IPv4. This fixes that and
ensure the appropriate IP version is used. This also fixes the wrong
endpoint urls (we have never enabled ssl for EC2 API).
Depends-on: https://review.opendev.org/872369
Change-Id: I9cf64609c4f2095ae0456388d3b05dd3a512b41f
This change enables memcache backend for authtoken middleware for
all services currently supported by this module.
In-process token cache was deprecated and memcache backend is
currently recommended.
Change-Id: I3599fd0318d617641bebcc4b990698d62f364289
Currently idempotency in Ubuntu is broken because of the below change
detected in collate in MySQL.
```
/Stage[main]/Keystone::Db::Mysql/Openstacklib::Db::Mysql[keystone]/
Mysql_database[keystone]/collate: collate changed 'utf8mb3_general_ci'
to 'utf8_general_ci'
```
Similarly to what we observed in the past about charset[1], it seems
MySQL in Ubuntu is automatically converting the collate value and that
is causing the "unexpected" change detected in the 2nd puppet run.
This fixes the idempotency by using utf8mb3_general_ci in Ubuntu to
avoid the mismatch caused by internal translation.
[1] 085d3569021441810c1dff7c8f4396003c690805
Change-Id: I56f31397669d3d7b08aa2e9808947141e003ab0b
We are observing the failure in Ubuntu integration job caused by
broken idempotency. It seems current mysql/mariadb in Ubuntu replaces
utf8 with uft8mb3 automatically and this behavior results in unexpected
change in second run.
This change ensures that we use utf8mb3 in Ubuntu to avoid such
mismatch caused by internal translation. Note this change is intended
to be a quick gate fix and the charset would be updated to utf8mb4
later.
Closes-Bug: #1929073
Change-Id: I7742120758057b5a00f1d093f355fda3791f4e02
This reverts commit 01f74c0ba5f0fce1a715255e45534853ee45cc42.
Reason for revert:
Now ec2api uses volumev3 by default so we don't need to set
it explicitly.
Depends-on: https://review.opendev.org/768182
Change-Id: I486c6f66294529544f0f2469ce2436bad935e957
In Puppet 3 there was a need to use absolute
names to prevent issues. Since Puppet 4 everything
is absolute by default which makes this not needed.
We need to change this everywhere so that we can
revert the pin in [1] that now prevents us from
using the latest version of the puppet-lint check
puppet-lint-absolute_classname_check that properly
checks that we dont use absolute names.
[1] https://review.opendev.org/#/c/697742/
Change-Id: I78b74fbeb08be7234189e4d266412fb7fb7a73c0
puppet-ec2api switched to www_authenticate_uri in
[1], update puppet-openstack-integration for the same.
[1] https://review.openstack.org/#/c/558441/
Change-Id: I02f4bf8328bd40a00a1901beb9c55d647cf13543
