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
The virtualisation driver may be selected via
globals.yml. Supported options are
The default is
Information on the libvirt-based drivers
qemu can be found in
Libvirt - Nova Virtualisation Driver.
Information on the VMware-based driver
vmware can be found in
VMware - Nova Virtualisation Driver.
Information on using Nova with Ironic to deploy compute instances to bare metal can be found in Ironic - Bare Metal provisioning.
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.
The console driver may be selected via
Valid options are
serial console support can be enabled by setting
Information on using Nova Cells V2 to scale out can be found in Nova Cells.
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
Compute service registration¶
During deployment, Kolla Ansible waits for Nova compute services to register themselves. By default, if a compute service does not register itself before the timeout, that host will be marked as failed in the Ansible run. This behaviour is useful at scale, where failures are more frequent.
Alternatively, to fail all hosts in a cell when any compute service fails
to register, set