Go to file

Sean Dague c9f5ad3bcf remove /v2.1/{tenant_id} from all urls

As discussed at summit, the version part of the URL is not really
relevant, or a thing a user should be filling out themselves, this
should instead be set by the service catalog and extracted from the
token.

This removes it's reference in all documented REST urls, and adds a
new section describing how one gets the base URL for all calls.

Change-Id: I4306b8c3de0225e54f3909dd8a1fb293c4e5944c

2016-06-03 08:47:33 -04:00

api-guide/source

Merge "Make available to build docs with python3"

2016-05-26 17:24:03 +00:00

api-ref/source

remove /v2.1/{tenant_id} from all urls

2016-06-03 08:47:33 -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

Microversion 2.28 changes cpu_info string to JSON object

2016-06-01 16:25:17 +00:00

etc/nova

Add proxy middleware to application pipeline

2016-05-30 08:12:20 +03:00

nova

Merge "Verify requested_destination in the scheduler"

2016-06-02 01:06:43 +00:00

plugins/xenserver

Merge "plugins/xenserver: Resolve PEP8 issues"

2016-03-10 14:27:09 +00:00

releasenotes

Merge "Microversion 2.28 changes cpu_info string to JSON object"

2016-06-02 00:15:50 +00:00

tools

remove db2 support from tree

2016-05-23 07:33:20 -04:00

.coveragerc

Change ignore-errors to ignore_errors

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

.gitignore

Add api-ref/build/* to .gitignore

2016-04-06 12:51:27 -04: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

Add tox -e functional

2014-11-12 15:31:06 -05: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

CONTRIBUTING.rst

Workflow documentation is now in infra-manual

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

HACKING.rst

Merge "Add a hacking check for test method closures"

2016-04-04 11:08:43 +00: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

Update links in README

2014-05-07 16:06:24 -07:00

requirements.txt

Updated from global requirements

2016-06-01 13:52:24 +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

Let setup.py compile_catalog process all language files

2016-05-20 17:56:06 +02:00

setup.py

Updated from global requirements

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

test-requirements.txt

Updated from global requirements

2016-05-31 03:04:34 +00:00

tests-py3.txt

Fixes python 3 urllib quote / unquote usage

2016-05-26 18:06:40 +03:00

tox.ini

Merge "Let setup.py compile_catalog process all language files"

2016-05-24 20:56:24 +00:00

README.rst

OpenStack Nova README

OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.

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.

Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.

To keep updated with new developments in the OpenStack project follow @openstack on Twitter.

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

http://docs.openstack.org

For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:

https://wiki.openstack.org/wiki/HypervisorSupportMatrix

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 wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:

https://git.openstack.org/cgit/openstack/nova

Developers should also join the discussion on the mailing list, at:

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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/

For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.

-- End of broadcast