OpenStack projects are no longer being tested under Python 2.6, so
remove the trove classifier implying that this project supports 2.6.
Change-Id: Ic4b90b965bda8e84f5dcaa90446282bb24a1cce1
This file was copied from the nova tree, remove some nova specific info.
Need to keep the gettextutils reference.
Update the setup.cfg file also.
Change-Id: I0cb66e6620900fd318f45d758a94f95b144e006a
Signed-off-by: Don Dugger <donald.d.dugger@intel.com>
This is the smallest set of changes needed to unwedge the gate. Because
the gate is wedged all these changes need to be in a single patch in
order to fix it.
* point .gitreview at correct repo
pep8
* Don't run tools/config/check_uptodate.sh, we don't even have a config
file to check yet.
* gantt, doesn't have any local hacking checks yet so remove that
section from tox.ini
* Update import_exceptions in tox.ini
pylint
* copy lintstack code in from nova.
docs
* add gantt version code, copied in from nova
Change-Id: I1d7adb5bf1bf383a2f8543dda6eb4cdeb26f3b9a
As per the discussion on the mailing list here:
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015490.html
and discussions at summit, this patch removes the os-personalities
from the V3 API.
DocImpact
Part of blueprint v3-api-remove-extensions
Change-Id: I1a57ca812a9d71c0b1bab5d16ffad8eb82cba539
As discussed at the summit in the QA session, this removes
the coverage extension from the V3 API. The coverage extension
doesn't work properly and has security issues. An alternative technique,
though more limited in nature will soon be proposed.
Partially implements blueprint nova-v3-api
Change-Id: Ib4296288fefeb7e1e11bb6e44bd1cf355f29b9b9
Remove the used_limits extension from the V3 API because
it shows usage for limits which are no longer going to be displayed
by the limits extension. See https://review.openstack.org/#/c/39872/
The limits are not being displayed there because they are already
available through the quotas extension.
Although the quotas extension currently only displays the quota limit
and not usage, the following proposed changeset adds display
of usage: https://review.openstack.org/#/c/32303/. And this is done
in a way which is much more consistent in terms of naming and interface
than used_limits does.
So we no longer need the used_limits extension
Partially implements blueprint nova-v3-api
Change-Id: I8ec1f300335ca4fc3b86323cc3af6bc1591da7bb
This patch enable extension access_ips, remove old 'access_ip_*'
attributes and related unittest from servers core. And remove
old attributes from api samples.
Partially implements bp nova-v3-api
DocImpact
Change-Id: Id4c8bb721550e317e0695d7876e2faa3d6e91a60
This should be accepted/merged once all the RC1 bugfixes are in.
This bumps the target version to 2014.1, effectively opening the master
branch to Icehouse development, ending the feature freeze.
The Havana release branch is cut from the previous commit in master.
Change-Id: Ia3a41177e3c91bd75b38833761f9f8af2b503e4b
Adds the missing entry in setup.cfg which allows the V3 API
shelve plugin to be loaded. Also adds a v3 version of the unittests
for the shelve plugin.
Change-Id: I737ca0cae503b726b0103a4ae169ffca91188c87
Closes-Bug: #1233454
Baremetal is scheduled to be deprecated in Nova soon. Since
the V3 API is experimental in Havana, we should revert the
extension to avoid maintenance of the extension and its tests
for no real gain.
Things have changed enough since it was added that a simple
git-revert won't work. This reverts the following changes:
5de5ae1b5d3763dbcf14bf3b4d43199ad5255adf
92c9975bd2d53624ae595b895c2e96991ee43778
2382186311794591fb4d35893ffa774157d6131b
Mailing list discussion:
http://lists.openstack.org/pipermail/openstack-dev/2013-September/014614.html
Change-Id: I3bdc7234f91eb4f9078ee24d7ab093b28f9930c9
Ports the flavormanage extension and the corresponding
unittests to the v3 framework.
Partially implements blueprint nova-v3-api
Change-Id: Iaf6b4a2d7f4e4993a6540e8a3afc774b7b158608
Create a new v3 extension called os-block-device-mapping to handle
the block devices specified on server creation. This extension was
os-block-device-mapping-v2-boot in the old API.
Only the new block device mapping syntax has been ported although the
old one can still be used with v2 API.
blueprint: improve-block-device-handling
Change-Id: I898ae56539c6101680983d1eca4bce6d92bd5ce6
Adds support for specifying the security group during the V3 API
server create to the security groups extensions. This was
accidentally missed during the initial port. Adds the
corresponding XML deserialization and unittests.
Partially implements blueprint nova-v3-api
Fixes bug #1208746
Change-Id: Ie9d9e03ae20357212b0f270d97a19a0d0f9b0557
Adds version information for the V3 API which is only displayed
when the V3 API is enabled. Even if the the V3 API is enabled the
V3 API status is "EXPERIMENTAL" and the V2 one "CURRENT". This was
done so autodiscovery tools would not yet use the V3 version by
default.
Ports the relevant parts of the version extension and associated
tests to the V3 API to display V3 version information for /v3 GET
requests.
DocImpact
Partially implements blueprint nova-v3-api
Change-Id: Idd335ce0df63d91e94a4a757f1fbae94b576c37e
Ports the multiple create extension to the V3 API. There is no part1
patch for this changeset because the original V2 file was just a stub
with all of the code in servers.py
DocImpact
Partially implements blueprint nova-v3-api
Change-Id: I5eba468e9c4b753215b91607a3e2441626d2cb57
Removes V3 API images and image_metadata extensions as the
same functionality can be accessed directly through glance. Also
removes the associated testcases. There is a discussion about
the decision here:
http://lists.openstack.org/pipermail/openstack-dev/2013-August/012958.html
Fixes the image bookmark links in server information requests
so they point to glance
Partially implements blueprint nova-v3-api
Change-Id: Id32be0c0794b0f4dd220a928345ddf0133e9ffca
The fixed ip extension was one of the first ported to the V3 API
but a later decision around not supporting nova network in the V3 API
means that this extension is not required for V3. The fixed ip extension
only supports nova network, not neutron and the same functionality
can be accessed directly through neutron.
Also changes some extension tests to use a different extension
for white/black list testing
Partially implements bp nova-v3-api
Change-Id: Ie589170e863ee489661e789c5134ed8349ced279
This patch move 'personality' from core into extensions.
* demote personality the attribute of server from servers
* add corresponding tests
* move some tests about personality from test_servers to test_personality
Partially implements blueprint nova-v3-api
Change-Id: I62254a94476271b1d8bcc206dfda1236f155960b
This patch contains the changes required to adapt the agent
extension and the corresponding unittest to the v3 framework.
Moves the commented out tests from the v3 version of test_servers
to the user data extension unittests.
Partially implements: bp v3-api-extension-versioning
Partially implements blueprint nova-v3-api
Change-Id: I7eef3ba18d7cc36c1ef78d093f50fd9122ac26c7
This extension was promoted to core API so it's code is moved inside
main controller
Related to blueprint nova-v3-api
Change-Id: Ia526f27382cf3bedea8b97de11659243d724497f
Glance can expose direct URL locations to its clients. In current
versions of nova the only URL that can be accessed directly is file://.
This patch adds a notion of download plug-ins. With this new download
protocol modules can be added without disruption to the rest of the
code base. Based on the scheme of the URL returned from Glance a
plug-in will be loaded and used to download the data directly, instead
of first routing it through Glance. If anything fails in the process
the image will be downloaded by way of Glance.
Handlers are loaded with stevedore. To add a new module follow the example
in nova.image.downloads.file.py. The module is required to have two
functions:
get_download_hander():
This must return a child of nova.image.download.TransferBase
get_scheme():
Return the URL scheme that this module handles (ex: 'file')
If additional configuration is needed it can be added by the specific
plug-in (as shown by file_download_module_config included with this
patch submission). Once the module is created it must be added as an
entry point to the python installation. For those included with nova
this can be done by adding the following it setup.cfg:
[entry_points]
nova.download.modules =
file = nova.image.xfers.file
Additionally, as part of the multiple-locations work in Glance meta data
comes back with each location describing it. As an example,
this is needed for direct access to file URLs. Nova cannot assume that
every file URL is accessible on its mounted file systems, nor can it
assume that the mount points are the same. This patch solves that
problem for direct access to files.
blueprint image-multiple-location
Change-Id: I79b863c0075cebaadce5b630f22b81d2959ddbb1
This patch move the action 'change_password' from core into extensions.
* Catch exception InstancePasswordSetFailed explicitly
* Add decorator 'expected_errors'
* Change naming style of action name and attributes
* Add testcase
Partially implements: bp v3-api-extension-versioning
DocImpact
Change-Id: I35fb73a47a58584ad6f8af78ffa087ecebde92a8
Ports the server usage extension and the corresponding
unittests to the v3 API framework
DocImpact
Partially implements blueprint nova-v3-api
Change-Id: Ic5c14ef83e0ec16f36672377f1daa046044dce78
The fping extension, was introduced in
I7d942270aa52bd6216eda0d7ae366ef0195d52a8. But this doesn't seem like a
good for nova-api. We have no other 'instance monitoring' support in
nova and doing it out of the nova-api doesn't seem like the right place.
Change-Id: I3e9bd9b1c04aa06b62f1d3d82b0966e69829a620
This patch contains changes to port migrations extension to v3.
Partially implements blueprint nova-v3-api
Change-Id: Ie79a0d1eeeee7d4fce7a61d8e0cec90982368cf2
This patch contains the changes required to adapt the BaremetalNodes
extension and the corresponding unittest to the v3 framework
Change-Id: Iceef736a3821a4628afc34be29a04766421d3e47
This patch contains the changes required to adapt the AttachInterfaces
extension and the corresponding unittest to the v3 framework
Partially implements: bp v3-api-extension-versioning
Change-Id: I0f3d4da962323a318448634e762f7c31490f9298
Ports the used limits extension and the corresponding unittests to
the v3 framework.
Partially implements blueprint nova-v3-api
Change-Id: I6f1aa507ffd297e56d9cfd23972bc3bb15ba181a
This includes a set of fixes and improvements to os-aggregates:
- eliminate the action method replacing its functionality with wsgi.action
decorator.
- Returns explicity and appropriate status codes for each REST action.
- Improves information error passed to the user.
In the unit test removes one test that in fact was testing the action method
itself instead of _remove_host and which no longer makes sense since action is
removed.
Partially implements blueprint nova-v3-api
Change-Id: Ie737333c6b058f5b57b3e7c75b3d3eda95b80402
This adapts server metadata API to v3 tree using the new extension
framework.
Partially implements bp v3-api-core-as-extensions
Change-Id: I2013ef255e00e256899f8048c97c1d6c73b3268f