Bug 1043708

Summary:	[RFE][keystone]: Make Assignment Controllers/Routers First Class
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-keystone	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Udi Kalifon <ukalifon>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	aberezin, apevec, ayoung, breeler, markmc, nkinder, yeylon
Target Milestone:	Upstream M2	Keywords:	FutureFeature
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/keystone/+spec/assignment-controller-first-class
Whiteboard:	upstream_milestone_icehouse-2 upstream_status_implemented upstream_definition_approved
Fixed In Version:	openstack-keystone-2014.1-4.el7ost	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-22 12:03:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-17 00:45:48 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/assignment-controller-first-class.

Description:

Identity API and Assignment API are split at the manager level.  Assignment's Controllers and Routers should also be made first-class (instead of meshed into the "Identity" section)

Specification URL (additional information):

None

Comment 2 Stephen Gordon 2014-01-23 20:51:21 UTC

Moving to POST based on upstream status (Implemented).