3b9116739d
Since the AMD SEV spec was approved for Stein, it was subsequently realised that a trait would not be sufficient for tracking SEV-capable compute hosts. A resource class is also needed to track the inventory of "slots" available on these hosts, since the number of slots limits how many guests with encrypted memory can run concurrently. Therefore the design pivoted somewhat, and now trait:HW_CPU_AMD_SEV=required will not be the correct way to request SEV functionality: https://specs.openstack.org/openstack/nova-specs/specs/train/approved/amd-sev-libvirt-support.html For reference, the previous spec is here: https://specs.openstack.org/openstack/nova-specs/specs/stein/approved/amd-sev-libvirt-support.html Another lesson learnt from the Stein cycle was that it is not safe to assume that the work targeted for one cycle will actually land in that cycle, therefore it's safer for documentation of an in-progress feature to be transparent that it's in progress and not yet usable. Change-Id: I6b652c20ba4f5ec775829a45939d708066dc3011 blueprint: amd-sev-libvirt-support |
||
|---|---|---|
| .. | ||
| index.rst | ||