Bug 1042150 - [RFE][heat]: Move to only using the keystone v3 API
Summary: [RFE][heat]: Move to only using the keystone v3 API
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-heat
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Upstream M3
: 5.0 (RHEL 7)
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/heat...
Whiteboard: upstream_milestone_icehouse-3 upstrea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 21:12 UTC by RHOS Integration
Modified: 2015-02-23 21:37 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
With this release, heat_keystoneclient now uses the Identity service's v3 API exclusively. This API version allows non-admin users to perform autoscaling and use wait conditions.
Clone Of:
Environment:
Last Closed: 2014-07-08 15:32:44 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:0849 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement - Orchestration 2014-07-08 19:23:00 UTC

Description RHOS Integration 2013-12-12 21:12:42 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/keystone-v3-only.

Description:

Currently, heat_keystoneclient uses a mixture of v2 and v3 clients, which is suboptimal from both a performance and code-elegance perspective.

We should move to just using the v3 API, but we need ec2tokens to work via the v3 API (and keystoneclient), before this will work.  I'm looking into what's needed to make that work, then we can port heat_keystoneclient to v3-only.

Specification URL (additional information):

None
Comment 4 Amit Ugol 2014-04-02 16:08:33 UTC 
Added no testplan needed in the WB.
During the testing phase the heat client is using v3. When the testing phase is over most pathways of communication between heat and keystone will be tested anyway.
If I do not see any issues with keystone I can safely mark this bug verified.
Comment 5 Amit Ugol 2014-05-27 07:00:56 UTC 
I am running current heat_keystoneclient which uses keystoneclient.v3.
So far so good.
In this file there is no reference to other keystoneclient versions.
Comment 6 Steve Baker 2014-05-27 23:40:06 UTC 
The v2 equivalent is in contrib/heat_keystoneclient_v2/heat_keystoneclient_v2/client.py
Comment 9 errata-xmlrpc 2014-07-08 15:32:44 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0849.html
Note You need to log in before you can comment on or make changes to this bug.