This change combines the previous puppet and docker files into a single
file that performs the docker service installation and configuration.
Change-Id: I6a9123627d754a153ab6cb68a33778a57846aeb7
Related-Blueprint: services-yaml-flattening
This changes moves podman service from puppet to deployment directory.
Change-Id: I31b8299b43158347f4f1f61f1e1fdf38b0a2102f
Related-Blueprint: services-yaml-flattening
Numerous files have incorrect modes set. Correct these so that executables
have 755 and yaml files are 644 to address rpmlint errors.
Change-Id: I8db36209b41a492f6b85e3469994de884bf556e8
This change combines the previous puppet and docker files into a single
file that performs the docker service installation and configuration.
With this patch the baremetal version of memcached services has been removed.
Depends-On: https://review.rdoproject.org/r/#/c/16994/
Change-Id: Ibb74d9e1673d079a6090efe4215c7ee041fce7d6
Related-Blueprint: services-yaml-flattening
This should have been fixed via:
https://review.openstack.org/#/c/460175/2
where we did:
service_config_settings:
haproxy:
tripleo.horizon.firewall_rules:
'127 horizon':
dport:
- 80
- 443
The problem is that the above does not work. Reason for this is the way
tripleo::firewall works. It will only apply iptables rules for that
show up in hiera('service_names'):
$service_names = hiera('service_names', [])
tripleo::firewall::service_rules { $service_names: }
And since horizon is not in the service running on the haproxy role, the
above rule would never have been created.
Tested this change and now I correctly get the iptables rules on the
haproxy role for horizon:
[root@overcloud-core-0 ~]# iptables -nvL |grep horizon
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 multiport dports 80,443 state NEW /* 127 horizon ipv4 */
[root@overcloud-core-0 ~]# hiera -c /etc/puppet/hiera.yaml service_names |grep horizon
[root@overcloud-core-0 ~]#
Closes-Bug: #1808530
Change-Id: Ia4a795d1a7fb926f5900c739c1932b20d81ed7fc
Co-Authored-By: Damien Ciabrini <dciabrin@redhat.com>
This job is required to cover designate.
UPDATE:
- Also ensure we run all jobs if zuul.d/* are changed.
- Removed:
tripleo-ci-centos-7-scenario003-multinode-oooq-container
Change-Id: I31ae7f873617b69bfd8fee7010bab133e384795b
Story: https://tree.taiga.io/project/tripleo-ci-board/us/338
This change combines the previous puppet and docker files into a single file
that performs the docker service installation and configuration.
With this patch the baremetal version of glance services has been removed.
Change-Id: Ie2ac2072f0742ec5e521fc6e3734e89f8a007077
Related-Blueprint: services-yaml-flattening
This change combines the previous puppet and docker files into a single file
that performs the docker service installation and configuration.
With this patch the baremetal version of Ironic services have been removed.
Change-Id: Icb33158a129356d939940433c82dae25a6334baf
Related-Blueprint: services-yaml-flattening
Update /etc/tuned/{{ _TUNED_PROFILE_NAME_ }}-variables.conf only
if it exists.
Change-Id: I20562efd61ba49b3ae0af62c079967681e05aeed
Closes-Bug: #1806812
It seems in some cases we get an empty list for services in
service_bootstrap_ips and the yaql expression fails. Though
there can be better solution to not look for EnabledServices
for roles that has zero count, this would probably fix the
immediate scenario008 failures.
Change-Id: Ife1fc3f7736ed5743c80fa3748a75cb0bb52b817
Closes-Bug: #1808240
https://review.openstack.org/#/c/619337/ switched the jobs to a noop for
master and since this file is branched we no longer need to keep this
template definition in THT.
Change-Id: I305c175392089e103dec85461f289ab38127398d
This change combines the previous puppet and docker files into a single file
that performs the docker service installation and configuration.
With this patch the baremetal version of keepalived service have been removed.
Change-Id: Ic0ddf1174e1d0a62f83f26f0ca6bc29ec7b078b7
Related-Blueprint: services-yaml-flattening
To help clarify current and future naming conventions in this directory.
Change-Id: Ib9d24f9844f5aecd47cdd6a47247562dce2092ee
Related-Blueprint: services-yaml-flattening
We want to include the way the service is deployed (container/baremetal)
and the configuration management tool used (ansible/puppet) in the
service file name so folks can easily identify how a service is being
deployed and with what tooling.
Change-Id: Id884009131ea1587042a8ac01eec7afd83d7eb6a
Related-Blueprint: services-yaml-flattening
On Octavia-enabled composable role deployments where the Octavia health
manager service doesn't run co-located with the API service, the
firewall rule to allow messages in to the o-hm0 interface was not being
created. As a result of that, the load balancers were not going ONLINE.
Closes-Bug: #1808190
Depends-On: https://review.openstack.org/#/c/624403/
Change-Id: Icc568a551b902e6d9f003250226468ed38a776fc
This exposes parameters to configure OpenIDC federation in Keystone.
Change-Id: I3e06ca5fde65f3e2c3c084f96209d1b38d5f8b86
Depends-on: Id2ef3558a359883bf3182f50d6a082b1789a900a
