Bug 1041951

Summary:	[RFE][keystone]: service metadata
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/keystone/+spec/service-metadata
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:22:47 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-12 20:15:33 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/service-metadata.

Description:

Deployment-specific workflows require a variety of metadata which cannot be facilitated by Keystone APIs today. Take Nova quota class and availability zones, for instance, ideally they should be able to attach to projects so Nova can effectively perform authorization based on those data.  Like policies, metadata should be service-specific. Like service catalog, metadata are returned for as the result of successful authentication and token validation, if the token is scoped to a project.


Specification URL (additional information):

None