Go to file

Pavel Kholkin df6e2d37f2 [proxy-api] microversion 2.39 deprecates image-metadata proxy API

Almost all proxy APIs were deprecated in microversion 2.36.
But the sub-resource image-metadata of image was forgotten to deprecate.
This patch deprecates the image-metdata API from 2.39.

Implements blueprint deprecate-image-meta-proxy-api
Closes-bug: #1614578

Change-Id: I5507337ab6fe4a377f66dec3fe275d75618cd7b4

2016-12-07 19:22:43 +03:00

api-guide/source

docs: cleanup wording for 'SOFT_DELETED' in api-guide

2016-11-28 11:51:00 -05:00

api-ref/source

[proxy-api] microversion 2.39 deprecates image-metadata proxy API

2016-12-07 19:22:43 +03: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

[proxy-api] microversion 2.39 deprecates image-metadata proxy API

2016-12-07 19:22:43 +03:00

etc/nova

Remove the sample policy file

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

nova

[proxy-api] microversion 2.39 deprecates image-metadata proxy API

2016-12-07 19:22:43 +03:00

plugins/xenserver

Add a hacking rule for string interpolation at logging

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

releasenotes

[proxy-api] microversion 2.39 deprecates image-metadata proxy API

2016-12-07 19:22:43 +03: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

Remove redundant VersionedObject Fields

2016-11-22 15:47:53 -05:00

run_tests.sh

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

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

setup.cfg

Remove deprecated nova-all binary

2016-10-12 10:02:17 -07:00

setup.py

Updated from global requirements

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

test-requirements.txt

Updated from global requirements

2016-11-16 21:59:09 +00:00

tests-py3.txt

Remove tests from tests-py3.txt

2016-11-25 10:39:04 +08: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/