Compute Service Customization

The nova_override.conf file is a custom configuration file used in Platform9's Private Cloud Director to allow you to override default configurations for Private Cloud Director compute service. These overrides persist across upgrades, ensuring that your customized settings remain intact.

Note that updating nova_override.conf file is an advance operation and should only be performed by Administrators with complete understanding of the option they are editing and the possible impact. We highly recommend that you do this only under guidance from Platform9 support or solution architect teams.

triangle-exclamation

The nova_override.conf file is typically located in the following directory.

/opt/pf9/etc/nova/conf.d/nova_override.conf
circle-info

Info

The nova_override file must be edited on each hypervisor host where the override configurations are required. This ensures that the custom settings apply consistently across all compute nodes.

You can use this override file to:

  • Adjust logging levels or enabling more verbose logging by enabling debug mode. (Mostly commonly used case).

  • Customize compute driver options.

  • Modify quota defaults for specific tenants.

Here is an example of a nova_override.conf file customized for common use cases like for logging, debugging, and optimization.. For more info, refer to nova.confarrow-up-right.

Logging & Debugging

Safe for troubleshooting but should be reverted in production.

[DEFAULT]
debug = true  # Enable detailed logging (useful for troubleshooting)
log_dir = /var/log/nova  # Log file storage location

Scheduler Configuration

Can be adjusted to improve VM scheduling behavior.

Compute Resource Limits

Can be modified based on hardware capacity.

Restart Service

After editing the nova_override.conf file, you must restart the Private Cloud Director compute service for the changes to take effect. Run the following command on the host:

Advance Settings

circle-exclamation

Compute Driver Configuration

Do not change unless you are configuring a different virtualization technology (e.g., VMware, Xen, KVM).

Networking Configuration

Changing networking parameters without proper testing may break VM connectivity.

Disk & Storage Settings

Modify only if you are implementing specific storage optimizations.

CPU Mode and Model Configuration

This configuration is typically used when you need consistent CPU features across different hypervisors.

Last updated

Was this helpful?