Hi Everyone,
Due to a critical bug [0] found in the daily PPA, the release of 2.0-beta9
will be delayed while we test the fix. We are aiming for a release
tomorrow.
Thanks!
-Cheryl
[0] https://bugs.launchpad.net/juju-core/+bug/1592210
On Fri, Jun 10, 2016 at 1:20 PM, Cheryl Jennings <
On 2016-06-13 09:35 AM, Ian Booth wrote:
> $ juju set-model-config foo=bar
>
> That sets foo on the current model. Or
>
> $ juju -m mymodel set-model-config foo=bar
>
> operates on model mymodel.
>
> The above are model commands. So we need a way to set foo=bar on the
> controller
> itself
For JAAS, doesn't a 'default model property' need to be a user level
setting, because it doesn't make sense as at a Controller level because
all-of-JAAS is your Controller (we don't expose the individual controllers).
We should also consider how Migration is impacted by defaults like this.
John
On 14/06/16 08:33, Ian Booth wrote:
>> That's why I prefer:
>>
>> set-controller-config
>> set-model-config
>> set-model-default
>>
> I like the above too. But some folks we've talked to have thought that
> introducing 3 commands (the ones above) is cognitive overhead.
Heh. Ian, if you like,
