I believe there is work being done so that you can do "juju get" and send that output directly into "juju set" or even "juju deploy --config". And I think that's a much better story around repeatable deployments than trying to make sure the defaults never change. If they really care about repeatable they're probably going to pin the version of the charm anyway.
So I'd bias clearly on the "fix something that isn't working well" rather than "fear change because someone might depend on the current sketchy behaviour". Obviously the call is somewhat situational. John =:-> On Aug 13, 2015 10:03 AM, "Jorge O. Castro" <jo...@ubuntu.com> wrote: > Hi everyone, > > See: https://bugs.launchpad.net/bugs/1373862 > > This morning Marco proposed that we change the default dataset-size > from "80%" of the memory to "128M". > > Ryan thinks that before we make a default change like this that we > should discuss the implications, for example, if you have an existing > Juju MySQL deployment, and say you want to replicate that in another > environment, the default change is an unexpected surprise to the user. > > I am of the opinion that MySQL is one of the first services people > play with when trying Juju and that the charm not working ootb with > the local provider is a big papercut we'd like to fix. > > > > -- > Jorge Castro > Canonical Ltd. > http://juju.ubuntu.com/ - Automate your Cloud Infrastructure > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
