Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Quantum Networking Clarification

So I'm new to Quantum but have been working with Openstack since Essex. There is one thing that I cannot seem to wrap my head around which are the Quantum network types. Coming from Nova Networking these options are a lot more detailed then what was available though Nova. I guess I'm trying to find out which would fit my setup best.

Configuration:

1 - Cloud Controller 1 - Network Node 7 - Compute Nodes

/23 public (access) IP range Unlimited NIC cards (If I need more I can add more, but have tried with 3) 48 port Cisco Switch

Questions that I have

Types: Local - Is this setting only for single node installations? Successfully setup an all-in-one Openstack node but networking fails when I add another node.

Flat - Initial figured this will work but see no documentation whatsoever on setting up Flat.

VLAN - If I have to I guess I can setup a VLAN but would rather not have to deal with contacting the network engineer. If I had access to the Cisco switch I would probably go down this route but I am still open to the idea of setting up a VLAN if its the easiest route.

GRE - don't know much about GRE networks and tunneling and see that tunneling requires you build from source. If it proves to be the easiest route then I can also do down this route.

Information

Ifconfig output http://pastebin.com/GumNSB1G

GRE plugin.ini http://pastebin.com/0pwFc3vW

Local plugin.ini http://pastebin.com/05K5xaZw

quantum.conf http://pastebin.com/8fZWLp13

Issue

Everytime I start openvswith I get the following error message.

2013-08-07T18:45:07Z|00002|worker(worker)|INFO|worker process started 2013-08-07T18:45:07Z|00002|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting... 2013-08-07T18:45:07Z|00003|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected 2013-08-07T18:45:07Z|00004|netdev_linux|ERR|ioctl(SIOCSIFHWADDR) on br-int device failed: Device or resource busy 2013-08-07T18:45:07Z|00005|bridge|ERR|bridge br-int: failed to set bridge Ethernet address: Device or resource busy 2013-08-07T18:45:07Z|00006|bridge|INFO|bridge br-int: using datapath ID 0000d62c8e91cc45 2013-08-07T18:45:07Z|00007|connmgr|INFO|br-int: added service controller "punix:/var/run/openvswitch/br-int.mgmt" 2013-08-07T18:45:07Z|00008|bridge|INFO|ovs-vswitchd (Open vSwitch) 1.10.0 2013-08-07T18:45:17Z|00009|memory|INFO|7724 kB peak resident set size after 10.0 seconds 2013-08-07T18:45:17Z|00010|memory|INFO|ports:1 rules:3

Quantum Networking ClarificationHow to solve error "failed to set bridge Ethernet address" with Neutron and OVS?

So I'm new to Quantum but have been working with Openstack since Essex. There is one thing that I cannot seem to wrap my head around which are the Quantum network types. Coming from Nova Networking these options are a lot more detailed then what was available though Nova. I guess I'm trying to find out which would fit my setup best.

Configuration:

  • 1 - Cloud Controller Controller
  • 1 - Network Node Node
  • 7 - Compute Nodes

  • /23 public (access) IP range range
  • Unlimited NIC cards (If I need more I can add more, but have tried with 3) 3)
  • 48 port Cisco Switch

Questions that I have

Types: - Local - Is this setting only for single node installations? Successfully setup an all-in-one Openstack node but networking fails when I add another node.


-
Flat - Initial figured this will work but see no documentation whatsoever on setting up Flat.

- VLAN - If I have to I guess I can setup a VLAN but would rather not have to deal with contacting the network engineer. If I had access to the Cisco switch I would probably go down this route but I am still open to the idea of setting up a VLAN if its the easiest route.

route. - GRE - don't know much about GRE networks and tunneling and see that tunneling requires you build from source. If it proves to be the easiest route then I can also do down this route.

Information

Issue

Everytime I start openvswith I get the following error message.

2013-08-07T18:45:07Z|00002|worker(worker)|INFO|worker process started
2013-08-07T18:45:07Z|00002|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting...
2013-08-07T18:45:07Z|00003|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected
2013-08-07T18:45:07Z|00004|netdev_linux|ERR|ioctl(SIOCSIFHWADDR) on br-int device failed: Device or resource busy
2013-08-07T18:45:07Z|00005|bridge|ERR|bridge br-int: failed to set bridge Ethernet address: Device or resource busy
2013-08-07T18:45:07Z|00006|bridge|INFO|bridge br-int: using datapath ID 0000d62c8e91cc45
2013-08-07T18:45:07Z|00007|connmgr|INFO|br-int: added service controller "punix:/var/run/openvswitch/br-int.mgmt"
2013-08-07T18:45:07Z|00008|bridge|INFO|ovs-vswitchd (Open vSwitch) 1.10.0
2013-08-07T18:45:17Z|00009|memory|INFO|7724 kB peak resident set size after 10.0 seconds
2013-08-07T18:45:17Z|00010|memory|INFO|ports:1 rules:3

rules:3