You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jclouds.apache.org by David Bosschaert <da...@gmail.com> on 2014/08/26 12:30:59 UTC
How to create an EC2 instance with more disk space
Hi all,
This might be a bit of a noob question, but I'm having issue creating
an EC2 image via jclouds with a large amount of disk space available.
I'm creating a new node of type InstanceType.C3_8XLARGE - I think that
should come with 320 GB of storage. However, I can't seem to access
it? I wasn't too sure how to mount it, at least the loop0/loop1
devices listed by lsblk [1] wouldn't let me format (using sudo mkfs -t
ext4 /dev/loop0) it....
I tried TemplateBuilder.minDisk(32) but that didn't seem to do anything.
Anyone an idea?
Cheers,
David
[1] $ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 8G 0 disk
└─xvda1 202:1 0 8G 0 part /
loop0 7:0 0 100G 0 loop
└─docker-202:1-269205-pool 253:0 0 100G 0 dm
└─docker-202:1-269205-base 253:1 0 10G 0 dm
loop1 7:1 0 2G 0 loop
└─docker-202:1-269205-pool 253:0 0 100G 0 dm
└─docker-202:1-269205-base 253:1 0 10G 0 dm
Re: How to create an EC2 instance with more disk space
Posted by Andrew Phillips <an...@apache.org>.
> I think I have figured out what the issue was.
Glad to hear it seems to be working. Thanks for sharing the solution!
ap
Re: How to create an EC2 instance with more disk space
Posted by David Bosschaert <da...@gmail.com>.
I think I have figured out what the issue was.
What I had to do was add the following to the template options:
EC2TemplateOptions opts = EC2TemplateOptions.Builder
.inboundPorts(inboundPorts)
.mapEphemeralDeviceToDeviceName("/dev/sdm", "ephemeral0")
...
Cheers,
David
On 26 August 2014 11:30, David Bosschaert <da...@gmail.com> wrote:
> Hi all,
>
> This might be a bit of a noob question, but I'm having issue creating
> an EC2 image via jclouds with a large amount of disk space available.
>
> I'm creating a new node of type InstanceType.C3_8XLARGE - I think that
> should come with 320 GB of storage. However, I can't seem to access
> it? I wasn't too sure how to mount it, at least the loop0/loop1
> devices listed by lsblk [1] wouldn't let me format (using sudo mkfs -t
> ext4 /dev/loop0) it....
>
> I tried TemplateBuilder.minDisk(32) but that didn't seem to do anything.
>
> Anyone an idea?
>
> Cheers,
>
> David
>
> [1] $ lsblk
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> xvda 202:0 0 8G 0 disk
> └─xvda1 202:1 0 8G 0 part /
> loop0 7:0 0 100G 0 loop
> └─docker-202:1-269205-pool 253:0 0 100G 0 dm
> └─docker-202:1-269205-base 253:1 0 10G 0 dm
> loop1 7:1 0 2G 0 loop
> └─docker-202:1-269205-pool 253:0 0 100G 0 dm
> └─docker-202:1-269205-base 253:1 0 10G 0 dm