Commit a507d42cf5 makes the
doc builds fail on warnings, so people are probably going
to be running 'tox -e docs' more often. To run that you
need the graphviz package from the distro, so add it to
the list of packages needed when setting up a development
environment.
Change-Id: I47ffe63fddfbbd73c3fc698490ad07235caaf459
Closes-Bug: #1356983
By setting this pbr option in setup.cfg, the doc build will fail in case
of any warnings or errors occur during the build process.
Closes-Bug: #1351350
Change-Id: Id4858062d2aaa4c2fe5b597e40e4e8947f544a4d
There is currently a misconception about how a patch gets merged:
Author proposes a patch, review team reviews it. Us, and Them. Instead
it should be a 'We.'
If the review bandwidth doesn't grow at the same rate as the patch
proposal rate then we end up with a massive backlog where people are
pinging cores for reviews.
Record a recommended policy of asking patch authors to offset the review
resources spent on their patch by reviewing other patches.
Change-Id: I50653f8ea58240fa664519f544ce16b2adf39006
Adds instructions on how to enable the ubuntu cloud-archive
and update to the latest libvirt-dev from the icehouse repo.
This is needed to run unit tests in Juno if you're still on
ubuntu precise.
Change-Id: I8c93afdd72256b2bdc487e1413bdd570a6ea59e8
Commit 8f505b8526 added
a test requirement on libvirt-python which requires
libvirt-dev(el) being installed, so update the docs
to add that package for the distro.
Change-Id: I7169d3c78a6babe6e20c0dc35874167d0bfee922
This previously just linked to api/autoindex which was removed in
I6c93f9aae1994961fdca690742398a0d540d541f (in 2011).
Change-Id: Iba86a5b84743fe6d65b797a2e9237d037c2bf1a8
devref already contains a list of all modules, so no need to explicitly
include files that just contain lists of modules under the section 'Module
Reference'. Most of the deleted files are very outdated and refer to
non-existent modules anyway.
Leave services for now as it contains some content
that should be preserved. A later patch will clean those files up.
Change-Id: I5dce1b523f3648667fcde49ee51206ae9ccfdec8
Now that we have an official devstack vagrant repo, lets point to that
instead of my own half maintained repo.
Change-Id: I944265d18f6e796608576ea71a7983aed0ece542
oslo.i18n provides the i18n functions that were provided by
oslo-incubator's gettextutils module. Some tests that were
using internal details of the library were removed.
Change-Id: I44cfd5552e0dd86af21073419d31622f5fdb28e0
This just removes the duplicate python-pip from the list
of packages to install via yum when setting up a development
environment on Fedora/RHEL.
Change-Id: I3bd0aa7230c29a97845d744f6522bd2ffd1bf130
Although many reviewers know that documentation isn't the source of
truth for API behavior, we have never written this policy down before.
Change-Id: Ibe7b355947200b668324028972c121e5357a0470
We now have a whole bunch of unwritten development policies about what is
allowed and what isn't, it is time to write some of them down.
A subsequent patch will add the first policy.
Change-Id: I91c2eb2b937f38b3b3c5380ac93fa0ce0f5e4156
Right now it is possible to pause, suspend and stop a VM in state RESCUED,
so after the state is changed, it's not possible to trigger unrescue anymore
since the original state is lost.
This patch remove vm_states.RESCUED as valid state from stop,
pause and suspend actions.
The vm_states devref is also updated to reflect this change including the
current reboot flow.( vm_states.RESCUED cannot be rebooted as per
today code)
DocImpact
Closes-Bug: #1319182
Co-Authored-By: Cyril Roelandt <cyril.roelandt@enovance.com>
Change-Id: I531dea5a5499bf93c24bea37850d562134dee281
We already have a document on how to run unit tests, so
development.environment should just point to that document instead of
trying to summarize it. Keeping this information in one less places
makes it easier to make sure the page is up to date (which
development.environment is not -- no mention of tox).
Change-Id: I9aecf439b6145b035b3457559ddb187058f5057b
Don't keep a copy of the run_tests.sh flag list here since it
inevitably will get out of sync with the real list.
No need to go into detail on how unit testing is set up, since we already have a wiki
on how to run tests that applies for all OpenStack projects. Keep
section with tox examples since that is the most commonly used command.
Change-Id: Ia8eb059be164d9df3edfd69aedcebfd028da45ff
Related-Bug: 1219040
The nova client already has the following flavor commands:
flavor-access-add Add flavor access for the given tenant.
flavor-access-list Print access information about the given flavor.
flavor-access-remove Remove flavor access for the given tenant.
flavor-create Create a new flavor
flavor-delete Delete a specific flavor
flavor-key Set or unset extra_spec for a flavor.
flavor-list Print a list of available 'flavors' (sizes of
flavor-show Show details about the given flavor.
This covers what nova-manage flavor was providing so let's deprecate the
legacy nova-manage subcommand and mark it for removal in the K release.
There is not a bug or blueprint for this. The flavor subcommand is
completely duplicated in nova client. It is accessing the database
directly and we want to move to using flavor objects which would go
through conductor. So this could be considered part of the objects
conversion for flavors.
For some other commands like service, db and host it makes sense to
leave those so you can access the database before the api service is
running, but that's not the case for flavors.
UpgradeImpact: nova-manage flavor command is deprecated, use nova client
Change-Id: I8709bc9af4e490142e44c6dc61fd0aaa3a392b68
As of commit 07ee9639 three years ago nova-manage.conf is no longer
used, so let's clean up the man page.
Closes-Bug: #1304580
Change-Id: Ie061733da4bd0337f510e17b6dd7ca5bae14b7de
Server group scheduler filters were added to the default set of
scheduler filters. Update the docs to reflect the updated defaults.
Change-Id: I614cf83e419c93038fc4ed7287ec743cedb4860e
Related-bug: #1303983
ServerGroupAffinityFilter was used instead of
ServerGroupAntiAffinityFilter in the filter description.
Change-Id: I16721db5a7dcf90e72047dd5ca5a4f55088c147d
The deprecated group filters do not work if both are enabled at the
same time. Add this in a note in the docs on the different scheduler
filters.
DocImpact
Related-bug: #1296913
Change-Id: Ic0e1b8b59c8a462e193dffb3b0f873d8aa35aa3c
Prior to Icehouse, there was a different type of handling of the
'group' scheduler hint that got lost in the completion of the server
groups API. This patch completes the code necessary to provide
backwards compatibility with the old behavior.
Previously, the policy for groups was simply based on what scheduler
filters you had enabled. You could have either the affinity or
anti-affinity filter enabled and that would be applied to all groups.
These filters now act on groups with a policy type of 'legacy'.
New filters have been added that can be enabled simultaneously and act
based on the policy set on the group via the server group API.
DocImpact
Change-Id: Ia65c151396415ca48725cb3c756f33efa01d2fe5
Closes-bug: #1296913
Matt Riedemann