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
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 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, 2:38 PM Andrew Wilkins
> mailto:andrew.wilk...@canonical.com>>
wrote:
>
> On Sat, Apr 23, 2016 at 4:15 AM Eric Snow <mailto:eric.s...@canonical.com>> wrote:
>
> In a recent bug I was working on the issue of auto-upgrading
models
>
AM Eric Snow <mailto:eric.s...@canonical.com>> wrote:
>
> In a recent bug I was working on the issue of auto-upgrading models
> came up. I also ran into this personally not too long ago.
> Currently, running "juju upgrade-juju -m admin --upload-tools"
te:
>
>> In a recent bug I was working on the issue of auto-upgrading models
>> came up. I also ran into this personally not too long ago.
>> Currently, running "juju upgrade-juju -m admin --upload-tools"[1]
>> upgrades the admin model to a new version. To set the
On Sat, Apr 23, 2016 at 4:15 AM Eric Snow wrote:
> In a recent bug I was working on the issue of auto-upgrading models
> came up. I also ran into this personally not too long ago.
> Currently, running "juju upgrade-juju -m admin --upload-tools"[1]
> upgrades the admin
On 26 April 2016 at 02:58, Katherine Cox-Buday <
katherine.cox-bu...@canonical.com> wrote:
> I like #4. I don't think we'd ever want to auto-upgrade all models,
> because having models be isolated from one another is kind of the point.
>
I agree. Remember that in some situations models may have c
I like #4. I don't think we'd ever want to auto-upgrade all models,
because having models be isolated from one another is kind of the point.
On 04/22/2016 03:14 PM, Eric Snow wrote:
> In a recent bug I was working on the issue of auto-upgrading models
> came up. I also ran into
In a recent bug I was working on the issue of auto-upgrading models
came up. I also ran into this personally not too long ago.
Currently, running "juju upgrade-juju -m admin --upload-tools"[1]
upgrades the admin model to a new version. To set the version of any
other model to the up
10 matches
Mail list logo
