Doug Szumski 9af42fcebc Support copying static Vendordata file into Nova API container
Nova provides a mechanism to set static vendordata via a file [1].
This patch provides support in Kolla Ansible for using this
feature.

Arguably this could be part of a generic mechansim for copying
arbitrary config, but:

- It's not clear if there is anything else that would take
  advantage of this
- One size might not fit all

[1] https://docs.openstack.org/nova/latest/configuration/config.html#api.vendordata_jsonfile_path

Change-Id: Id420376d96d0c40415c369ae8dd36e845a781820
2021-11-25 17:24:05 +00:00

1.8 KiB

Nova - Compute Service

Nova is a core service in OpenStack, and provides compute services. Typically this is via Virtual Machines (VMs), but may also be via bare metal servers if Nova is coupled with Ironic.

Nova is enabled by default, but may be disabled by setting enable_nova to no in globals.yml.

Virtualisation Drivers

The virtualisation driver may be selected via nova_compute_virt_type in globals.yml. Supported options are qemu, kvm, and vmware. The default is kvm.

Libvirt

Information on the libvirt-based drivers kvm and qemu can be found in libvirt-guide.

VMware

Information on the VMware-based driver vmware can be found in vmware-guide.

Bare Metal

Information on using Nova with Ironic to deploy compute instances to bare metal can be found in ../bare-metal/ironic-guide.

Fake Driver

The fake driver can be used for testing Nova's scaling properties without requiring access to a large amount of hardware resources. It is covered in nova-fake-driver.

Consoles

The console driver may be selected via nova_console in globals.yml. Valid options are none, novnc and spice. Additionally, serial console support can be enabled by setting enable_nova_serialconsole_proxy to yes.

Cells

Information on using Nova Cells V2 to scale out can be found in nova-cells-guide.

Vendordata

Nova supports passing deployer provided data to instances using a concept known as Vendordata. If a Vendordata file is located in the following path within the Kolla configuration, Kolla will automatically use it when the Nova service is deployed or reconfigured: /etc/kolla/config/nova/vendordata.json.