openstack/openstack-ansible-os_nova - openstack-ansible-os_nova - OpenDev: Free Software Needs Free Tools

Some extra packages needs to be installed from Debian updates
repository, so we pin them with higher priority.
Change-Id: I49c75dd11d6c4e8d37fe013b7ffdfd56ff193fcd

Since libvirt 5.7 we should not use traditional mode. Instead systemd
mode should be choosen. Sockets are provided by libvirt package.
We just need to conditionally enable or disable them.
As addition we changed nova_libvirtd_listen_tls to 0 by default
because listen_tls requires certificate to be provided which is not
the case in the current role state. So we also fix behaviour of the role
when nova_libvirtd_listen_tls is 1, supposing that deployer has manually
distributed certificates across compute hosts.
Change-Id: Id73cb67de26c305908d0245551fa57a7e6448784
Closes-Bug: #1903846 

Change-Id: Ie0525a258e859e1545d473175440719ce298631a

Warning message is:
Option "image_cache_manager_interval" from group "DEFAULT" is
deprecated. Use option "manager_interval" from group "image_cache".
Change-Id: Ieabd209733ea640d0776f7d2ee96efe3f3c49ec4

This patch corrects a templating issue with nova.conf related to
a newline and conditional.
Change-Id: I81f03573c4fe9b7a4b112cdd9e89b0c601481c49

Even the most modest 4C/8T system would run with the maximum 16 processes
due to the calculation being VCPU*2.
We devide amount of CPUs to number of threads for hyperthreaded CPUs
Change-Id: Id1cd254fb758a09c07b7b56ba735b00b94d7a040

UPPER_CONSTRAINTS_FILE is deprecated and TOX_CONSTRAINTS_FILE is
the new environment variable name that replaces it [1].
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
[1] https://zuul-ci.org/docs/zuul-jobs/python-roles.html#rolevar-tox.tox_constraints_file
[2] https://review.opendev.org/#/c/722814/
Change-Id: Id479e07817e2c405564dad2e2dacd1812cabdacd

ceph_client role checks length of the `openstack_service_venv_bin` variable
to determine if libraries symlinking into venv should occur. So for
distro path this should be empty string as no symlinking should be done.
Change-Id: I7395ba58e10d1c0ed57b53fc9c797297d94df6f8

Nova on Victoria requires qemu to bo no less then 4.0.0. To satisfy
this requirement we need to install qemu from backports repo
Change-Id: I6e8fbfb8dec58933f854fd0688eb6030a2110279

This patch changes the listener address for spicehtml5proxy from 0.0.0.0
(default) to the nova_management_address to avoid "Address already in use"
errors.
Change-Id: I952998f3c6dd7db218b572c057149352c41c1d65

While we don't test all these virt types, see no reason in explicitly
limiting list of them, considering that they are supported by nova and
libvirt itself [1]
[1] https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.virt_type
Change-Id: Iebea20e8344c21137f1e1e5f23174d3b9b688495

Change-Id: I4953ee9de704c90dac67a70f9296062e5a071a77

We use the same condition, which defines against what host some "service"
tasks should run against, several times. It's hard to keep it the same
across the role and ansible spending additional resources to evaluate
it each time, so it's simpler and better for the maintenance to set
a boolean variable which will say for all tasks, that we want to run
only against signle host, if they should run or not now.
Change-Id: I78d44704a0224b2c73832a607e84ea8d9499f8c2

Change-Id: If5f5640b80c62fa249a0706b6f64d751b04293a6

Add 'nova_scheduler_extra_filters' to allow operators to enable
additional scheduler filters without overriding the entire list of
filters as in [0].
This also reduces the burden on ops to maintain the list of overridden
default schedulers because of things like [1].
[0] 3886dbc40d/openstack_deploy/user_variables.yml (L51-L69)
[1] https://review.openstack.org/#/c/596502/
Change-Id: I9ab6bcbef2b496df7f6ecf11a7d8f5f7891aeeca

When we were migrating service to uwsgi usage, we clean forgot to
trigger uwsgi restart on service config change.
Change-Id: I850db85234cbdf50e18f355ba39fa14e57081efd

there is some race condition on focal because the cell is discovered
after the check, the scheduler have discover_hosts_in_cells_interval=60
adjunsting the attemd to cover more than this 60sec will fix this issue.
Change-Id: Ibe32da3aa6e28d346063b1707d4aafb284cf18fd

Change-Id: I76a8fb75cfe58c642a9f6b0d4e219000c29549ea

Change-Id: I140b92dc6ccee3023d2a8965af768bd1c6488c5d

Checking if nova_libvirt_images_rbd_pool is defined leaves us without
an opportunity to disable ceph usage for specific node.
Instead of that we will use bool filter, which will be true if line
is not empty, and false if it is. That way by setting variable to empty
string in host_vars we can disable all relevant options for specific node
Change-Id: Id7c03399bd54ac790dcfc28ad1dcd7f6d48979db

Change-Id: I608b68e9bd78be4cf5ef6e4e9f10a7829f9ce8b6

These were previously the defaults and resulted in the novncproxy port
not being adustable by the expected variable, and the novncproxy process
always bound to 0.0.0.0
Change-Id: Ic4cd75ff8fa88b3bfa37fea0f8ce0438611ba1db

libvirt-python 6.7.0 makes nova-compute with [1]
Since urls can't be used with constraints, we're bumping
libvirt-python right in the requirements.
[1] http://paste.openstack.org/show/797571/
Change-Id: Ie05c8c2b7e0afe1aa7f84468e22f80debb689232

VM interfaces need to connect to a nsx-specific bridge vs the default
of br-int in order for NSX integration to be successful.
Change-Id: I152d9d4d161f18336d9b412d578846f749a0162b

Move it to the service setup host (defaults to utility[0]) instead
of the galera[0] host, and use galera_address (defaults to internal VIP)
as the endpoint instead of a local connection on the db host.
Change-Id: Ic4a2dfeeb022e1dbe0b1ba8aa0d0dd5feb7a8ffe

Change-Id: Id3e63118d8785c6c8e82e792ff3c49434485cd87

Our installation uses separate networks for deployment and
OpenStack management. The current default of 'ansible_host' for
the VNC server results in it binding to our deployment network.
Whilst this could be resolved via variable overrides, the majority
of the defaults and templated options in this role use the Nova
management address as the default choice for binding to.
This patch changes the default VNC bind address to match the
existing standard pattern, which should avoid the need for
overrides in most cases. As a result, for our setup, when
nova_management_address is identified and set in the OSA nova
playbooks to match the OpenStack management network, the VNC server
bind address gets set to the correct address.
Change-Id: I9c5e2584f8f1d9bd76120b8b236e25f63804473a

Until now the necessary pip packages differ between nova-api and
compute hosts, when novnc is used, because 'websockify' was only
added to nova-api containers. As a result, the venv is rebuilt twice
for each run. With this change 'websockify' is always added to
the needed pip packages.
Change-Id: I3f284e6d32f4aa614f311d3e4e754830be2f11a6

Our installation uses separate networks for deployment and for
OpenStack management. By default, live migrations depend upon a
hostname, which resolves to an IP on our (lower speed) deployment
network. Dependent on the deployment, the hostname may not be a
reliable mechanism for determining the correct network for live
migrations.
Nova exposes a live_migration_inbound_addr which can be used to
correct this. This patch defaults the inbound_addr to match the
Nova service bind address, but provides the option for it to be
overwritten through variables.
Whilst the Nova docs suggest that live_migration_inbound_addr
is ignored when live_migration_tunnelled is enabled this appears
to be inaccurate from our testing.
Change-Id: Iff6326f72971364d275ea999418d476007690ef8
Related-Bug: #1576724 

nova_management_address is used extensively in
templates/nova.conf.j2, but this relies upon its definition in
external variables and playbooks.
This matches the similar default chosen in the os_cinder repository
Change-Id: I1ead90c82becc1fbeae5670b7703c8389e6a78b6

We shouldn't need this anymore since interpreter patch has been merged
https://review.opendev.org/#/q/topic:interpreter+(status:open+OR+status:merged)
Change-Id: Ibc8c9b92c8c3c705964fbc85019b357913583ca7

Change-Id: I0ebcdfcb5ee54f645f9c0f3734388ac93851c8fa

Change-Id: I9a94ed995efbb5f2c2cc3de7ef77470f23b5367c

The sync from https://review.opendev.org/733244 updated to
openstackdocstheme 2.2.1 and reno 3.1.0 versions.
Set openstackdocs_pdf_link to link to PDF file. Note that
the link to the published document only works on docs.openstack.org
where the PDF file is placed in the top-level html directory. The
site-preview places the PDF in a pdf directory.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I0cc73a4e714f8b533b5c1381124141c3d07d47d1

Add file to the reno documentation build to show release notes for
stable/ussuri.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/ussuri.
Change-Id: Ifdf38a2a6c9d96d45fd8c2370e49977c4cfc8700
Sem-Ver: feature

Change-Id: I80e39bc85108ee82a3da401fcc3315a5c9a33573

New version of openstackdocstheme (Victoria+) respects pygments_style.
Since this repo is using now Victoria (master) requirements but has
not branched for Ussuri yet, it uses the new version.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
Change-Id: Ie089410c6ef26c6beb38179730afe641503c0eb9