Re: [openstack-dev] [Neutron] Neutron team social event in Barcelona
I would like to join. == Aihua Li == On Saturday, October 15, 2016 11:02 PM, Cathy Zhang wrote: #yiv6312206573 #yiv6312206573 -- _filtered #yiv6312206573 {font-family:SimSun;panose-1:2 1 6 0 3 1 1 1 1 1;} _filtered #yiv6312206573 {panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv6312206573 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv6312206573 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;} _filtered #yiv6312206573 {panose-1:2 1 6 0 3 1 1 1 1 1;}#yiv6312206573 #yiv6312206573 p.yiv6312206573MsoNormal, #yiv6312206573 li.yiv6312206573MsoNormal, #yiv6312206573 div.yiv6312206573MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv6312206573 a:link, #yiv6312206573 span.yiv6312206573MsoHyperlink {color:blue;text-decoration:underline;}#yiv6312206573 a:visited, #yiv6312206573 span.yiv6312206573MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv6312206573 span.yiv6312206573EmailStyle17 {color:#1F497D;}#yiv6312206573 .yiv6312206573MsoChpDefault {} _filtered #yiv6312206573 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv6312206573 div.yiv6312206573WordSection1 {}#yiv6312206573 +1 From: Miguel Lavalle [mailto:mig...@mlavalle.com] Sent: Friday, October 14, 2016 11:31 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [Neutron] Neutron team social event in Barcelona Dear Neutrinos, I am organizing a social event for the team on Thursday 27th at 19:30. After doing some Google research, I am proposing Raco de la Vila, which is located in Poblenou:http://www.racodelavila.com/en/index.htm. The menu is here:http://www.racodelavila.com/en/carta-racodelavila.htm It is easy to get there by subway from the Summit venue:https://goo.gl/maps/HjaTEcBbDUR2. I made a reservation for 25 people under 'Neutron' or "Miguel Lavalle". Please confirm your attendance so we can get a final count. Here's some reviews: https://www.tripadvisor.com/Restaurant_Review-g187497-d1682057-Reviews-Raco_De_La_Vila-Barcelona_Catalonia.html Cheers Miguel __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Multi-ip use cases
I have attempted to use the fixed_ip for our internal use. I found too many issues with the existing feature, and would propose to rewrite it as new feature. The problem I experienced are: 1. ) I have to repeatedly enter the option --fixed_ip for as many IPs as I need to apply. This will not scale if I wanted many IPs.2). The operation does not guarantee you get your original IP assigned, the VM instance become non-reachable.3). I can not requested seperate MAC addresses to go with the IP address.4.) The command acces privilage is controlled by policy. It would be more appropriate to use quota to control how many IPs a user can request instead of granting a privilage to the user. To use the mulitple IP,you can use OVS, mac-vlan etc. But that requires seperate MAC address to go with IPs. == Aihua Edward Li == On Friday, October 30, 2015 12:00 PM, Shraddha Pandhe wrote: Hi folks, James Penick from Yahoo! presented a talk on Thursday about how Yahoo uses Neutron for Ironic. I would like to follow up on one particular use case that was discussed: Multi-IP support. Here's our use-case for Multi-ip: For Ironic, we want user to specify the number of IPs on boot. Now, we want scheduler to find a network with sufficient IPs and then pick a host in that subnet (Note: static IPs for baremetal). Now, when allocating network, we want to assign all requested IPs from the same subnet as the host's static IP. Also, we don't want to configure those IPs on the host. We only want to display them on "nova show". So basically we will only create one port for the host, and append all fixed_ips in the ports fixed_ip list field. Questions:1. Hows do most people use the fixed_ips field in the port? What are different ways you can populate multiple IPs in fixed_ips? One way I know is, using neutron-client to create port, you can specify --fixed-ip as many times as you want, and that will append fixed_ips to the port. Any other way? 2. Is anybody else using multi-ip? __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron][networking-ovn][l3] Add/delete router interface
>From your description, it seems the issue is still on the OVN side. This does >not justify changing the gating criterion. If the gate is temporarily lifted and put in place later, that will push the burden of fixing to other contributor. == Aihua Edward Li == On Friday, October 16, 2015 7:11 PM, Chandra Sekhar Vejendla wrote: Hello Everyone, We are currently working on a patch set to add/delete router interfaces in the OVN plugin. This patch was initially worked on by Gal Sagie (https://review.openstack.org/#/c/206919/) and we took over to take it completion. There are bunch of gate tests that are failing as a result of this patch and we have fixed a few of them. What remain to be fixed are the following. test_dhcp6_stateless_from_os test_dualnet_multi_prefix_dhcpv6_stateless test_dualnet_multi_prefix_slaac test_multi_prefix_dhcpv6_stateless test_multi_prefix_slaac test_slaac_from_os The reason for the failure of these tests has got to do with the way OVN handles router interface. In openstack multiple subnets can be added to a network and for each of these subnets the router interface has to be explicitly configured. So for a given network there can be multiple router interfaces. With the current NB schema in OVN there can be only 1 router interface for a network. Most of the above test cases try to add multiple subnets in a network, configure router interfaces, do some connectivity tests and then clean up. When a router interface is configured for the first subnet all the DB tables are populated correctly, but when the router interface for the second subnet is created, it results in deletion of the router interface of the first subnet. So every time a router interface is configured for a subnet, it results in deletion of the previous subnets router interface, provided both the subnets belong to the same network. The test cases fail when they are trying to remove the router interface that has already been deleted from OVN NB. We considered an option to see if we can have a router port in "Logical Switch" table refer to multiple rows in the "Logical Router Port" table, but the router port in the schema is defined as a hard reference to uuid of the "Logical Router Port" table. Given that we want to demo l3 in Tokyo, should we consider disabling these tests until we figure out how to fix the issue ? Should i start a separate thread on ovs-dev to follow up on the issue? Thanks, Chandra __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] REST API to return ip-margin
>Network names are not guaranteed to be unique. This could cause >problems. If >I recall correctly we had a similar discussion about one of the >plugins (One >of the IBM ones?) where they ran into the issue of network >names and >uniqueness. My proposal is to use network-uuid as the key, and send the network name in the body, as shown below. { "network-1-uuid": { "total-ips" : 256 "available-ips" : count1, "name" : test-network, }} == Aihua Edward Li == On Friday, October 9, 2015 1:27 PM, Sean M. Collins wrote: On Fri, Oct 09, 2015 at 02:38:03PM EDT, Aihua Li wrote: > For this use-case, we need to return network name in the response.We also >have the implementation and accompanying tempest test scripts.The issue >1457986 is currently assigned to Mike Dorman. I am curious to see where we are >on this issue. Is the draft REST API ready? Can we incorporate my use-case >input into the considerations. Network names are not guaranteed to be unique. This could cause problems. If I recall correctly we had a similar discussion about one of the plugins (One of the IBM ones?) where they ran into the issue of network names and uniqueness. -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [neutron] REST API to return ip-margin
Hi, Neutrons, We have desire to have an API for neutron to return ip-margin, or the number of IP still available for use, for each network belong to a tenant. I have filed a launchpad issue 1503462. This is now marked as duplicate of 1457986. I am glad to see there are more parties that are interested in this feature. I would like to see how we can coordinate the effort on this feature.We have two use-cases for this feature: 1. To assist nova to select a network when creating a new VM instance. For this use-case, we like to have a tenant-id in GET request and get ip-margins for all the networks belong to the network.2. To provide information to monitor tools to show the capacities on dash-board. For this use-case, we need to return network name in the response.We also have the implementation and accompanying tempest test scripts.The issue 1457986 is currently assigned to Mike Dorman. I am curious to see where we are on this issue. Is the draft REST API ready? Can we incorporate my use-case input into the considerations. -- Aihua Reference:1. https://bugs.launchpad.net/neutron/+bug/15034622. https://bugs.launchpad.net/neutron/+bug/1457986 Reply, Reply All or Forward | moreopenstack-dev-ow...@lists.openstack.org toaihuaedwar...@yahoo.com Oct 8 at 11:41 AM- Forwarded Message - You have to be a subscriber to post to this mailing list, so your message has been automatically rejected. You can subscribe at: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev If you think that your messages are being rejected in error, contact the mailing list owner at %(listowner) Hi, Neutrons, We have desire to have an API for neutron to return ip-margin, or the number of IP still available for use, for each network belong to a tenant. I have filed a launchpad issue 1503462. This is now marked as duplicate of 1457986. I am glad to see there are more parties that are interested in this feature. I would like to see how we can coordinate the effort on this feature.We have two use-cases for this feature: 1. To assist nova to select a network when creating a new VM instance. For this use-case, we like to have a tenant-id in GET request and get ip-margins for all the networks belong to the network.2. To provide information to monitor tools to show the capacities on dash-board. For this use-case, we need to return network name in the response.We also have the implementation and accompanying tempest test scripts.The issue 1457986 is currently assigned to Mike Dorman. I am curious to see where we are on this issue. Is the draft REST API ready? Can we incorporate my use-case input into the considerations. -- Aihua Reference:1. https://bugs.launchpad.net/neutron/+bug/15034622. https://bugs.launchpad.net/neutron/+bug/1457986 == Aihua Edward Li ==__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev