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.

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

Partition sizes on Vagrant boxes are smaller than on AMIs. #154

Closed
eseglem opened this issue Feb 28, 2018 · 4 comments
Closed

Partition sizes on Vagrant boxes are smaller than on AMIs. #154

eseglem opened this issue Feb 28, 2018 · 4 comments

Comments

@eseglem
Copy link

eseglem commented Feb 28, 2018

Expected behavior

I would expect the partition sizes on all builds to be the same in order to have identical environments for development / deployment.

Actual behavior

The Vagrant partitions are significantly (about 50%) smaller than the AMI partitions, as listed below.

                Vagrant AMI
/               1.6G    3.9G
/boot           190M    453M
/home           380M    976M
/var            772M    2.0G
/var/log        772M    2.0G
/var/log/audit  3.4G    8.3G

This causes builds to fail on Vagrant because the / volume fills up when running yum install, where they would not fail on the AMI.

Steps to reproduce behavior

Launch the Vagrant box and run df -h then launch an AMI and run df -h and compare the results.

Suggestions for fix

Adjust the Vagrant box to meet the expected partition sizes.

@lorengordon
Copy link
Member

In the vagrant boxes only 8GB is allocated of the 20GB disk, where on the AMIs the whole 20GB is allocated. I believe you should be able to extend the free space across whichever partition you need it.

@eseglem
Copy link
Author

eseglem commented Feb 28, 2018

Right, we can expand the partitions, however that then requires changes to scripts to match them together. I would think the Vagrant boxes should be identical in partition size to the AMIs, so that there is no different to install scripts needed. What is the reason for the partitions being smaller in Vagrant than the AMI? If it is no possible to change it on the Vagrant box being provided, would you be able to provide a script / config to increase the sizes of them to match?

@lorengordon
Copy link
Member

The creation of the vagrant boxes is far enough back in the memory of things that it's impossible to say what the original reasoning was for this configuration. All I remember is the vagrant boxes were a bit of an experiment, and I was trying to make the partition sizes proportional to those in the AMI. I do not remember why only 8GB was allocated in the first place. Probably some attempt (possibly mis-guided) to minimize the vagrant box size? Eh.

There hasn't really been a lot of demand for the vagrant boxes, and we ourselves have very little expertise with vagrant... Which goes to mean that we do not have strong opinions here and our time priorities are elsewhere. If you are partial to the vagrant boxes and have stronger opinions about what they should be, this is an open source project and community contributions are highly welcome (via pull requests)...

@eseglem
Copy link
Author

eseglem commented Feb 28, 2018

Yeah, we are looking into it, and will see what we can do. Looks like it might be a simple change in https://github.com/plus3it/spel/blob/develop/spel/kickstarts/ks.centos6.minimal.cfg to up the sizes to approximately equivalent.

ksmith211 pushed a commit to ksmith211/spel that referenced this issue Mar 1, 2018
lorengordon added a commit that referenced this issue Mar 2, 2018
…han-AMIs

Fixes #154 Partition sizes smaller on AMIs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants