openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
55,263 Commits 10 Branches 82 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
LuyaoZhong c39ad2383c libvirt: Support VM creation with vpmems and vpmems cleanup 
Add the vpmems config into guest config xml according to
resources info in the instance object, then users can build
a VM with vpmems. Also this patch add the support for
data cleanup on the backend device of the vpmems.

note:
We modify the root <domain> element generated for libvirt to
include <maxMemory> elements when memory device is used.[1]

Requiring vpmems implies a NUMA topology because libvirt won't let us
use vpmem without NUMA.[2]

[1]https://github.com/libvirt/libvirt/blob/master/src/qemu/qemu_domain.c#L11593-L11599
[2]https://github.com/libvirt/libvirt/blob/master/src/qemu/qemu_domain.c#L11604-L11615

Change-Id: I725deb0312c930087c9e60115abe68b4e06e6804
Partially-Implements: blueprint virtual-persistent-memory
Co-Authored-By: He Jie Xu <hejie.xu@intel.com>
 		2019-09-13 08:50:35 +00:00
api-guide/source Remove 'hw:cpu_policy', 'hw:mem_page_size' extra specs from API samples 2019-08-27 17:00:46 +01:00
api-ref/source api-ref: fix server topology "host_numa_node" field param name 2019-09-06 17:31:42 -04:00
devstack Convert nova-lvm job to zuul v3 2019-08-02 13:08:50 -04:00
doc Add nova-status to man-pages list 2019-09-12 15:05:41 +02:00
etc/nova Cleanup no longer required filters and add a release note. 2019-02-27 20:45:16 +00:00
gate Add cold migrate and resize to nova-grenade-multinode 2019-08-30 15:35:46 -04:00
nova libvirt: Support VM creation with vpmems and vpmems cleanup 2019-09-13 08:50:35 +00:00
playbooks Merge "Convert nova-lvm job to zuul v3" 2019-09-04 20:08:05 +00:00
releasenotes Cleanup reno live-migration-with-PCI-device 2019-09-12 18:48:53 -04:00
roles/run-post-test-hook Convert nova-next to a zuul v3 job 2019-07-23 11:32:35 -04:00
tools Replace git.openstack.org URLs with opendev.org URLs 2019-04-24 13:59:57 +08:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore Delete the placement code 2019-04-28 20:06:15 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:45:52 +00:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml Merge "Modernize nova-lvm job" 2019-09-04 20:43:02 +00:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Remove descriptions of nonexistent hacking rules 2019-08-26 14:55:51 +09:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Fix broken URLs 2017-09-07 15:42:31 +02:00
README.rst Update api-ref location 2019-07-22 19:17:28 +02:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt bindep: Remove dead markers 2019-07-18 11:27:13 +01:00
lower-constraints.txt Bump min for oslo.service & .privsep to fix SIGHUP 2019-09-05 18:16:43 -05:00
requirements.txt Bump min for oslo.service & .privsep to fix SIGHUP 2019-09-05 18:16:43 -05:00
setup.cfg Remove nova-consoleauth 2019-07-05 15:04:47 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Tests: autospecs all the mock.patch usages 2019-08-19 09:43:10 -05:00
tox.ini Update api-ref location 2019-07-22 19:17:28 +02:00

README.rst

Team and repository tags

image

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: