juju-core bootstrap change

[Ian Booth]

Hi

Once bootstrap is done, the version of tools selected is stored in the 
environment so after upgrading juju it should continue to use 
previously selected tools in any existing environments. But any new 
bootstrapped environments will need the updated tools available.

On Mon 02 Sep 2013 14:26:57 EST, Juan Negron wrote:
> How would this affect private OpenStack users that upgrade juju-core but,
> already have existing environments?
> Would they have to re-deploy after the juju-core update ?
>
> Thanks,
>
> Juan L. Negron <juan.negron at canonical.com>
> Mobile: +1 408 634 0292
> Cloud Architect
> Canonical Technical Services
> Canonical USA
> GPG : 0A62 BC70 5CBC B4DD F3E6  8A27 A6B1 F3F0 E6B5 F5A3
>
>
> On Mon, Sep 2, 2013 at 1:19 PM, Ian Booth <ian.booth at canonical.com> wrote:
>
>> Hi folks
>>
>> If you are running from source, you need to be aware of a change made to
>> trunk
>> and which will be in the next release AFTER 1.13.3.
>> Previously, when juju bootstrapped a new environment, it would be happy if
>> it
>> could find tools which matched the major version number of the juju used to
>> bootstrap. Now, the check has been made stricter and both the major and
>> minor
>> version numbers need to be consistent with the juju version.
>>
>> This change should not have any visible effects for most people;
>> developers tend
>> to --upload-tools and the correct tools are always in place for clouds like
>> Amazon, HP Cloud, Azsure, MAAS etc. Those people running private Openstack
>> deployments need to be aware so that they can ensure their tools
>> repository is
>> up to date (if they do not rely on the S3 public repository).
>>
>> --
>> Juju-dev mailing list
>> Juju-dev at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>
>