8e5d6767bb
Track compute node inventory for the new MEM_ENCRYPTION_CONTEXT resource class (added in os-resource-classes 0.4.0) which represents the number of guests a compute node can host concurrently with memory encrypted at the hardware level. This serves as a "master switch" for enabling SEV functionality, since all the code which takes advantage of the presence of this inventory in order to boot SEV-enabled guests is already in place, but none of it gets used until the inventory is non-zero. A discrete inventory is required because on AMD SEV-capable hardware, the memory controller has a fixed number of slots for holding encryption keys, one per guest. Typical early hardware only has 15 slots, thereby limiting the number of SEV guests which can be run concurrently to 15. nova needs to track how many slots are available and used in order to avoid attempting to exceed that limit in the hardware. Work is in progress to allow QEMU and libvirt to expose the number of slots available on SEV hardware; however until this is finished and released, it will not be possible for nova to programatically detect the correct value with which to populate the MEM_ENCRYPTION_CONTEXT inventory. So as a stop-gap, populate the inventory using the value manually provided by the cloud operator in a new configuration option CONF.libvirt.num_memory_encrypted_guests. Since this commit effectively enables SEV, also add all the relevant documentation as planned in the AMD SEV spec[0]: - Add operation.boot-encrypted-vm to the KVM hypervisor feature matrix. - Update the KVM section of the Configuration Guide. - Update the flavors section of the User Guide. - Add a release note. [0] http://specs.openstack.org/openstack/nova-specs/specs/train/approved/amd-sev-libvirt-support.html#documentation-impact blueprint: amd-sev-libvirt-support Change-Id: I659cb77f12a38a4d2fb118530ebb9de88d2ed30d |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| playbooks | ||
| releasenotes | ||
| roles/run-post-test-hook | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| babel.cfg | ||
| bindep.txt | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| lower-constraints.txt | ||
| MAINTAINERS | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: