Bug 1041646

Summary:	[RFE][cinder]: ACL(access control list) Rule for Cinder Volumes
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-cinder	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:	Dafna Ron <dron>
Severity:	low	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	eharney, markmc, scohen, yeylon
Target Milestone:	---	Keywords:	FutureFeature, TestOnly, Triaged
Target Release:	9.0 (Mitaka)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/cinder/+spec/volume-acl
Whiteboard:	upstream_milestone_none upstream_status_needs-code-review upstream_definition_superseded
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-10 14:26:23 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 18:28:30 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/cinder/+spec/volume-acl.

Description:

The volume can only be accessed by a certain user in a certain project. There is no ACL rule for cinder volume. Adding ACL configration can make the volume read or written by other users or other projects. The volume creator has the capability to edit the ACL rule. The ACL model can be similar to the one in Amazon S3.

Use case: several users can share the data in one volume.

Specification URL (additional information):

None