<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi,<div><br><div>I am khushbu an GSOC applicant. <div>So I want help knowing more about this bug. <div><a href="https://blueprints.launchpad.net/zaqar/+spec/prefix-queue-pagination" target="_blank">https://blueprints.launchpad.net/zaqar/+spec/prefix-queue-pagination</a></div><div>or some documentation like what exactly they mean or how to approach and the link to repo we need to make changes as I am new to this project.<br><br>Regards,<br>Khushbu Parakh<div>Arya College Of Engineering and IT</div><div>Linkedin: http://linkedin.com/in/khushbuparakh</div><div><div>about.me/khushbu.parakh</div><div><br></div><div> <span class="ecxApple-tab-span" style="white-space:pre;"> </span></div><div> </div></div><div><br></div><div><br></div><br><br><div>> From: openstack-request@lists.openstack.org<br>> Subject: Openstack Digest, Vol 32, Issue 18<br>> To: openstack@lists.openstack.org<br>> Date: Wed, 17 Feb 2016 12:00:04 +0000<br>> <br>> Send Openstack mailing list submissions to<br>> openstack@lists.openstack.org<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack<br>> or, via email, send a message with subject or body 'help' to<br>> openstack-request@lists.openstack.org<br>> <br>> You can reach the person managing the list at<br>> openstack-owner@lists.openstack.org<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of Openstack digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. Re: [OpenStack] [CINDER] how to get updated pool info when<br>> multi users create volumes on pool configured? (yang, xing)<br>> 2. Guest networking and magic IP (Andre Goree)<br>> 3. Nexus 9K - Nexus: Segment is an invalid type or not supported<br>> by this driver?? (Michael Gale)<br>> 4. Re: Nexus 9K - Nexus: Segment is an invalid type or not<br>> supported by this driver?? (Anthony T CHOW)<br>> 5. Re: Nexus 9K - Nexus: Segment is an invalid type or not<br>> supported by this driver?? (Michael Gale)<br>> 6. Re: Virtual Firewall Appliance (Martinx - ?????)<br>> 7. Re: Nexus 9K - Nexus: Segment is an invalid type or not<br>> supported by this driver?? (Anthony T CHOW)<br>> 8. add an extra external network (Priyanka)<br>> 9. Re: add an extra external network (Erik McCormick)<br>> 10. Re: Guest networking and magic IP (Tomas Vondra)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Tue, 16 Feb 2016 18:47:34 +0000<br>> From: "yang, xing" <xing.yang@emc.com><br>> To: Dilip Sunkum Manjunath <Dilip.SunkumManjunath@toshiba-tsip.com><br>> Cc: "itzdilip@gmail.com" <itzdilip@gmail.com>,<br>> "openstack@lists.openstack.org" <openstack@lists.openstack.org><br>> Subject: Re: [Openstack] [OpenStack] [CINDER] how to get updated pool<br>> info when multi users create volumes on pool configured?<br>> Message-ID: <875B4123-013F-4924-B9BD-CAF125925F09@emc.com><br>> Content-Type: text/plain; charset="us-ascii"<br>> <br>> Sounds good. Let me know how it goes. <br>> <br>> Thanks Dilip,<br>> Xing<br>> <br>> <br>> > On Feb 16, 2016, at 1:21 AM, Dilip Sunkum Manjunath <Dilip.SunkumManjunath@toshiba-tsip.com> wrote:<br>> > <br>> > Hi Xing,<br>> > <br>> > <br>> > Thanks for replay,<br>> > <br>> > <br>> > <br>> > I tried because the use case was to support both in single pool.<br>> > <br>> > I was thinking in same as to read the volume type in scheduler, however since it is a new requirement that affects everyone it might not be good to change now.<br>> > <br>> > I shall try with the other approach pools for thin /thick and update you.<br>> > <br>> > <br>> > Thanks<br>> > Dilip<br>> > <br>> > <br>> > <br>> > <br>> > <br>> > <br>> > <br>> > <br>> > -----Original Message-----<br>> > From: yang, xing [mailto:xing.yang@emc.com] <br>> > Sent: Friday, February 12, 2016 12:42 PM<br>> > To: Dilip Sunkum Manjunath<br>> > Cc: openstack@lists.openstack.org; itzdilip@gmail.com<br>> > Subject: Re: [OpenStack] [CINDER] how to get updated pool info when multi users create volumes on pool configured?<br>> > <br>> > Hi Dilip,<br>> > <br>> > I see. If thin_provisioning is true and max_over_subscription_ratio is valid, the scheduler will treat it as thin provisioning. We do not prevent driver from reporting both thin and thick support to be true. However, I think we need to make a change.<br>> > <br>> > I suggest that you have one pool for thin and the other one for thick but don't report both thin and thick support from the same pool. That will avoid this problem.<br>> > <br>> > Another possible alternative is to require thin/thick provisioning to be in extra specs and use that info in the scheduler, however that will be a new requirement that affects everyone. So I am not in favor of that approach.<br>> > <br>> > Can you use one pool for thin and another for thick in your testing?<br>> > <br>> > Thanks,<br>> > Xing<br>> > <br>> > <br>> > <br>> >> On Feb 12, 2016, at 12:05 AM, Dilip Sunkum Manjunath <Dilip.SunkumManjunath@toshiba-tsip.com> wrote:<br>> >> <br>> >> max_over_subscription_ratio<br>> > The information contained in this e-mail message and in any<br>> > attachments/annexure/appendices is confidential to the <br>> > recipient and may contain privileged information. <br>> > If you are not the intended recipient, please notify the<br>> > sender and delete the message along with any <br>> > attachments/annexure/appendices. You should not disclose,<br>> > copy or otherwise use the information contained in the<br>> > message or any annexure. Any views expressed in this e-mail <br>> > are those of the individual sender except where the sender <br>> > specifically states them to be the views of <br>> > Toshiba Software India Pvt. Ltd. (TSIP),Bangalore.<br>> > <br>> > Although this transmission and any attachments are believed to be<br>> > free of any virus or other defect that might affect any computer <br>> > system into which it is received and opened, it is the responsibility<br>> > of the recipient to ensure that it is virus free and no responsibility <br>> > is accepted by Toshiba Embedded Software India Pvt. Ltd, for any loss or<br>> > damage arising in any way from its use.<br>> > <br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Tue, 16 Feb 2016 15:37:06 -0500<br>> From: Andre Goree <andre@drenet.net><br>> To: openstack@lists.openstack.org<br>> Subject: [Openstack] Guest networking and magic IP<br>> Message-ID: <2ae919336ea558e2c957b3c6121f7d07@drenet.net><br>> Content-Type: text/plain; charset=US-ASCII; format=flowed<br>> <br>> I have some questions regarding the way that networking is handled via <br>> qemu/kvm+libvirt, namely I'm trying to replicate OpenStack's use of the <br>> magic IP on newly spun-up instances. My apologies in advance if this is <br>> not the proper mailing list for such a question. I've already been to <br>> the libvirt mailing list, but to no avail.<br>> <br>> I am trying to determine how exactly I can manipulate traffic from a <br>> _guest's_ NIC using iptables on the _host_. On the host, there is a <br>> bridged virtual NIC that corresponds to the guest's NIC. That interface <br>> does not have an IP setup on it on the host, however within the vm <br>> itself the IP is configured and everything works as expected. I was <br>> told on the libvirt list that nwfilter handles things like this, but <br>> after further discussion was able to determine that nwfilter does NOT <br>> handle a situation in which one would redirect traffic destined for one <br>> IP to another IP -- a situation that iptables would normally handle.<br>> <br>> I'm wondering, in that case, how OpenStack is (seemingly) "magically" <br>> making this happen? Because libvirt (via nwfilter) handles outbound <br>> traffic produced by a guest system (and thus, that traffic does not <br>> traverse iptables) that there would be no way to facilitate this...but <br>> as we all know, OpenStack does it :)<br>> <br>> Any insight or pointing in the right direction would be so helpful, <br>> thanks in advance!<br>> <br>> <br>> -- <br>> Andre Goree<br>> -=-=-=-=-=-<br>> Email - andre at drenet.net<br>> Website - http://www.drenet.net<br>> PGP key - http://www.drenet.net/pubkey.txt<br>> -=-=-=-=-=-<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Tue, 16 Feb 2016 13:41:44 -0700<br>> From: Michael Gale <gale.michael@gmail.com><br>> To: "openstack@lists.openstack.org" <openstack@lists.openstack.org><br>> Subject: [Openstack] Nexus 9K - Nexus: Segment is an invalid type or<br>> not supported by this driver??<br>> Message-ID:<br>> <CA+YXe5kNKqJjjtbX69x4qoPFpzVQ2DYj6ZBuDnsh0p2mVJbcvw@mail.gmail.com><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> Hello,<br>> <br>> I am having issues getting my Liberty environment working with VXLAN<br>> and N9K.<br>> <br>> Currently I am getting the following errors in the logs on startup:<br>> --snip--<br>> 2016-02-16 13:18:42.097 595 WARNING<br>> networking_cisco.plugins.ml2.drivers.cisco.nexus.mech_cisco_nexus<br>> [req-825a9891-0467-4958-86ca-c98486a7bf52 - - - - -] Nexus: Segment is an<br>> invalid type or not supported by this driv<br>> er. Network type = vxlan Physical network = None. Event not processed.<br>> --snip--<br>> <br>> When trying to launch an instance:<br>> --snip--<br>> ERROR neutron.plugins.ml2.managers<br>> [req-d15ab080-7aa4-46e5-a5c3-b62a13c5646d d2b4e18cf27d41418845439f5d788523<br>> eaa185709c79477fa1e3edfffa4e4c7f - - -] Failed to bind port<br>> 9b32f0e7-6b5b-4ced-84b7-262ea12e090c on host compute1<br>> <br>> Nexus: Segment is None, Event not processed<br>> --snip--<br>> <br>> I am assuming I am missing something in the configuration file however I<br>> can't figure it out. Any help is greatly appreciated.<br>> <br>> Thanks<br>> Michael<br>> <br>> Here is my ml2_conf.ini<br>> <br>> --snip--<br>> # ML2 general<br>> [ml2]<br>> type_drivers = flat,vlan,nexus_vxlan,local<br>> tenant_network_types = nexus_vxlan<br>> mechanism_drivers = linuxbridge,l2population,cisco_nexus<br>> extension_drivers = port_security<br>> path_mtu = 0<br>> segment_mtu = 0<br>> <br>> <br>> <br>> # ML2 VLAN networks<br>> [ml2_type_vlan]<br>> network_vlan_ranges = physeth1:100:163<br>> <br>> [ml2_mech_cisco_nexus:10.92.192.45]<br>> infra1_neutron_agents_container-ee5293cb=1/17<br>> infra1_neutron_server_container-ed083568=1/17<br>> infra2_neutron_agents_container-65f32f70=1/18<br>> infra2_neutron_server_container-1e0b996b=1/18<br>> infra3_neutron_agents_container-2faafbe7=1/19<br>> infra3_neutron_server_container-9eabc975=1/19<br>> compute1=1/21<br>> compute2=1/22<br>> username=openstack<br>> password=foo123<br>> ssh_port=22<br>> physnet=physeth1<br>> <br>> [ml2_mech_cisco_nexus:10.92.192.46]<br>> infra1_neutron_agents_container-ee5293cb=1/17<br>> infra1_neutron_server_container-ed083568=1/17<br>> infra2_neutron_agents_container-65f32f70=1/18<br>> infra2_neutron_server_container-1e0b996b=1/18<br>> infra3_neutron_agents_container-2faafbe7=1/19<br>> infra3_neutron_server_container-9eabc975=1/19<br>> compute1=1/21<br>> compute2=1/22<br>> username=openstack<br>> password=foo123<br>> ssh_port=22<br>> physnet=physeth1<br>> <br>> # ML2 VXLAN networks<br>> [ml2_type_vxlan]<br>> vxlan_group =<br>> vni_ranges = 1:1000<br>> <br>> [ml2_type_nexus_vxlan]<br>> # Comma-separated list of <vni_min>:<vni_max> tuples enumerating<br>> # ranges of VXLAN VNI IDs that are available for tenant network allocation.<br>> vni_ranges=50000:55000<br>> <br>> # Multicast groups for the VXLAN interface. When configured, will<br>> # enable sending all broadcast traffic to this multicast group. Comma<br>> separated<br>> # list of min:max ranges of multicast IP's<br>> # NOTE: must be a valid multicast IP, invalid IP's will be discarded<br>> mcast_ranges=225.1.1.1:225.1.1.2<br>> <br>> # Security groups<br>> [securitygroup]<br>> enable_security_group = True<br>> enable_ipset = True<br>> <br>> --snip--<br>> <br>> <br>> and my linuxbridge_agent.ini:<br>> --snip--<br>> # Linux bridge agent physical interface mappings<br>> [linux_bridge]<br>> <br>> physical_interface_mappings = physeth1:eth11<br>> <br>> # Linux bridge agent VXLAN networks<br>> [vxlan]<br>> <br>> enable_vxlan = True<br>> vxlan_group =<br>> # VXLAN local tunnel endpoint<br>> local_ip = 10.96.2.141<br>> l2_population = True<br>> <br>> <br>> # Agent<br>> [agent]<br>> prevent_arp_spoofing = False<br>> <br>> # Security groups<br>> [securitygroup]<br>> firewall_driver =<br>> neutron.agent.linux.iptables_firewall.IptablesFirewallDriver<br>> enable_security_group = True<br>> <br>> --snip--<br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160216/8ddf820d/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 4<br>> Date: Tue, 16 Feb 2016 20:53:44 +0000<br>> From: Anthony T CHOW <anthony.chow@al-enterprise.com><br>> To: Michael Gale <gale.michael@gmail.com>,<br>> "openstack@lists.openstack.org" <openstack@lists.openstack.org><br>> Subject: Re: [Openstack] Nexus 9K - Nexus: Segment is an invalid type<br>> or not supported by this driver??<br>> Message-ID:<br>> <HE1PR08MB0427E643C54E32D3B2557626D6AD0@HE1PR08MB0427.eurprd08.prod.outlook.com><br>> <br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> Michael,<br>> <br>> Are you using Linux Bridge or OvS?<br>> <br>> There is a bug report: Linux bridge does not work with cisco_nexus ml2 plugins<br>> <br>> https://bugs.launchpad.net/networking-cisco/+bug/1421024<br>> <br>> anthony.<br>> <br>> From: Michael Gale [mailto:gale.michael@gmail.com]<br>> Sent: Tuesday, February 16, 2016 12:42 PM<br>> To: openstack@lists.openstack.org<br>> Subject: [Openstack] Nexus 9K - Nexus: Segment is an invalid type or not supported by this driver??<br>> <br>> Hello,<br>> <br>> I am having issues getting my Liberty environment working with VXLAN and N9K.<br>> <br>> Currently I am getting the following errors in the logs on startup:<br>> --snip--<br>> 2016-02-16 13:18:42.097 595 WARNING networking_cisco.plugins.ml2.drivers.cisco.nexus.mech_cisco_nexus [req-825a9891-0467-4958-86ca-c98486a7bf52 - - - - -] Nexus: Segment is an invalid type or not supported by this driv<br>> er. Network type = vxlan Physical network = None. Event not processed.<br>> --snip--<br>> <br>> When trying to launch an instance:<br>> --snip--<br>> ERROR neutron.plugins.ml2.managers [req-d15ab080-7aa4-46e5-a5c3-b62a13c5646d d2b4e18cf27d41418845439f5d788523 eaa185709c79477fa1e3edfffa4e4c7f - - -] Failed to bind port 9b32f0e7-6b5b-4ced-84b7-262ea12e090c on host compute1<br>> <br>> Nexus: Segment is None, Event not processed<br>> --snip--<br>> <br>> I am assuming I am missing something in the configuration file however I can't figure it out. Any help is greatly appreciated.<br>> <br>> Thanks<br>> Michael<br>> <br>> Here is my ml2_conf.ini<br>> <br>> --snip--<br>> # ML2 general<br>> [ml2]<br>> type_drivers = flat,vlan,nexus_vxlan,local<br>> tenant_network_types = nexus_vxlan<br>> mechanism_drivers = linuxbridge,l2population,cisco_nexus<br>> extension_drivers = port_security<br>> path_mtu = 0<br>> segment_mtu = 0<br>> <br>> <br>> <br>> # ML2 VLAN networks<br>> [ml2_type_vlan]<br>> network_vlan_ranges = physeth1:100:163<br>> <br>> [ml2_mech_cisco_nexus:10.92.192.45]<br>> infra1_neutron_agents_container-ee5293cb=1/17<br>> infra1_neutron_server_container-ed083568=1/17<br>> infra2_neutron_agents_container-65f32f70=1/18<br>> infra2_neutron_server_container-1e0b996b=1/18<br>> infra3_neutron_agents_container-2faafbe7=1/19<br>> infra3_neutron_server_container-9eabc975=1/19<br>> compute1=1/21<br>> compute2=1/22<br>> username=openstack<br>> password=foo123<br>> ssh_port=22<br>> physnet=physeth1<br>> <br>> [ml2_mech_cisco_nexus:10.92.192.46]<br>> infra1_neutron_agents_container-ee5293cb=1/17<br>> infra1_neutron_server_container-ed083568=1/17<br>> infra2_neutron_agents_container-65f32f70=1/18<br>> infra2_neutron_server_container-1e0b996b=1/18<br>> infra3_neutron_agents_container-2faafbe7=1/19<br>> infra3_neutron_server_container-9eabc975=1/19<br>> compute1=1/21<br>> compute2=1/22<br>> username=openstack<br>> password=foo123<br>> ssh_port=22<br>> physnet=physeth1<br>> <br>> # ML2 VXLAN networks<br>> [ml2_type_vxlan]<br>> vxlan_group =<br>> vni_ranges = 1:1000<br>> <br>> [ml2_type_nexus_vxlan]<br>> # Comma-separated list of <vni_min>:<vni_max> tuples enumerating<br>> # ranges of VXLAN VNI IDs that are available for tenant network allocation.<br>> vni_ranges=50000:55000<br>> <br>> # Multicast groups for the VXLAN interface. When configured, will<br>> # enable sending all broadcast traffic to this multicast group. Comma separated<br>> # list of min:max ranges of multicast IP's<br>> # NOTE: must be a valid multicast IP, invalid IP's will be discarded<br>> mcast_ranges=225.1.1.1:225.1.1.2<br>> <br>> # Security groups<br>> [securitygroup]<br>> enable_security_group = True<br>> enable_ipset = True<br>> <br>> --snip--<br>> <br>> <br>> and my linuxbridge_agent.ini:<br>> --snip--<br>> # Linux bridge agent physical interface mappings<br>> [linux_bridge]<br>> <br>> physical_interface_mappings = physeth1:eth11<br>> <br>> # Linux bridge agent VXLAN networks<br>> [vxlan]<br>> <br>> enable_vxlan = True<br>> vxlan_group =<br>> # VXLAN local tunnel endpoint<br>> local_ip = 10.96.2.141<br>> l2_population = True<br>> <br>> <br>> # Agent<br>> [agent]<br>> prevent_arp_spoofing = False<br>> <br>> # Security groups<br>> [securitygroup]<br>> firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver<br>> enable_security_group = True<br>> <br>> --snip--<br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160216/98b7c0f7/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 5<br>> Date: Tue, 16 Feb 2016 13:57:26 -0700<br>> From: Michael Gale <gale.michael@gmail.com><br>> To: Anthony T CHOW <anthony.chow@al-enterprise.com><br>> Cc: "openstack@lists.openstack.org" <openstack@lists.openstack.org><br>> Subject: Re: [Openstack] Nexus 9K - Nexus: Segment is an invalid type<br>> or not supported by this driver??<br>> Message-ID:<br>> <CA+YXe5mkM+oB-yYGHv-0A4ahqj+MOkQ-ap423tWYvcR2nhY+9w@mail.gmail.com><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> Hello,<br>> <br>> I am using Linux Bridge, I did see that bug report however it is marked<br>> as a duplicate of: https://bugs.launchpad.net/neutron/+bug/1433461 which<br>> indicates the issue was fixed in kilo. If I understand the report correctly.<br>> <br>> Michael<br>> <br>> On Tue, Feb 16, 2016 at 1:53 PM, Anthony T CHOW <<br>> anthony.chow@al-enterprise.com> wrote:<br>> <br>> > Michael,<br>> ><br>> ><br>> ><br>> > Are you using Linux Bridge or OvS?<br>> ><br>> ><br>> ><br>> > There is a bug report: *Linux bridge does not work with cisco_nexus ml2<br>> > plugins*<br>> ><br>> ><br>> ><br>> > https://bugs.launchpad.net/networking-cisco/+bug/1421024<br>> ><br>> ><br>> ><br>> > anthony.<br>> ><br>> ><br>> ><br>> > *From:* Michael Gale [mailto:gale.michael@gmail.com]<br>> > *Sent:* Tuesday, February 16, 2016 12:42 PM<br>> > *To:* openstack@lists.openstack.org<br>> > *Subject:* [Openstack] Nexus 9K - Nexus: Segment is an invalid type or<br>> > not supported by this driver??<br>> ><br>> ><br>> ><br>> > Hello,<br>> ><br>> ><br>> ><br>> > I am having issues getting my Liberty environment working with VXLAN<br>> > and N9K.<br>> ><br>> ><br>> ><br>> > Currently I am getting the following errors in the logs on startup:<br>> ><br>> > --snip--<br>> ><br>> > 2016-02-16 13:18:42.097 595 WARNING<br>> > networking_cisco.plugins.ml2.drivers.cisco.nexus.mech_cisco_nexus<br>> > [req-825a9891-0467-4958-86ca-c98486a7bf52 - - - - -] Nexus: Segment is an<br>> > invalid type or not supported by this driv<br>> ><br>> > er. Network type = vxlan Physical network = None. Event not processed.<br>> ><br>> > --snip--<br>> ><br>> ><br>> ><br>> > When trying to launch an instance:<br>> ><br>> > --snip--<br>> ><br>> > ERROR neutron.plugins.ml2.managers<br>> > [req-d15ab080-7aa4-46e5-a5c3-b62a13c5646d d2b4e18cf27d41418845439f5d788523<br>> > eaa185709c79477fa1e3edfffa4e4c7f - - -] Failed to bind port<br>> > 9b32f0e7-6b5b-4ced-84b7-262ea12e090c on host compute1<br>> ><br>> ><br>> ><br>> > Nexus: Segment is None, Event not processed<br>> ><br>> > --snip--<br>> ><br>> ><br>> ><br>> > I am assuming I am missing something in the configuration file however I<br>> > can't figure it out. Any help is greatly appreciated.<br>> ><br>> ><br>> ><br>> > Thanks<br>> ><br>> > Michael<br>> ><br>> ><br>> ><br>> > Here is my ml2_conf.ini<br>> ><br>> ><br>> ><br>> > --snip--<br>> ><br>> > # ML2 general<br>> ><br>> > [ml2]<br>> ><br>> > type_drivers = flat,vlan,nexus_vxlan,local<br>> ><br>> > tenant_network_types = nexus_vxlan<br>> ><br>> > mechanism_drivers = linuxbridge,l2population,cisco_nexus<br>> ><br>> > extension_drivers = port_security<br>> ><br>> > path_mtu = 0<br>> ><br>> > segment_mtu = 0<br>> ><br>> ><br>> ><br>> ><br>> ><br>> ><br>> ><br>> > # ML2 VLAN networks<br>> ><br>> > [ml2_type_vlan]<br>> ><br>> > network_vlan_ranges = physeth1:100:163<br>> ><br>> ><br>> ><br>> > [ml2_mech_cisco_nexus:10.92.192.45]<br>> ><br>> > infra1_neutron_agents_container-ee5293cb=1/17<br>> ><br>> > infra1_neutron_server_container-ed083568=1/17<br>> ><br>> > infra2_neutron_agents_container-65f32f70=1/18<br>> ><br>> > infra2_neutron_server_container-1e0b996b=1/18<br>> ><br>> > infra3_neutron_agents_container-2faafbe7=1/19<br>> ><br>> > infra3_neutron_server_container-9eabc975=1/19<br>> ><br>> > compute1=1/21<br>> ><br>> > compute2=1/22<br>> ><br>> > username=openstack<br>> ><br>> > password=foo123<br>> ><br>> > ssh_port=22<br>> ><br>> > physnet=physeth1<br>> ><br>> ><br>> ><br>> > [ml2_mech_cisco_nexus:10.92.192.46]<br>> ><br>> > infra1_neutron_agents_container-ee5293cb=1/17<br>> ><br>> > infra1_neutron_server_container-ed083568=1/17<br>> ><br>> > infra2_neutron_agents_container-65f32f70=1/18<br>> ><br>> > infra2_neutron_server_container-1e0b996b=1/18<br>> ><br>> > infra3_neutron_agents_container-2faafbe7=1/19<br>> ><br>> > infra3_neutron_server_container-9eabc975=1/19<br>> ><br>> > compute1=1/21<br>> ><br>> > compute2=1/22<br>> ><br>> > username=openstack<br>> ><br>> > password=foo123<br>> ><br>> > ssh_port=22<br>> ><br>> > physnet=physeth1<br>> ><br>> ><br>> ><br>> > # ML2 VXLAN networks<br>> ><br>> > [ml2_type_vxlan]<br>> ><br>> > vxlan_group =<br>> ><br>> > vni_ranges = 1:1000<br>> ><br>> ><br>> ><br>> > [ml2_type_nexus_vxlan]<br>> ><br>> > # Comma-separated list of <vni_min>:<vni_max> tuples enumerating<br>> ><br>> > # ranges of VXLAN VNI IDs that are available for tenant network allocation.<br>> ><br>> > vni_ranges=50000:55000<br>> ><br>> ><br>> ><br>> > # Multicast groups for the VXLAN interface. When configured, will<br>> ><br>> > # enable sending all broadcast traffic to this multicast group. Comma<br>> > separated<br>> ><br>> > # list of min:max ranges of multicast IP's<br>> ><br>> > # NOTE: must be a valid multicast IP, invalid IP's will be discarded<br>> ><br>> > mcast_ranges=225.1.1.1:225.1.1.2<br>> ><br>> ><br>> ><br>> > # Security groups<br>> ><br>> > [securitygroup]<br>> ><br>> > enable_security_group = True<br>> ><br>> > enable_ipset = True<br>> ><br>> ><br>> ><br>> > --snip--<br>> ><br>> ><br>> ><br>> ><br>> ><br>> > and my linuxbridge_agent.ini:<br>> ><br>> > --snip--<br>> ><br>> > # Linux bridge agent physical interface mappings<br>> ><br>> > [linux_bridge]<br>> ><br>> ><br>> ><br>> > physical_interface_mappings = physeth1:eth11<br>> ><br>> ><br>> ><br>> > # Linux bridge agent VXLAN networks<br>> ><br>> > [vxlan]<br>> ><br>> ><br>> ><br>> > enable_vxlan = True<br>> ><br>> > vxlan_group =<br>> ><br>> > # VXLAN local tunnel endpoint<br>> ><br>> > local_ip = 10.96.2.141<br>> ><br>> > l2_population = True<br>> ><br>> ><br>> ><br>> ><br>> ><br>> > # Agent<br>> ><br>> > [agent]<br>> ><br>> > prevent_arp_spoofing = False<br>> ><br>> ><br>> ><br>> > # Security groups<br>> ><br>> > [securitygroup]<br>> ><br>> > firewall_driver =<br>> > neutron.agent.linux.iptables_firewall.IptablesFirewallDriver<br>> ><br>> > enable_security_group = True<br>> ><br>> ><br>> ><br>> > --snip--<br>> ><br>> ><br>> ><br>> <br>> <br>> <br>> -- <br>> <br>> ?The Man who says he can, and the man who says he can not.. Are both<br>> correct?<br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160216/ed5bd571/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 6<br>> Date: Tue, 16 Feb 2016 20:41:36 -0200<br>> From: Martinx - ????? <thiagocmartinsc@gmail.com><br>> To: Georgios Dimitrakakis <giorgis@acmac.uoc.gr><br>> Cc: Openstack <openstack@lists.openstack.org><br>> Subject: Re: [Openstack] Virtual Firewall Appliance<br>> Message-ID:<br>> <CAJSM8J2tizFp5wgk8CffDvXm05pZpEqLktLC0iw_LvGcjipcgg@mail.gmail.com><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> I don't think that you'll be able to do that in IceHouse, neither on Juno.<br>> <br>> Only Kilo and Liberty have a native function to disable the port_security<br>> per port. Without it, OpenStack Neutron (and also Nova Network, I guess)<br>> will not allow the firewall Instance to work correctly. It will not see any<br>> packets that are not destined to it and also, it will not be able to<br>> forward packets, because the Neutron (and Nova Network), will drop the<br>> packets soon as it leaves the firewall Instance.<br>> <br>> I'm not aware of a solution nice for IceHouse...<br>> <br>> On 16 February 2016 at 06:26, Georgios Dimitrakakis <giorgis@acmac.uoc.gr><br>> wrote:<br>> <br>> > Mark and Martinx thank you both for your suggestions.<br>> ><br>> > I had tried to build PFSense in the past but without success.<br>> ><br>> > Indeed my goal is to run the virtual firewall as an instance since I am on<br>> > an older OpenStack version (IceHouse) with nova-networking and therefore I<br>> > cannot have control over the outgoing connections.<br>> ><br>> > Regards,<br>> ><br>> > G.<br>> ><br>> ><br>> > For running it as an Instance?<br>> >><br>> >> You can try:<br>> >><br>> >> - PFSense;<br>> >><br>> >> - Zentyal;<br>> >><br>> >> However, youll need to make use of the Neutron feature called<br>> >> "port_security_enabled = false" for the vNIC attached to the<br>> >> "internal" subnet (behind the firewall).<br>> >><br>> >> Just a curiosity, why dont you use the Neutron native firewall that<br>> >> resides on each L3 Router?<br>> >><br>> >> On 15 February 2016 at 15:56, Georgios Dimitrakakis wrote:<br>> >><br>> >> Hi!<br>> >>><br>> >>> Can anyone suggest me of a virtual firewall appliance which is<br>> >>> compatible with OpenStack?<br>> >>><br>> >>> Best regards,<br>> >>><br>> >>> G.<br>> >>><br>> >>> _______________________________________________<br>> >>> Mailing list:<br>> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [1]<br>> >>> Post to : openstack@lists.openstack.org [2]<br>> >>> Unsubscribe :<br>> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [3]<br>> >>><br>> >><br>> >><br>> >><br>> >> Links:<br>> >> ------<br>> >> [1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack<br>> >> [2] mailto:openstack@lists.openstack.org<br>> >> [3] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack<br>> >> [4] mailto:giorgis@acmac.uoc.gr<br>> >><br>> ><br>> > _______________________________________________<br>> > Mailing list:<br>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack<br>> > Post to : openstack@lists.openstack.org<br>> > Unsubscribe :<br>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack<br>> ><br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160216/584d71dd/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 7<br>> Date: Tue, 16 Feb 2016 22:43:06 +0000<br>> From: Anthony T CHOW <anthony.chow@al-enterprise.com><br>> To: Michael Gale <gale.michael@gmail.com><br>> Cc: "openstack@lists.openstack.org" <openstack@lists.openstack.org><br>> Subject: Re: [Openstack] Nexus 9K - Nexus: Segment is an invalid type<br>> or not supported by this driver??<br>> Message-ID:<br>> <HE1PR08MB04270ADF6A8AF33DB00201FED6AD0@HE1PR08MB0427.eurprd08.prod.outlook.com><br>> <br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> Michael,<br>> <br>> I am not a neutron expect but this bug 1433461 does not seem to be a duplicate of 1421024.<br>> <br>> Bug 1433461 is for port binding while 1421024 is for Nexus switch not configured at all.<br>> <br>> This is the fix for 1433461:<br>> <br>> @@ -1337,7 +1337,7 @@ class Ml2Plugin(db_base_plugin_v2.NeutronDbPluginV2,<br>> <br>> 1337<https://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/plugin.py?id=2b1c4f121e3e8ba1c5eb2ba6661bf6326e1507c5#n1337><br>> <br>> updated_port = self._make_port_dict(port)<br>> <br>> 1337<https://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/plugin.py?id=355ab2f31cf81575c6e1c0899526177711425428#n1337><br>> <br>> updated_port = self._make_port_dict(port)<br>> <br>> 1338<https://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/plugin.py?id=2b1c4f121e3e8ba1c5eb2ba6661bf6326e1507c5#n1338><br>> <br>> network = self.get_network(context,<br>> <br>> 1338<https://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/plugin.py?id=355ab2f31cf81575c6e1c0899526177711425428#n1338><br>> <br>> network = self.get_network(context,<br>> <br>> 1339<https://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/plugin.py?id=2b1c4f121e3e8ba1c5eb2ba6661bf6326e1507c5#n1339><br>> <br>> original_port['network_id'])<br>> <br>> 1339<https://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/plugin.py?id=355ab2f31cf81575c6e1c0899526177711425428#n1339><br>> <br>> original_port['network_id'])<br>> <br>> 1340<https://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/plugin.py?id=2b1c4f121e3e8ba1c5eb2ba6661bf6326e1507c5#n1340><br>> <br>> levels = db.get_binding_levels(session, port_id,<br>> <br>> 1340<https://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/plugin.py?id=355ab2f31cf81575c6e1c0899526177711425428#n1340><br>> <br>> levels = db.get_binding_levels(session, port.id,<br>> <br>> 1341<https://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/plugin.py?id=2b1c4f121e3e8ba1c5eb2ba6661bf6326e1507c5#n1341><br>> <br>> port.port_binding.host)<br>> <br>> 1341<https://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/plugin.py?id=355ab2f31cf81575c6e1c0899526177711425428#n1341><br>> <br>> port.port_binding.host)<br>> <br>> 1342<https://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/plugin.py?id=2b1c4f121e3e8ba1c5eb2ba6661bf6326e1507c5#n1342><br>> <br>> mech_context = driver_context.PortContext(<br>> <br>> 1342<https://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/plugin.py?id=355ab2f31cf81575c6e1c0899526177711425428#n1342><br>> <br>> mech_context = driver_context.PortContext(<br>> <br>> 1343<https://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/plugin.py?id=2b1c4f121e3e8ba1c5eb2ba6661bf6326e1507c5#n1343><br>> <br>> self, context, updated_port, network, port.port_binding,<br>> <br>> 1343<https://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/plugin.py?id=355ab2f31cf81575c6e1c0899526177711425428#n1343><br>> <br>> self, context, updated_port, network, port.port_binding,<br>> <br>> <br>> It is to correctly passing the port id to db.get_binding_levels and not just the first 11 characters of the port id.<br>> <br>> I am interested to find out too.<br>> <br>> Anthony.<br>> <br>> From: Michael Gale [mailto:gale.michael@gmail.com]<br>> Sent: Tuesday, February 16, 2016 12:57 PM<br>> To: Anthony T CHOW<br>> Cc: openstack@lists.openstack.org<br>> Subject: Re: [Openstack] Nexus 9K - Nexus: Segment is an invalid type or not supported by this driver??<br>> <br>> Hello,<br>> <br>> I am using Linux Bridge, I did see that bug report however it is marked as a duplicate of: https://bugs.launchpad.net/neutron/+bug/1433461 which indicates the issue was fixed in kilo. If I understand the report correctly.<br>> <br>> Michael<br>> <br>> On Tue, Feb 16, 2016 at 1:53 PM, Anthony T CHOW <anthony.chow@al-enterprise.com<mailto:anthony.chow@al-enterprise.com>> wrote:<br>> Michael,<br>> <br>> Are you using Linux Bridge or OvS?<br>> <br>> There is a bug report: Linux bridge does not work with cisco_nexus ml2 plugins<br>> <br>> https://bugs.launchpad.net/networking-cisco/+bug/1421024<br>> <br>> anthony.<br>> <br>> From: Michael Gale [mailto:gale.michael@gmail.com<mailto:gale.michael@gmail.com>]<br>> Sent: Tuesday, February 16, 2016 12:42 PM<br>> To: openstack@lists.openstack.org<mailto:openstack@lists.openstack.org><br>> Subject: [Openstack] Nexus 9K - Nexus: Segment is an invalid type or not supported by this driver??<br>> <br>> Hello,<br>> <br>> I am having issues getting my Liberty environment working with VXLAN and N9K.<br>> <br>> Currently I am getting the following errors in the logs on startup:<br>> --snip--<br>> 2016-02-16 13:18:42.097 595 WARNING networking_cisco.plugins.ml2.drivers.cisco.nexus.mech_cisco_nexus [req-825a9891-0467-4958-86ca-c98486a7bf52 - - - - -] Nexus: Segment is an invalid type or not supported by this driv<br>> er. Network type = vxlan Physical network = None. Event not processed.<br>> --snip--<br>> <br>> When trying to launch an instance:<br>> --snip--<br>> ERROR neutron.plugins.ml2.managers [req-d15ab080-7aa4-46e5-a5c3-b62a13c5646d d2b4e18cf27d41418845439f5d788523 eaa185709c79477fa1e3edfffa4e4c7f - - -] Failed to bind port 9b32f0e7-6b5b-4ced-84b7-262ea12e090c on host compute1<br>> <br>> Nexus: Segment is None, Event not processed<br>> --snip--<br>> <br>> I am assuming I am missing something in the configuration file however I can't figure it out. Any help is greatly appreciated.<br>> <br>> Thanks<br>> Michael<br>> <br>> Here is my ml2_conf.ini<br>> <br>> --snip--<br>> # ML2 general<br>> [ml2]<br>> type_drivers = flat,vlan,nexus_vxlan,local<br>> tenant_network_types = nexus_vxlan<br>> mechanism_drivers = linuxbridge,l2population,cisco_nexus<br>> extension_drivers = port_security<br>> path_mtu = 0<br>> segment_mtu = 0<br>> <br>> <br>> <br>> # ML2 VLAN networks<br>> [ml2_type_vlan]<br>> network_vlan_ranges = physeth1:100:163<br>> <br>> [ml2_mech_cisco_nexus:10.92.192.45]<br>> infra1_neutron_agents_container-ee5293cb=1/17<br>> infra1_neutron_server_container-ed083568=1/17<br>> infra2_neutron_agents_container-65f32f70=1/18<br>> infra2_neutron_server_container-1e0b996b=1/18<br>> infra3_neutron_agents_container-2faafbe7=1/19<br>> infra3_neutron_server_container-9eabc975=1/19<br>> compute1=1/21<br>> compute2=1/22<br>> username=openstack<br>> password=foo123<br>> ssh_port=22<br>> physnet=physeth1<br>> <br>> [ml2_mech_cisco_nexus:10.92.192.46]<br>> infra1_neutron_agents_container-ee5293cb=1/17<br>> infra1_neutron_server_container-ed083568=1/17<br>> infra2_neutron_agents_container-65f32f70=1/18<br>> infra2_neutron_server_container-1e0b996b=1/18<br>> infra3_neutron_agents_container-2faafbe7=1/19<br>> infra3_neutron_server_container-9eabc975=1/19<br>> compute1=1/21<br>> compute2=1/22<br>> username=openstack<br>> password=foo123<br>> ssh_port=22<br>> physnet=physeth1<br>> <br>> # ML2 VXLAN networks<br>> [ml2_type_vxlan]<br>> vxlan_group =<br>> vni_ranges = 1:1000<br>> <br>> [ml2_type_nexus_vxlan]<br>> # Comma-separated list of <vni_min>:<vni_max> tuples enumerating<br>> # ranges of VXLAN VNI IDs that are available for tenant network allocation.<br>> vni_ranges=50000:55000<br>> <br>> # Multicast groups for the VXLAN interface. When configured, will<br>> # enable sending all broadcast traffic to this multicast group. Comma separated<br>> # list of min:max ranges of multicast IP's<br>> # NOTE: must be a valid multicast IP, invalid IP's will be discarded<br>> mcast_ranges=225.1.1.1:225.1.1.2<br>> <br>> # Security groups<br>> [securitygroup]<br>> enable_security_group = True<br>> enable_ipset = True<br>> <br>> --snip--<br>> <br>> <br>> and my linuxbridge_agent.ini:<br>> --snip--<br>> # Linux bridge agent physical interface mappings<br>> [linux_bridge]<br>> <br>> physical_interface_mappings = physeth1:eth11<br>> <br>> # Linux bridge agent VXLAN networks<br>> [vxlan]<br>> <br>> enable_vxlan = True<br>> vxlan_group =<br>> # VXLAN local tunnel endpoint<br>> local_ip = 10.96.2.141<br>> l2_population = True<br>> <br>> <br>> # Agent<br>> [agent]<br>> prevent_arp_spoofing = False<br>> <br>> # Security groups<br>> [securitygroup]<br>> firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver<br>> enable_security_group = True<br>> <br>> --snip--<br>> <br>> <br>> <br>> <br>> --<br>> <br>> ?The Man who says he can, and the man who says he can not.. Are both correct?<br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160216/f520c0e4/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 8<br>> Date: Wed, 17 Feb 2016 10:18:43 +0530<br>> From: Priyanka <ppnaik@cse.iitb.ac.in><br>> To: OpenStack Mailing List <openstack@lists.openstack.org><br>> Subject: [Openstack] add an extra external network<br>> Message-ID: <56C3FBAB.8060106@cse.iitb.ac.in><br>> Content-Type: text/plain; charset=utf-8; format=flowed<br>> <br>> Hi,<br>> <br>> I have an multinode openstack juno setup with VXLAN tunneling. I have an <br>> external network ext-net through which I assign floating IPs to the <br>> VMs. I have limited IPs in the external network subnet. I want to assign <br>> an additional external network so that I can assign the IPs from this <br>> new external network to the new VMs that I create. The VMs are attached <br>> to the same internal network demo-net and router demo-router.<br>> <br>> Thanks,<br>> <br>> <br>> Priyanka<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 9<br>> Date: Wed, 17 Feb 2016 01:21:13 -0500<br>> From: Erik McCormick <emccormick@cirrusseven.com><br>> To: Priyanka <ppnaik@cse.iitb.ac.in><br>> Cc: OpenStack Mailing List <openstack@lists.openstack.org><br>> Subject: Re: [Openstack] add an extra external network<br>> Message-ID:<br>> <CAHUi5cO3817Uu8kuXkYDGBTUqNTVMAuyXUwhuDydip1vwtp9eg@mail.gmail.com><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> Is the additional IP block contiguous with the existing one or at least on<br>> the neighbirhood?<br>> <br>> -Erik<br>> On Feb 17, 2016 12:06 AM, "Priyanka" <ppnaik@cse.iitb.ac.in> wrote:<br>> <br>> > Hi,<br>> ><br>> > I have an multinode openstack juno setup with VXLAN tunneling. I have an<br>> > external network ext-net through which I assign floating IPs to the VMs. I<br>> > have limited IPs in the external network subnet. I want to assign an<br>> > additional external network so that I can assign the IPs from this new<br>> > external network to the new VMs that I create. The VMs are attached to the<br>> > same internal network demo-net and router demo-router.<br>> ><br>> > Thanks,<br>> ><br>> ><br>> > Priyanka<br>> ><br>> > _______________________________________________<br>> > Mailing list:<br>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack<br>> > Post to : openstack@lists.openstack.org<br>> > Unsubscribe :<br>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack<br>> ><br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160217/69a5aace/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 10<br>> Date: Wed, 17 Feb 2016 11:02:24 +0000 (UTC)<br>> From: Tomas Vondra <vondra@czech-itc.cz><br>> To: openstack@lists.openstack.org<br>> Subject: Re: [Openstack] Guest networking and magic IP<br>> Message-ID: <loom.20160217T115824-638@post.gmane.org><br>> Content-Type: text/plain; charset=us-ascii<br>> <br>> Andre Goree <andre@...> writes:<br>> <br>> > I am trying to determine how exactly I can manipulate traffic from a <br>> > _guest's_ NIC using iptables on the _host_. On the host, there is a <br>> > bridged virtual NIC that corresponds to the guest's NIC. That interface <br>> > does not have an IP setup on it on the host, however within the vm <br>> > itself the IP is configured and everything works as expected. <br>> <br>> Hi!<br>> No IP on the interface does not prevent you from using iptables. The kernel<br>> filters any packets it sees. From what I remember from the OpenStack<br>> developers, you can't use iptables with OpenVSwitch, but attaching rules to<br>> a linux brcrl bridge should be perfectly fine. <br>> Tomas<br>> <br>> <br>> <br>> <br>> <br>> <br>> ------------------------------<br>> <br>> _______________________________________________<br>> Openstack mailing list<br>> openstack@lists.openstack.org<br>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack<br>> <br>> <br>> End of Openstack Digest, Vol 32, Issue 18<br>> *****************************************<br></div></div></div></div></div> </div></body>
</html>