Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Trim volume size as needed to fit in pool free space #199

Merged
merged 3 commits into from
Mar 12, 2021
Merged

Trim volume size as needed to fit in pool free space #199

merged 3 commits into from
Mar 12, 2021

Commits on Feb 22, 2021

  1. Automatically reduce volume size as needed to fit in pool. 

    This adds a mechanism for trimming requested volume sizes so that
they fit in their pool. The intention is to accommodate small
shortages arising from metadata space usage, eg: creating a lvm
pool on an unpartitioned 10GiB drive and trying to create a single
100GiB volume in that pool. There is no reason a user of this role
should have to learn about LVM's metadata usage.

The maximum reduction of the volume size is 10% of the requested
size.
    @dwlehman
    dwlehman committed Feb 22, 2021
    Configuration menu
    Copy the full SHA
    74968ba View commit details
    Browse the repository at this point in the history

  2. Remove obsolete test of handling too-large lvm volume size.

    @dwlehman
    dwlehman committed Feb 22, 2021
    Configuration menu
    Copy the full SHA
    4f4df33 View commit details
    Browse the repository at this point in the history

  3. Add new test case for bz1894647 

    Playbook will fail when lv size is equal to vg size

Signed-off-by: Changhui Zhong <[email protected]>
    @zhongchanghui @dwlehman
    zhongchanghui authored and dwlehman committed Feb 22, 2021
    Configuration menu
    Copy the full SHA
    50a3801 View commit details
    Browse the repository at this point in the history