openstack/tripleo-heat-templates
Code Issues Proposed changes
c290ddf2db
tripleo-heat-templates/ci
History
Sandeep Yadav 382e76fe9d Replace qdrouterd backend with rabbitmq in Sc03 
qdrouterd for RPC is not a supported backend in RHOSP,
updating sc03 to test rabbitmq which is a supported
backend for RPC communication.

Trying to run with qdrouterd backend in downstream fails
because python-pyngus is not added as dependency downstream[1]
python-pyngus available since RHOSP13 but is not added as dep
for oslo-messaging rpm with reasoning[2].

~~~
 ModuleNotFoundError: No module named 'pyngus'
~~~

Sc03 provides desginate testing coverage, This change will
allow us to run standalone sc03 in downstream pipelines keeping
sc03 env files in sync in upstream and downstream.

This patch will be backported to wallaby.

[1] https://github.com/rdo-packages/oslo-messaging-distgit/blob/wallaby-rdo/python-oslo-messaging.spec#L89-L91
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1791364#c13

Change-Id: Ib49223709e20931abcec4d16301db9882c64c06f
(cherry picked from commit 9962b52a0a)
2023-01-23 14:29:30 +00:00
..
common Use 'wallaby' heat_template_version 2021-03-31 17:35:12 +05:30
environments Replace qdrouterd backend with rabbitmq in Sc03 2023-01-23 14:29:30 +00:00
custom_ci_roles_data.yaml Deploy separate glance-api services for OSSN-0090 2023-01-09 06:48:57 -08:00
custom_names_network_data.yaml Add templates for custom network ci job 2021-12-06 17:12:07 +05:30
custom_names_vip_data.yaml Add templates for custom network ci job 2021-12-06 17:12:07 +05:30
network_data_v6.yaml Add ipv6 network_data/vip_data for CI jobs 2021-09-21 16:45:46 +05:30
network_data.yaml Network data v2 YAML definition for CI 2020-11-19 02:43:29 +01:00
README.rst Fix typos in comments and parameter descriptions 2022-08-03 17:07:11 +05:30
vip_data_v6.yaml Add ipv6 network_data/vip_data for CI jobs 2021-09-21 16:45:46 +05:30
vip_data.yaml CI - Add vip_data file 2021-03-16 20:35:41 +00:00

README.rst

TripleO CI environments

TripleO CI environments are exclusively used for Continuous Integration purpose or for development usage. They should not be used in production and we don't guarantee they work outside TripleO CI.

For more information about TripleO CI, please look: https://github.com/openstack-infra/tripleo-ci