reviews and feedbacks to move this forward.
Thanks,
Robert
On 6/7/17, 12:36 PM, "Robert Li (baoli)" <ba...@cisco.com> wrote:
Hi Bence,
Thanks for the pointers. I was aware of this
https://bugs.launchpad.net/neutron/+bug/1631371, but not the blueprint you
wrote.
Hi Bence,
Thanks for the pointers. I was aware of this
https://bugs.launchpad.net/neutron/+bug/1631371, but not the blueprint you
wrote.
As suggested by Matt in https://bugs.launchpad.net/nova/+bug/1693535, I wrote a
blueprint https://blueprints.launchpad.net/nova/+spec/expose-vlan-trunking,
I created a nova bug for this: https://bugs.launchpad.net/nova/+bug/1693535. I
am currently working on a code patch for it.
--Robert
On 5/24/17, 3:52 PM, "Robert Li (baoli)"
<ba...@cisco.com<mailto:ba...@cisco.com>> wrote:
Thanks for the pointer. I think your suggestion
ndo M." <arma...@gmail.com<mailto:arma...@gmail.com>>
wrote:
On 24 May 2017 at 08:53, Robert Li (baoli)
<ba...@cisco.com<mailto:ba...@cisco.com>> wrote:
Hi Kevin,
In that case, I will start working on it. Should this be considered a RFE or a
regular bug?
There have
expose it as
metadata to the VM in Nova.
On May 22, 2017 1:27 PM, "Robert Li (baoli)"
<ba...@cisco.com<mailto:ba...@cisco.com>> wrote:
Hi Levi,
Thanks for the info. I noticed that support in the nova code, but was wondering
why something similar is not available for vlan trunk
oses thing that I know about is tagging of SR-IOV physical function’s
VLAN tag to guests see [1]
Maybe you can leverage the same mechanism to config vlan trunking in guest.
[1] -
https://specs.openstack.org/openstack/nova-specs/specs/ocata/implemented/sriov-pf-passthrough-neutron-port-vlan.html
Hi,
I’m trying to find out if there is support in nova (in terms of metadata and
cfgdrive) to configure vlan trunking in the guest. In the ‘CLI usage example’
provided in this wiki https://wiki.openstack.org/wiki/Neutron/TrunkPort, it
indicates:
# The typical cloud image will auto-configure
As far as I know, it was discussed but not supported yet. It requires change in
nova and support in the neutron plugins.
—Robert
On 9/8/15, 9:39 AM, "Vladyslav Gridin"
>
wrote:
Hi All,
Is there a way to
First of all, your network contains an IPv4 and an IPv6 SLAAC subnet.
Given the the definition of SLAAC, your port will receive an IPv6 address
from the Ipv6 subnet. On the other hand, if you want your network to have
both IPv6 and IPv4, and want to selectively assign either IPv4 or IPv6 to
your
Hi,
On your controller node, you can add in local.conf:
[[post-config|$NOVA_CONF]]
[DEFAULT]
scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, RamFilter,
ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter,
ServerGroupAntiAffinityFilter, ServerGroupAffinityFilter,
Hi Mike,
Currently dual stack is supported. Can you be specific on what
interoperation/transition techniques you are interested in? We’ve been thinking
about NAT64 (stateless or stateful).
thanks,
Robert
On 5/4/15, 9:56 PM, Mike Spreitzer
mspre...@us.ibm.commailto:mspre...@us.ibm.com wrote:
Hi,
I will not be available tomorrow morning for the meeting. Please feel free to
go ahead without me.
Cheers,
Robert
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
“extra_info” is no longer a key in the stats pool, nor the “physical_function”.
If you check pci/stats.py, the keys are pool_keys = ['product_id',
'vendor_id', 'numa_node’] plus whatever tags are used in the whitelist. So I
believe it’s something like this:
os-pci:pci_stats: [
{
count: 5,
My guess is that your dhcp client running inside the VM set up the subnet
mask as /128. Dhcpv6 doesn¹t provide prefix length, but the client system
sometime adds the net mask based on the link type. Some of the dhcp
clients use a script to configure the interface, and I think you can use
/64 if
.
John Davidge
OpenStack@Cisco
On 13/02/2015 16:01, Ihar Hrachyshka
ihrac...@redhat.commailto:ihrac...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the write-up! See inline.
On 02/13/2015 04:34 PM, Robert Li (baoli) wrote:
Hi,
while trying to integrate dibbler
If you just use SR-IOV for networking, then pci_alias is not needed.
—Robert
On 2/16/15, 3:11 PM, Harish Patil
harish.pa...@qlogic.commailto:harish.pa...@qlogic.com wrote:
Hello,
Do we still need “pci_alias config under /etc/nova/nova.conf for SR-IOV PCI
passthru’ ?
I have Juno release of
Hi,
while trying to integrate dibbler client with neutron to support PD, we
countered a few issues with the dibbler client (and server). With a neutron
router, we have the qg-xxx interface that is connected to the public network,
on which a dhcp server is running on the delegating router. For
Hi,
I won’t be able to make it for tomorrow’s meeting. But you guys are welcome to
have the meeting without me.
—Robert
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
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
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
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
-with-stateless-offloads
Thanks for your kindly consideration.
—Robert
On 12/22/14, 1:20 PM, Joe Gordon
joe.gord...@gmail.commailto:joe.gord...@gmail.com wrote:
On Fri, Dec 19, 2014 at 6:53 AM, Robert Li (baoli)
ba...@cisco.commailto:ba...@cisco.com wrote:
Hi Joe,
See this thread on the SR-IOV CI from
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,
.
Thanks,
Robert
On 12/18/14, 9:13 PM, Joe Gordon
joe.gord...@gmail.commailto:joe.gord...@gmail.com wrote:
On Thu, Dec 18, 2014 at 2:18 PM, Robert Li (baoli)
ba...@cisco.commailto:ba...@cisco.com wrote:
Hi,
During the Kilo summit, the folks in the pci passthrough and SR-IOV groups
discussed what
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
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
majop...@redhat.commailto: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)
will be there too
On 11/7/14, 4:53 AM, Brian Haley brian.ha...@hp.com 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
On 11/3/14, 6:32 PM, Doug Hellmann d...@doughellmann.com wrote:
On Oct 31, 2014, at 9:27 PM, Robert Li (baoli) ba...@cisco.com wrote:
On 10/28/14, 11:01 AM, Daniel P. Berrange berra...@redhat.com wrote:
On Tue, Oct 28, 2014 at 10:18:37AM -0400, Jay Pipes wrote:
On 10/28/2014 07:44 AM
On 10/28/14, 11:01 AM, Daniel P. Berrange berra...@redhat.com 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 =
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
xyzje...@gmail.commailto:xyzje...@gmail.com wrote:
Unfortunately, it seems to be the case. Just saw there is a
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
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
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
:
neutron port-create extra_dhcp_opts
opt_name=dhcp_option_name,opt_value=value,version=4(or 6) network
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
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
pengxu...@gmail.commailto:pengxu...@gmail.com wrote:
Mark's suggestion works for me as well. If no one objects, I am going to
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.
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
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
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
gkot...@vmware.commailto:gkot...@vmware.com wrote:
Hi,
At the moment all of the drivers are required CI support. Are there any plans
regarding the
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
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:
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
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
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 rbry...@redhat.com 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 submit for SR-IOV
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
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
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
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
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
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:
traveling last few days.
Thanks,
John
On 27 May 2014 19:21, Robert Li (baoli) ba...@cisco.com 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:
https://review.openstack.org/#/c/86606/16
Please let us
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
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 - ジェ�`ムズ
thiagocmarti...@gmail.commailto:thiagocmarti...@gmail.com wrote:
Precisely Anthony! We
:
- Original Message -
From: Robert Li (baoli) ba...@cisco.com
Subject: Re: Informal meeting before SR-IOV summit presentation
This is the one that Irena created:
https://etherpad.openstack.org/p/pci_passthrough_cross_project
Thanks, I missed this as it wasn't linked from the design
to a router.
Xuhan
On Wed, Mar 26, 2014 at 9:52 PM, Robert Li (baoli)
ba...@cisco.commailto: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
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.
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
it, or don't give a chance.
3. i raise couple of question and questioning the aggregate solution.
see
inline comments.
https://docs.google.com/document/d/1zgMaXqrCnad01-jQH7Mkmf6amlghw9RMScGL
BrKslmw/edit
Yongli He
Thanks,
Irena
From: Robert Li (baoli) [mailto:ba...@cisco.com]
Sent
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
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
a way to
configure
infra-required rules.
Thanks,
Akihiro
On Sat, Mar 8, 2014 at 12:50 AM, Robert Li (baoli) ba...@cisco.com
wrote:
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
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
Hi Sean,
See embedded commentsŠ
Thanks,
Robert
On 3/4/14 3:25 PM, Collins, Sean sean_colli...@cable.comcast.com 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's
discussion, I
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 Development
Mailing List (not for usage questions); Robert Kukura
haven't been
convinced yet.
thanks,
Robert
On 3/5/14 10:21 AM, Collins, Sean sean_colli...@cable.comcast.com
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 change, it will end up having two LLA
-
From: yongli he [mailto:yongli...@intel.com]
Sent: Tuesday, March 04, 2014 3:28 AM
To: Robert Li (baoli); Irena Berezovsky; OpenStack Development Mailing
List
Subject: PCI SRIOV meeting suspend?
HI, Robert
does it stop for while?
and if you are convenient please review this patch set
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 sean_colli...@cable.comcast.com
wrote:
Hi All,
We've got a lot of work in
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 sean_colli...@cable.comcast.com
wrote:
On Tue, Mar 04, 2014 at 04:06:02PM +, Robert Li (baoli) wrote:
Hi Sean,
I just added the ipv6-prefix-delegation BP that can
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
questions); Irena Berezovsky; Robert Li (baoli); Brian Bowen
(brbowen)
Subject: Re: [openstack-dev] [nova][neutron] PCI pass-through SRIOV
binding of ports
On 02/04/2014 04:35 PM, Sandhya Dasu (sadasu) wrote:
Hi,
I have a couple of questions for ML2 experts regarding support
of
SR-IOV ports
Hi Xuhan,
Thank you for your summary. see comments inline.
--Robert
On 2/27/14 12:49 AM, Xuhan Peng
pengxu...@gmail.commailto: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
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
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
Hi Folks,
I put the recap in here:2 Feb. 12th, 2014
Recaphttps://wiki.openstack.org/wiki/Meetings/Passthrough#Feb._12th.2C_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.
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,
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
: Robert Li (baoli) [mailto:ba...@cisco.com]
Sent: Thursday, January 30, 2014 10:45 PM
To: Robert Kukura; Sandhya Dasu (sadasu); Irena Berezovsky; OpenStack
Development Mailing List (not for usage questions); Brian Bowen (brbowen)
Subject: [openstack-dev] [nova][neutron] PCI pass-through SRIOV on Jan
...@cack.org.ukmailto:ijw.ubu...@cack.org.uk wrote:
My proposals:
On 29 January 2014 16:43, Robert Li (baoli)
ba...@cisco.commailto:ba...@cisco.com wrote:
1. pci-flavor-attrs is configured through configuration files and will be
available on both the controller node and the compute nodes. Can the cloud
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
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
ire...@mellanox.commailto:ire...@mellanox.com wrote:
Will attend
From: Robert Li (baoli) [mailto:ba
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) ba...@cisco.com wrote:
Hi,
I added a few comments in this wiki that Yongli came up with:
https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support
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]
Sent
the existing examples.
thanks,
Robert
On 1/29/14 12:17 PM, Irena Berezovsky
ire...@mellanox.commailto: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: Wednesday, January 29, 2014 6:03 PM
To: Irena
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 rkuk...@redhat.com wrote:
On 01/29/2014 09:46 AM, Robert Li (baoli) wrote:
Another issue that came up
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 rkuk...@redhat.com wrote:
On 01/29/2014 05:44 PM, Robert Li (baoli) wrote:
Hi Bob,
that's a good find. profileid
, 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 Mailing
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
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
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)
ba...@cisco.commailto:ba...@cisco.com wrote:
Hi Folks,
Based on Thursday's discussion and a chat
Hi Irena,
I agree on your first comment.
see inline as well.
thanks,
Robert
On 1/27/14 10:54 AM, Irena Berezovsky
ire...@mellanox.commailto:ire...@mellanox.com wrote:
Hi Robert, all,
My comments inline
Regards,
Irena
From: Robert Li (baoli) [mailto:ba...@cisco.com]
Sent: Monday, January 27
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
ire...@mellanox.commailto:ire...@mellanox.com wrote:
Hi Robert,
Please see inline
From: Robert Li (baoli
. 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)
ba...@cisco.commailto:ba...@cisco.com wrote:
Sounds great! Let's do it on Thursday.
--Robert
On 1/22/14 12:46 AM, Irena Berezovsky
ire...@mellanox.commailto:ire
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 Mailing
, thanks for your long reply. Personally I'd prefer option 2/3 as
it keep Nova the only entity for PCI management.
Glad you are ok with Ian's proposal and we have solution to resolve the
libvirt network scenario in that framework.
Thanks
--jyh
-Original Message-
From: Robert Li (baoli
flavor, rather than
introducing a new flavor.
Thanks,
Robert
On 1/17/14 7:03 PM, yunhong jiang yunhong.ji...@linux.intel.com wrote:
On Fri, 2014-01-17 at 22:30 +, Robert Li (baoli) wrote:
Yunhong,
I'm hoping that these comments can be directly addressed:
a practical
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
we had a conversation
earlier:
On 15 January 2014 23:47, Robert Li (baoli) ba...@cisco.com wrote:
--- do we agree that BDF address (or device id, whatever
you call it), and node id shouldn't be used as attributes in
defining a PCI flavor?
Note that the current
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 questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through
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
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'] .
1 - 100 of 112 matches
Mail list logo