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
keystone is creating default roles for member since [1]. This
is "member" and it's not configurable so we need to switch it
in p-o-i too to avoid conflicting names errors (keystone is not
case sensitive in object names).
[1] https://review.openstack.org/#/c/572243/
Depends-On: Icd91bd27d0c0f375d2e99e9c018d3971fc49ce18
Change-Id: Id838d69e4ace9b2ea6c2a9cc6f8fd079d2115dd6
Debian package uses swift:adm with 0750, let's not force something else,
as this makes the puppet run not indempotent.
Change-Id: I325e2f722b11deb51a1b8f40d21fddac4593834c
manifests/swift.pp attemps to create /var/log/swift using the syslog user
in Debian, but this user doesn't exist in this OS (it only exists in
Ubuntu). This patch fixes this.
Change-Id: I2ef53b6f5865eb0d42834d9c4580caea530d54c1
Swift after [1] requires directories to pre exist when
using mount_check=False, so we need to create the directories
in advance.
[1] https://review.openstack.org/#/c/500158
Change-Id: I136f481ad542b35d945c84c4348691392bfca5c3
In RDO-CI we are hitting timeouts in swift operations
intermittently when running swift tempest tests in
scenario002.
This patch increases timeout swift::proxy as default
value seems to be too low for slow hardware as the one
used in RDO CI.
Change-Id: I05da916f9cef54873aa70460a293f16c79c0d8b4
1) Remove usage of verbose in Trove.
2) Rename Tempest parameter.
3) Rename Swift parameter.
4) Update parameters for Heat so we use 'password' auth_plugin.
5) Remove metering_secret, replaced by telemetry_secret.
Change-Id: Id770a7b03323b72ba37317e48085d9c15f106bc1
If IPv6 is enabled (on centos7 now), deploy Swift using this binding.
Note: adding notes in TODO to also deploy memcached in IPv6 later.
Change-Id: I8c8e8e8870212765f8b8a0d639194e040963d6e0
* Deploy Self-Signed Certificates for both IPv6 & IPv4 deployments.
* Disable IPv6 for RabbitMQ now, for SSL reasons, will be enabled again
later in a next iteration.
* Deploy Ironic API under WSGI instead of eventlet.
* Switch Glance API, Ironic API and Keystone to SSL.
* Configure Tempest with SSL endpoints when needed.
* Reduce the Ironic tests because of [1].
[1] https://bugs.launchpad.net/ironic/+bug/1554237
Note #1: puppet-swift, and puppet-cinder will require some work to support SSL, so it's not
implemented in this patch.
Note #2: we don't enable SSL for Neutron because of
https://bugs.launchpad.net/neutron/+bug/1514424
Change-Id: Ib2b5289b6f5e82f43cf60dee3152b2c2ddd5a014
Reducing workers will help us to consume less memory reduce the number
of timeouts we have in upstream CI.
* Neutron & Swift: reduce from 4 to 2 workers
* When possible, set workers to 2: aodh, ceilometer, gnocchi.
Change-Id: Ie064a9ad0389f112bbb69f4253f7f6dbc26deb0a
mount_check is about [1] to change from False to True in puppet-swift.
This patch keeps this parameter to False which is required to make Swift
working All-In-One in our CI.
[1] https://review.openstack.org/#/c/261333/
Change-Id: I0bb1ccf4c0adc4e217e2989bd50d96741fa156f7
Create manifests for each project and include them in the right
fixtures manifests, so we can reduce the code and avoid dupplicated
puppet manifests.
Change-Id: I66a98691b3014998f4c2529d2e3389ef1cbcc5f4
