Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1355700 - Support host storage for persistent volumes [NEEDINFO]
Summary: Support host storage for persistent volumes
Keywords:
Status: ASSIGNED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Steve Watt
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-12 09:49 UTC by Miheer Salunke
Modified: 2019-03-01 02:09 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
erich: needinfo? (misalunk)


Attachments (Terms of Use)

Description Miheer Salunke 2016-07-12 09:49:42 UTC
1. Proposed title of this feature request 
Support host storage for persistent volumes




3. What is the nature and description of the request? 
We have direct attached disks for large bare metal servers used for installing openshift. We want to effectively use these disks as persistent volumes.  This will provide us an opportunity to use storage without having performance loss due to use of other options like NFS. If these disks could be used as for eg. flocker volumes and can then be selected as persistent volumes in openshift, we wont even have to restrict the pod to that specific node.
Each of our servers have around 2 TB of disk space and we want to use this storage effectively without having to deal with performance issues associated with network attached storage


7. Is there already an existing RFE upstream or in Red Hat Bugzilla? 
- do not know


9. List any affected packages or components.
persistent volumes


Note You need to log in before you can comment on or make changes to this bug.