Revision as of 12:40, 22 March 2012

Nova flags for XenServer

When configuring Nova and XenServer, please take care with the following settings in nova.conf

Networking

For more information on networking, see:

• XenServer/NetworkingFlags

Flat Injection

Unless you know what guests you are having and test this works, it is best to use FlatDHCP, and so turn off the network injection (uses DHCP instead)

flat_injected=False

Connection

It is common to use the "Host Internal Management Network" to contact XenAPI. This means every node can use the same IP address to contact XenServer: 169.254.0.1

You will need to set these flags to talk to XenServer:

xenapi_connection_url=http://169.254.0.1
xenapi_connection_username=root
xenapi_connection_password=your_password_goes_here

Note: When using host aggregates you may need to use the IP address of the XenServer on the management network, so the pool can be correctly configured to talk to the other XenServer hosts.

VNC Proxy Address

Assuming you are talking to XenAPI through the host local managmenet network, and XenServer is on the address: 169.254.0.1, you can use the following:

vncserver_proxyclient_address=169.254.0.1

Firewall

The default firewall may be specific to libvirt. There are two options.

• Using IP Tables in mova network:

firewall_driver=nova.virt.firewall.IptablesFirewallDriver

• Doing the isolation in Dom0:

firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver

Guest Agent

If you don't have the guest agent on your VMs, it will take a long time for nova to decide the VM has successfully started.

While the large timeout is required for Windows instances, you may want to tweak the following flag:

agent_version_timeout=300 # number of seconds to wait, 300 is the default