Bug 1312808

Summary: RFE:Admin/user should be able to choose default tier for new creates
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Nag Pavan Chilakam <nchilaka>
Component: glusterfsAssignee: Bug Updates Notification Mailing List <rhs-bugs>
Status: CLOSED WONTFIX QA Contact: storage-qa-internal <storage-qa-internal>
Severity: low Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: amukherj, nlevinki, vbellur
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-06 02:47:38 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:
Embargoed:

Description Nag Pavan Chilakam 2016-02-29 09:48:31 UTC
Currently any file created in a normal tiered volume(where there is sufficient space on cold and hot tier), gets created on hot tier.
But there can be usecases just like hospitals, where they create and save files to rest, till recalled due to an event. In such cases it would be good to use the slower disks directly than create the file on hot tier and then move them to cold, when in such environments it is highly improbable to immediately recall a file created just few seconds or minutes back.
This will help save the life of ssd with unncessary writes and save on n/w bandwidth by not having files to be moved from hot to cold once the file becomes unaccessed for long.

Having hot tier as default makes sense in significant usecases where the newly created files will be reaccessed again.
But having hot tier as default create place will not be much useful for files in work environments we know the files are not re-accessed once created