Skip to content
This repository has been archived by the owner on Mar 26, 2020. It is now read-only.

Auto distribute count for Intelligent Volume Provisioning #999

Closed
aravindavk opened this issue Jul 12, 2018 · 3 comments
Closed

Auto distribute count for Intelligent Volume Provisioning #999

aravindavk opened this issue Jul 12, 2018 · 3 comments
Assignees
Labels
FW: Device Management FW: Volume Management GCS/0.5 GCS 0.5 release GCS/1.0 Issue is blocker for Gluster for Container Storage priority: high

Comments

@aravindavk
Copy link
Member

Current dynamic Volume create API accepts distribute count as input and defaults to 1 if no distribute count is specified. New feature is required to find distribute count automatically based on given Volume size and available size.

If Distribute count is not specified and disk space is not enough to create volume, try again with increased distribute count till all the bricks can be planned(till max distribute count)

@aravindavk
Copy link
Member Author

Issue #851 is split into multiple issues. This is one among them

@aravindavk aravindavk changed the title Auto distribute count for dynamically created Volumes Auto distribute count for Intelligent Volume Provisioning Jul 12, 2018
@aravindavk
Copy link
Member Author

Alternate idea compared to Iterative method till max distribute count: New API tunable max-brick-size.

if (requested-size > max-brick-size) 
{
    distribution_count = int(requested-size / max-brick-size);
    if (requested-size % max-brick-size > 0)
    {
        distribution_count++;
    }
} 

@JohnStrunk
Copy link
Member

I like the notion of having max-brick-size as it makes efficient bin packing easier when item size is constrained.

@atinmu atinmu added priority: high GCS/1.0 Issue is blocker for Gluster for Container Storage and removed priority: low GCS1.0-Stretch Not a blocker for GCS but good to have. labels Nov 28, 2018
@aravindavk aravindavk added the GCS/0.5 GCS 0.5 release label Dec 12, 2018
aravindavk added a commit that referenced this issue Dec 13, 2018
While creating auto provisioned volume, support added to automatically
calculate the distribute count based on max brick size specified in
the request.

For example, below command creates 2x3(Distributed replicate) volume

```
glustercli volume create gv1 --replica 3 --size 1G \
        --max-brick-size 512M
```

Fixes: #999
Signed-off-by: Aravinda VK <avishwan@redhat.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FW: Device Management FW: Volume Management GCS/0.5 GCS 0.5 release GCS/1.0 Issue is blocker for Gluster for Container Storage priority: high
Projects
None yet
Development

No branches or pull requests

3 participants