Deploying units with a specific AMI
Francis J. Lacoste
francis.lacoste at canonical.com
Thu Apr 26 20:04:59 UTC 2012
On 12-04-26 03:47 PM, Graham Binns wrote:
> Hi all,
>
> Long story short: I'd like to be able to launch Juju nodes on EC2
> using a specific AMI. I know I used to be able to do this by setting
> default-image-id in my environments.yaml, but this now causes Juju to
> shout at me and then exit. Clint mentioned that he thought there was a
> way to use default-image-id still, but he couldn't recall it. Does
> anyone know what it might be?
>
> To save bikeshedding, I know that this is not the best way to do
> things. I'm looking to solve a particular problem and whilst there are
> other, more elegant solutions I'd quite like to know if my original,
> ugly solution could actually work.
>
juju bootstrap --constraints instance-type=XXX
All future deploy not specifying an instance-type constraints will use
that one.
Cheers
--
Francis J. Lacoste
francis.lacoste at canonical.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/juju/attachments/20120426/14208c0e/attachment.pgp>
More information about the Juju
mailing list