This patch is adding missing documentation of two collectd write plugins
in the collectd-evnironment.yaml and fixes deprecated configuration keys
for metrics_qdr in metrics-collectd-qdr.yaml.
Change-Id: I7d41bbf1ca46114cfa5f1784baa8da03aee9fcab
We want to enable podman on the undercloud first, this patch just
install the rpm and configure the insecure registry if needed.
Change-Id: If469e584e2905a002931277bbe2f7301f7b8fd93
Podman service will be in charge of installing, configuring, upgrading
and updating podman in TripleO.
For now, the service is disabled by default but included in all roles.
In the cycle, we'll make it the default.
Note: when Podman will be able to run in TripleO without Docker,
we'll do like https://review.openstack.org/#/c/586679/ and make it as
a generic service that can be switched to either podman or docker.
But for now, we need podman & docker working side by side.
Depends-On: Ie9f5d3b6380caa6824ca940ca48ed0fcf6308608
Change-Id: If9e311df2fc7b808982ee54224cc0ea27e21c830
https://github.com/openstack/tripleo-heat-templates/blob/master/environments/ssl/enable-internal-tls.yaml#L22
uses RPCUseSSL only and misses the NotifyUseSSL variable.
The reason this is a problem is that commands/services that will kick
off a notification are likely to hang due to this. Imagine the
following scenario:
1. TLS configured everywhere
2. keystone-manage bootstrap actually hangs
The reason for this is that the messaging string in the keystone container will look like the following:
[oslo_messaging_notifications]
transport_url=rabbit://guest:AC8DjGviXCQks8MWjQdAjYW9L@overcloud-controller-0.internalapi.tripleodomain.example.com:5672/?ssl=0
By gdb-ing on to the keystone-manage process (thanks Damien, for the
idea) we can see that we are stuck in oslo calls connecting to rabbit
without tls
Closes-Bug: #1795462
Change-Id: I0d25527131fa4cd293994a0511bba1144510c4d8
NeutronEnableDHCPAgent is no longer consumed anywhere in OpenStack so
this patch is removing all occurrences of it in the environment files.
Change-Id: I042944c3f24d22fa60d4ed13fd9a56c5b93f465f
Signed-off-by: Daniel Alvarez <dalvarez@redhat.com>
The undercloud needs to be able to run the playbooks shipping with
ceph-ansible so we mount them from the hosting node in undercloud.yaml
Change-Id: I8d1db69d520da069099f919f286e6a553dd645a5
Closes-Bug: 1794027
This sets the mysql connect timeout in the containerized undercloud
case. It mirrors Ia3799cdaf171892431151e4f2f7d2095081b8242.
Related-Bug: #1783995
Change-Id: I727a38eb537f83accadca9ee7f38bd7ace62500e
The main purpose of this file is to enable the zaqar service
but, unlike the environments/services/zaqar.yaml file it explicitely
disables the redis service as this is meant to be used with
swift/sqlalchemy.
The main use case here being the containerized undercloud
Change-Id: Ic11b4790a1a2c2336cd432784f19922e76e028ad
Partial-Bug: #1795027
It isn't useful for much of anything in a production deployment
and it conflicts with the local DNS server in CI.
Change-Id: Ied3ecdc71bfdf9bb6439e2c9464aa01346e69226
Closes-Bug: 1795043
The standalone role can be used either with the tripleo deploy command
to deploy locally, or it can be used with an undercloud to deploy an
all-in-one node. This change provides a sample set of environment files
for both deployment mechanisms.
Change-Id: Ibc735ac4326a9217469e368c074de8b0df7689bd
Related-Blueprint: all-in-one
The Dell EMC SC configuration option excluded_domain_ip has been
deprecated and will be removed in a future release. Deployments
should now migrate to the option excluded_domain_ips for
equivalent functionality.
Depends-On: https://review.openstack.org/604444
Change-Id: I27c02be4d306a55a1ee8617de81d145b086a8a1b
Openshift Routers are located on the infra node and need to be highly
available on ports 80 and 443.
Depends-On: I5de14152904d06c49e9d5b2df6e3f09a35f23d92
Change-Id: Iee088e1279bff2cdb7a3601288804f626bff29a3
instack-undercloud had a workaround (30-reload-keepalived)
in place to always restart keepalived on install/upgrade.
This is required to ensure VIP's are present in case the
network config was changed and os-net-config restarts
the network interface. When containerizing the undercloud
this workaround was missed.
This change adds a similar workaround. A pre_deploy
NodeExtraconfig script will restart the keepalived
container when the undercloud installer is (re-)run.
NOTE: We can remove this workaround once keepalived
v2.0.6 or later is available.
Closes-Bug: #1791238
Change-Id: I8cada7be57cd50c54ca5f2f38ec010062512ae06
Upstream will deprecate usage of eventlet of all the WSGI-run
services, including nova-api and nova-metadata-api.
See https://review.openstack.org/#/c/549510/ for more details.
With this change we move nova-metadata to run via httpd wsgi
and therefore uses its own config volume.
Closes-Bug: 1781405
Change-Id: I7206925c5416814bcbf92021e606afeaedde4b1b
Depends-On: Ic65736cb0e95c400a728cd699ecf06c6aecff832
Depends-On: Ic46acdbac280ac648ec5ed9d7af0139126334fe0
Depends-On: I47d79ab8e274e94cbe0d4cadd204e63cbbe3dca8
Depends-On: I069510b8dfc8e6a7c5ff6f07826f10a2038856d7
Depends-On: I3d572dda2e90b7e24f2f8912d704462b9332d807
ODL and OVN services are mutually exclusive and
leads to deployment failure when enabled on a role.
This patch sets OVN services to OS::Heat::None in
ODL env file to disable it whenever ODL is enabled.
Change-Id: Iaa757339f24fbadf51152326fe62f194c25e2384
In order to support switching between multiple timesync backends, let's
simplify the service configurations for the roles so that there is a
single timesync service. This timesync service should point to the
expected backend (ntp/ptp/chrony).
Change-Id: I986d39398b6143f6c11be29200a4ce364575e402
Related-Blueprint: tripleo-chrony
Core/Ram/Disk Filters are not required when using filter_scheduler.
After https://review.openstack.org/#/c/565841 when using these
Filters nova is not scheduling to the ironic nodes and overcloud
deployment fails.
For now just testing the undercloud, good to see what scheduler/filters
are being enabled in overcloud and reflect there as well.
Related-Bug: #1787910
Depends-On: Ia82f1c6be0d5504498e77a90268cad8abecdeae2
Change-Id: I0e376d99adeaa318118833018be81491c6b14095
In the environment/network-environment*.yaml files the
itaration is done only on networks that is enabled.
We do not need conditionals inside the loop to check
wheather the network is enabled or not.
Change-Id: I621c205aebcdb353ac487a5804bbe83fbc20c95d
DVR doesn't imply the "External" networks, simply some type of
connection that is being used for floating IP traffic. This patch
removes the External network from the DVR role and "left overs" from
environment files. It also corrects the multiple-nics version of the
templates so that the ComputeDVR role is attached to the external
bridge with no IP.
Co-Authored-By: Dan Sneddon <dsneddon@redhat.com>
Change-Id: Ia599e01dbefe4e4c752b7d4c1c7e5682963101f7
There are no additional octavia specific neutron service plugins for
octavia required so this parameter should be removed from the
environment files.
Change-Id: I3da329db28701c7e9798083982953c5c9c861c50
OVN based backend setups don't need RPC communications as they
don't deploy Neutron agents (except for the SRIOV case).
For this reason and to minimize the resources used, this patch
is setting the number of RPC workers to the minimum, which is 1.
Change-Id: Icf84516f24873717cb7615233d2e6341414abfc7
Closes-Bug: #1786952
Signed-off-by: Daniel Alvarez <dalvarez@redhat.com>
I've cloned the neutron-sfc.yaml file and added to the parameter_defaults NeutronSfcDriver:'ovn'
There could be other param defaults needs to be added and i'm not aware of.
Change-Id: I82fc10fb75ed4d804eda8a1b7bee5dd63e5efd11
This patch enables collectd on overcloud nodes to connect to local QDR
running on each overcloud node.
Depends-On: I4cb6aa95e253b7fd19ed265fbcba0dfe6663592d
Change-Id: I1d95454f049ca22d694b21b5102e24c63c6009cd