openstack team mailing list archive

[Kevin Jackson <kevin@xxxxxxxxxxxxxxxxxxx>]

Heyup good folk of OpenStack,
I'm having the same issue as Sina.  My configuration seems to look OK (I
have an instance, with IP that can ping its default route to on an internal
network) but I get the failure to contact the metadata server with the
explanation that Sina gave.

In my /var/log/quantum/l3_agent.log I have the following:
http://paste.openstack.org/show/24801/
There's also a paste of an iptables output that I would've expected to see
the DNAT rules in.

What am I missing?

Cheers,
Kev


On 7 November 2012 14:35, Choe, Cheng-Dae <whitekid@xxxxxxxxx> wrote:

> - DNAT rule to metadata server is done by l3_agent. but your node
> configuration has no l3_agent
> - and metadata_ip configuration can find l3_agent.ini.
>
> 2012. 11. 7., 오후 9:15, Sina Sadeghi <sina@xxxxxxxxxx> 작성:
>
>  Hello all,
>
> I thought I would giv
> e quantum a shot and I've got a 50-60% working configuration, but having
> trouble understanding where to go from here as the docs are pretty sparse.
>
>
> Ubuntu 12.04.1 + "ubuntu cloud archive" folsom repo
>
> node A: nova-api, nova-scheduler, quantum-server, quantum-plug
> in-openvswitch
> node B: nova-compute, nova-api-metadata, quantum-dhcp-agent, quantum-plug
> in-openvswitch-agent
> node C: nova-compute,
> nova-api-metadata, quantum-dhcp-agent, quantum-plugin-openvswitch-agent
>
> configured as follows:
>
> quantum.conf:
> ...
> core_plugin =
> quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
> ...
>
> ovs_quantum_plugin.ini:
> ...
> tenant_network_type=vlan
> network_vlan_ranges = default:2000:3999
> integration_bridge = br-int
> bridge_mappings = default:br-eth3
> ...
>
> node B,C `ovs-vstl list-br`:
> br-eth3
> br-int
>
> node B,C `ovs-vsctl list-ports br-int`:
> int-br-eth3 (created by quantum?)
>
> node B,C `ovs-vsctl list-ports br-eth3`:
> eth3 (added by me)
> phy-br-eth3 (created by quantum?)
>
> eth3 is a NIC which is connected to a switchport accepting VLAN
> 2000:3999. It has no IP assigned currently.
>
> When I start the 12.04 ubuntu "cloud-image" in the dashboard, it
> successfully boots and obtains an IP address as seen in the co
> nsole output:
> cloud-init-nonet waiting 120 seconds for a network device.
>
> ci-info: lo    : 1 127.0.0.1       255.0.0.0       .
> ci-info: eth0  : 1 192.168.253.5   255.255.255.0   fa:16:3e:80:33:71
> ci-info: route-0: 0.0.0.0         192.168.253.1   0.0.0.0         eth0   UG
> ci-info: route-1: 192.168.253.0   0.0.0.0         255.255.255.0   eth0   U
>
> However, immediately after that output I see this
>
> 2012-11-07 11:27:29,598 - util.py[WARNING]: '
> http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]:
> url error [[Errno 113] No route to host]
>
> which runs until it times out.
>
> In older versions of
> OpenStack, when I ran 'iptables-save | grep 169.254.169.254' on a metadataserver I was used to seeing a rule show up
> which translated that 169 address to the variable assigned by metadata_host
> in nova.conf, but I note that rule doesn't show up in this version of
> nova? I added the old rule in (to see what would happen) but the result
> was the same, still no route to host.
>
>
> What steps do I need to take here to allow my instance to retrieve its
> metadata? Is my quantum misconfigured somehow? Perhaps
> I need to go back and reconfigure my switch port (for example, there is
> no real 192.168.253.1 gw, but does there need to be for the instance to
> simply fetch metdata)? After that, what steps do I need to take to get
> the VM connected to the rest of the world? Is the quantum-l3-agent the only
> real choice right now?
>
> Thx.
>
> --
>
> --
> *Sina Sadeghi*
> Lead Cloud Engineer
> <logo.jpg>
>
> *Aptira Pty Ltd*
> 1800 APTIRA
> aptira.com <http://www.aptira.com/>
> Follow @aptira <https://twitter.com/#/aptira>
>
>  _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Kevin Jackson
@itarchitectkev