On Wed, Apr 29, 2015 at 11:33 PM, Kelly Prescott kpresc...@coolip.net wrote:
to follow-up, I will give an example.
Here is the listing for the official centos AMI:
IMAGE ami-96a818feaws-marketplace/CentOS 7 x86_64 (2014_09_29) EBS
HVM-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-d2a117ba.2
I think the command-line is far more flexable then the GUI interface.
I use ec2-api-tools, but the python boto stuff works virtually the same.
On Thu, 30 Apr 2015, Nico Kadel-Garcia wrote:
On Wed, Apr 29, 2015 at 11:33 PM, Kelly Prescott kpresc...@coolip.net wrote:
to follow-up, I will give
So you're working from the command line tools in the EPEL 'cloud-init'
package, not the AWS GUI? Because when I tried expanding the size of
the base disk image in the GUI, I wound up with an an 8 Gig default
/dev/xvda1 on a 20 Gig /dev/xvda. That's why I was looking at how do
I resize
I'm staring at the free CentOS images on AWS, and seeing that whoever
set those up elected to use a partition for /dev/xvda1 rather than
taking advantage of Amazon's tendency to use /dev/xvda, /dev/xvdb,
etc. for each disk and use those directly as a file system.
The result is that if you elect
This is not really a problem at all.
when you launch your image for the first time, you can specify a larger /
volume size and cloud-init-tools will take care of the rest.
This is well documented in the AWS userguides.
-- Kelly Prescott
On Wed, 29 Apr 2015, Nico Kadel-Garcia wrote:
I'm
to follow-up, I will give an example.
Here is the listing for the official centos AMI:
IMAGE ami-96a818feaws-marketplace/CentOS 7 x86_64 (2014_09_29) EBS
HVM-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-d2a117ba.2
aws-marketplace available public [marketplace:
On Wed, Apr 29, 2015 at 11:24 PM, Kelly Prescott kpresc...@coolip.net wrote:
This is not really a problem at all.
when you launch your image for the first time, you can specify a larger /
volume size and cloud-init-tools will take care of the rest.
This is well documented in the AWS
