[BIGTOP-1151] Default VM disk sizes, might be a little too small? Or maybe just need recipes for making them bigger?

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.7.0
• Fix Version/s: backlog
• Component/s: vm
• Assignee: Unassigned
• Reporter: jay vyas
• Created: 25/Nov/13 18:53
• Updated: 26/Mar/14 22:02

Description

The BigTop VMs come with very small disks, (partitions = "/" ; size: 2 --> 2GB).

Either Default VM sizes could be larger, or (better) maybe we could curate a VM deployment methodology that is more flexible.

At least in KVM, you can :

1) Follow :
http://serverfault.com/questions/452794/increasing-a-linux-partition-once-vm-size-increased-in-vsphere

2) And then Run your virt-install:
virt-install --import -n vmname -r 2048 --os-type=linux --disk ./bigtop-vm-kvm-master/bigtop_hadoop-sda.raw,device=disk,bus=virtio,size=8,sparse=true,format=raw --vnc --noautoconsole

To create a "large" bigtop VM.

But that seems a little bit like too much work. Options to create a more useable VM are:

1) Just hardcode the boxgrinder generators to make bigger default disk size for the VM

2) Have docs for vagrant/kvm/vmware that show how to setup the BigTop VM and then resize it using QEMU tools or VBoxModify, etc...