Why Gemfury?
Push, build, and install
RubyGems
npm packages
Python packages
Maven artifacts
PHP packages
Go Modules
Debian packages
RPM packages
NuGet packages
triliodata-3-4 / contego deb
Repository URL to install this package:
|
Version:
3.4.52 ▾
|
ó
±EYc @ s¸ d Z d d l Z d d l Z d d l m Z d d l Z d d l Z d d l m Z d d l m
Z
d d l m Z
d d l m Z d d l m Z d d l m Z d
Z d Z i e j j e
j 6Z e j j Z e j j e j j e j j g Z d g Z i d
d 6e d 6i i d d 6d d 6d d 6d 6i d d 6e d 6d 6i d d 6e j! d 6d 6i d d 6e j! d 6d 6i d d 6e d 6d 6d 6d g d 6Z" d Z# d Z$ d Z% d S(! sG Example of a PCI alias::
| pci_alias = '{
| "name": "QuicAssist",
| "product_id": "0443",
| "vendor_id": "8086",
| "device_type": "type-PCI",
| }'
Aliases with the same name and the same device_type are OR operation::
| pci_alias = '{
| "name": "QuicAssist",
| "product_id": "0442",
| "vendor_id": "8086",
| "device_type": "type-PCI",
| }'
These 2 aliases define a device request meaning: vendor_id is "8086" and
product id is "0442" or "0443".
iÿÿÿÿN( t jsonutils( t exception( t _( t model( t objects( t fields( t utilst physical_networkt dev_typet pcit objectt typet additionalPropertiest stringi t minLengthi t maxLengtht namet enumt capability_typet patternt
product_idt vendor_idt device_typet
propertiest requiredc C s6 t j } i } yÜ xÕ | D]Í } t j | } t j | t | j d j } | j d d } | rx | | d <n | | k r | g | | <q | | d d | d k rÄ | | j
| q t d | } t j
d | q WWnD t j
k
r n. t k
r1} t j
d t j | n X| S( s4 Parse and validate PCI aliases from the nova config.R R R i s# Device type mismatch for alias '%s't reasonN( t CONFt pci_aliasR t loadst
jsonschemat validatet
_ALIAS_SCHEMAt popt stript Nonet appendR R t PciInvalidAliast Exceptiont sixt text_type( t jaliasest aliasest jsonspecst specR R R t e( ( sE /home/tvault/.virtenv/lib/python2.7/site-packages/nova/pci/request.pyt _get_alias_from_configb s*
c C sº t } g } x¤ g | j d D] } | j d ^ q" D]w \ } } | j } | | k rt t j d | q; t j d t | d t j | | d | } | j
| q; W| S( s> Generate complete pci requests from pci aliases in extra_spec.t ,t :t aliast countR+ t
alias_name( R- t splitR! R t PciRequestAliasNotDefinedR t InstancePCIRequestt intt copyt deepcopyR# ( t
alias_spect pci_aliasest pci_requestsR+ R R1 t request( ( sE /home/tvault/.virtenv/lib/python2.7/site-packages/nova/pci/request.pyt _translate_alias_to_requests s 8 c C sI g } d | k r9 d | d k r9 t | d d } n t j d | S( s Get flavor's pci request.
The pci_passthrough:alias scope in flavor extra_specs
describes the flavor's pci requests, the key is
'pci_passthrough:alias' and the value has format
'alias_name_x:count, alias_name_y:count, ... '. The alias_name is
defined in 'pci_alias' configurations.
The flavor's requirement is translated into pci requests list,
each entry in the list is a dictionary. The dictionary has
three keys. The 'specs' gives the pci device properties
requirement, the 'count' gives the number of devices, and the
optional 'alias_name' is the corresponding alias definition name.
Example:
Assume alias configuration is::
| {'vendor_id':'8086',
| 'device_id':'1502',
| 'name':'alias_1'}
The flavor extra specs includes: 'pci_passthrough:alias': 'alias_1:2'.
The returned pci_requests are::
| pci_requests = [{'count':2,
| 'specs': [{'vendor_id':'8086',
| 'device_id':'1502'}],
| 'alias_name': 'alias_1'}]
:param flavor: the flavor to be checked
:returns: a list of pci requests
t extra_specss pci_passthrough:aliast requests( R= R t InstancePCIRequests( t flavorR; ( ( sE /home/tvault/.virtenv/lib/python2.7/site-packages/nova/pci/request.pyt get_pci_requests_from_flavor s " (& t __doc__R7 R t oslo_serializationR R& t nova.conft novaR t nova.i18nR t nova.networkR t
network_modelR t nova.objectsR t
obj_fieldst nova.pciR t PCI_NET_TAGt PCI_DEVICE_TYPE_TAGt
PciDeviceTypet SRIOV_PFt VNIC_TYPE_DIRECT_PHYSICALt DEVICE_TYPE_FOR_VNIC_TYPEt confR t STANDARDt SRIOV_VFt _ALIAS_DEV_TYPEt _ALIAS_CAP_TYPEt Falset PCI_VENDOR_PATTERNR R- R= RB ( ( ( sE /home/tvault/.virtenv/lib/python2.7/site-packages/nova/pci/request.pyt <module>% sX