Bug 1041051

Summary:	[RFE][nova]: Switch Nova to use tenant ID authentication with Neutron
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-nova	Assignee:	Vladan Popovic <vpopovic>
Status:	CLOSED ERRATA	QA Contact:	Ami Jeain <ajeain>
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	markmc, ndipanov, sgordon, slong, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature, Triaged
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/tenant-id-based-auth-for-neutron
Whiteboard:	upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_approved
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.	Story Points:	---
Clone Of:
Clones:	1081952 (view as bug list)		Environment:
Last Closed:	2014-07-08 15:27:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1081952

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