Go to file

Maho Koshiya 8b8a29c8b5 Add os-start/stop functional negative tests

The negative tests of os-start/stop API are not covered enough
in functional tests. We want to add the conflict tests of when
this API runs in the unexpected state of server.
* Case of os-start API, the server status must be SHUTOFF.
* Case of os-stop API, the server status must be ACTIVE or ERROR.

Change-Id: I1c44ae737ad39bc58dd3ebfd554176d6400fd9fd

2016-11-29 14:32:24 +09:00

api-guide/source

Fix small RST markup errors

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

api-ref/source

Merge "Fix API doc for os-console-auth-tokens"

2016-10-10 12:38:49 +00: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 "doc: add dev policy about no new metrics monitors"

2016-10-12 17:24:40 +00:00

etc/nova

Remove the sample policy file

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

nova

Add os-start/stop functional negative tests

2016-11-29 14:32:24 +09:00

plugins/xenserver

Add a hacking rule for string interpolation at logging

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

releasenotes

conf: Remove deprecated `use_glance_v1`

2016-10-12 12:21:59 +00:00

tools

Merge "Add Apache 2.0 license to source file"

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

.coveragerc

Change ignore-errors to ignore_errors

2015-09-21 14:34:39 +00:00

.gitignore

Ignore generated merged policy files

2016-08-31 08:54:25 -07: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

bandit.yaml

Add bandit for security static analysis testing

2015-07-02 09:17:48 -07: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

Require WebOb>=1.6.0

2016-10-12 10:25:09 -04: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-09-30 10:21:30 +00:00

tests-py3.txt

Merge "numa: Fixes NUMA topology related unit tests"

2016-10-03 16:57:20 +00:00

tox.ini

Always use python2.7 for functional tests

2016-10-12 00:02:50 +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/