Hi Stein This does appear to be a bug in Juju's constraints handling for EC2. I'd have to do an experiment to confirm, but certainly reading the code appears to show a problem.
Given how EC2 works, in that Juju asks for the specified root disk size when starting an instance, I don't have a workaround that I can think of to share with you. The fix for this would be relatively simple to implement and so can be done in time for the next stable release (1.20) which is due in a few weeks. Alternatively, we hope to have a new development release out next week (1.19.3). I'll try to get any fix done in time for that also. I've raised bug 1324729 for this issue. On Fri 30 May 2014 09:29:15 EST, GMail wrote: > Trying to deploy a charm with some extra root disk space. When using the > root-disk constraint defined above I get the following error: > > '(error: no instance types in us-east-1 matching constraints "cpu-power=100 > root-disk=16384M")' > > I’m deploying a bundle with the following constraints: constraints: "mem=4G > arch=amd64”, but need more disk-space then the default provided. > > Any suggestions ? > > > Stein Myrseth > Bjørkesvingen 6J > 3408 Tranby > mob: +47 909 62 763 > mailto:[email protected] > > > > -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
