Adds support for configuring vGPUs on NVIDIA hardware.

Closes-Bug: #2028843
Change-Id: I4c8481f7429dbf50d51e26bd7acee24e16ee6c79

If inline Ansible vault encryption is used to define an encrypted
variable in kayobe-config, running 'kayobe configuration dump -l <host>'
fails with the following:

  Failed to decode config dump YAML file /tmp/tmp_fg1bv_j/localhost.yml:
  ConstructorError(None, None, "could not determine a constructor for
  the tag '!vault'", <yaml.error.Mark object at 0x7f1e5c7404c0>)

This change fixes the error by using the Ansible YAML loader which
supports the vault tag. Any vault encrypted variables are sanitised in
the dump output. Note that variables in vault encrypted files are not
sanitised.

Change-Id: I4830500d3c927b0689b6f0bca32c28137916420b
Closes-Bug: #2031390

Change-Id: I73fad29af6a57b29afea46947d1ae90546253a2a

I missed this when I refactored the code to fallback
to templating. We need to deduplicate before picking
the strategy for the fallback to work for symlinked files.

Change-Id: Iddd6c90a6daa41e1d1cdaa6b598491792c13394d
Closes-Bug: #2042689

Change-Id: I06b0bd4634ebb8b78baa23656c891333fd96b88b

Change-Id: Id80e7d28c20b1f9ecc52473013c78c28d2ab5532

Change-Id: I2577245440d510ab19f48915479a8e3575b996b7

Updating requirements.yml with latest os-networks role

Following up:
Ia3550644e5fc3e83f792e46d42b4c35d5eec4705

Change-Id: I9cb1b4c5329dc9db8562cf317616101d35f13edb

This is a backwards compatability improvement, since it was previously
permitted to have a config file that templated to invalid yaml/ini.

Change-Id: I53a0894cc64e83c7342a82ad987b7e5a4696ece2
Closes-Bug: #2042690

This change bumps up the maximum supported version of Ansible to 8.x
(ansible-core 2.15.x) and minimum to 7.x (ansible-core 2.14.x).

Depends on:
https://github.com/stackhpc/ansible-role-systemd-networkd/pull/10

https://github.com/stackhpc/ansible-role-dell-powerconnect-switch/pull/13

https://github.com/stackhpc/ansible-role-mellanox-switch/pull/8

gateway_ip was being set to empty string. This was triggering neutron
""Invalid input for gateway_ip. Reason: '' is not a valid IP address."
Omitting by default.

Installing openstack.cloud collection.
Upgrade failed as Ansible in kayobe-venv was not upgraded.

Change-Id: Ia3550644e5fc3e83f792e46d42b4c35d5eec4705

Setting network mode to host.
Enables testing without additional configuration of the host.

Change-Id: I46406d414290ed785a4644c88cbc76ff074e96a2

This can result in duplicated configuration options.

Change-Id: I4dd6ffae027345b8c1cc217a63e85f8af7fc9746
Closes-Bug: #2042689

I8bf75ce44b9ec1fdd477fcddf2deebf2929d9fc1 added a workaround to remove
incorrectly named DNF repository files.

This workaround has been in place since the Antelope release and can now
be removed.

Change-Id: I7ba61ffa8aaabcedf1c5249e5f39f39257410f9a

Ie59f0c729381e5bea112ab7f5d0c738a9488b772 changed the provision-net and
cleaning-net to be non-shared when they are VLAN networks. It also
added some transitional tasks to modify existing VLAN networks to unset
the shared property.

This change removes the transitional code since it has been in place for
over 3 years.

This change also slightly refactors the code to use only a 'tasks' list.

Change-Id: I6d358502d37e6a2d0098ad4733840613e93b4279

Match ML2/OVS agents only when OVN is not enabled.

Change-Id: Ia2ba7414202de6750b18ada47e7a5bb0b636e7b3

We no longer support EL8 or network-scripts.

Debian systems never used this role, so also removing those tasks.

Change-Id: I17b93c75a1ff8eb8d636247696f4a1709ca486d5

Kayobe has fairly coarse-grained default groups - controller, compute,
etc, which work well in the majority of cases. Kolla Ansible allows much
more fine-grained placement on a per-service basis, e.g.
ironic-conductor. If the operator has taken advantage of this
fine-grained placement, then it is possible that some of the assumptions
in Kayobe may be incorrect. This is one downside of the split between
Kayobe and Kolla Ansible.

For example, Ironic conductor services may have been moved to a subset
of the top level 'controllers' group. In this case, we would not want
the Ironic networks to be mapped to all hosts in the controllers group -
only those running Ironic conductor services. The same argument can be
made if the loadbalancer services (HAProxy & keepalived) or Neutron
dataplane services (e.g. L3 & DHCP agents) have been separated from the
top level 'network' group.

This change abstracts the placement of Ironic conductor Ironic
inspector, loadbalancer and network services into separate variables,
rather than referencing the top level 'controllers' and 'network' groups
directly. These variables may be updated by the operator to match the
service placement.

Change-Id: Idbf181c795ee98ad653f11ae483f9dab4ef1b599