On May 16, 2012, at 7:53 AM, Ask Stack wrote: > Kyle > > Thanks. Below is my nova.conf > > > [DEFAULT] > logdir = /var/log/nova > state_path = /var/lib/nova > lock_path = /var/lib/nova/tmp > dhcpbridge = /usr/bin/nova-dhcpbridge > dhcpbridge_flagfile = /etc/nova/nova.conf > force_dhcp_release = True > injected_network_template = /usr/share/nova/interfaces.template > libvirt_xml_template = /usr/share/nova/libvirt.xml.template > libvirt_nonblocking = True > vpn_client_template = /usr/share/nova/client.ovpn.template > credentials_template = /usr/share/nova/novarc.template > network_manager = nova.network.quantum.manager.QuantumManager > #network_manager = nova.network.manager.FlatDHCPManager > iscsi_helper = tgtadm > sql_connection = mysql://nova:nova@localhost/nova > connection_type = libvirt > firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver > rpc_backend = nova.rpc.impl_qpid > root_helper = sudo nova-rootwrap > auth_strategy = keystone > admin_token = a19c602bc5f8c10c47ea > libvirt_vif_type = ethernet > libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtOpenVswitchDriver > linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver > quantum_use_dhcp = True OK, so you are using the old style libvirt + OVS driver. This means that Nova will be creating tap devices during plug operations, and removing them during unplug operations. In your case, it appears the tap is being added to the OVS bridge. You also have a gateway device being added to the bridge as well. From your previous output, it looks like both devices are up even, given your tcpdump output. So it's unclear to me why the ping isn't working. What does the output of "ovs-ofctl dump-flows br-int" indicate? It should be setup to use L2 learning in your case, verify that. _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud
