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
Since [1], nova does not accept to create non-volume instances with
flavors with disk size to 0 so tempest tests fail.
This patch is creating disks with size 2GB to all flavors used by
tempest. cirros image is used in these tests so it should be fine.
[1] https://review.openstack.org/#/c/603910/
Change-Id: Ica694dee7ec0b9a5a7a1f998f50be4f339a42f5c
Also modify provision manifest to skip provisioning
some services.
The new scenario will be used for testing py3 services
starting with keystone and glance.
Also update puppet-apache reference to the required commit,
this can be updated once a new tag is released with the commit.
Change-Id: I55558f35068457175e2ef508f9e5989151db4aa2
https://review.openstack.org/#/c/480848/ changed required
flavor for murano from m1.small to m1.tiny for some tests.
Change-Id: If3c0564ae315b805f8589f535181fafdfb569023
* TEMPEST_FROM_SOURCE is set to true to install tempest from source.
* Added capability to use tempest rpm
* change the cirros image directory to /tmp/openstack/image
if the image gets firstly downloaded in tempest workspace,
Tempest init will fail to create tempest workspace.
* Create image_dir if not exists.
Change-Id: I349783ace314a3575e93e6c853a7756f0f9b85ac
It was suggested by Nova team to not deploying Nova API in WSGI with
Apache in production.
It's causing some issues that we didn't catch until now (see in the bug
report). Until we figure out what was wrong, let's disable it so we can
move forward in the upgrade process.
Note: we also need to fix orchestration in provision to make sure
Keystone is ready before creating nova flavors, and other resources.
Depends-On: I1688eae1369f6da2c7084dc3864d19708d15c78d
Change-Id: I4a0d999d5290785a416bbb11953fee7a5028a00b
Related-Bug: 1661360
In run_tests.sh we symlink a cached image to /tmp/openstack/tempest
or it is downloaded to that location using wget which is more reliable.
Let's use that instead.
Change-Id: I3777d9d035ceb31827b8df4264c2f7d213f50aea
Require to first create admin keystone before trying to create nova
flavors.
The reason of such a change is that we figured when running a single
node deployment, we need to make sure to create the flavor at the right
time in the catalog otherwise we have seen some cases where the flavor
was created before having Nova API actually working.
Change-Id: I299d4c372da702232eaa7cb34b690e372f56e701
This commit will add explicit dependencies in some resources in the
provision profile.
Without this change the CI does not pass on Puppet 4 because of the
change in default run order.
Depends-On: Ifc3f40ae1cb71c215b8a0bf6cd5f6d05101a6168
Change-Id: Iedfa6f78936676ba54ebb888734a3b381a2378e7
* 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
The current provision template creates an ovs bridge, but no port
is added to it, so the vs_port part of puppet-vswitch is not
exercised. Creating a dummy device and adding it to the bridge helps
testing that part.
Depends-On: I5878448a1616e127c3b39c5f1c446fea151ba202
Change-Id: Id5d41502c0c88799f55bcbc5db3c080c035d3a6e
The keystone documentation highly recommends disabling the admin_token
authentication after the initial bootstrap because it exposes a major
attack vector.
A patch in puppet-keystone [1] added the support to remove
admin_token_auth keyword from the pipeline lists.
This patch aims to use this new class when deploying Keystone.
[1] https://review.openstack.org/#/c/256248
Change-Id: Ic545005122a0f7b92b8a9d3f1e4978b397bfc9c2
* Deploy Gnocchi services
* Create default archive policy and archive policy rule
* Configure Aodh with Gnocchi which is used to evaluate the alarms for threshold
Note: Tempest does not fully support Gnocchi yet.
* test_alarming_api will work (Aodh) with Gnocchi
* test_telemetry_notification_api will not work (Ceilometer) with
Gnocchi. That's why we don't configure Ceilometer to use Gnocchi
dispatcher.
Depends-On: I4ed26d3e294e82c383afc443914b0d7bb1906e46
Depends-On: Ib818b5ae4fa301c6c496fe800ae45c9b0a73222c
Change-Id: I32e5f80e4eb8a5cd8fc07798aaf6d710332fcdda
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
