On Mon, Apr 25, 2016 at 6:38 PM, Andrew Wilkins
wrote:
> Whatever we do, #2 should never be optional.
Agreed.
>
> I would like us to have all of #2, #3, #4, #7.
This is my opinion too. Menno suggested another option (call it #8):
a model config setting equivalent to the flag suggested by #7.
On Mon, Apr 25, 2016 at 5:24 PM, Menno Smits wrote:
> A per-model flag which indicates that the model should automatically upgrade
> when the controller does might be nice too (this what #7 means I think?).
I meant a CLI flag for "juju upgrade-juju". If I understood right,
you are suggesting a p
On 26/04/16 17:44, John Meinel wrote:
> How do we get the tools on the new controller? Since we did a fresh
> bootstrap it won't have the old tools cached. Is part of the pre-flight
> migration checks ensuring that the new controller can get the right
> version of tools? How does it work if someon
Hi Everyone,
Just a heads up that I'm merging a PR to rename the create-model command to
add-model to be more consistent in our terminology.
The next 2.0 release will contain this rename, and those of you building
from master will need to use add-model once the PR lands.
Thanks!
-Cheryl
--
Juju
Copying juju list.
On Tue, Apr 26, 2016 at 5:15 PM, Cheryl Jennings <
cheryl.jenni...@canonical.com> wrote:
> Hi Everyone,
>
> Just a heads up that I'm merging a PR to rename the create-model command
> to add-model to be more consistent in our terminology.
>
> The next 2.0 release will contain th
