This repository was archived by the owner on Mar 25, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 211
Update EC2 instance type volumes specification for m2.xlarge #1571
Copy link
Copy link
Open
Description
The definition for m2.xlarge in org.jclouds.ec2.compute.domain.EC2HardwareBuilder has a single 420GB Volume that is also the boot drive.
/**
* @see InstanceType#M2_XLARGE
*/
public static EC2HardwareBuilder m2_xlarge() {
return new EC2HardwareBuilder(InstanceType.M2_XLARGE).ram(17510)
.processors(ImmutableList.of(new Processor(2.0, 3.25)))
.volumes(ImmutableList.<Volume> of(new VolumeImpl(420.0f, "/dev/sda1", true, false))).is64Bit(true);
}However, when I create an instance using Ubuntu 10.04 AMI ami-bffa6fd6, what you actually get looks like it has a 10GB boot volume on /dev/sda1
$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 10403128 1156388 8827312 12% /
devtmpfs 8685400 108 8685292 1% /dev
none 8960512 0 8960512 0% /dev/shm
none 8960512 56 8960456 1% /var/run
none 8960512 0 8960512 0% /var/lock
none 8960512 0 8960512 0% /lib/init/rw
And then a 420GB volume unmounted on /dev/sdb:
$ cat /etc/fstab
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/sda1 / ext3 defaults 0 0
# cloud-config mounts
/dev/sdb /mnt auto defaults 0 0
After mounting /dev/sdb on /data1:
$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 10403128 1156392 8827308 12% /
devtmpfs 8685400 108 8685292 1% /dev
none 8960512 0 8960512 0% /dev/shm
none 8960512 56 8960456 1% /var/run
none 8960512 0 8960512 0% /var/lock
none 8960512 0 8960512 0% /lib/init/rw
/dev/sdb 423135208 203084 401438084 1% /data1
The definition should be updated to reflect the current volumes.
I'm not sure about other instance types, it might be worth checking them too.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels