Red Hat Bugzilla – Bug 1032024
[RFE] Add nova compute v3 endpoint
Last modified: 2016-04-18 02:46:45 EDT
Description of problem:
There is no computev3 endpoint, causing the new tempest tests of this feature to fail.
# The type of endpoint for a Compute v3 API service. Unless you have a
# custom Keystone service catalog implementation, you probably want to leave
# this value as "computev3"
catalog_v3_type = computev3
To not have the computev3 tests run in tempest, just set this in tempest.conf:
api_v3 = false
I think this feature should be enabled when and just when, the feature is completed. https://blueprints.launchpad.net/nova/+spec/nova-v3-api
Moving this RFE to RHOS 5.0. The API is still WIP.
The upstream patch for that is already released, I gonna update our o-p-m to support V3 endpoint:
The v3 API is still experimental and still subject to major changes. I honestly wouldn't worry about this for RHOS 5.0.
Further, I think having a separate API endpoint is the wrong thing long term anyway. We would want it (optionally) exposed via the same API endpoint. So, I wouldn't do this for RHOS at all.
Moving to RHOS-6. Thanks for clarification Russell.
Creating patch for packstack after checking the tempes puppet module
It seems that tempest does not include this tests, contactig David Kranz to confirm this.
this feature is not implemented in tempest
The tempest tests for nova v3 were removed in Dec. 2014 because they were not running in the upstream gate any more and that api was being removed from nova.