Differentiate thick and thin provisioning logic in scheduler

Registered by Xing Yang on 2016-06-21

Currently in the capacity filter and weigher of the scheduler, we use the the logic to evaluate whether there is enough capacity to thin provision a volume on a backend if the driver reports thin_provisioning_support to be True. However, a driver may be able to support both thin and non-thin provisioning. The logic does not check whether the user wants the volume to be provisioned as thin or not. This blueprint proposes to fix the problem by checking 'thin_provisioning_support' in extra specs of the volume type.

Blueprint information

Status:
Complete
Approver:
Sean McGinnis
Priority:
Medium
Drafter:
Xing Yang
Direction:
Approved
Assignee:
Xing Yang
Definition:
Approved
Series goal:
Accepted for newton
Implementation:
Implemented
Milestone target:
milestone icon newton-3
Started by
Xing Yang on 2016-06-21
Completed by
Xing Yang on 2016-09-08

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/differentiate-thick-thin-in-scheduler,n,z

Addressed by: https://review.openstack.org/332488
    Differentiate thick and thin provisioning

Gerrit topic: https://review.openstack.org/#q,topic:bug/1580866,n,z

Addressed by: https://review.openstack.org/315352
    Check 'thin_provisioning_support' in extra specs

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.