Skip to content
This repository was archived by the owner on Aug 7, 2025. It is now read-only.

accommodate upstream libvirt boxes changes in a forward and backward way#330

Merged
CraigSterrett merged 1 commit intoclearlinux:masterfrom
AntonioMeireles:newBoxesCompatibility
Aug 19, 2020
Merged

accommodate upstream libvirt boxes changes in a forward and backward way#330
CraigSterrett merged 1 commit intoclearlinux:masterfrom
AntonioMeireles:newBoxesCompatibility

Conversation

@AntonioMeireles
Copy link
Copy Markdown
Contributor

Hi all,

per AntonioMeireles/ClearLinux-packer#24 the
ClearLinux libvirt boxes default size was lowered from the previous 40G
to a more manageable 5G, having the user the ability to, at box
instantiation, to increase that value to whatever is adequate.

In order to avoid surprises in this side the Vagrantfile was modded to
have hardcoded the previous default value.

This change is forward and backward compatible as it will just be
ignored when using older boxes ( since the 'new' root volume size just
the same as original one) and will resize the box to the expected 40G in
newer ones.

Please do note that albeit code is committed, i'm not yet build new boxes with
new code - as i think it would be handy to have this merged this side first to avoid breakages

All the best!

per AntonioMeireles/ClearLinux-packer#24 the
ClearLinux libvirt boxes default size was lowered from the previous 40G
to a more manageable 5G, having the user the ability to, at box
instantiation, to increase that value to whatever is adequate.

In order to avoid surprises in this side the Vagrantfile was modded to
have hardcoded the previous default value.

This change is forward and backward compatible as it will just be
ignored when using older boxes ( since the 'new' root volume size just
the same as original one) and will resize the box to the expected 40G in
newer ones.

Signed-off-by: António Meireles <antonio.meireles@reformi.st>
@CraigSterrett CraigSterrett merged commit 55b2aa2 into clearlinux:master Aug 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants