When using the multiple nic-config templates in THT
and in tripleo-ansible the ordering of networks in
the network_data file matters.
Add a a tag 'tripleo_net_idx' to neutron resources
to keep track of the ordering.
Depends-On: https://review.opendev.org/772795
Partial-Implements: blueprint network-data-v2-ports
Change-Id: I0d39ea713ce1201b60f3def69f453792e402eb33
When a node has hugepages enabled, we can help with live migrations by
enabling NovaLiveMigrationPermitPostCopy and
NovaLiveMigrationPermitAutoConverge.
Related: https://bugzilla.redhat.com/1298201
Change-Id: I1133c210f35181d44f8ba56f09b52f00589e035c
Now that [0] has finally merged and the upgrade path
will allow jumping multiple releases, we don't require
to have multiple environment files for the upgrade and
the ffwd.
Removing the ffwd-upgrade-prepare.yaml and ffwd-upgrade-
converge.yaml files from environments/lifecycle folder.
[0] - I39b8a846145fdc2fb3d0f6853df541c773ee455e
Change-Id: I5a83ebda6d20336d8c82024bf673d88358a6a675
[DEPRECATION WARNING]: evaluating 'swift_raw_disks' as a bare variable,
this behaviour will go away and you might need to add |bool to the
expression in the future. Also see CONDITIONAL_BARE_VARS configuration
toggle. This feature will be removed in version 2.12. Deprecation
warnings can be disabled by setting deprecation_warnings=False in
ansible.cfg.
Change-Id: I1d99dccc3ad8c6550581e69d48c7e7b365d53c7a
We currently forcefully install pacemaker + pcs in a number of upgrade
tasks. This is suboptimal because on certain nodes pcs/pacemaker repos
are not enabled. Let's let puppet pull in those packages normally.
Tested this during a queen -> train FFU successfully on a composable
roles environment.
Closes-Bug: #1911684
Change-Id: I97b42e618bcd31e408374157eb10d315ac62f306
Add a new deployed_port template which will replace
the current neutron port templates when ports are
managed outside of the heat stack.
Partial-Implements: blueprint network-data-v2-ports
Change-Id: Ia71b74e80122e6a12d4f88a90ede02d39763914e
libvirt-daemon is part of the default overcloud image but it's also
possible that it's not installed or simply removed by operators. In this
case, tripleo_nova_libvirt_guests will fail.
Related: https://bugzilla.redhat.com/1810319
Change-Id: I0814bd8794ab82792837b27d0128e15c34b90adc
Add support for the [compute]/image_type_exclude_list parameter to
prevent image types being reported as supported by a compute node.
Depends-On: I389d4b586468720d73ac69b025a3c34df54fe73e
Change-Id: I326cb9facf33693fdf8f361f9bc58aa28b3c20af
In order to configure OVN+SRIOV, the following THT files need to be
imported:
- neutron-ovn-ha.yaml
- neutron-ovn-sriov.yaml
Change-Id: Ia918d8b92d9bb1efac9bec2017b88593bf362834
Resolves: rhbz#1913700
CephFS gatewayed by NFS is more generally suitable for multi-tenant
OpenStack deployments than native CephFS since the latter requires
that VMs belonging to regular members of Keystone projects be exposed
to the Ceph infrastructure and run client software with capabilities
that are not appropriate for untrusted cloud tenants.
Depends-on: https://review.opendev.org/c/openstack/puppet-tripleo/+/769906
Depends-on: https://review.opendev.org/c/openstack/tripleo-ci/+/770049
Change-Id: I269607d43f45f65efcbce33dd776e7eb4f475311
[1] introduced a workaround that was required when TLS-everywhere was
implemented with novajoin. The workaround is no longer required because
novajoin is deprecated in favor of the tripleo-ipa ansible module. The
workaround is disabled by changing the EnableEtcdInternalTLS parameter's
default value changes from False to True.
[1] Iec0d02f8f51067098dd58beb4fe57a7fd5ab5651
Change-Id: Ic41738392fbbe9239b927e26c0b2ed3b7abe3a09
We need to specify doc requirements in doc/requirements.txt
to avoid problems with the pip resolver [1] for the release team [2][3].
Removed specific doc requirements from test-requirements.txt.
The problem here is that this repos haven't doc/requirements.txt file
and by default in this case zuul will use the test-requirements.txt file
to
pull requirements [4].
This requirements file contains extra requirements like flake8 that
collided with those allowed in our job environment and so the new pip
resolver fails to install these requirements and the job exits in error.
This project meet the conditions leading to the bug.
/!\/!\/!\
Notice that I voluntarily added the doc directory even if no docs
are generated here because zuul will try to pull this requirements from
there first and the contained requirements are needed for reno but AFAIK
the releasenotes dir is ignored by zuul. c.f [4] for further details.
/!\/!\/!\
[1] http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html
[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html
[3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html
[4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36
Change-Id: I519ef389448acb3dde328a0e61c074e48d7e0466
Default CephAnsibleSkipClient to True and CephConfigPath to
/var/lib/tripleo-config/ceph (instead of /etc/ceph) and set
these paramters explicitly in scenario00{1,4}. This will
result in all Ceph client configuration being done not by
ceph-ansible but by the new tripleo-ceph-client role from
tripleo-ansible.
Add the CephClient service to all Controller* roles which will
use Ceph. The service could have always been there as there are
Ceph clients on the these controllers, but it was not because
ceph-ansible configured clients as a side effect. With new
CephConfigPath default they no longer overlap so the service
is required.
Add support for CephExternalMultiConfig via tripleo-ceph-client
by looping on the contents of the CephExternalMultiConfig list
and passing each map as the dcn variable while including the
tripleo-ceph-client role each time.
Related-Bug: #1708302
Depends-On: I938ab604859fda88f3491399444841a3a373d162
Change-Id: I784e6a476752ed701192b3a0155c42edd4836d97
This change moves the release note file which was added to the wrong
place[1].
Note that this file was added during this cycle so we can move it to
reno directory so that the note is added to the current release note.
[1] cb982440d7
Change-Id: I3ded156dfc0c954ee862ddf98f7d97a672f347f1
Now configurations for LoginDefs service is managed by ansible[1].
This change renames its template file to follow the name pattern used
for resources managed by ansible.
[1] 2ae95677fe
Change-Id: I14bafd6bbef5ea67430c2f1176df78c8ca210d17
Harald Jensås