Go to file

Andrew Laski d17a20d3d7 Remove the sample policy file

The sample file has been empty for a little while now since default
policies are registered in code. Shipping an empty file may be
confusing, so let's remove it. A README has been added explaining how to
generate an actual sample policy file.

Change-Id: I23c934d2b610a451d6ebbd4276721c455365cedc
Depends-On: I85a251376dfe38caa4b100861bf764014a98bc37

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

api-guide/source

Merge "Remove last sentence"

2016-09-26 13:12:57 +00:00

api-ref/source

Fix a few typos in API reference

2016-09-28 14:34:23 +09: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

libvirt: support user password settings in virtuozzo

2016-09-28 18:46:26 +00:00

etc/nova

Remove the sample policy file

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

nova

Remove the sample policy file

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

plugins/xenserver

plugins/xenserver: Add '.py' extension

2016-09-21 10:56:39 +01:00

releasenotes

Merge "libvirt: support user password settings in virtuozzo"

2016-09-29 00:26:53 +00:00

tools

Add a post-test-hook to run the archive command

2016-09-28 13:28:55 +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: Always use 'assertIs(Not)None'

2016-09-23 15:40:35 +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

Remove nova.image.s3 and configs

2016-09-22 19:29:47 -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-29 00:08:21 +00:00

tests-py3.txt

Merge "libvirt: fixes python 3 related unit tests"

2016-09-28 13:59:08 +00:00

tox.ini

Revert "tox: Don't create '.pyc' files"

2016-09-14 10:45:44 +01: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/