Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1201115 - [RFE][cinder]: Add support for over subscription with thin provisioning in GlusterFS Driver
[RFE][cinder]: Add support for over subscription with thin provisioning in Gl...
Status: CLOSED EOL
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder (Show other bugs)
unspecified
Unspecified Unspecified
low Severity unspecified
: beta
: 8.0 (Liberty)
Assigned To: lkuchlan
lkuchlan
https://blueprints.launchpad.net/cind...
upstream_milestone_none upstream_defi...
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-03-12 00:09 EDT by RHOS Integration
Modified: 2016-04-26 22:57 EDT (History)
5 users (show)

See Also:
Fixed In Version: openstack-cinder-7.0.0-2.el7ost
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-02-16 05:37:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:0603 normal SHIPPED_LIVE Red Hat OpenStack Platform 8 Enhancement Advisory 2016-04-07 20:53:53 EDT

  None (edit)
Description RHOS Integration 2015-03-12 00:09:31 EDT
Cloned from launchpad blueprint https://blueprints.launchpad.net/cinder/+spec/glusterfs-over-subscription-thin-provisioning.

Description:

We will want to modify the GlusterFS Driver capacity reporting as outlined in the https://blueprints.launchpad.net/cinder/+spec/over-subscription-in-thin-provisioning specification so that the scheduler can be aware of the thin provisioning/data reduction provided by the GlusterFS back end.

Specification URL (additional information):

None
Comment 5 lkuchlan 2016-02-16 05:37:50 EST
GlusterFG driver is not supported any more in openstack

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