Bug 1112485

Summary:	[RFE][cinder]: Private Volume Types
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-cinder	Assignee:	Eric Harney <eharney>
Status:	CLOSED ERRATA	QA Contact:	lkuchlan <lkuchlan>
Severity:	medium	Docs Contact:
Priority:	high
Version:	unspecified	CC:	ddomingo, eharney, markmc, nlevinki, rfreire, scohen, yeylon
Target Milestone:	Upstream M1	Keywords:	FutureFeature, Triaged
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/cinder/+spec/private-volume-types
Whiteboard:	upstream_milestone_kilo-1 upstream_definition_approved upstream_status_implemented
Fixed In Version:	openstack-cinder-2015.1.0-2.el7ost	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	1275093 (view as bug list)		Environment:
Last Closed:	2015-08-05 13:12:46 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1213676, 1275093

Description RHOS Integration 2014-06-24 04:10:11 UTC

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

Description:

Currently, all cinder volume types are visible to all users, regardless of their project. Some volume types should only be restricted. Examples are test volume types where a new technology is being tried out or ultra high performance volumes for special needs where most users should not be able to select these volumes. Similar approaches are taken with the is_public flag on flavors in Nova.

Specification URL (additional information):

None

Comment 6 Yogev Rabl 2015-07-14 07:47:03 UTC

verified in 
python-cinder-2015.1.0-3.el7ost.noarch
openstack-cinder-2015.1.0-3.el7ost.noarch
python-cinderclient-1.2.1-1.el7ost.noarch

with the following bugs:
Bug 1242530
Bug 1242516

Comment 8 errata-xmlrpc 2015-08-05 13:12:46 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.

https://access.redhat.com/errata/RHEA-2015:1548