Re: [openstack-dev] [Openstack-operators] PCI pass through settings on a flavor without aliases on the API nodes

2017-10-18 Thread Yaguang Tang
Hi Van,

You can try to create a pci-passthrough port with PCI info, then create vm
using that port  without any alias.

On Wed, Oct 18, 2017 at 11:27 PM, Eric Fried  wrote:

> Robert-
>
> No.
>
> Some day, once generic device management is baked, there will be.
> Depending how your favorite virt driver decides to model things, one
> could envision a flavor with extra specs like:
>
> resources:SRIOV_NET_PF:1
> trait:CUSTOM_PCI_VENDORID_8086=required
> trait:CUSTOM_PCI_PRODUCTID_154D=required
>
> In the meantime, it's especially useful to get this kind of
> feedback
> from ops so we can ensure we're meeting the right requirements as we
> design things.  Please reach out if you want to discuss further.
>
> Thanks,
> Eric Fried (efried)
>
> On 10/18/2017 09:56 AM, Van Leeuwen, Robert wrote:
> > Hi,
> >
> >
> >
> > Does anyone know if it is possible to set PCI pass through on a flavor
> > without also needing to set the alias on the nova API nodes as mentioned
> > here:
> > https://docs.openstack.org/nova/pike/admin/pci-passthrough.html
> >
> >
> >
> > E.G you need to set in nova.conf:
> >
> > [pci]
> >
> > alias = { "vendor_id":"8086", "product_id":"154d ",
> > "device_type":"type-PF", "name":"a1" }
> >
> >
> >
> > Then you can set the flavor:
> >
> > openstack flavor set m1.large --property "pci_passthrough:alias"="a1:2"
> >
> >
> >
> >
> >
> > E.g. I would be fine with just setting the PCI vendor/product on the
> > flavor instead of also needing to set this at the api node
> >
> > So something like:
> >
> > openstack flavor set m1.large –property “pci_passthrough:vendor”=”8086”
> >  “pci_passthrough:device”=”154d:1”
> >
> >
> >
> > Thx,
> >
> > Robert  van Leeuwen
> >
> >
> >
> > ___
> > OpenStack-operators mailing list
> > openstack-operat...@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> >
>
> __
> 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
>



-- 
Tang Yaguang
__
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] [Openstack-operators] PCI pass through settings on a flavor without aliases on the API nodes

2017-10-18 Thread Eric Fried
Robert-

No.

Some day, once generic device management is baked, there will be.
Depending how your favorite virt driver decides to model things, one
could envision a flavor with extra specs like:

resources:SRIOV_NET_PF:1
trait:CUSTOM_PCI_VENDORID_8086=required
trait:CUSTOM_PCI_PRODUCTID_154D=required

In the meantime, it's especially useful to get this kind of feedback
from ops so we can ensure we're meeting the right requirements as we
design things.  Please reach out if you want to discuss further.

Thanks,
Eric Fried (efried)

On 10/18/2017 09:56 AM, Van Leeuwen, Robert wrote:
> Hi,
> 
>  
> 
> Does anyone know if it is possible to set PCI pass through on a flavor
> without also needing to set the alias on the nova API nodes as mentioned
> here:
> https://docs.openstack.org/nova/pike/admin/pci-passthrough.html
> 
>  
> 
> E.G you need to set in nova.conf:
> 
> [pci]
> 
> alias = { "vendor_id":"8086", "product_id":"154d ",
> "device_type":"type-PF", "name":"a1" }
> 
>  
> 
> Then you can set the flavor:
> 
> openstack flavor set m1.large --property "pci_passthrough:alias"="a1:2"
> 
>  
> 
>  
> 
> E.g. I would be fine with just setting the PCI vendor/product on the
> flavor instead of also needing to set this at the api node
> 
> So something like:
> 
> openstack flavor set m1.large –property “pci_passthrough:vendor”=”8086”
>  “pci_passthrough:device”=”154d:1”
> 
>  
> 
> Thx,
> 
> Robert  van Leeuwen
> 
> 
> 
> ___
> OpenStack-operators mailing list
> openstack-operat...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> 

__
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