To help adding new notification to nova we shall have a guideline
what should and what should not be in the notification payload.
Change-Id: Ic85d304974bbfa7e02999ec3d6c9bba1d1aed3c8
Add a paragraph which clarifies that a specless blueprint needs to
be approved and the normal process for doing so, with links to
additional information.
Change-Id: I1d4fc40a2e5acb8b63f90e00dc19ee5a65fbe870
This is the initial set of docs for the placement API
service introduced in the Newton release.
We still have to flesh out the API reference in detail
but this gets us started.
The deployment steps are taken from how devstack does
this today.
Change-Id: Ic2436d92a7cefaeb1ae67ed878da968444f2f18d
Update the documents, making the following changes:
* Reference Fedora 24 instead of the outdated Fedora 21
* Don't reference the removed 'rejoin-stack' script
* Let devstack do as much work for us as possible (NUMATopologyFilter)
* Don't overcomplicate anything (installing emacs, using non-standard
devstack install dir)
* Use '$' prefix for non-root commands
* Update XML with latest examples
* Use the 'openstack' client, rather than the 'nova' client
* Random formatting fixes
...and, finally, stop hating on poor, innocent vi.
Change-Id: Idc89a5c0617ccf7044e1cfc2b5d7f5ff4004b5bf
There are two changes here:
1. The serial_console config option group help text is
updated to point out that hyper-v also supports serial
console access. This is based on virt drivers that
implement the 'get_serial_console' method.
2. The hypervisor feature matrix is updated to point out
that the vmware driver does not support getting serial
console output. This is based on virt drivers that
implement the 'get_console_output' method.
Closes-Bug: #1632135
Change-Id: Ibf7f865e2b768e5ea3d7a7ec7cbf77bd8997c50f
Add a section in "core-review" to document how experimental pipeline would
be used by Nova developers in order to consume the resources at the
right time.
Change-Id: I5df377032c2fcec18cdf71af2568e028373bcced
Modify rolling upgrade steps from exisitng nova upgrades
documentation. Also, add pre-requisites required for the
zero downtime upgrade under newly created "Plan your upgrade"
section.
Change-Id: I4e884ac051614d25258734c35208b3abfe5fd3a4
Co-Authored-By: Sivasathurappan Radhakrishnan <siva.radhakrishnan@intel.com>
This was deprecated and to set to be removed in Ocata. It was only
intended for testing purposes and not for production use. Individual
binaries will be used instead.
Change-Id: I260962ec7c4167b07e9480a04454a9cb5666f8ed
At the newton midcycle we talked about the proposed
memory bandwidth monitor plugin and decided that we
really just don't want nova in the business of metrics
gathering, and are moving to deprecate that functionality.
There are several specs open related to adding more
metrics monitors and/or exposing existing ones, so this
codifies the policy on nova as metrics gatherer.
Change-Id: Ie47e91776bc36a22fd48d3673c69c842509489a1
The out of tree support section of the nova dev policy
document was pretty old and basically said hooks and
extension points are buyer beware, but doesn't mention
anything about why we don't want them (interoperability)
and the efforts the last few releases to actively
deprecate and remove hooks/extension points/classloading.
This change adds some more wording to that effect to
the doc.
Change-Id: Iaa1cf3ef7ac6e8e1d75f94e17aaba1058474acca
This updates the docs to point at our flashy new(ish)
api-ref compute REST API docs instead of those gross
crusty old inaccurate ones.
Change-Id: Ib5e157f3ff7a215be4cbf7e8744b3507f3b4b106
The auto generated class documentation link was 404 in the notification
devref as that documenation is not generated automatically any more.
This patch modifies the notification devref to include the interesting
part of the class documentation inline.
Change-Id: I7cbea16fc9682fa3c00eac16a51c4ed8588ba45c
Move all scheduler options into their one of two groups. Many of the
options are simply renamed to remove their 'scheduler_' prefix, with
some exceptions:
* scheduler_default_filters -> enabled_filters
* scheduler_baremetal_default_filters -> baremetal_enabled_filters
* scheduler_driver_task_period -> periodic_task_interval
* scheduler_tracks_instance_changes -> track_instance_changes
Change-Id: I3f48e52815e80c99612bcd10cb53331a8c995fc3
Co-Authored-By: Stephen Finucane <sfinucan@redhat.com>
Implements: blueprint centralize-config-options-ocata
Libvirt has "domainSetUserPassword" callback and virtuozzo driver
has an implementation for it. So in this patch we allow to use this
functionality for virtuozzo hypervisor.
Change-Id: Ia398afadfd9fd9544c5d843338ab25c0930d9f74
Implements: blueprint virtuozzo-instance-admin-password
Right on now the Filter Scheduler page it is difficult to find where the
section is on configuring and writing your own. The page is very long.
So this adds some section headers. In addition a note is added to
clarify that when you write your own filter "all_filters" doesn't
include "write your own", both available and default settings need to be
changed.
Change-Id: I99878d3b4dc839ff87bc581e61c85e4ae2c66b2c
This patch updates link that the patch [1] added to general purpose
feature matrix
[1] https://review.openstack.org/#/c/344483/
Implements: blueprint feature-classification
Change-Id: I0f5abaf68adcbb49e013c2778cce692c6d8a7327
Copy edit the feature classification document
to improve language and structure.
blueprint feature-classification
Change-Id: I0ca1f8270439109c3b525b2a22ba3f035f0426f0
Added details for:
1. Server create and delete
2. Server snapshot
3. Server power operations
4. Server rebuild and resize
blueprint feature-classification
Change-Id: I2f10b797432ca441bb067e026c6c31419144c110