Bug 1041051 - [RFE][nova]: Switch Nova to use tenant ID authentication with Neutron
Summary: [RFE][nova]: Switch Nova to use tenant ID authentication with Neutron
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Upstream M3
: 5.0 (RHEL 7)
Assignee: Vladan Popovic
QA Contact: Ami Jeain
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_icehouse-3 upstrea...
Depends On:
Blocks: 1081952
TreeView+ depends on / blocked
 
Reported: 2013-12-12 13:30 UTC by RHOS Integration
Modified: 2019-09-09 15:31 UTC (History)
5 users (show)

Fixed In Version: openstack-nova-2014.1-3.el7ost
Doc Type: Enhancement
Doc Text:
The Compute service now uses the tenant identifier instead of the tenant name when authenticating with OpenStack Networking (neutron). This improves support for the OpenStack Identity API v3, which allows non-unique tenant names.
Clone Of:
: 1081952 (view as bug list)
Environment:
Last Closed: 2014-07-08 15:27:02 UTC
Target Upstream Version:

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


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 69972 0 None None None Never
Red Hat Product Errata RHEA-2014:0853 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement - Compute 2014-07-08 19:22:38 UTC

Description RHOS Integration 2013-12-12 13:30:34 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/tenant-id-based-auth-for-neutron.

Description:

Keystone v3 supports non-unique project names, which means that authentication needs to be by tenant ID.

The Neutron  client supports authentication via Tenant_ID: https://review.openstack.org/#/c/35116/

But Nova currently only supports name based authentication, via neutron_admin_tenant_name.

This change would introduce a neutron_admin_tenant_id value, and deprecate the tenant_name option  

Specification URL (additional information):

None
Comment 6 errata-xmlrpc 2014-07-08 15:27:02 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-0853.html
Note You need to log in before you can comment on or make changes to this bug.