Bug 1296554

Summary: [SME] Need way to segment access to PVs by namespaces
Product: OpenShift Container Platform Reporter: Peter Larsen <plarsen>
Component: RFEAssignee: Bradley Childs <bchilds>
Status: CLOSED DUPLICATE QA Contact: Johnny Liu <jialiu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-13 21:41:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Peter Larsen 2016-01-07 14:19:49 UTC 
Description of problem:

The current OSE Cluster has a set of PVs which are only selectable by capacity and read/write requirements. A PV needs to be assigned to a region/zone to allow local storage to be used for a namespace, and to be able to separate storage types by need by namespace. 

Ie. a storage pool may have some SSD for fast storage needed for high IO apps which is needed for high-IO applications, other pools for slower and basic storage. Geographically spread clusters also need a way to ensure that pods running in region A does not try to access storage attached in region B to ensure low latency, faster speed and less points of failure between the pod and storage pool.

Being able to specify a namespace per PV would be one option. Labels, as long as they can be enforced by project (locking a project to specific storage labels) would satisfy the need too.
Comment 1 Dan McPherson 2016-04-13 21:41:05 UTC 

*** This bug has been marked as a duplicate of bug 1276082 ***