Adds a tag tripleo_default_route=$BOOL to neutron ports
created by heat indicating if the ports interface is
used for the default route.
The value is controlled by the 'default_route_networks'
in roles data.
With network-data-v2 the same tag will be used to
set up ansible vars appropriately. Having the heat driven
process add the tag can be useful for upgrade/migration
automation.
Related: blueprint network-data-v2-ports
Change-Id: I20d48b3a29193dbcb70ec5cb13daf153bb0aeff2
The tags field in neutron has a max length of
60 characters. A hostname can be longer, and in
the case it is longer adding the tag will cause
a "Invalid input exceeds maximum length of 60"
error will be raised.
Related-Bug: #1921713
Change-Id: I72fd4a9575482389900145a03a6142cccd1111ba
- removes duplicate keys from yaml files by assuming that the last
one was the desired one (matches current loader behavior)
- prevent regressions by activating yaml lint rule that detects them
(yaml skip was silencing all yaml checks, so the long list seen
is in fact shorter than just 'yaml')
- includes sorting of some of the keys, was needed in order to spot
the duplicates.
Change-Id: Idf5c0041a0c6d3ed7d5d49fb68be856719916663
- fixed bindep to allow execution under fedora
- fixed flake8 config to use officially recommended use patterns
- assured that git does not report dirty after running tox (both
pep8 and tht environments where breaking this by creating untracked
files). tox-extra plugin addition will prevent future regressions.
Change-Id: I4137056853f8c5f1c2304bfb6ec1188a82b12130
Bug: #1921409
The ML2/OVN driver does support AZ-aware routing scheduling from
stable/train and newer versions.
This patch also removes the check from the DHCP agent container because
although not a typical deployment, the Neutron DHCP agent can be
deployed with OVN for special cases such as baremetal provisioning where
the agent would serve DHCP to the baremetal instances.
Change-Id: I8941c4d9a8e68eb775c910495de4aff9fbc67206
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
This change adds an artifact push task to deployments, which helps
support operators to ensure they've a better overall user experience
without needing to deploy an http server or running Swift on the
undercloud.
Depends-On: I5d18cf334c1bc4011db968fbeb4f9e41869611cd
Change-Id: I7bef7c4c7613a2475784dde135d71232b412d79f
Signed-off-by: Kevin Carter <kecarter@redhat.com>
Do not inject public certificates in pacemaker bundles by means
of "podman cp", as this pauses the container for a short amount
of time and can make pacemaker operation fail during that time
window and impact cluster for no reason.
Keep "podman cp" for non-HA containers, as the freeze is short
and doesn't seem to impact podman monitoring anyway.
The new certificate injection only works for podman 1.9+, lower
version won't overwrite the existing certificate.
Closes-Bug: #1917868
Change-Id: Id7308f028f33716be5e3df6699c3f2c12e33e344
- Use version agnostic "py" inside tox default envs
- Enable py39 testing jobs (new template contains them)
- Address deprecation warning in setup.cfg regarding use of dashes
instead of underlines (avoid future breakage with setuptools)
Change-Id: I26be50e029393e01db6718a21ac67d669ccd2e0c
The CinderBackupBackend parameter now supports 'gcs' and 's3' values,
and new parameters for configuring the associated backup backends.
The template now generates hiera config_settings for only the selected
backup backend, rather than generating hiera data for all backup
backends regardless of which one is selected.
Depends-On: I06857dd2fb64071ea734a0d3ef68ada5e5d2c077
Change-Id: I08293c7a15187b8c60f56bbc0d2d64ccf6e38227
There isn't any actual upstream support for this hardware vendor, and
the liquidio driver has been deprecated since rhel-8.
Change-Id: I25516157df02ef8299f4a3cfeff2508ca59b5959
There isn't a 1:1 correlation between the designate worker and bind
instances nor is it always desirable to run them on the same host.
Depends-On: If97e16a125537c1b5d9f5cfac1de0ffae0edb99a
Change-Id: I624299476a2911f12b1f5ce01964e5d926c6b38e
There are some typos in the post_script that gets called
when certmonger renews the HAProxy certificates. Fix them.
Change-Id: Ie9a64feddf7483036983f242d477fc8bdb6dbc1f
All heat params have been copied over, there are a bunch
that are used for conditionals.
The outputs and conditionals secions in *-puppet do a lot
of configuration, and provides lists of defaults for
puppet. These will be moved to ansible, role is at [1]
and in tripleo_ansible.
[1] https://github.com/infrawatch/collectd-config-ansible-role
[x] https://github.com/infrawatch/tripleo-collectd-ansible-role
Depends-On: Ib75702bf17a76cae3a811db503d3365e6aacf663
Change-Id: I9939a524795bb3fbc63e44f203f851dadeb7c30a
This change introduces a new CephCrushRule parameter that can be
used to describe the tiering rules for a target Ceph deployed
cluster.
Depends-On: If51cdfab825c86cd78da4520cb130d93148a1d43
Change-Id: Ia1557125859cab2d9a05715fbc0ebfaebe000b53
- manila::backend::cephfsnative::ceph_client_key was initially
used by tripleo::pacemaker::manila class to define Ceph keyring
for manila user. During Ocata release this class was adjusted
to integrate TripleO with ceph-ansible (change:
I2b5567a39ac8737e80758b705818cc1807dc8bf1) and
manila::backend::cephfs::ceph_client_key parameter was removed
from puppet-tripleo.
For some reason, artifact definition was not removed from THT
and was renamed to manila::backend::cephfs::ceph_client_key
(change: Ib408c7827e5fba0c1b01388db26363806fc64370). At this
point this parameter looks meaningless.
Partial-Bug: #1916386
Change-Id: Id4fa40a046037a90a72ac1ed1a7e77bd5a636e32
- swift::proxy::s3token::www_authenticate_uri doesn't exist,
swift::proxy::s3token::auth_uri should likely be used
instead.
Partial-Bug: #1916386
Change-Id: I48ada3704f96d858d79e31d4b1600c7905d1f62d
- ceilometer::agent::compute class was removed in Train release.
ceilometer::agent::polling class should be used instead.
change: I33c45e1ac69348df3d4f0a0df4561295123bdcce
Partial-Bug: #1916386
Change-Id: I597929128741be97bd859ea76e7f8dd8f7ac19fd
- aodh::api::host parameter was removed during Train release.
Aodh API was for testing purposes only,
aodh::wsgi::apache::host parameter should be used instead and is
already defined in THT. Changes:
I0da4dc1ba52bae5becd5e2a9c0f008cbe2907446 and
I887d86893e90cebf5bc28dd539e42436f9a31c6a
- there was a typo in aodh::alarm_history_time_to_live definition.
Partial-Bug: #1916386
Change-Id: I8f59623867a1802e2da103b8f56f68dc018f54cb