Re: [openstack-dev] [Nova] PCI support

Gary, Cisco is adding it in our CI testbed. I guess that mlnx is doing the same for their MD as well. —Robert On 8/11/14, 9:05 AM, "Gary Kotton" mailto:gkot...@vmware.com>> wrote: Hi, At the moment all of the drivers are required CI support. Are there any plans regarding the PIC support. I u

[openstack-dev] [nova][sr-iov] Tomorrow's IRC meeting

Hi, I won’t be able to make it tomorrow. Please feel free having the meeting without me. Thanks, Robert ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron][IPv6] Neighbor Discovery for HA

Hi Xuhan, What I saw is that GARP is sent to the gateway port and also to the router ports, from a neutron router. I’m not sure why it’s sent to the router ports (internal network). My understanding for arping to the gateway port is that it is needed for proper NAT operation. Since we are not p

[openstack-dev] [nova][SR-IOV] Please review this patch series: replace pci_request storage with proper object usage

Hi, the patch series: https://review.openstack.org/#/c/117781/5 https://review.openstack.org/#/c/117895/ https://review.openstack.org/#/c/117839/ https://review.openstack.org/#/c/118391/ is ready for review. This needs to get in before Juno feature freeze so that the sr-iov patches can land i

[openstack-dev] [nova] requesting an FFE for SRIOV

Hi, The main sr-iov patches have gone through lots of code reviews, manual rebasing, etc. Now we have some critical refactoring work on the existing infra to get it ready. All the code for refactoring and sr-iov is up for review. https://blueprints.launchpad.net/nova/+spec/pci-passthrough-sriov

Re: [openstack-dev] [nova] requesting an FFE for SRIOV

Thanks!!! —Robert On 9/5/14, 7:48 AM, "John Garbutt" wrote: >In the nova-meeting we agreed this gets a FFE, based on previous >agreements in nova-meetings. > >Blueprint is approved for juno-rc1. > >Thanks, >John > >On 4 September 2014 16:38, Nikola Đipanov wrote: >> On 09/04/2014 05:16 PM, Dan

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Hi John, We had one on 12/14/2013 with the log: http://eavesdrop.openstack.org/meetings/pci_passthrough_meeting/2013/pci_pa ssthrough_meeting.2013-12-24-14.02.log.html The next one will be at UTC 1400 on Jan. 7th, Tuesday. --Robert On 1/2/14 10:06 AM, "John Garbutt" wrote: >On 22 December 2

Re: [openstack-dev] [nova] [neutron] Todays' meeting log: PCI pass-through network support

Somehow I missed this email until today. See inline… thanks, Robert On 12/24/13 1:31 AM, "Irena Berezovsky" mailto:ire...@mellanox.com>> wrote: Please, see inline From: Ian Wells [mailto:ijw.ubu...@cack.org.uk] Sent: Tuesday, December 24, 2013 1:38 AM To: OpenStack Development Mailing List (no

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Hi Folks, With John joining the IRC, so far, we had a couple of productive meetings in an effort to come to consensus and move forward. Thanks John for doing that, and I appreciate everyone's effort to make it to the daily meeting. Let's reconvene on Monday. But before that, and based on our t

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

rty like nuertron’s physical net name etc. And then, it’s about how to get these property, how to select/group devices based on the property, how to store/fetch these properties. I agree. But that's exactly what we are trying to accomplish. Thanks --jyh From: Robert Li (baoli) [mailto:ba.

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

AM, "yongli he" mailto:yongli...@intel.com>> wrote: On 2014年01月10日 00:49, Robert Li (baoli) wrote: Hi Folks, HI, all basiclly i flavor the pic-flavor style and against massing the white-list. please see my inline comments. With John joining the IRC, so far, we had a couple of produ

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

As I have responded in the other email, and If I understand PCI flavor correctly, then the issue that we need to deal with is the overlapping issue. A simplest case of this overlapping is that you can define a flavor F1 as [vendor_id='v', product_id='p'], and a flavor F2 as [vendor_id = 'v'] .

[openstack-dev] [nova] [neutron] PCI pass-through network support

Hi Folks, In light of today's IRC meeting, and for the purpose of moving this forward, I'm fine to go with the following if that's what everyone wants to go with: https://docs.google.com/document/d/1vadqmurlnlvZ5bv3BlUbFeXRS_wh-dsgi5plSjimWjU/edit But with some concerns and reservatio

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

wrote: >> To clarify a couple of Robert's points, since we had a conversation >> earlier: >> On 15 January 2014 23:47, Robert Li (baoli) wrote: >> --- do we agree that BDF address (or device id, whatever >> you call it), and node id shouldn&#x

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

olve the >libvirt network scenario in that framework. > >Thanks >--jyh > >> -Original Message- >> From: Robert Li (baoli) [mailto:ba...@cisco.com] >> Sent: Friday, January 17, 2014 7:08 AM >> To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

7;s proposal and we have solution to resolve the >libvirt network scenario in that framework. > >Thanks >--jyh > >> -Original Message- >> From: Robert Li (baoli) [mailto:ba...@cisco.com] >> Sent: Friday, January 17, 2014 7:08 AM >> To: OpenStack Development Mail

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

n the nova flavor, rather than introducing a new flavor. Thanks, Robert On 1/17/14 7:03 PM, "yunhong jiang" wrote: >On Fri, 2014-01-17 at 22:30 +, Robert Li (baoli) wrote: >> Yunhong, >> >> I'm hoping that these comments can be direc

[openstack-dev] [nova][neutron] PCI passthrough SRIOV

Hi Folks, As the debate about PCI flavor versus host aggregate goes on, I'd like to move forward with the SRIOV side of things in the same time. I know that tomorrow's IRC will be focusing on the BP review, and it may well continue into Thursday. Therefore, let's start discussing SRIOV side of

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV

n interaction points and interfaces this Thursday. Once we have the interaction points well defined, we can run parallel patches to cover the full story. Thanks a lot, Irena From: Robert Li (baoli) [mailto:ba...@cisco.com] Sent: Wednesday, January 22, 2014 12:02 AM To: OpenStack Development

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV

week. The goal is to determine the BPs that need to get approved, and to start coding. thanks, Robert On 1/22/14 8:03 AM, "Robert Li (baoli)" mailto:ba...@cisco.com>> wrote: Sounds great! Let's do it on Thursday. --Robert On 1/22/14 12:46 AM, "Irena Berezovsky"

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV

a better solution in a later release. And for now, people can either use host aggregate or resort to their own means. Let's keep the discussion going on this. Thanks, Robert On 1/24/14 4:50 PM, "Robert Li (baoli)" mailto:ba...@cisco.com>> wrote: Hi Folks, Based on

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV

Hi Irena, I agree on your first comment. see inline as well. thanks, Robert On 1/27/14 10:54 AM, "Irena Berezovsky" mailto:ire...@mellanox.com>> wrote: Hi Robert, all, My comments inline Regards, Irena From: Robert Li (baoli) [mailto:ba...@cisco.com] Sent: Monday, January

[openstack-dev] [nova][neutron] PCI pass-through SRIOV on Jan. 28th

Hi Folks, Check out 1 Agenda on Jan 28th, 2014. Please update if I have missed any thing. Let's finalize who's doing what tomorrow. I'm thinking to work on the nova SRIOV items, but the live migration may be a s

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV

le to support multiple vnic types? Or is it possible to reuse ovs agent, in the same time running another agent to support sriov? Any thoughts? --Robert On 1/27/14 4:01 PM, "Irena Berezovsky" mailto:ire...@mellanox.com>> wrote: Hi Robert, Please see inline From: Robert Li (baoli) [m

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV

27, 2014 1:01 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV Hi Robert, Please see inline From: Robert Li (baoli) [mailto:ba...@cisco.com] Sent: Monday, January 27, 2014 10:29 PM To: OpenStack Development M

[openstack-dev] PCI Request, associating a device to its original request

Hi Yongli, In today's IRC meeting, we discussed this a little bit. I think the answer probably lies in the definition of the PCI request. In the current implementation of _translate_alias_to_requests(), a new property (assume it's called requestor_id) maybe added to the PCI request. And this is

[openstack-dev] [nova][neutron] PCI pass-through SRIOV on Jan. 29th

Hi Folks, Can we have one more meeting tomorrow? I'd like to discuss the blueprints we are going to have and what each BP will be covering. thanks, Robert ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-b

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Hi, I added a few comments in this wiki that Yongli came up with: https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support Please check it out and look for Robert in the wiki. Thanks, Robert On 1/21/14 9:55 AM, "Robert Li (baoli)" wrote: >Yunhong, > >Just try to

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV on Jan. 29th

profile:vnic-type. We also need one or two BPs to cover the change in the neutron port-create/port-show CLI/API. Another thing is that we need to define the binding:profile dictionary. Thanks, Robert On 1/29/14 4:02 AM, "Irena Berezovsky" mailto:ire...@mellanox.com>> wrote:

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

that, and how many of PCI stats groups are there? What's the reasonable guidelines in defining the PCI flavors. thanks, Robert On 1/28/14 10:16 PM, "Robert Li (baoli)" wrote: >Hi, > >I added a few comments in this wiki that Yongli came up with: >https://wiki.openst

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV on Jan. 29th

type and PCI-passthru via two separate patches. Adding vnic_type will probably impose changes to existing Mech. Drivers while PCI-passthru is about introducing some pieces for new SRIOV supporting Mech. Drivers. More comments inline BR, IRena From: Robert Li (baoli) [mailto:ba...@cisco.com] Sen

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV on Jan. 29th

ot have options other than following the existing examples. thanks, Robert On 1/29/14 12:17 PM, "Irena Berezovsky" mailto:ire...@mellanox.com>> wrote: Hi Robert, Please see inline, I’ll try to post my understanding. From: Robert Li (baoli) [mailto:ba...@cisco.com] Sent: Wednes

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV on Jan. 29th

min_or_network_owner" "create_port:binding:profile:profileid": "rule:admin_or_network_owner" If it's not appropriate, then I agree with you we may need another extension. --Robert On 1/29/14 4:57 PM, "Robert Kukura" wrote: >On 01/29/2014 09:46 AM,

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV on Jan. 29th

ege to select a specific vlan, which the admin does. Those are just my thoughts, which may be wrong. And we can continue our discussion tomorrow. thanks, Robert On 1/29/14 5:50 PM, "Robert Kukura" wrote: >On 01/29/2014 05:44 PM, Robert Li (baoli) wrote: >> Hi Bob, >> >>

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

M, "Ian Wells" mailto:ijw.ubu...@cack.org.uk>> wrote: My proposals: On 29 January 2014 16:43, Robert Li (baoli) mailto:ba...@cisco.com>> wrote: 1. pci-flavor-attrs is configured through configuration files and will be available on both the controller node and the co

[openstack-dev] [nova][neutron] PCI pass-through SRIOV on Jan. 30th

Hi, We made a lot of progress today. We agreed that: -- vnic_type will be a top level attribute as binding:vnic_type -- BPs: * Irena's https://blueprints.launchpad.net/neutron/+spec/ml2-request-vnic-type for binding:vnic_type * Bob to submit a BP for binding:profile in ML2. SRIOV input

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV on Jan. 30th

Hi Irena, Thanks for the Reply. See inline… If possible, can we put details on what would be exactly covered by each BP? --Robert On 1/30/14 4:13 PM, "Irena Berezovsky" mailto:ire...@mellanox.com>> wrote: Robert, Thank you very much for the summary. Please, see inline From:

Re: [openstack-dev] The simplified blueprint for PCI extra attributes

Hi Yunhong, A couple of questions: -- about the pci_information config item in your spec. What is a device_id? -- in libvirt driver, we need to retrieve the PCI devices allocated for the requested networks. These PCI devices won't be treated as hostdev devices in the domain xml, rather as

Re: [openstack-dev] The simplified blueprint for PCI extra attributes and SR-IOV NIC blueprint

Hi John and all, Yunhong's email mentioned about the SR-IOV NIC support BP: https://blueprints.launchpad.net/nova/+spec/pci-passthrough-sriov I'd appreciate your consideration of the approval of both BPs so that we can have SR-IOV NIC support in Icehouse. Thanks, Robert On 2/4/14 1:36 AM, "Jia

[openstack-dev] [nova][neutron] SRIOV: Recap of Feb 12th and agenda on Feb 13th

Hi Folks, I put the recap in here:2 Feb. 12th, 2014 Recap. Please take a look at and see if everything is fine and correct any misunderstandings. I also put together an Agenda for tomorrow in here:1 Agenda on Feb. 13

[openstack-dev] [nova][neutron] SRIOV Meeting on Wednesday Feb.19th

Hi Folks, Irena suggested to have another sync-up meeting on Wednesday. So let's meet at 8:00am at #openstack-meeting-alt. Thanks, Robert ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listin

[openstack-dev] [nova][neutron] SR-IOV networking patches available

Hi, The following two Work In Progress patches are available for end-to-end SR-IOV networking: nova client: https://review.openstack.org/#/c/67503/ nova: https://review.openstack.org/#/c/67500/ Please check the commit messages for how to use them. Neutron changes required to support SR-IOV have

Re: [openstack-dev] [Neutron][IPv6] BP:Store both IPv6 LLA and GUA address on router interface port

Hi Xuhan, Thank you for your summary. see comments inline. --Robert On 2/27/14 12:49 AM, "Xuhan Peng" mailto:pengxu...@gmail.com>> wrote: As the follow up action of IPv6 sub-team meeting [1], I created a new blueprint [2] to store both IPv6 LLA and GUA address on router interface port. Here

Re: [openstack-dev] PCI SRIOV meeting suspend?

;>Juno. >> BR, >thanks, Irena. > >Yongli he >> Irena >> >> -Original Message- >> From: yongli he [mailto:yongli...@intel.com] >> Sent: Tuesday, March 04, 2014 3:28 AM >> To: Robert Li (baoli); Irena Berezovsky; OpenStack Development Mailing >>

Re: [openstack-dev] [Neutron][IPv6] Update the Wiki with links to blueprints and reviews

Hi Sean, I just added the ipv6-prefix-delegation BP that can be found using the search link on the ipv6 wiki. More details about it will be added once I find time. thanks, --Robert On 3/4/14 10:05 AM, "Collins, Sean" wrote: >Hi All, > >We've got a lot of work in progress, so if you >have a blu

Re: [openstack-dev] [Neutron][IPv6] Update the Wiki with links to blueprints and reviews

Yea. that's a good idea. I will try to find out time working on the spec. --Robert On 3/4/14 11:17 AM, "Collins, Sean" wrote: >On Tue, Mar 04, 2014 at 04:06:02PM +, Robert Li (baoli) wrote: >> Hi Sean, >> >> I just added the ipv6-prefix-delegation BP t

Re: [openstack-dev] Change in openstack/neutron[master]: Permit ICMPv6 RAs only from known routers

Hi Xu Han & Sean, Is this code going to be committed as it is? Based on this morning's discussion, I thought that the IP address used to install the RA rule comes from the qr-xxx interface's LLA address. I think that I'm confused. Also this bug: Allow LLA as router interface of IPv6 subnet https:

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV binding of ports

to write the >>below mentioned Base/Mixin class that inherits from >>AgentMechanismDriverBase class? When you mentioned port state, were you >>referring to the validate_port_binding() method? >> >>Pls clarify. >> >>Thanks, >>Sandhya >> >>On

Re: [openstack-dev] Change in openstack/neutron[master]: Permit ICMPv6 RAs only from known routers

Hi Sean, See embedded commentsŠ Thanks, Robert On 3/4/14 3:25 PM, "Collins, Sean" wrote: >On Tue, Mar 04, 2014 at 02:08:03PM EST, Robert Li (baoli) wrote: >> Hi Xu Han & Sean, >> >> Is this code going to be committed as it is? Based on this morning

Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV binding of ports

py, and very simple code for >mech_sriov_nic_switch.py. > >Please take a look and review. > >BR, >Irena > >-Original Message- >From: Irena Berezovsky [mailto:ire...@mellanox.com] >Sent: Wednesday, March 05, 2014 9:04 AM >To: Robert Li (baoli); Sandhya Dasu (sadasu); OpenStack Devel

Re: [openstack-dev] Change in openstack/neutron[master]: Permit ICMPv6 RAs only from known routers

t so far I haven't been convinced yet. thanks, Robert On 3/5/14 10:21 AM, "Collins, Sean" wrote: >Hi Robert, > >I'm reaching out to you off-list for this: > >On Wed, Mar 05, 2014 at 09:48:46AM EST, Robert Li (baoli) wrote: >> As a result of this chang

[openstack-dev] [nova][sriov] SRIOV related specs pending for approval

Hi, During the Kilo summit, the folks in the pci passthrough and SR-IOV groups discussed what we’d like to achieve in this cycle, and the result was documented in this Etherpad: https://etherpad.openstack.org/p/kilo_sriov_pci_passthrough To get the work going, we’ve submitted a few design specs

Re: [openstack-dev] [nova][sriov] SRIOV related specs pending for approval

. Thanks, Robert On 12/18/14, 9:13 PM, "Joe Gordon" mailto:joe.gord...@gmail.com>> wrote: On Thu, Dec 18, 2014 at 2:18 PM, Robert Li (baoli) mailto:ba...@cisco.com>> wrote: Hi, During the Kilo summit, the folks in the pci passthrough and SR-IOV groups discussed what we’d l

Re: [openstack-dev] [qa] host aggregate's availability zone

Hi Danny, check this link out. https://wiki.openstack.org/wiki/Scheduler_Filters Add the following into your /etc/nova/nova.conf before starting the nova service. scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, RamFilter, ComputeFilter, ComputeCapabilitiesFilter, ImageProperti

Re: [openstack-dev] [nova][sriov] SRIOV related specs pending for approval

-stateless-offloads Thanks for your kindly consideration. —Robert On 12/22/14, 1:20 PM, "Joe Gordon" mailto:joe.gord...@gmail.com>> wrote: On Fri, Dec 19, 2014 at 6:53 AM, Robert Li (baoli) mailto:ba...@cisco.com>> wrote: Hi Joe, See this thread on the SR-IOV CI from Ir

[openstack-dev] [nova] Request Spec Freeze Exception

Hi, During the Kilo summit, the folks in the pci passthrough and SR-IOV groups discussed what we’d like to achieve in this cycle, and the result was documented in this Etherpad: https://etherpad.openstack.org/p/kilo_sriov_pci_passthrough To get the work going, we’ve submitted a few design specs

[openstack-dev] SR-IOV IRC meeting on Jan, 13th Canceled

Hi, I’m canceling the meeting since I’m traveling this week. Regards, Robert __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://li

[openstack-dev] [openstack][nova] Question on rollback live migration at the destination

Hi, I’m looking at rollback_live_migration_at_destination() in compute/manager.py. If it’s shared storage (such as NFS, is_shared_instance_path is True), it’s not going to be called since _live_migration_cleanup_flags() will return False. Can anyone let me know what’s the reason behind it? So n

[openstack-dev] SR-IOV summit session

Hi John, With the summit around the corner, please advise how we should run this session: http://summit.openstack.org/cfp/details/248 We are currently working on this nova spec, https://review.openstack.org/#/c/86606/. I guess its content will be a candidate to be presented in the session. T

Re: [openstack-dev] [Neutron][IPv6] Neutron Routers and LLAs

DR be attached to a router. Xuhan On Wed, Mar 26, 2014 at 9:52 PM, Robert Li (baoli) mailto:ba...@cisco.com>> wrote: Hi Sean, Unless I have missed something, this is my thinking: -- I understand that the goal is to allow RAs from designated sources only. -- initially, xuhanp posted a diff

Re: [openstack-dev] Informal meeting before SR-IOV summit presentation

This is the one that Irena created: https://etherpad.openstack.org/p/pci_passthrough_cross_project On 5/8/14, 4:33 PM, "Steve Gordon" wrote: >- Original Message - >> > It would be nice to have an informal discussion / unconference session >> > before the actual summit session on SR-IOV.

Re: [openstack-dev] Informal meeting before SR-IOV summit presentation

gt;Thanks, >Sandhya > >On 5/9/14 11:44 AM, "Steve Gordon" wrote: > >>- Original Message - >>> From: "Robert Li (baoli)" >>> Subject: Re: Informal meeting before SR-IOV summit presentation >>> >>> This is the one that Irena

Re: [openstack-dev] Informal meeting before SR-IOV summit presentation

the program pods area should be open. On 5/9/14, 3:33 PM, "Sandhya Dasu (sadasu)" wrote: >I have no idea, how to pick a location. >Should we meet at the Cisco booth at 1pm and then take it from there? > >Any other ideas? > >Thanks, >sandhya > >On 5/9/14 3:17 PM, "Brent Eagles" wrote: > >>On 09/

Re: [openstack-dev] [Neutron][IPv6] Privacy extension

Dane put some notes on the session’s ether pad to support multiple prefixes. Seem like this is really something that everyone want to support in openstack. ―Robert On 5/16/14, 2:23 PM, "Martinx - ジェ�`ムズ" mailto:thiagocmarti...@gmail.com>> wrote: Precisely Anthony! We talked about this topic (

[openstack-dev] [nova] SR-IOV nova-specs

Hi John, Now that we have agreement during the summit on how to proceed in order to get it in to Juno, please take a look at this: https://review.openstack.org/#/c/86606/16 Please let us know your comments or what is still missing. I’m also not sure if your –2 needs to be removed before the o

Re: [openstack-dev] [nova] SR-IOV nova-specs

d, been traveling last few days. > >Thanks, >John > >On 27 May 2014 19:21, Robert Li (baoli) wrote: >> Hi John, >> >> Now that we have agreement during the summit on how to proceed in order >>to >> get it in to Juno, please take a look at this: >&

[openstack-dev] [nova][pci] A couple of questions

Hi Yunhong & Yongli, In the routine _prepare_pci_devices_for_use(), it’s referring to dev[‘hypervisor_name’]. I didn’t see code that’s setting it up, or the libvirt nodedev xml includes hypervisor_name. Is this specific to Xen? Another question is about the issue that was raised in this review:

Re: [openstack-dev] [nova][pci] A couple of questions

For your first question, I suspect it’s something wrong and should be ‘devi_id’, which is the hypervisor’s identification for the device. I will leave Yongli to have more comments on it. For the second one, thanks for point the issue out. Yes, I’m working on fixing it. --jyh From:

[openstack-dev] [neutron][ipv6] Support ipv6 RA in neutron

Hi, I was mistakenly reusing the Blueprint https://blueprints.launchpad.net/neutron/+spec/neutron-ipv6-radvd-ra to draft up the ipv6 RA support in neutron. I apologize for any confusion that this may have caused. To correct it, I created a new blueprint https://blueprints.launchpad.net/neutron

[openstack-dev] [neutron][ipv6] ipv6 dual stack

Hi, I added ipv6 support in devstack https://review.openstack.org/#/c/87987/. This is a WIP patch given that neutron ipv6 is not fully implemented yet. With this script, dual stack data network can be created with neutron as well. The only thing that needs to be done manually is starting the RA

[openstack-dev] [nova] need core reviewers for https://review.openstack.org/#/c/81954/

Hi, The SR-IOV work depends on this fix. It has got +1’s for quite some time, and need core reviewers to review and approve. thanks, Robert ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/list

[openstack-dev] [nova] tomorrow's PCI passthrough IRC meeting

Hi, I’m taking tomorrow off, and therefore I won’t be present in the IRC meeting. We made a lot of progress last week. We’ve got the first +2 for our spec, and therefore it’s a big step forward toward getting approval. A lot of progress on the coding front as well, and more patches will be comi

Re: [openstack-dev] [Neutron][IPv6][Security Group] BP: Support ICMP type filter by security group

Hi Akihiro, In the case of IPv6 RA, its source IP is a Link Local Address from the router's RA advertising interface. This LLA address is automatically generated and not saved in the neutron port DB. We are exploring the idea of retrieving this LLA if a native openstack RA service is running on th

Re: [openstack-dev] [Neutron][IPv6][Security Group] BP: Support ICMP type filter by security group

llow RA is reasonable as >a workaround. >However, for a long time solution, it is better to explore a way to >configure >infra-required rules. > >Thanks, >Akihiro > > >On Sat, Mar 8, 2014 at 12:50 AM, Robert Li (baoli) >wrote: >> Hi Akihiro, >> >>

Re: [openstack-dev] [nova][PCI] one use case make the flavor/extra-info based solution to be right choice

Hi Yongli, I'm very glad that you bring this up and relive our discussion on PCI passthrough and its application on networking. The use case you brought up is: user wants a FASTER NIC from INTEL to join a virtual networking. By FASTER, I guess that you mean that the user is allowed t

Re: [openstack-dev] [Neutron][IPv6] Neutron Routers and LLAs

Hi Sean, Unless I have missed something, this is my thinking: -- I understand that the goal is to allow RAs from designated sources only. -- initially, xuhanp posted a diff for https://review.openstack.org/#/c/72252. And my comment was that subnet that was created with gateway ip not on the sa

Re: [openstack-dev] [nova][pci]PCI SR-IOV use cases initial doc

ntel >>>and >>> Mellanox take HW VEB (HW embedded switch) approach. >>> >>> 1. open to mail list. >>> 2. admin/usr won't mixing Intel/Cisco/Mellanox card, does not mean >>>we >>> should disable it, or don't give a chanc

[openstack-dev] [Devstack] [IPv6]

Hi folks, If you want to use IPv6 with devstack, Check this out https://review.openstack.org/87987. The commit message has all the details on how to use it. thanks, Robert ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.o

Re: [openstack-dev] [neutron] [IPv6] New API format for extra_dhcp_opts

Hi Xu Han, My question is how the CLI user interface would look like to distinguish between v4 and v6 dhcp options? Thanks, Robert On 9/28/14, 10:29 PM, "Xu Han Peng" mailto:pengxu...@gmail.com>> wrote: Mark's suggestion works for me as well. If no one objects, I am going to start the implem

Re: [openstack-dev] [neutron] [IPv6] New API format for extra_dhcp_opts

ark's suggestion: neutron port-create extra_dhcp_opts opt_name=,opt_value=,version=4(or 6) This extra_dhcp_opts can be repeated and version is optional (no version means version=4). Xu Han On 09/29/2014 08:51 PM, Robert Li (baoli) wrote: Hi Xu Han, My question is how the CLI user interface

Re: [openstack-dev] [devstack] local.conf ini file setting issues

Hi Ian, I agree with your plan. I¹ve +1ed the first two patches. I responded to your comments on [3]. Basically I think that iniadd_literal is necessary. In addition, [3] will also keep the original order of items. With all of the three patches, I think the end result would be that it¹s almost e

Re: [openstack-dev] [Neutron] Proposing to disallow updates of IPv6 attributes on subnets

Hi Thiago, A couple of things to consider: ― As it is now, it doesn’t seem to be fully functional if you change your subnet to use SLAAC. The addresses that were assigned to your existing ports in neutron wouldn’t be updated/changed. So basically, you can not simply make an API call to change

Re: [openstack-dev] [nova] pci pass through turing complete config options?

Sean, Are you talking about this one: https://review.openstack.org/#/c/128805/? is it still breaking something after fixing the incompatible awk syntax? Originally https://review.openstack.org/#/c/123599/ proposed a simple patch to support that config. But it was abandoned in favor of the local.c

Re: [openstack-dev] ipv6 and ipv4 dual stack for floating IP

ipv6 floating Ip is currently not supported. Check out this review and the associated bug: https://review.openstack.org/#/c/131145/ —Robert On 10/30/14, 6:47 AM, "Jerry Xinyu Zhao" mailto:xyzje...@gmail.com>> wrote: Unfortunately, it seems to be the case. Just saw there is a summit talk about

Re: [openstack-dev] [nova] pci pass through turing complete config options?

On 10/28/14, 11:01 AM, "Daniel P. Berrange" wrote: >On Tue, Oct 28, 2014 at 10:18:37AM -0400, Jay Pipes wrote: >> On 10/28/2014 07:44 AM, Daniel P. Berrange wrote: >> >One option would be a more CSV like syntax eg >> > >> >pci_passthrough_whitelist = >>address=*0a:00.*,physical_network=phy

Re: [openstack-dev] [nova] pci pass through turing complete config options?

On 11/3/14, 6:32 PM, "Doug Hellmann" wrote: > >On Oct 31, 2014, at 9:27 PM, Robert Li (baoli) wrote: > >> >> >> On 10/28/14, 11:01 AM, "Daniel P. Berrange" wrote: >> >>> On Tue, Oct 28, 2014 at 10:18:37AM -0400, Jay Pipe

Re: [openstack-dev] [Neutron] IPv6 team summit meetup

will be there too On 11/7/14, 4:53 AM, "Brian Haley" wrote: >On 11/06/2014 04:18 PM, Xuhan Peng wrote: >> Hey, >> >> Since we don't have any slot for ipv6 in summit to meet up, can we have >> a lunch meetup together tomorrow (11/7 Friday)? >> >> We can meet at 12:30 at the meet up place Neuilly

Re: [openstack-dev] [neutron] Is this fix introducing another different bug to dhcp-agent?

Nice catch. Since it’s already merged, a new bug may be in order. —Robert On 11/13/14, 10:25 AM, "Miguel Ángel Ajo" mailto:majop...@redhat.com>> wrote: I believe this fix to IPv6 dhcp spawn breaks isolated metadata when we have a subnet combination like this on a network: 1) IPv6 subnet, with

Re: [openstack-dev] [Neutron][IPv6] Neutron IPv6 in Icehouse and further

Hi, There is a patch for radvd https://review.openstack.org/#/c/102648/2 that you can use in addition to the devstack patch. You want to make sure that ipv6 is enabled and ra accepted with your VM’s image. Both patches are under development. To use dhcpv6, the current dhcp agent should be wor

[openstack-dev] [nova][sriov] weekly meeting for july 1st and july 8th

Hi, I will be on PTO from Tuesday, and come back to office on July 9th Wednesday. Therefore, I won’t be present in the next two SR-IOV weekly meetings. Regarding the sr-iov development status, I finally fixed all the failures in the existing unit tests. Rob and I are still working on adding new

[openstack-dev] [nova][sriov] today's IRC meeting

Hi, I need to pick up my son at 9:00. It’s a short trip. So I will be late about 15 minutes. Status wise, if everything goes well, the patches should be up in a couple of days. One of the challenges is due to dividing them up, some unit tests will fail due to missing module and it took time t

Re: [openstack-dev] [nova][sriov] patch that depends on multiple existing patches under review

Hi, I was working on the last patch that I’d planned to submit for SR-IOV. It turned out this patch would depend on multiple existing patches. “git review –d” seems to be supporting one dependency only. Do let me know how we can create a patch that depends on multiple existing patches under rev

Re: [openstack-dev] [nova][sriov] patch that depends on multiple existing patches under review

Thanks Russell for the quick response. I¹ll give it a try rearranging the dependencies. ‹Robert On 7/15/14, 3:26 PM, "Russell Bryant" wrote: >On 07/15/2014 03:12 PM, Robert Li (baoli) wrote: >> Hi, >> >> I was working on the last patch that I¹d planned to subm

[openstack-dev] [neutron][SR-IOV]: RE: ML2 mechanism driver for SR-IOV capable NIC based switching, ...

Hi Kyle, Sorry I missed your queries on the IRC channel today. I was thinking about this whole BP. After chatting with Irena this morning, I think that I understand what this BP is trying to achieve overall. I also had a chat with Sandhya afterwards. I¹d like to discuss a few things in here:

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Hi Irena, This is Robert Li from Cisco Systems. Recently, I was tasked to investigate such support for Cisco's systems that support VM-FEX, which is a SRIOV technology supporting 802-1Qbh. I was able to bring up nova instances with SRIOV interfaces, and establish networking in between the insta

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

nterested to exchange more emails or set an IRC/WebEx meeting during this week before the summit? Sure. If folks want to discuss it before the summit, we can schedule a webex later this week. Or otherwise, we can continue the discussion with email. Regards, Irena From: Robert Li (baoli) [mailt

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

onfiguration can be applied by a dedicated L2 neutron agent. BR, Irena From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com] Sent: Tuesday, October 29, 2013 9:04 AM To: Robert Li (baoli); Irena Berezovsky; prashant.upadhy...@aricent.com<mailto:prashant.upadhy...@aricent.com>; chris

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

he nova scheduler make host decision? Thanks --jyh From: Robert Li (baoli) [mailto:ba...@cisco.com] Sent: Monday, October 28, 2013 12:22 PM To: Irena Berezovsky; prashant.upadhy...@aricent.com<mailto:prashant.upadhy...@aricent.com>; Jiang, Yunhong; chris.frie...@windriver.com<mailto:chris.fr

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

;be >> also responsible for managing update requests coming from the neutron >> server. >> >> >> >> For macvtap vNIC type assignment, the networking configuration can be >> applied by a dedicated L2 neutron agent. >> >> >> >> BR, >

[openstack-dev] [nova] [neutron] #openstack IRC meeting UTC 1300 Friday on PCI pass-through network support

Hi, Let's have a meeting with the #openstack IRC channel at UTC 1300 Friday. Based on our email discussions so far, I listed the topics in below: -- physical network binding -- nova/neutron APIs to support SRIOV -- PCI Alias thanks, Robert ___

  1   2   >