Ask Your Question
0

Instances running on VMware ESXi cannot access metadata service

asked 2013-06-28 08:29:23 -0500

Marin gravatar image

updated 2013-07-05 08:23:25 -0500

smaffulli gravatar image

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

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
1

answered 2013-06-28 10:09:03 -0500

smaffulli gravatar image
edit flag offensive delete link more
0

answered 2013-08-16 05:16:35 -0500

openstack gravatar image

Can you launch windows instance with esxi ?

edit flag offensive delete link more

Comments

I could try, but to what purpose?

Marin gravatar imageMarin ( 2013-11-06 10:02:43 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2013-06-28 08:29:23 -0500

Seen: 1,492 times

Last updated: Aug 16 '13