provisionr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrei Savu <savu.and...@gmail.com>
Subject Re: default ami not supporting EBS mapping
Date Tue, 21 May 2013 08:36:34 GMT
Hi Tudor -

Provisionr supports custom AMIs. You can use the --image-id option on the
provisionr:create command or SoftwareBuilder.imageId if you are using the
Java API.

Make sure you also set the right region for the custom AMI ID in
org.apache.provisionr.amazon.cfg

Cheers,

-- Andrei Savu / axemblr.com


On Tue, May 21, 2013 at 10:55 AM, Tudor Rogoz <rogoz@adobe.com> wrote:

> Hi,
>
> There is the possibility to select a different ami image for the ec2
> instances?
> The problem that I have is that I want to create a pool of instances, each
> having several EBS volumes attached.The default image that provisioner uses
> (on us-west-2 region in my case) is ami-3e4fc10e which doesn't support ebs
> mapping on startup [0].I manually tried to create this kind of instance,
> but with a different ami, and works, so having the possibility to change
> the ami id from provisionr will solve the issue.
>
> [0]  AWS Error Code: UnsupportedOperation, AWS Error Message: EBS block
> device mappings not supported for instance-store AMIs
>
> Thanks,
> Tudor
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message