Attaching virtual GPU devices to guests in nova - libvirt reshaping
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Sylvain Bauza | ||
Stein |
Fix Committed
|
Medium
|
melanie witt |
Bug Description
- [x] This is a doc addition request.
This is coming up from discussion about what to document in the release notes for the libvirt VGPU reshaper work that happened in Stein:
https:/
Specifically about the upgrade impact of VGPU inventory and allocations moving from the root compute node resource provider to a child resource provider.
The release notes and docs for VGPUs are not very clear about this change (the docs don't actually mention anything about it). So this bug is for tracking that gap.
I think it would be good to at the very least mention that starting in the Stein release, VGPU inventory and allocations are tracked on a child resource provider of the root compute node resource provider. And we could illustrate this using examples from openstack CLIs:
https:/
For example, list resource providers where there are two, one for the root compute node resource provider and one for a VGPU provider. Then list inventories on each and see there is VCPU/MEMORY_
-------
Release: 18.1.0.dev1645 on 2019-02-27 13:28:37
SHA: 592658aafcb5de8
Source: https:/
URL: https:/
tags: | added: stein-rc-potential |
Changed in nova: | |
assignee: | nobody → Sylvain Bauza (sylvain-bauza) |
Fix proposed to branch: master /review. openstack. org/647519
Review: https:/