Bug 1312808 - RFE:Admin/user should be able to choose default tier for new creates
RFE:Admin/user should be able to choose default tier for new creates
Status: NEW
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterfs (Show other bugs)
3.1
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Bug Updates Notification Mailing List
storage-qa-internal@redhat.com
: FutureFeature, ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-29 04:48 EST by nchilaka
Modified: 2017-03-25 12:26 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description nchilaka 2016-02-29 04:48:31 EST
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

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