Go to file

Matt Riedemann be11fab555 api-ref: remove user_id from keypair list response and fix 2.10

The user_id has always been returned for the keypair create and
show operations. The user_id has never been returned in the list
response. The docs were a bit confusing for create and show since
they said 'New in version 2.10' for the user_id description in the
response.

This change clarifies the response docs so that we don't make it
sound like user_id is only getting returned for create/show with
microversion 2.10 and removes user_id from the response docs for
the list operation.

Change-Id: I4bd06c8ed88e526f44bb0d6e927c09175bf103b1
Closes-Bug: #1638606

2016-11-04 10:31:29 -04:00

api-guide/source

Fix small RST markup errors

2016-09-29 16:24:21 +00:00

api-ref/source

api-ref: remove user_id from keypair list response and fix 2.10

2016-11-04 10:31:29 -04:00

contrib

Merge "changed quantum to neutron in vif-openstack"

2014-03-05 10:45:05 +00:00

devstack

Add RC file for excluding tempest tests for LVM job

2016-05-17 10:25:45 -04:00

doc

Merge "Transform instance.resume notifications"

2016-10-28 10:58:26 +00:00

etc/nova

Remove the sample policy file

2016-09-29 14:41:39 -04:00

nova

Merge "TrivialFix: Fixed typo in 'MemoryPageSizeInvalid' exception name in docstrings"

2016-11-01 16:21:23 +00:00

plugins/xenserver

Add a hacking rule for string interpolation at logging

2016-10-11 08:39:48 +00:00

releasenotes

Merge "Clarify what changed with scheduler_host_manager."

2016-10-28 12:37:01 +00:00

tools

Merge "Add Apache 2.0 license to source file"

2016-10-10 12:38:13 +00:00

.coveragerc

Remove nova/openstack/* from .coveragerc

2016-10-12 16:20:49 -04:00

.gitignore

doc: Integrate oslo_policy.sphinxpolicygen

2016-10-20 10:31:01 +01:00

.gitreview

Add .gitreview config file for gerrit.

2011-10-24 15:07:19 -04:00

.mailmap

Add mailmap entry

2014-05-07 12:14:26 -07:00

.testr.conf

[placement] Adjust the name of the gabbi tests

2016-09-20 19:14:44 +00:00

babel.cfg

Get rid of distutils.extra.

2012-02-08 19:30:39 -08:00

bindep.txt

List system dependencies for running common tests

2016-08-24 06:49:32 +02:00

CONTRIBUTING.rst

Workflow documentation is now in infra-manual

2014-12-05 03:30:37 +00:00

HACKING.rst

hacking: Use assertIs(Not), assert(True|False)

2016-10-12 11:14:33 +01:00

LICENSE

initial commit

2010-05-27 23:05:26 -07:00

MAINTAINERS

Add a maintainers file

2015-05-23 03:22:07 +10:00

README.rst

Refresh README and its docs links

2016-08-08 10:26:08 +01:00

requirements.txt

Updated from global requirements

2016-10-27 12:19:17 +00:00

run_tests.sh

Add description on how to run ./run_test.sh -8

2016-01-11 13:17:04 +00:00

setup.cfg

Merge "Adds nova-policy-check cmd"

2016-09-01 17:56:56 +00:00

setup.py

Updated from global requirements

2015-09-17 16:41:48 +00:00

test-requirements.txt

Updated from global requirements

2016-10-22 01:24:04 +00:00

tests-py3.txt

compute: fixes python 3 related unit tests

2016-10-18 07:07:43 +00:00

tox.ini

Remove bandit.yaml in favor of defaults

2016-10-20 18:09:54 +00:00

README.rst

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 and OpenStack Ironic.

OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.

API

To learn how to use Nova's API, consult the documentation available online at:

http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/

For more information on OpenStack APIs, SDKs and CLIs, please see:

http://www.openstack.org/appdev/ http://developer.openstack.org/

Operators

To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:

http://docs.openstack.org

For information about the different compute (hypervisor) drivers supported by Nova, please read:

http://docs.openstack.org/developer/nova/feature_classification.html

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:

http://bugs.launchpad.net/nova

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:

http://docs.openstack.org/developer/nova/