sunil-srivastava's profile - activity

2016-03-23 08:27:15 -0600 received badge  Famous Question (source)
2016-03-23 08:27:15 -0600 received badge  Notable Question (source)
2016-03-23 08:27:15 -0600 received badge  Popular Question (source)
2015-08-18 17:04:37 -0600 received badge  Famous Question (source)
2015-08-06 08:15:29 -0600 received badge  Famous Question (source)
2014-11-10 10:01:24 -0600 received badge  Notable Question (source)
2014-09-24 16:01:32 -0600 received badge  Popular Question (source)
2014-09-24 16:01:32 -0600 received badge  Notable Question (source)
2014-06-16 06:43:31 -0600 received badge  Popular Question (source)
2012-11-20 23:07:26 -0600 answered a question Can quantum-l3-agent run on each compute node?

Dan,

Can you please point to a blue-print on the feature planned for Grizzly?

Thanks, Sunil.

2012-11-20 21:47:36 -0600 asked a question Can quantum-l3-agent run on each compute node?

Know Network Node can be only one and for HA Pacemaker is used.

But I see compute node to communicate to External Network or Internet, has to always go via Local Network to Network Node and then to External Network Node. This is an unnecessary hop and for tens of thousands of VMs, this may become a bottleneck.

Can't the compute nodes stil use Local Network to communicate with each other, but use External Network, through their own Network NS and IP Tables maps?

Thanks, Sunil.

2012-11-16 22:11:53 -0600 asked a question nova boot silently picks up IP Address for External Network

I ran devstack stack.sh, and it created private and external network.

I could do ssh using private, access Internet from inside VM, and also do Floating IP. nova boot did not have any options for --nic. VMs had not picked up any addresses on External Net.

Then I manually removed the port, network, subnet, gateway and router, besides deleting detaching and deleting floating ip assigned.

Afterwards, I manually did the same steps which devstack stack.sh does and did nova boot without --nic option.

The two VMs I had spawned had also picked up external IP Addresses.

192.168.128/28 was used as external network. 129 went to br-ex, 130 went to gg*, and 131 and 132 got assigned to 2 VMs. I could still do FLoating IP with 133 and 134. Besides ssh from Management Controller Node on Floating IPs, I could only SSH 131 which went to remote node but not to local 132. Routes point to br-ex. There were no DNAT/SNAT rules for 132 and 131.

Following CLIs were run.

quantum net-create ext_net -- --router:external=True quantum subnet-create --ip_version 4 66bb2246-51db-4b09-a608-e91f83b64bbb $FLOATING_RANGE -- --enable_dhcp=False

This sounds like some bug.

2012-11-08 20:17:17 -0600 asked a question LibvirtOpenVswitchDriver vs LibvirtHybridOVSBridgeDriver

I understand the differences and looked at code.

But trying to understand why " ip', 'tuntap', 'add', dev, 'mode', 'tap'" is used in OVS and why it is not used for Linux Bridges or OVS Bridge?

Then trying to understand usage of vether in the HYbrid case. We have qvo* on OVS and qvb* on Linux Bridge. VM is attached to qbr* directly or qvb*?

Understand qvo* and qvb* are linked together as vether, but do this go via qbr*?

Also, if someone could explain how a VM VIF is instantiated through LibVIrt.

Things a bit hazy reading the code and need some good soul to walk through it and clarify for me.

Regards, Sunil.

2012-09-26 21:55:55 -0600 answered a question Why would an OVS bridge not forward ARP

Thanks Eoghan, that solved my question.

2012-09-21 07:03:31 -0600 answered a question Why would an OVS bridge not forward ARP

Sorry, I need to go. Someone from EMC would follow up.

2012-09-21 07:03:28 -0600 answered a question Why would an OVS bridge not forward ARP

Sorry, I need to go. Someone from EMC would follow up.

2012-09-21 07:01:47 -0600 answered a question Why would an OVS bridge not forward ARP

Someone else has been on the setup and things have changed a bit.

He said he entered a flow entry - but I did not have time to follow up. I am in R/O mode. :-)

br-eth0 was brought up and that may have changed the behavior.

Now ARP is reach the other machine, and I can see the traffic on eth0, phy-br-eth0 and int-br-eth0.

But there is not ARP reply. The ARPs are not getting to any of the TAP interfaces (but I only did once).

The br-int seems to be dropping now.

BTW, one TAP interface is not there as VM was brought down but ovs-vsctl has it.

stack@esg-dell-c4-s10:~/devstack$ ovs-dpctl show br-eth0 flows system@br-eth0: lookups: hit:658100 missed:119465 lost:0 flows: 27 port 0: br-eth0 (internal) port 6: eth0 port 9: phy-br-eth0 ovs-dpctl: opening datapath flows failed (No such device)

stack@esg-dell-c4-s10:~/devstack$ sudo ovs-ofctl dump-flows br-eth0 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=54070.378s, table=0, n_packets=80, n_bytes=6552, priority=2,in_port=9 actions=drop cookie=0x0, duration=54070.663s, table=0, n_packets=632974, n_bytes=79155773, priority=1 actions=NORMAL

stack@esg-dell-c4-s10:~/devstack$ ovs-dpctl show br-eth0 flows system@br-eth0: lookups: hit:660125 missed:119838 lost:0 flows: 30 port 0: br-eth0 (internal) port 6: eth0 port 9: phy-br-eth0 ovs-dpctl: opening datapath flows failed (No such device)

stack@esg-dell-c4-s10:~/devstack$ sudo ovs-ofctl dump-flows br-int NXST_FLOW reply (xid=0x4): cookie=0x0, duration=54307.045s, table=0, n_packets=608686, n_bytes=77906470, priority=2,in_port=18 actions=drop cookie=0x0, duration=54307.359s, table=0, n_packets=14395, n_bytes=2748282, priority=1 actions=NORMAL

stack@esg-dell-c4-s10:~/devstack$ ovs-dpctl show br-int flows system@br-int: lookups: hit:631616 missed:143682 lost:0 flows: 26 port 0: br-int (internal) Sep 21 03:00:32|00001|netdev_linux|WARN|/sys/class/net/tap26583155-34/carrier: open failed: No such file or directory port 1: tap26583155-34 (internal) port 14: tapd1802d22-b4 port 15: tapfa0e7fcf-8d port 16: tap5eb27feb-05 port 18: int-br-eth0 ovs-dpctl: opening datapath flows failed (No such device)

2012-09-21 06:26:42 -0600 answered a question Why would an OVS bridge not forward ARP

Hi Aron,

Here is the TCP Dumps.

The following output show there is no link issue between phy-br-eth0 and int-br-eth0.

(1)

root@esg-dell-c4-s11:~# ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_req=1 ttl=64 time=0.056 ms 64 bytes from 10.0.0.2: icmp_req=2 ttl=64 time=0.052 ms 64 bytes from 10.0.0.2: icmp_req=3 ttl=64 time=0.032 ms 64 bytes from 10.0.0.2: icmp_req=4 ttl=64 time=0.041 ms 64 bytes from 10.0.0.2: icmp_req=5 ttl=64 time=0.048 ms --- 10.0.0.2 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms

The above triggers this below on int-br-eth0

stack@esg-dell-c4-s11:~/devstack$ sudo tcpdump -i int-br-eth0 arp and src 10.0.0.2 tcpdump: WARNING: int-br-eth0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on int-br-eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 00:41:55.755545 ARP, Request who-has http://inenbasavbl1c.corp.emc.com tell http://usxxstephc2mbp1.corp.emc.com , length 28 00:41:56.753793 ARP, Request who-has http://inenbasavbl1c.corp.emc.com tell http://usxxstephc2mbp1.corp.emc.com , length 28 00:41:57.753782 ARP, Request who-has http://inenbasavbl1c.corp.emc.com tell http://usxxstephc2mbp1.corp.emc.com , length 28 00:41:58.771011 ARP, Request who-has http://inenbasavbl1c.corp.emc.com tell http://usxxstephc2mbp1.corp.emc.com , length 28 00:41:59.769790 ARP, Request who-has http://inenbasavbl1c.corp.emc.com tell http://usxxstephc2mbp1.corp.emc.com , length 28 00:42:00.769796 ARP, Request who-has http://inenbasavbl1c.corp.emc.com tell http://usxxstephc2mbp1.corp.emc.com , length 28

(2)

And again on phy-br-eth0.

root@esg-dell-c4-s11:~# ping 10.0.0.3 PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data. From 10.0.0.2 icmp_seq=1 Destination Host Unreachable From 10.0.0.2 icmp_seq=2 Destination Host Unreachable From 10.0.0.2 icmp_seq=3 Destination Host Unreachable ^C --- 10.0.0.3 ping statistics --- 5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4024ms

stack@esg-dell-c4-s11:~/devstack$ sudo tcpdump -i phy-br-eth0 arp and src 10.0.0.2 tcpdump: WARNING: phy-br-eth0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on phy-br-eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 00:43:35.871097 ARP, Request who-has http://inenbasavbl1c.corp.emc.com tell http://usxxstephc2mbp1.corp.emc.com , length 28 00:43:36.869787 ARP, Request who-has http://inenbasavbl1c.corp.emc.com tell http://usxxstephc2mbp1.corp.emc.com , length 28 00:43:37.873777 ARP, Request who-has http://inenbasavbl1c.corp.emc.com tell http://usxxstephc2mbp1.corp.emc.com , length 28 00:43:38.887008 ARP, Request who-has http://inenbasavbl1c.corp.emc.com tell http://usxxstephc2mbp1.corp.emc.com , length ... (more)

2012-09-21 05:24:04 -0600 answered a question Why would an OVS bridge not forward ARP

Hi Yong,

That is not the root cause. Still.

stack@esg-dell-c4-s11:~/gitstack/devstack$ quantum net-list +--------------------------------------+---------+--------------------------------------+ | id | name | subnets | +--------------------------------------+---------+--------------------------------------+ | 68f76ec1-407b-4e42-a089-d0e6553473f8 | ext_net | 09851d25-806f-492c-b708-bf03838d77b3 | | fa8f9c5e-e41a-4f80-955c-94b3a45b9dcb | net1 | 31ed889f-f3f5-4faa-bb51-1d92344c91a3 | +--------------------------------------+---------+--------------------------------------+

stack@esg-dell-c4-s11:~/gitstack/devstack$ quantum net-show net1 +---------------------------+--------------------------------------+ | Field | Value | +---------------------------+--------------------------------------+ | admin_state_up | True | | id | fa8f9c5e-e41a-4f80-955c-94b3a45b9dcb | | name | net1 | | provider:network_type | local | | provider:physical_network | | | provider:segmentation_id | | | router:external | False | | shared | False | | status | ACTIVE | | subnets | 31ed889f-f3f5-4faa-bb51-1d92344c91a3 | | tenant_id | b0d8717a0f8b4cf8bdff8d84156622af |

stack@esg-dell-c4-s11:~/gitstack/devstack$ quantum net-show ext_net +---------------------------+--------------------------------------+ | Field | Value | +---------------------------+--------------------------------------+ | admin_state_up | True | | id | 68f76ec1-407b-4e42-a089-d0e6553473f8 | | name | ext_net | | provider:network_type | local | | provider:physical_network | | | provider:segmentation_id | | | router:external | True | | shared | False | | status | ACTIVE | | subnets | 09851d25-806f-492c-b708-bf03838d77b3 | | tenant_id | 44cb33fdc72b44ad8e200a1326199895 | +---------------------------+--------------------------------------+

+---------------------------+--------------------------------------+

2012-09-21 05:20:44 -0600 answered a question Why would an OVS bridge not forward ARP

Hi Aaron,

I am leaving on some trip, and would not have access.

The br-eth0 is up and tried that still but did not work.

stack@esg-dell-c4-s11:~/gitstack/devstack$ ifconfig br-eth0 Link encap:Ethernet HWaddr 00:21:9b:c9:d9:83 inet6 addr: fe80::221:9bff:fec9:d983/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:660411 errors:0 dropped:1883 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:84199314 (84.1 MB) TX bytes:468 (468.0 B)

Sunil.

2012-09-21 00:53:06 -0600 answered a question Why would an OVS bridge not forward ARP

The switch is connected to eth0 and configured to take VLAN #1 and set in trunk mode.

2012-09-21 00:48:17 -0600 answered a question Why would an OVS bridge not forward ARP

Hi Aaron,

Please see this outout. It is phy-br-eth0.

stack@esg-dell-c4-s11:~$ sudo ovs-ofctl show br-eth0 OFPT_FEATURES_REPLY (xid=0x1): ver:0x1, dpid:000000219bc9d983 n_tables:255, n_buffers:256 features: capabilities:0xc7, actions:0xfff 5(phy-br-eth0): addr:06:ee:0f:8c:92:b3 config: 0 state: 0 current: 10GB-FD COPPER 8(eth0): addr:00:21:9b:c9:d9:83 config: 0 state: 0 current: 1GB-FD FIBER AUTO_NEG advertised: 1GB-FD AUTO_NEG supported: 10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-FD COPPER FIBER AUTO_NEG LOCAL(br-eth0): addr:00:21:9b:c9:d9:83 config: PORT_DOWN state: LINK_DOWN OFPT_GET_CONFIG_REPLY (xid=0x3): frags=normal miss_send_len=0

2012-09-21 00:35:49 -0600 answered a question Why would an OVS bridge not forward ARP

--- 10.0.0.6 ping statistics --- 70 packets transmitted, 0 received, +65 errors, 100% packet loss, time 69300ms

The drops packets (7780-7717 = 63) come close to 65 errors but not sure if 100% co relation can be made.

But we did tcp dump on ARPs for src IP on Rx and Tx side.

Rx side showed ARP packets coming and Tx side showed no ARP Packets leaving.

2012-09-21 00:29:56 -0600 answered a question Why would an OVS bridge not forward ARP

This is a sample when ping was going on and failing.

stack@esg-dell-c4-s11:~$ sudo ovs-ofctl dump-flows br-eth0 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=30832.687s, table=0, n_packets=7717, n_bytes=326498, priority=2,in_port=5 actions=drop cookie=0x0, duration=30833.044s, table=0, n_packets=336783, n_bytes=41878623, priority=1 actions=NORMAL stack@esg-dell-c4-s11:~$ sudo ovs-ofctl dump-flows br-eth0 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=30835.541s, table=0, n_packets=7717, n_bytes=326498, priority=2,in_port=5 actions=drop cookie=0x0, duration=30835.898s, table=0, n_packets=336806, n_bytes=41881064, priority=1 actions=NORMAL stack@esg-dell-c4-s11:~$ sudo ovs-ofctl dump-flows br-eth0 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=30845.057s, table=0, n_packets=7720, n_bytes=326628, priority=2,in_port=5 actions=drop cookie=0x0, duration=30845.414s, table=0, n_packets=336907, n_bytes=41893018, priority=1 actions=NORMAL stack@esg-dell-c4-s11:~$ sudo ovs-ofctl dump-flows br-eth0 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=30847.233s, table=0, n_packets=7722, n_bytes=326712, priority=2,in_port=5 actions=drop cookie=0x0, duration=30847.59s, table=0, n_packets=336925, n_bytes=41895113, priority=1 actions=NORMAL stack@esg-dell-c4-s11:~$ sudo ovs-ofctl dump-flows br-eth0 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=30853.972s, table=0, n_packets=7729, n_bytes=327006, priority=2,in_port=5 actions=drop cookie=0x0, duration=30854.329s, table=0, n_packets=337000, n_bytes=41903665, priority=1 actions=NORMAL stack@esg-dell-c4-s11:~$ sudo ovs-ofctl dump-flows br-eth0 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=30861.609s, table=0, n_packets=7736, n_bytes=327300, priority=2,in_port=5 actions=drop cookie=0x0, duration=30861.966s, table=0, n_packets=337083, n_bytes=41911871, priority=1 actions=NORMAL stack@esg-dell-c4-s11:~$ sudo ovs-ofctl dump-flows br-eth0 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=30873.43s, table=0, n_packets=7748, n_bytes=327804, priority=2,in_port=5 actions=drop cookie=0x0, duration=30873.787s, table=0, n_packets=337217, n_bytes=41927882, priority=1 actions=NORMAL stack@esg-dell-c4-s11:~$ sudo ovs-ofctl dump-flows br-eth0 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=30886.031s, table=0, n_packets=7761, n_bytes=328350, priority=2,in_port=5 actions=drop cookie=0x0, duration=30886.388s, table=0, n_packets=337345, n_bytes=41942673, priority=1 actions=NORMAL stack@esg-dell-c4-s11:~$ sudo ovs-ofctl dump-flows br-eth0 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=30902.643s, table=0, n_packets=7780, n_bytes=329156, priority=2,in_port=5 actions=drop cookie=0x0, duration=30903s, table=0, n_packets=337542, n_bytes=41964462, priority=1 actions=NORMAL

2012-09-20 23:55:49 -0600 answered a question Why would an OVS bridge not forward ARP

$ sudo ovs-ofctl dump-flows br-int NXST_FLOW reply (xid=0x4): cookie=0x0, duration=27644.955s, table=0, n_packets=285993, n_bytes=36330627, priority=2,in_port=20 actions=drop cookie=0x0, duration=27645.393s, table=0, n_packets=38985, n_bytes=7265979, priority=1 actions=NORMAL $ sudo ovs-ofctl dump-flows br-eth0 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=27656.544s, table=0, n_packets=7708, n_bytes=326108, priority=2,in_port=5 actions=drop cookie=0x0, duration=27656.901s, table=0, n_packets=299545, n_bytes=37154475, priority=1 actions=NORMAL

2012-09-20 23:07:13 -0600 asked a question Why would an OVS bridge not forward ARP

Bridge "br-eth0" Port "br-eth0" Interface "br-eth0" type: internal Port "eth0" Interface "eth0" Port "phy-br-eth0" Interface "phy-br-eth0" Bridge br-int Port "tap55d1e5e8-ab" tag: 1 Interface "tap55d1e5e8-ab" type: internal Port "qr-4b50a17d-3c" tag: 1 Interface "qr-4b50a17d-3c" type: internal Port "int-br-eth0" Interface "int-br-eth0" Port "tape8d6e0a5-52" tag: 1 Interface "tape8d6e0a5-52" Port "tap6176588e-48" tag: 1 Interface "tap6176588e-48" Port br-int Interface br-int type: internal

I can see ARP packets sent from int-br-eth0 to phy-br-eth0 but not to upstream eth0.

So we cannot ping from one VM (or DHCP NetNS) on one machine to another VM on another machine.

I see the ping triggering ARPs. The Tx counter of int-br-eth0 and Rx counter of phy-br-eth0 were also corelated with ping.

2012-09-18 17:25:22 -0600 answered a question Quantum L3 on multinode

Did not follow

C. create ovs bridge for default (we have to do it because we must provide physical binding for virtual network) sudo ovs-vsctl add-br br-default

understood for br-ex and br-eth0.

2012-09-18 16:58:58 -0600 answered a question Quantum L3 on multinode

Thanks. Had similar idea.

For HA, don't we meed Router on each Node?

The model I had was they have private network to talk to each other, but when going on to internet, they would have a dedciated route on each node.

Otherwise one node with Routing becomes a Single Point of Failure.

Then how does the S NAT and D NAT Rules apply for Compute Node to talk to Internet - with remote Router Node as well as local Router Node.

I am keeping VLAN model from Nova Network in mind but with HA as an add on option. I hope all these are expalined.

2012-09-17 15:50:24 -0600 asked a question Quantum L3 on multinode

Can anyone share the config flags for multinode, for controller and compute nodes?

And between compute nodes we would have VLAN bridging.

And one compute Node with Dual NIC would act as a router to external network.

Can this functionality be on each Compute node for HA?

Sunil.

2012-09-11 00:10:13 -0600 answered a question Connection to meta-data server

Can someone give an update on this? Is this working? I am still having issues.

I have got latest devstack as of 09/10/2012 and also defined Q_META_DATA_IP variable to local N-API server. I am just trying 1 node config only.

See the stack.sh is calling

quantum router-gateway-set $ROUTER_ID $EXT_NET_ID

I see the router and exteneral gatway but do not see any NAT rules created.

2012-03-08 21:58:33 -0600 answered a question Quantum with vSwitch on 2 Compute Nodes

Thanks for the reply. I am new to Open Stack and treat me as an end user for now.

I have read the docs and would read them again but have some conceptual questions as the docs are very confusing. ;-)

I like to see diagrams. ;-)

If we can speak, it would be better.

(1)

I am running devstack stack.sh to install s/w.

For running stack.sh on second node, what flags I need? I am not sure of what all components I need to install when running stack.sh.

I could narrow down to these but that is still a larger combination.

ENABLED_SERVICES="n-api,n-cpu,n-net,n-vnc,openstackx,quantum,q-agt"

(3)

Assume you have two Compute Nodes connected on 2 Ports of an Upstream Access Switch.

We create a network L2 N1, and launch Guest 1 on Host 1 and Guest 2 on Host 2.

So will the two Guests G1 and G2 be on same L2 Network N1, or we have to create a seperate L2 Network N2 for G2.

How will L2 connectivity work between G1 and G2 in regards to switch ports? How does Physical Switch know VLAN Tags for N1 to allow Trunk mode? Or they will be internal to Hosts and not span Vswitches?

How will L3 connectivity work in regards to NAT and routing for VMs? Think the Nova Network on Node 1 would be acting as Router/Default Gatway for Node 2, and do NAT, but it brings into dual NIC topology and without switch direct connect.

I was thinking of all Compute Nodes being connected to Switch with one NIC.

How does two Vswitches talk with a Switch in middle

(2) For Floating IP

http://docs.openstack.org/diablo/openstack-compute/admin/content/associating-public-ip.html (http://docs.openstack.org/diablo/open...)

Will this be Ok example to follow?

I was not sure if G1 and G2 could share a L3 Subnet on different nodes.

Here a topology diagram becomes very important as there are many ways to connect L2/L3.

2012-03-08 18:06:43 -0600 asked a question Quantum with vSwitch on 2 Compute Nodes

Assume one node to have all Openstack Controllers.

And second node to be running Compute Node.

What flags I need for second node installation ? I will run devstack stack.sh.

ENABLED_SERVICES="g-api,g-reg,key,n-api,n-cpu,n-net,n-sch,n-vnc,horizon,mysql,rabbit,openstackx,q-svc,quantum,q-agt" Q_PLUGIN=openvswitch

How does Floating IP work in this config of Quantum and Vswitch?

How do one VM communicate from one compute Node to another compute Node - and to Internet?