Re: [Openstack] using vlan tagged ports in cluster

2013-03-16 Thread Pranav
It is common to loose your network in 3 NIC setup that is why the third NIC
card, its ok if you cant ping your public IP directly. But this work around
wont hurt either. This work around has been implemented in two nic VLAN
method in the same git repo.
Regards,
Pranav


On Fri, Mar 15, 2013 at 10:08 PM, JR botem...@gmail.com wrote:

 Rain, I owe you a beer!  That did the trick.  Thanks.

 JR

 On 3/15/2013 11:32 AM, Rain Li wrote:
  Hi, JR,
 
  You should check your route. Before ovs-vsctl add-port br-ex p1p1.4,
  you should have the route entry like:
  192.168.251.0   0.0.0.0  255.255.255.0 U 0 0 0 p1p1.4
  But after that, since p1p1.4 is plugged in br-ex, you should change the
  above route to go through br-ex, and may also change other (default
  route) to this interface as well, if they originally go through p1p1.4.
 
  Regards,
  Rain
 
 
  On Thu, Mar 14, 2013 at 5:22 AM, JR botem...@gmail.com
  mailto:botem...@gmail.com wrote:
 
  Greetings,
 
  I'm setting up openstack on some machines using
 
 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
 .
 
  I'm using 3 nodes: a controller, network node and compute node.  All
 the
  network interfaces are VLAN tagged use the same underlying physical
 10G,
  e.g.,
 
  controller: p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
  net: 10.10.10.*/24)
  network:p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
  net: 10.10.10.*/24), p1p1.6 (vm net: 10.20.20.*/24)
 
  # I haven't gotten to the compute node yet but it should be
  compute:   p1p1.5 (management net: 10.10.10.*/24), p1p1.6 (vm net:
  10.20.20.*/24)
 
  When I bring up my openvswitch bridges on the network node, I can not
  longer get out to the public net (see *MORE* below).
 
  I'm running ubuntu 12.10 and have run apt-get dist-upgrade.  The 10G
  nics are intel 82599EB.  ubuntu seems a bit flakey; initially I'd
  created /etc/udev/rules/70-persistent-net.rules to map p1p1 to eth2,
  however, the config was ignored and eth2 wound up being a 1G NIC.
 
  Is it not allowed to use VLAN interfaces for my networks?
 
  If I remove, say, the br-ex bridge I can get out again:
  root@nebula03:~# ping 192.168.251.1
  PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
  ^C
  --- 192.168.251.1 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms
 
  root@nebula03:~# ovs-vsctl del-port p1p1.4
  root@nebula03:~# ovs-vsctl del-br br-ex
  root@nebula03:~# ping 192.168.251.1
  PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
  64 bytes from 192.168.251.1 http://192.168.251.1: icmp_req=1
  ttl=64 time=0.650 ms
  ^C
  --- 192.168.251.1 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.650/0.650/0.650/0.000 ms
  root@nebula03:~#
 
 
  Thanks for any help,
  JR
 
  
  *MORE*
  
  root@nebula03:~# ovs-vsctl show
  1bdf2f73-1a5d-4893-b745-7501557acaea
  Bridge br-int
  Port br-int
  Interface br-int
  type: internal
  Bridge br-ex
  Port br-ex
  Interface br-ex
  type: internal
  Port p1p1.4
  Interface p1p1.4
  Bridge br-vm
  Port br-vm
  Interface br-vm
  type: internal
  Port p1p1.6
  Interface p1p1.6
  ovs_version: 1.4.3
  root@nebula03:~# ifconfig p1.4
  p1.4: error fetching interface information: Device not found
  root@nebula03:~# ifconfig p1p1.4
  p1p1.4Link encap:Ethernet  HWaddr 90:e2:ba:2c:8a:08
inet addr:192.168.251.92  Bcast:192.168.251.255
  Mask:255.255.255.0
inet6 addr: fe80::92e2:baff:fe2c:8a08/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:20964 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:22269341 (22.2 MB)  TX bytes:594 (594.0 B)
 
  root@nebula03:~# ping 192.168.251.1
  PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
  ^C
  --- 192.168.251.1 ping statistics ---
  2 packets transmitted, 0 received, 100% packet loss, time 1007ms
 
  root@nebula03:~# ping 192.168.251.91`
   ^C
  root@nebula03:~# ping 192.168.251.91
  PING 192.168.251.91 (192.168.251.91) 56(84) bytes of data.
  ^C
 
 
 
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  mailto:openstack@lists.launchpad.net
  

Re: [Openstack] using vlan tagged ports in cluster

2013-03-15 Thread Rain Li
Hi, JR,

You should check your route. Before ovs-vsctl add-port br-ex p1p1.4, you
should have the route entry like:
192.168.251.0   0.0.0.0  255.255.255.0 U 0 0 0 p1p1.4
But after that, since p1p1.4 is plugged in br-ex, you should change the
above route to go through br-ex, and may also change other (default route)
to this interface as well, if they originally go through p1p1.4.

Regards,
Rain


On Thu, Mar 14, 2013 at 5:22 AM, JR botem...@gmail.com wrote:

 Greetings,

 I'm setting up openstack on some machines using

 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
 .

 I'm using 3 nodes: a controller, network node and compute node.  All the
 network interfaces are VLAN tagged use the same underlying physical 10G,
 e.g.,

 controller: p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
 net: 10.10.10.*/24)
 network:p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
 net: 10.10.10.*/24), p1p1.6 (vm net: 10.20.20.*/24)

 # I haven't gotten to the compute node yet but it should be
 compute:   p1p1.5 (management net: 10.10.10.*/24), p1p1.6 (vm net:
 10.20.20.*/24)

 When I bring up my openvswitch bridges on the network node, I can not
 longer get out to the public net (see *MORE* below).

 I'm running ubuntu 12.10 and have run apt-get dist-upgrade.  The 10G
 nics are intel 82599EB.  ubuntu seems a bit flakey; initially I'd
 created /etc/udev/rules/70-persistent-net.rules to map p1p1 to eth2,
 however, the config was ignored and eth2 wound up being a 1G NIC.

 Is it not allowed to use VLAN interfaces for my networks?

 If I remove, say, the br-ex bridge I can get out again:
 root@nebula03:~# ping 192.168.251.1
 PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
 ^C
 --- 192.168.251.1 ping statistics ---
 1 packets transmitted, 0 received, 100% packet loss, time 0ms

 root@nebula03:~# ovs-vsctl del-port p1p1.4
 root@nebula03:~# ovs-vsctl del-br br-ex
 root@nebula03:~# ping 192.168.251.1
 PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
 64 bytes from 192.168.251.1: icmp_req=1 ttl=64 time=0.650 ms
 ^C
 --- 192.168.251.1 ping statistics ---
 1 packets transmitted, 1 received, 0% packet loss, time 0ms
 rtt min/avg/max/mdev = 0.650/0.650/0.650/0.000 ms
 root@nebula03:~#


 Thanks for any help,
 JR

 
 *MORE*
 
 root@nebula03:~# ovs-vsctl show
 1bdf2f73-1a5d-4893-b745-7501557acaea
 Bridge br-int
 Port br-int
 Interface br-int
 type: internal
 Bridge br-ex
 Port br-ex
 Interface br-ex
 type: internal
 Port p1p1.4
 Interface p1p1.4
 Bridge br-vm
 Port br-vm
 Interface br-vm
 type: internal
 Port p1p1.6
 Interface p1p1.6
 ovs_version: 1.4.3
 root@nebula03:~# ifconfig p1.4
 p1.4: error fetching interface information: Device not found
 root@nebula03:~# ifconfig p1p1.4
 p1p1.4Link encap:Ethernet  HWaddr 90:e2:ba:2c:8a:08
   inet addr:192.168.251.92  Bcast:192.168.251.255
 Mask:255.255.255.0
   inet6 addr: fe80::92e2:baff:fe2c:8a08/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:20964 errors:0 dropped:0 overruns:0 frame:0
   TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:22269341 (22.2 MB)  TX bytes:594 (594.0 B)

 root@nebula03:~# ping 192.168.251.1
 PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
 ^C
 --- 192.168.251.1 ping statistics ---
 2 packets transmitted, 0 received, 100% packet loss, time 1007ms

 root@nebula03:~# ping 192.168.251.91`
  ^C
 root@nebula03:~# ping 192.168.251.91
 PING 192.168.251.91 (192.168.251.91) 56(84) bytes of data.
 ^C





 ___
 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] using vlan tagged ports in cluster

2013-03-15 Thread JR
Rain, I owe you a beer!  That did the trick.  Thanks.

JR

On 3/15/2013 11:32 AM, Rain Li wrote:
 Hi, JR, 
 
 You should check your route. Before ovs-vsctl add-port br-ex p1p1.4,
 you should have the route entry like:
 192.168.251.0   0.0.0.0  255.255.255.0 U 0 0 0 p1p1.4
 But after that, since p1p1.4 is plugged in br-ex, you should change the
 above route to go through br-ex, and may also change other (default
 route) to this interface as well, if they originally go through p1p1.4.
 
 Regards,
 Rain
 
 
 On Thu, Mar 14, 2013 at 5:22 AM, JR botem...@gmail.com
 mailto:botem...@gmail.com wrote:
 
 Greetings,
 
 I'm setting up openstack on some machines using
 
 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst.
 
 I'm using 3 nodes: a controller, network node and compute node.  All the
 network interfaces are VLAN tagged use the same underlying physical 10G,
 e.g.,
 
 controller: p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
 net: 10.10.10.*/24)
 network:p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
 net: 10.10.10.*/24), p1p1.6 (vm net: 10.20.20.*/24)
 
 # I haven't gotten to the compute node yet but it should be
 compute:   p1p1.5 (management net: 10.10.10.*/24), p1p1.6 (vm net:
 10.20.20.*/24)
 
 When I bring up my openvswitch bridges on the network node, I can not
 longer get out to the public net (see *MORE* below).
 
 I'm running ubuntu 12.10 and have run apt-get dist-upgrade.  The 10G
 nics are intel 82599EB.  ubuntu seems a bit flakey; initially I'd
 created /etc/udev/rules/70-persistent-net.rules to map p1p1 to eth2,
 however, the config was ignored and eth2 wound up being a 1G NIC.
 
 Is it not allowed to use VLAN interfaces for my networks?
 
 If I remove, say, the br-ex bridge I can get out again:
 root@nebula03:~# ping 192.168.251.1
 PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
 ^C
 --- 192.168.251.1 ping statistics ---
 1 packets transmitted, 0 received, 100% packet loss, time 0ms
 
 root@nebula03:~# ovs-vsctl del-port p1p1.4
 root@nebula03:~# ovs-vsctl del-br br-ex
 root@nebula03:~# ping 192.168.251.1
 PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
 64 bytes from 192.168.251.1 http://192.168.251.1: icmp_req=1
 ttl=64 time=0.650 ms
 ^C
 --- 192.168.251.1 ping statistics ---
 1 packets transmitted, 1 received, 0% packet loss, time 0ms
 rtt min/avg/max/mdev = 0.650/0.650/0.650/0.000 ms
 root@nebula03:~#
 
 
 Thanks for any help,
 JR
 
 
 *MORE*
 
 root@nebula03:~# ovs-vsctl show
 1bdf2f73-1a5d-4893-b745-7501557acaea
 Bridge br-int
 Port br-int
 Interface br-int
 type: internal
 Bridge br-ex
 Port br-ex
 Interface br-ex
 type: internal
 Port p1p1.4
 Interface p1p1.4
 Bridge br-vm
 Port br-vm
 Interface br-vm
 type: internal
 Port p1p1.6
 Interface p1p1.6
 ovs_version: 1.4.3
 root@nebula03:~# ifconfig p1.4
 p1.4: error fetching interface information: Device not found
 root@nebula03:~# ifconfig p1p1.4
 p1p1.4Link encap:Ethernet  HWaddr 90:e2:ba:2c:8a:08
   inet addr:192.168.251.92  Bcast:192.168.251.255
 Mask:255.255.255.0
   inet6 addr: fe80::92e2:baff:fe2c:8a08/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:20964 errors:0 dropped:0 overruns:0 frame:0
   TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:22269341 (22.2 MB)  TX bytes:594 (594.0 B)
 
 root@nebula03:~# ping 192.168.251.1
 PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
 ^C
 --- 192.168.251.1 ping statistics ---
 2 packets transmitted, 0 received, 100% packet loss, time 1007ms
 
 root@nebula03:~# ping 192.168.251.91`
  ^C
 root@nebula03:~# ping 192.168.251.91
 PING 192.168.251.91 (192.168.251.91) 56(84) bytes of data.
 ^C
 
 
 
 
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 mailto: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


[Openstack] using vlan tagged ports in cluster

2013-03-14 Thread JR
Greetings,

I'm setting up openstack on some machines using
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst.

I'm using 3 nodes: a controller, network node and compute node.  All the
network interfaces are VLAN tagged use the same underlying physical 10G,
e.g.,

controller: p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
net: 10.10.10.*/24)
network:p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
net: 10.10.10.*/24), p1p1.6 (vm net: 10.20.20.*/24)

# I haven't gotten to the compute node yet but it should be
compute:   p1p1.5 (management net: 10.10.10.*/24), p1p1.6 (vm net:
10.20.20.*/24)

When I bring up my openvswitch bridges on the network node, I can not
longer get out to the public net (see *MORE* below).

I'm running ubuntu 12.10 and have run apt-get dist-upgrade.  The 10G
nics are intel 82599EB.  ubuntu seems a bit flakey; initially I'd
created /etc/udev/rules/70-persistent-net.rules to map p1p1 to eth2,
however, the config was ignored and eth2 wound up being a 1G NIC.

Is it not allowed to use VLAN interfaces for my networks?

If I remove, say, the br-ex bridge I can get out again:
root@nebula03:~# ping 192.168.251.1
PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
^C
--- 192.168.251.1 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

root@nebula03:~# ovs-vsctl del-port p1p1.4
root@nebula03:~# ovs-vsctl del-br br-ex
root@nebula03:~# ping 192.168.251.1
PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
64 bytes from 192.168.251.1: icmp_req=1 ttl=64 time=0.650 ms
^C
--- 192.168.251.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.650/0.650/0.650/0.000 ms
root@nebula03:~#


Thanks for any help,
JR


*MORE*

root@nebula03:~# ovs-vsctl show
1bdf2f73-1a5d-4893-b745-7501557acaea
Bridge br-int
Port br-int
Interface br-int
type: internal
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
Port p1p1.4
Interface p1p1.4
Bridge br-vm
Port br-vm
Interface br-vm
type: internal
Port p1p1.6
Interface p1p1.6
ovs_version: 1.4.3
root@nebula03:~# ifconfig p1.4
p1.4: error fetching interface information: Device not found
root@nebula03:~# ifconfig p1p1.4
p1p1.4Link encap:Ethernet  HWaddr 90:e2:ba:2c:8a:08
  inet addr:192.168.251.92  Bcast:192.168.251.255 
Mask:255.255.255.0
  inet6 addr: fe80::92e2:baff:fe2c:8a08/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:20964 errors:0 dropped:0 overruns:0 frame:0
  TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:22269341 (22.2 MB)  TX bytes:594 (594.0 B)

root@nebula03:~# ping 192.168.251.1
PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
^C
--- 192.168.251.1 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1007ms

root@nebula03:~# ping 192.168.251.91`
 ^C
root@nebula03:~# ping 192.168.251.91
PING 192.168.251.91 (192.168.251.91) 56(84) bytes of data.
^C





___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp