It is a nice idea, but it should definitely fire up a warning saying that the machine will have larger specs, as well as asking for confirmation. I don't want to see any surprise charges in my AWS bills!
On 08/27/2014 02:34 AM, Mark Shuttleworth wrote: > On 27/08/14 00:10, Matt Bruzek wrote: >> First and most importantly the hpcc charm deploys according to the readme >> file! I had to increase the memory constraints on the HP-cloud to 4GB per >> machine (juju set-constraints mem=4GB) so all the services had enough >> memory to start up. After that I was able to cluster by adding units of >> hpcc. > > We have a couple of charms which break on tiny instances on some clouds > because of this sort of disconnect. Would it be helpful to be able to > encode minimum requirements in the charm metadata? > > Obviously, real requirements are configuration and load dependent, but I > think we could avoid the obvious "try it then debug it" cycle if we had > some explicit minimum requirements up front. > > Thanks for the review commentary and advice to charmers! > > Mark > -- José Antonio Rey -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
