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
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:
I am tentatively +1 for adding some charm metadata for minimum requirements
for the charm. We could certainly add that kind of information in the
README but having it in the metadata would make it automatic (magic).
José makes a great point about how something like this could increase the
cloud
About immutable configuration parameters. IMHO it'd make a better user
experience if juju added support for them.
It's understandable that the desire is for juju to be a full 'life-cycle'
management interface for the services it deploys, from deployment to operations
and all the way to
