https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NEUTRON-51 neutron <p><span class="error">&#91;11:00:45&#93;</span> &lt;flaviof&gt; regXboi: <a href="https://review.openstack.org/#/c/177257/" class="external-link" target="_blank" rel="nofollow noopener">https://review.openstack.org/#/c/177257/</a> is merged. I expect issues unless 'vlan_transparent', 'mtu' is handled.</p> <p><span class="error">&#91;11:01:14&#93;</span> &lt;regXboi&gt; flaviof: feel free to add the attributes to the POTS</p> <p>=====</p> <p>Send mtu and vlan_transparent for network operations</p> <p>We were previously removing these. But in the spirit of transparently<br/> passing through all attributes and API calls from Neutron to ODL,<br/> stop pruning these.</p> <p>Operating System: All<br/> Platform: All</p> NEUTRON-51

vlan_transparent and mtu attributes in network_attributes

Bug Resolved Cannot Reproduce Vishal Thapar Flavio Fernandes Fri, 19 Jun 2015 15:07:59 +0000 Mon, 30 Oct 2017 19:52:45 +0000 Mon, 25 Jan 2016 15:41:43 +0000 Multiple northbound-api 0 4 <p>likely breaking stable/lithium</p> <p>I've loaded the latest lithium with openstack build that contains <br/> <a href="https://review.openstack.org/#/c/177257/" class="external-link" target="_blank" rel="nofollow noopener">https://review.openstack.org/#/c/177257/</a> changes.</p> <p>Even though the new fields are present in the rpc from ml2, neutron-northbound<br/> is happy to ignore them, so there is no breakage. With that, I'd lower the<br/> importance of this bug to minor. Sorry for the knee jerk reaction when I<br/> created this bug.</p> <p>tcpdump capture that shows the neutron network with the two new<br/> fields. As you can see odl's neutron northobund has no issues with<br/> them being there.</p> <p>sudo tcpdump -vv -w openstackTalk.cap -i eth1 -s 0 tcp port 8080</p> <p>Attachment openstackTalk.cap has been added with description: tcpdump capture of neutron rpc messages</p> <p>openstack commands used to generate the attachment:</p> <p><a href="https://gist.github.com/41f42281671490ae6bf6" class="external-link" target="_blank" rel="nofollow noopener">https://gist.github.com/41f42281671490ae6bf6</a></p> <p>source openrc admin admin</p> <p>keystone tenant-create --name=tenant1 --enabled=true 2&gt; /dev/null<br/> keystone user-create --name=user1 --pass=user1 --email=user1@example.com 2&gt; /dev/null<br/> keystone user-role-add --user=user1 --role=<em>member</em> --tenant=tenant1 2&gt; /dev/null</p> <p>keystone tenant-create --name=tenant2 --enabled=true 2&gt; /dev/null<br/> keystone user-create --name=user2 --pass=user2 --email=user2@example.com 2&gt; /dev/null<br/> keystone user-role-add --user=user2 --role=<em>member</em> --tenant=tenant2 2&gt; /dev/null</p> <p>IMG_ID=$(nova image-list | grep 'cirros-0.3..-x86_64-uec\s' | awk '</p> {print $2}')<br/> TNT1_ID=$(keystone tenant-list 2&gt; /dev/null | grep '\s'tenant1'' | awk '{print $2} <p>')<br/> TNT2_ID=$(keystone tenant-list 2&gt; /dev/null | grep '\s'tenant2'' | awk '</p> {print $2}')<br/> <br/> neutron net-create ext1 --router:external --tenant_id=${TNT1_ID} --provider:network_type flat \<br/> --provider:physical_network physnetext1<br/> neutron subnet-create --tenant_id=${TNT1_ID} \<br/> --allocation-pool start=192.168.111.21,end=192.168.111.40 --gateway=192.168.111.254 \<br/> --disable-dhcp --name subext1 ext1 192.168.111.0/24<br/> <br/> neutron net-create ext2 --router:external --tenant_id=${TNT2_ID} --provider:network_type flat \<br/> --provider:physical_network physnetext2<br/> neutron subnet-create --tenant_id=${TNT2_ID} \<br/> --allocation-pool start=192.168.111.41,end=192.168.111.60 --gateway=192.168.111.254 \<br/> --disable-dhcp --name subext2 ext2 192.168.111.0/24<br/> <br/> # &#8211;<br/> <br/> unset SERVICE_TOKEN SERVICE_ENDPOINT<br/> export OS_AUTH_URL=<a href="http://192.168.50.20:35357/v2.0/" class="external-link" target="_blank" rel="nofollow noopener">http://192.168.50.20:35357/v2.0/</a><br/> export OS_REGION_NAME=RegionOne<br/> <br/> ####=================<br/> <br/> export OS_USERNAME=user1<br/> export OS_TENANT_NAME=tenant1<br/> export OS_PASSWORD=user1<br/> export PS1='<span class="error">&#91;\u@\h \W(keystone_user1)&#93;</span>\$ '<br/> <br/> rm -f id_rsa_demo* ; ssh-keygen -t rsa -b 2048 -N '' -f id_rsa_demo &gt; /dev/null<br/> nova keypair-add --pub-key id_rsa_demo.pub demo_key &gt; /dev/null<br/> <br/> neutron router-create rtr1<br/> neutron router-gateway-set rtr1 ext1<br/> <br/> ## neutron net-create net1 --tenant-id $TNT1_ID --provider:network_type vxlan --provider:segmentation_id 256 &gt; /dev/null<br/> neutron net-create net1<br/> neutron subnet-create net1 10.1.0.0/24 --name subnet1 --dns-nameserver 192.168.111.254<br/> neutron router-interface-add rtr1 subnet1<br/> <br/> neutron net-create net2<br/> neutron subnet-create net2 10.2.0.0/24 --name subnet2 --dns-nameserver 192.168.111.254<br/> neutron router-interface-add rtr1 subnet2<br/> <br/> NET1_ID=$(neutron net-list | grep -w net1 | awk '{print $2} <p>') ; echo "net1 $NET1_ID"<br/> NET2_ID=$(neutron net-list | grep -w net2 | awk '</p> {print $2}') ; echo "net2 $NET2_ID"<br/> <br/> nova boot --poll --flavor m1.nano --image $IMG_ID --key-name demo_key --nic net-id=${NET1_ID} vm1<br/> nova boot --poll --flavor m1.nano --image $IMG_ID --key-name demo_key --nic net-id=${NET1_ID} vm2<br/> nova boot --poll --flavor m1.nano --image $IMG_ID --key-name demo_key --nic net-id=${NET2_ID} vm3<br/> nova boot --poll --flavor m1.nano --image $IMG_ID --key-name demo_key --nic net-id=${NET2_ID} vm4<br/> <br/> nova list<br/> <br/> for VMNAME in vm1 vm2 vm3 vm4 ; do \<br/> # Floating ip create<br/> neutron floatingip-create ext1<br/> FLOAT_IP=$(neutron floatingip-list | grep 192\.168\.111\. | grep -v 10\..\.0\. | head -1 | awk '{print $5}')<br/> echo "Assigning floating ip ${FLOAT_IP} to ${VMNAME}"<br/> nova floating-ip-associate ${VMNAME} ${FLOAT_IP}<br/> done<br/> <br/> ##------<br/> <br/> export OS_USERNAME=user2<br/> export OS_TENANT_NAME=tenant2<br/> export OS_PASSWORD=user2<br/> export PS1='<span class="error">&#91;\u@\h \W(keystone_user2)&#93;</span>\$ '<br/> <br/> rm -f id_rsa_demo* ; ssh-keygen -t rsa -b 2048 -N '' -f id_rsa_demo &gt; /dev/null<br/> nova keypair-add --pub-key id_rsa_demo.pub demo_key &gt; /dev/null<br/> <br/> neutron router-create rtr2<br/> neutron router-gateway-set rtr2 ext2<br/> <br/> neutron net-create net10<br/> neutron subnet-create net10 10.10.0.0/24 --name subnet10 --dns-nameserver 192.168.111.254<br/> neutron router-interface-add rtr2 subnet10<br/> <br/> neutron net-create net20<br/> neutron subnet-create net20 10.20.0.0/24 --name subnet20 --dns-nameserver 192.168.111.254<br/> neutron router-interface-add rtr2 subnet20<br/> <br/> NET10_ID=$(neutron net-list | grep -w net10 | awk '{print $2} <p>') ; echo "net10 $NET10_ID"<br/> NET20_ID=$(neutron net-list | grep -w net20 | awk '</p> {print $2} <p>') ; echo "net20 $NET20_ID"</p> <p>nova boot --poll --flavor m1.nano --image $IMG_ID --key-name demo_key --nic net-id=${NET10_ID} vm5<br/> nova boot --poll --flavor m1.nano --image $IMG_ID --key-name demo_key --nic net-id=${NET10_ID} vm6<br/> nova boot --poll --flavor m1.nano --image $IMG_ID --key-name demo_key --nic net-id=${NET20_ID} vm7<br/> nova boot --poll --flavor m1.nano --image $IMG_ID --key-name demo_key --nic net-id=${NET20_ID} vm8</p> <p>for VMNAME in vm5 vm6 vm7 vm8 ; do \</p> <ol> <li>Floating ip create<br/> neutron floatingip-create ext2<br/> FLOAT_IP=$(neutron floatingip-list | grep 192\.168\.111\. | grep -v 10\...\.0\. | head -1 | awk ' {print $5} <p>')<br/> echo "Assigning floating ip ${FLOAT_IP} to ${VMNAME}"<br/> nova floating-ip-associate ${VMNAME} ${FLOAT_IP}<br/> done</p></li> </ol> <p>On Neutron side, those two extended attributes are implemented such that they can co-exist with the existing plugin/mechanism driver as long as they are ignored.<br/> So for short term, it should work given ODL ignores them.</p> <p>So the next step to address this, support by data store and have neutron provider support it.</p> <p>partially addressed by <a href="https://git.opendaylight.org/gerrit/24257" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/24257</a></p> <p>we will need to add a vlan-transparent augmentation to the yang model and update tests</p> <p>I'd like to take this up for Be and potentially backport to Li.</p> Development External issue ID 3824 External issue URL Issue Type ODL SR Target Milestone Priority Rank 0|i02uen: