|
Hello all, I thought I would give 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-plugin-openvswitch node B: nova-compute, nova-api-metadata, quantum-dhcp-agent, quantum-plugin-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 console 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 metadata server 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. |
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
