Re: [Openstack] OpenStack Multi Node Problems with OVS
Hi Folks, I am working on bringing up a multi node OpenStack environment with OVS. I have a Controller, Compute and a Gateway/Network node. This is running Folsom. Most of the services are up, except that I cannot ping the floating ip of the VM. What kind of setup are you creating? Bridge_mapped networks? Private networks (with GRE tunnels)? If you are setting this up with GRE I'm missing the GRE tunnels in the ovs-vsctl show overview. You should have GRE tunnels to all Compute nodes in the network. To start troubleshooting I would first check if networking works between compute nodes: Start two VM's, on different Compute nodes, in the same subnet and see if they can reach each other. (If they do not get a DHCP IP just put in a static IP for now) There is bug with rebooting the machines running dhcp / l3-agent which might be good to be aware of: https://bugs.launchpad.net/quantum/+bug/1091605 Cheers, Robert van Leeuwen ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack Multi Node Problems with OVS
It is Private Networks (VLAN). Networking works between all the devices. I am pretty sure this is a bug. I am also seeing the following message on my compute server (see below). The error message is indicating that it is not getting the proper values when running the command. I confirmed as user root, quantum, nova that I can easily run the command get the output. Atif... == /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini [OVS] tenant_network_type=vlan network_vlan_ranges = physnet1:500:1000 bridge_mappings = physnet1:br-eth1 === openvswitch-agent.log 2013-04-17 07:29:37 DEBUG [quantum.agent.linux.utils] Running command: sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf ovs-vsctl --timeout=2 list-ports br-int 2013-04-17 07:29:38 DEBUG [quantum.agent.linux.utils] Command: ['sudo', '/usr/bin/quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ovs-vsctl', '--timeout=2', 'list-ports', 'br-int'] Exit code: 0 From: Robert van Leeuwen robert.vanleeu...@spilgames.com To: openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Wednesday, April 17, 2013 3:45 AM Subject: Re: [Openstack] OpenStack Multi Node Problems with OVS Hi Folks, I am working on bringing up a multi node OpenStack environment with OVS. I have a Controller, Compute and a Gateway/Network node. This is running Folsom. Most of the services are up, except that I cannot ping the floating ip of the VM. What kind of setup are you creating? Bridge_mapped networks? Private networks (with GRE tunnels)? If you are setting this up with GRE I'm missing the GRE tunnels in the ovs-vsctl show overview. You should have GRE tunnels to all Compute nodes in the network. To start troubleshooting I would first check if networking works between compute nodes: Start two VM's, on different Compute nodes, in the same subnet and see if they can reach each other. (If they do not get a DHCP IP just put in a static IP for now) There is bug with rebooting the machines running dhcp / l3-agent which might be good to be aware of: https://bugs.launchpad.net/quantum/+bug/1091605 Cheers, Robert van Leeuwen ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack Multi Node Problems with OVS
hi folks, so an update to the networking issues various people have been seeing. I updated the openvswitch package from source instead of apt-get and things are much better now. The errors/warnings in the various log files are now gone. the ovs-dpctl works now without complaint. Im still not able to get the VMs to talk to the outside world but Im beginning to think its a fault with my understanding. I have a node that is both controller and network that is the gateway for the rest of the compute nodes. I suspect that since I only have 1 routable IP address from our network folks Ive configured things wrong. s -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # signature.asc Description: OpenPGP digital signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack Multi Node Problems with OVS
Welcome to the club :)
Been fighting the same problem for a week now. Nothing is working...
Found lots of other people complaining on the web even with grizzly like I'm
using.
S
Atif Wasi aw...@yahoo.com wrote:
Hi Folks,
I am working on bringing up a multi node OpenStack environment with
OVS. I have a Controller, Compute and a Gateway/Network node. This is
running Folsom. Most of the services are up, except that I cannot ping
the floating ip of the VM.
Below are the error messages I am seeing the Gateway/Network node:
root@gateway:/var/log/quantum# ovs-vsctl show
9f3f021a-cb8e-4ef4-87a5-f5bab9f3
Bridge br-ex
Port eth2
Interface eth2
Port qg-0aff855e-9c
Interface qg-0aff855e-9c
type: internal
Port br-ex
Interface br-ex
type: internal
Bridge br-eth1
Port eth1
Interface eth1
Port phy-br-eth1
Interface phy-br-eth1
Port br-eth1
Interface br-eth1
type: internal
Bridge br-int
Port br-int
Interface br-int
type: internal
Port int-br-eth1
Interface int-br-eth1
Port tap47ac110a-fe
tag: 1
Interface tap47ac110a-fe
type: internal
Port qr-12091c58-8a
tag: 1
Interface qr-12091c58-8a
type: internal
ovs_version: 1.4.3
=
L3 Agent.log:
2013-04-16 22:06:08DEBUG [quantum.agent.linux.utils] Running
command: ip -o link show br-ex
2013-04-16 22:06:08DEBUG [quantum.agent.linux.utils]
Command: ['ip', '-o', 'link', 'show', 'br-ex']
Exit code: 0
Stdout: '20: br-ex: BROADCAST,MULTICAST mtu 1500 qdisc noop state
DOWN mode DEFAULT \\link/ether 00:04:23:c9:64:ac brd
ff:ff:ff:ff:ff:ff\n'
Stderr: ''
2013-04-16 22:06:08DEBUG [quantumclient.client] REQ: curl -i
http://192.168.0.2:9696//v2.0/networks.json?router%3Aexternal=True -X
GET -H User-Agent: python-quantumclient -H Content-Type:
application/json -H Accept: application/json -H X-Auth-Token:
3c2cc4afb68f4042bf4bddd9908186d0
2013-04-16 22:06:08DEBUG [quantumclient.client] RESP:{'date': 'Wed,
17 Apr 2013 02:06:08 GMT', 'status': '200', 'content-length': '376',
'content-type': 'application/json', 'content-location':
u'http://192.168.0.2:9696//v2.0/networks.json?router%3Aexternal=True'}
2013-04-16 22:06:08DEBUG [quantumclient.client] RESP
BODY:{networks: [{status: ACTIVE, subnets:
[487ccc01-81ea-4abc-bbb4-061cde722801], name: ext_net,
provider:physical_network: physnet1, admin_state_up: true,
tenant_id: 6bd416e48a394f06bfbf4d0856740262,
provider:network_type: vlan, router:external: true, shared:
false, id: 2f2aa2c9-47be-4b3e-9f05-a547a8d3aaa9,
provider:segmentation_id: 500}]}
2013-04-16 22:06:08DEBUG [quantumclient.client] REQ: curl -i
http://192.168.0.2:9696//v2.0/routers.json -X GET -H User-Agent:
python-quantumclient -H Content-Type: application/json -H Accept:
application/json -H X-Auth-Token: 3c2cc4afb68f4042bf4bddd9908186d0
2013-04-16 22:06:08DEBUG [quantumclient.client] RESP:{'date': 'Wed,
17 Apr 2013 02:06:08 GMT', 'status': '200', 'content-length': '262',
'content-type': 'application/json', 'content-location':
u'http://192.168.0.2:9696//v2.0/routers.json'}
2013-04-16 22:06:08DEBUG [quantumclient.client] RESP
BODY:{routers: [{status: ACTIVE, external_gateway_info:
{network_id: 2f2aa2c9-47be-4b3e-9f05-a547a8d3aaa9}, name:
router_proj_one, admin_state_up: true, tenant_id:
b443045cd0d54377b637cc0ba998bf89, id:
49a92bbc-5f58-400a-a8cb-aebcf54db446}]}
2013-04-16 22:06:08DEBUG [quantumclient.client] REQ: curl -i
http://192.168.0.2:9696//v2.0/ports.json?device_owner=network%3Arouter_gatewaydevice_id=49a92bbc-5f58-400a-a8cb-aebcf54db446
-X GET -H User-Agent: python-quantumclient -H Content-Type:
application/json -H Accept: application/json -H X-Auth-Token:
3c2cc4afb68f4042bf4bddd9908186d0
2013-04-16 22:06:08DEBUG [quantumclient.client] RESP:{'date': 'Wed,
17 Apr 2013 02:06:08 GMT', 'status': '200', 'content-length': '417',
'content-type': 'application/json', 'content-location':
u'http://192.168.0.2:9696//v2.0/ports.json?device_owner=network%3Arouter_gatewaydevice_id=49a92bbc-5f58-400a-a8cb-aebcf54db446'}
2013-04-16 22:06:08DEBUG [quantumclient.client] RESP BODY:{ports:
[{status: ACTIVE, name: , admin_state_up: true, network_id:
2f2aa2c9-47be-4b3e-9f05-a547a8d3aaa9, tenant_id: ,
device_owner: network:router_gateway, mac_address:
fa:16:3e:3a:fe:6a, fixed_ips: [{subnet_id:
487ccc01-81ea-4abc-bbb4-061cde722801, ip_address: 192.168.1.10}],
id: 0aff855e-9cab-4dad-a490-7019e104603a, device_id:
49a92bbc-5f58-400a-a8cb-aebcf54db446}]}
2013-04-16 22:06:08DEBUG [quantumclient.client] REQ: curl -i
