Sphinx 1.6.x gained a cross-reference check warning that caused
the build to fail in "tox -e docs" environment. Removing underscores
from the citation reference identifier ensures that the cross references
are properly detected. Similarly missing references to footnotes are
now a warning (which is upgraded to an error in the docs tox
environment) so adjust references where it makes sense and is needed.
Closes-Bug: #1695127
Change-Id: I7e55dcf910e0ba6dd85b565db8cb1ecbdd39634a
The 'hw:numa_mempolicy' parameter was never implemented and will likely
never be, however, it's located in the 'implemented' folder suggesting
otherwise. Seeing as specs are as much a reference as anything, this
invalid information should not be retained. Correct this, taking the
opportunity to fix some other typo, line wrapping and general
formatting.
Change-Id: I4aca0073f1fa26ff0c3a34407370f6ba6d916879
s/prefered/preferred for hw_numa_mempolicy's setting.
Change-Id: Id82b919c27c0ebf166b6ab7ee6b64e968a8b991f
Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
The NUMA work did not integrate with the extensible resource
tracker since it was not suitable at the time.
The memory property values should be recorded in MB rather
than in GB.
Change-Id: I76c56e5e0a9eed7faf44d1fe376b6d15247c2c92
This spec outlines the process for upgrading from nova-baremetal to
Ironic, and descibes the changes in Nova which will be required prior
to deleting the nova-baremetal code from the Nova tree.
blueprint deprecate-baremetal-driver
Change-Id: I2a9e6ca2f19d5b0f80954cdec45a9eca17960fa1
Due to the 80 character line limit the original blueprint URL, was
wrapped and didn't render properly.
Change-Id: I7338e20decea674cebec2ccdf38ba6cc27bf9631
As discussed at our nova meetings, reorganize the juno specs into
three directories:
- proposed: things proposed which weren't approved
- approved: things we approved but didn't implement
- implemented: things approved and implemented
The first I suspect is the most controversial. I've done this
because I worry about the case where a future developer wants to
pick up something dropped by a previous developer, but has trouble
finding previous proposed specifications on the topic. Note that
the actual proposed specs for Juno are adding in a later commit.
Change-Id: Idcf55ca37a83d7098dcb7c2971240c4e8fd23dc8
Powering off a VM without giving the Guest Operating system a chance
to perform a controlled shutdown can lead to data corruption.
The proposed changes will make the default behavior for stop, rescue, resize,
and shelve to give the GuestOS a chance to perform a controlled shutdown
before the VM is powered off.
The change will encapsulate the complexity of signaling to and waiting for
the GuestOS in the hypervisor, and allow image owners the ability to tune
the associated timing via image metadata to take account of GuestOSs that
require an extended period to shutdown (such as Windows).
Users will be able to specify the shutdown behavior on a per operation basis
via a new shutdown_type parameter where, in keeping with the current reboot
operation, a "soft" shutdown will give the GuestOS a chance to perform a
clean shutdown, and a "hard" shutdown will cause an immediate power off. The
default behavior will be a "soft" shutdown.
https://blueprints.launchpad.net/nova/+spec/user-defined-shutdown
Change-Id: Ie2c13c9173566c6d545fcaf6a3ab88df636a7d33
Currently RBD-backed ephemeral disks are created by downloading an image from
Glance to a local file, then uploading that file into RBD. Even if the file is
cached, uploading may take a long time, since 'rbd import' is synchronous and
slow. If the image is already stored in RBD by Glance, there's no need for any
local copies - it can be cloned to a new image for a new disk without copying
the data at all.
blueprint rbd-clone-image-handler
Change-Id: Ie71699e845e14251233efc993a690713f1118c31
Add a new nova scheduler weighter, sort the filter
hosts according to host io ops number, aims to
booting instances on light workload hosts.
blueprint io-ops-weight
Change-Id: I09dbe0ffc71230d75538572daf30890f3d4e746b
This feature aims to improve the libvirt driver so that it is
able to strictly pin guest vCPUS to host pCPUs. This provides
the concept of "dedicated CPU" guest instances.
Change-Id: I29e2f3cbf45ae36c6c6b7a089d46cc6710bfbbe0
The libvirt driver.py class is growing ever larger and more
complicated. There are circular dependencies between this
class and other libvirt classes. This work aims to split
some of the functionality out into new classes
Change-Id: I50ec5334b2cd1f6bb1f16f223ac065b411a847f5
This blueprint aims to add a max_length validation to the
`nova.objects.fields.String` class.
Change-Id: I1ed8f0804996af86c7eadc83914d81df1ab4a88d
Blueprint: string-field-max-length
Expose an interactive web-based serial console to openstack VMs through
a websocket proxy.
Implements: blueprint serial-ports
Change-Id: I3bfe44bc4cfc8987e3c853eeed795d1503df79c5
Allow Nova to create multiple interfaces on a single network from one VM.
bp multiple-if-1-net
NFVImpact
Change-Id: I986c84e355dec1c78389661ff480f4de93869447
scheduler prep_resize() is only necessary when rescheduling a cold
migration, but all of this can be done in conductor.
Implements: blueprint move-prep-resize-to-conductor
Change-Id: I4143aa011e18edcc609e1095f0054c3a8670bc86
jiasirui