On Jun 20, 2012, at 5:44 PM, Lars Kellogg-Stedman wrote:
Is the DNAT rule expected to work? Does linux_net.py need a special
case for when the metadata address is on the local host?
I have confirmed that the DNAT rule works *unless* metadata_host is
127.0.0.1, in which case you need a
We seem to have OpenStack working correctly with a FlatDHCP network
environment, running in multi_host mode. Outbound connectivity works just fine:
instance# curl http://google.com
HTMLHEADmeta http-equiv=content-type content=text/html;charset=utf-8
TITLE301 Moved/TITLE/HEADBODY
H1301
We are having problems with connectivity from the instance to our
OpenStack controller (particularly the metadata service)...
zynzel on #openstack suggested that the metadata api service is
supposed to run alongside the compute service, so I've modified our
configuration accordingly to start
When using the multi-host network mode, the simplest solution is to install
either the whole nova-api service, or better yet, just the
nova-api-metadata service alongside every nova-network.
If you're on Ubuntu, just install the nova-api-metadata package..
Thanks,
Kiall
Sent from my phone.
On
or better yet, just the
nova-api-metadata service alongside every nova-network.
Right, that's what we've got. The issue right now appears to be that
of a DNAT rule failing where a REDIRECT rule succeeds, and I'm not
sure what's causing that behavior.
Presumably other people have this working
Is the DNAT rule expected to work? Does linux_net.py need a special
case for when the metadata address is on the local host?
For now, I've modified linux_net.py so that it conditionally creates a REDIRECT
rule if FLAGS.metadata_host is 127.0.0.1:
def metadata_forward():
Create
Is the DNAT rule expected to work? Does linux_net.py need a special
case for when the metadata address is on the local host?
I have confirmed that the DNAT rule works *unless* metadata_host is
127.0.0.1, in which case you need a REDIRECT rule.
--
Lars Kellogg-Stedman l...@seas.harvard.edu
7 matches
Mail list logo
