Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Instances running on VMware ESXi cannot access metadata service

Hi,

I've configured OpenStack Grizzly to use ESXi 5.1 as hypervisor, following instructions in the docs. I have one machine running ESXi and another running a nova-compute instance that monitors it. Creating/deleting instances from OpenStack works as expected, instanced are created in ESXi (verified via vSphere Console) and started ok.

The trouble is that VMs can't access the nova metadata service and are unable to configure IPs. For instance, Ubuntu cloud images expect to access EC2 metadata-compatible service on http://169.254.169.254/.... Normally, with nova running on the same host as the hypervisor, this address is assigned to loopback interface and metadata service listens on it. Here I have two machines, and the ESXi host for VMs is not running nova-* anything. Is this setup ok? Should I enable anything else?

Thx, Marin

Instances running on VMware ESXi cannot access metadata service

Hi,

I've configured OpenStack Grizzly to use ESXi 5.1 as hypervisor, following instructions in the docs. I have one machine running ESXi and another running a nova-compute instance that monitors it. Creating/deleting instances from OpenStack works as expected, instanced are created in ESXi (verified via vSphere Console) and started ok.

The trouble is that VMs can't access the nova metadata service and are unable to configure IPs. For instance, Ubuntu cloud images expect to access EC2 metadata-compatible service on http://169.254.169.254/.... Normally, with nova running on the same host as the hypervisor, this address is assigned to loopback interface and metadata service listens on it. Here I have two machines, and the ESXi host for VMs is not running nova-* anything. Is this setup ok? Should I enable anything else?

Thx, Marin