PCI passthrough: extra info/flavor enhancement
PCI devices has not only PCI standard property like BDF, vendor_id etc, it also has some extra information which may be application specific. For example, attached network switch for NIC, or resolution for GPU etc.
Blueprint information
Related branches
Sprints
Whiteboard
I am ducking out of the review for this if possible, there is more agreement now I think, but I have spend too many hours trying to review this. Parting thoughts:
* PCI flavor seems like a good user facing concept
* NICs having extra info the suggests a PCI flavor makes sense too
* the host details should store the mapping of what PCI flavors are available
* main worry for me is how to persist the PCI flavor info, I recon host-aggregates would work - but need to see what extra db tables would be better
-- johnthetubagy
johnthetubaguy,
all requement comments is address, bp also merged. -- yongli He
use case updated to
https:/
--yonglihe
It is hard to review this without seeing the API implemented. We generally don't like to accept code that is not used or exposed, and each checkin should leave nova working. I am not sure I quite understand the split between this blueprint and the blueprint below. vote we combine them.
--johnthetubaguy
discuss about use caseļ¼
https:/
This is targeted for icehouse but all the reviews below are extremely preliminary and all have been auto-abandoned. Should this still be targeted for I2? I'm not sure I'd approve this for I2 unless things are farther along than they appear to be. --dansmith
hi, dansmith
all because some design consideration is not resloved yet, but we are work hard on it. --yonglihe
Gerrit topic: https:/
Addressed by: https:/
PCI base group support
Addressed by: https:/
PCI whitelist support group with by PCI address
Addressed by: https:/
PCI reqeust support group
Gerrit topic: https:/
Addressed by: https:/
PCI stats group on demand
Addressed by: https:/
PCI allocation marking
Addressed by: https:/
Fix init of pci_stats in resource tracker
Addressed by: https:/
PCI config database support
deferred from icehouse-3 to "next": http://
Addressed by: https:/
pci request mark interface
Addressed by: https:/
Enhance PCI alias to support pci flavor attr
Realizing that I am going to seem like a broken record, but we need a plan for how this is going to be tested. e.g. how much can be done in tempest, how much reliance is there on third party testing for adequate coverage etc.. - beagles
Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy
Gerrit topic: https:/
Addressed by: https:/
proposed blueprint for PCI extra information support
Gerrit topic: https:/
