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
Moves all the <module>::debug parameters
to be set in <module>::logging::debug instead.
This is so that we can remove the deprecated
logging options in the init classes of all the
modules.
Change-Id: I107be315a6e1a0429c32d02b9a1df8a8957bb7ab
This reverts commit 1d884ac12d340c94c58aad004ca0cf76219df97f.
Indeed, using uwsgi doesn't work over SSL. After trying locally on
my machine, switching back to mod-wsgi-py3 fixes the problem.
Change-Id: I577ac720ef6f9a5487cfbc9f6376f2535d918520
puppet-cinder switched to www_authenticate_uri in
[1], update puppet-openstack-integration for the same.
[1] https://review.openstack.org/#/c/558453/
Change-Id: Ie2d166a56409fa2b7d85ee58d30193687344e831
Cleanup but use the default key_manager class when barbican isn't
deployed.
Also use the new keymgr_backend parameter, since keymgr_api_class is
deprecated.
Depends-On: I6f015a4ed4980d37622bb2931477af916cfc9003
Change-Id: Id3fd2123823d6ad8406ee93211cad76bdf9b4fc7
This will test the functionality of the cinder-backup installation
regardless if it is configured or not.
Change-Id: Ifd37eb1fbf5b2726955da2e891d8149019a34452
https://review.openstack.org/#/c/505752 has switched to use
key_manager.backend which is set by default to 'barbican'.
However, until fix in cinder [1] is merged, cinder expects
it to be a full class path. Castellan uses key_manager/api_class
to resolve key_manager.backend so, setting this parameter
to an existing class will fix jobs until [1] is merged.
[1] https://review.openstack.org/#/c/468252/
Change-Id: If25905cf4826b7e14d9699b70e2f524c12d1d813
This patch refactors all creation of RabbitMQ resources such
as users and ACLs to a define called openstack_integration::mq_user.
This will make sure RabbitMQ is automatically installed as well,
as there are times where dependencies to RabbitMQ are added to things
like Keystone which break Beaker tests in other repos (but we don't
know they're broken until the change merges).
In addition, instead of setting up dependencies on the tagged services,
we use the anchors provided which should hopefully test against them
as well.
Change-Id: Ib122ddd105529de5e12389cc9db2e4e09ec4ad54
Introduce configuration parameters to specify the oslo.messaging
rpc or notification backend as one of rabbit, amqp. The default
config is to use rabbit broker for both rpc and notification. Selection
of amqp for rpc will use brokerless qpid-dispatch router.
This patch:
* Adds notification_transport_url parameter across services where needed
* Adds rpc and notification parameters to config
* Adds qdr for rpc amqp1 configuration
* Modifies scenario001 for dual messaging backends
* supports ssl config
Depends-On: Id6ebc4ce8b0ffdb0be92a758dbf89c84c3274725
Change-Id: Ia2a79a2e1482f6f72426bc81c8e6d2a04cb211e3
The rabbit_host, rabbit_hosts, rabbit_userid, rabbit_password,
rabbit_port and rabbit_virtual_host parameters are being deprecated.
This change updates the p-o-i tests to use the default_transport_url for
the rabbit connection instead.
Change-Id: Icb15ad3b5d75a35afcb685f4ae03c5755031fc3d
Depends-On: I43ac3079da9e52179457ca1a34f4faee60d5617b
Depends-On: Ie63457370ae37ef5af5878b1a97b8bafa80a8189
Depends-On: Ia0c5b5072431bbc186c8b96b7f034e68e9248af3
Depends-On: I43500ac7be4296ea534266fa14ca37fc700b0092
Depends-On: If4dfe8b82518fc4e590731a805ee3115b11f4f47
Depends-On: I00d4782693c1f67b82673624d4d36822c9762303
Depends-On: If83c0f0e61a08061334536399a42767a305966b7
There is already manage_volume_type parameter to manage cinder volume
type in cinder backend class, so we can use the parameter instead.
Change-Id: I6375ff506483e0481624a2295f7365cace45126d
Configure cinder backup to use swift and test
Change-Id: I9b645b2e7b76e97403b95459578979ec9f53c0b4
Depends-On: I588c9864cd20c75de7caecf733603a3587c34d12
Deploy Cinder API in WSGI with Apache instead of eventlet.
Change-Id: I6e6fb66cf79c43e063a2f4b3fea1017dd4ccd661
Depends-On: Ia1d3cfaa5ce6e4719b6c008bcc4f75d3c1db3487
This is a first iteration of testing IPv6 deployment.
This patch will deploy scenario002 on centos7 by using IPv6 network.
To make it work on Ubuntu, it will require more work, that will be done
in future iterations. During my testing, I found some bugs and did not
investigate because I wanted a first scenario working on v6.
Same for scenario001 and scenario003, they'll be tested later.
Change-Id: Ib28b379645b5a3d351438e0408a9de62b9f48302
* 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
* Configure RabbitMQ to bind on IPv6 (scenario002 only).
* Configure OpenStack service to connect with an IPv6 on
RabbitMQ (scenario002 only).
Change-Id: I0e4ab4b03d7b1c7bb47c55a751bc04f29292a621
Add config.pp file so we can enable common features (ssl, ipv6, ...)
more easily.
Also move the logic into config.pp so we avoid dupplicated code.
Change-Id: Ib7993ad1fbabfc22dc4ee22f72671303190e39e2
* Manage Puppet OpenStack CI CA and create a common certificate,
auto-signed.
* Configure RabbitMQ to activate SSL on scenario002
* Configure OpenStack services that run on scenario002 to connect to
RabbitMQ using SSL protocol.
Change-Id: Ic435078472ba4e0e0eaf04a64e5bcb7aabba7b3d
This patch enables robust and complete testing of a compute scenario
where RBD is used for Cinder and Nova.
* Allow cinder.pp and nova.pp to configure RBD backend.
* Switch scenario001 to run Cinder and Nova with RBD backend.
* Update README with more documentation about Cinder & Nova backends.
* Configure volume_clear option to 'none' so volumes are quickly
deleted.
* Enable rbd_default_features to 15 to increase ceph performances.
* Increase compute build_interval in Tempest to 60s, useful for
Bootfromvolume test where instance deletion can take time with RBD
backend.
Depends-On: I69a7d40e7d1847be06a843986ace4f0602272fe1
Depends-On: I7302b89da5a995e779ec349ab0c0f519c69a3a98
Depends-On: Ic410cb66e7620b6ca6acbea38360d8dd890000c9
Change-Id: I5c8d9cf2ff8fc361553b3eed73b697ad87170434
PyMySQL is the new database driver when running MySQL.
This patch updates our manifests to run it, since our modules already
support it.
Change-Id: I758c5c3bc7295f57102098cbe0d2d0f3b0f2692e
Depends-On: I7604cca9e2d7bf0b93c820adec5f937f72b64fa8
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
