Is upgrade-juju provider/cloud dependant?

[John Meinel]

The steps to upgrade is not changed between providers (though as mentioned
local and manual might be a bit different). However, what *is* different is
the search paths for tools.
If you remember some of our earlier transitions, where we had to have 2
copies of the tools so that (e.g.) the 1.16 tools are where 1.16 wanted
them to be, but they *also* had to be placed where 1.14 could find them so
that it could actually perform the upgrade.
And the location for where to find tools is unique to each cloud, isn't it?

Now, we haven't moved tools in a while, and I don't think we're planning to
move them again. So it is possible that we could drop the redundant tests
at this point. But I think they *did* have usefulness in the past. (In the
case that one of the mirrors wasn't updated in both locations.)

Upgrade *shouldn't* be very slow, so it sounds like something that could
use some investigation to understand why it is being a problem. (Maybe
downloading the new tools is slow, maybe it isn't using a cloud-local
mirror and has to download all the data from streams.canonical.com,
maybe... ?)

John
=:->




On Wed, Jun 18, 2014 at 8:44 AM, Andrew Wilkins <
andrew.wilkins at canonical.com> wrote:

> On Wed, Jun 18, 2014 at 12:27 PM, Curtis Hovey-Canonical <
> curtis at canonical.com> wrote:
>
>> CI tests deploy and upgrade in every CPC because I *think* these two
>> scenario test the provider and the streams that were placed in the
>> clouds. The upgrade test verifies stable juju understands the new
>> streams, can can upgrade to the next juju.
>>
>> But does juju-upgrade have provider nuances? I don't recall seeing
>> upgrade fail in one provider. It fails in all, or it fails for the
>> same reason deploy failed. We have several tests with very slow
>> upgrades.
>>
>
> There is currently a step that only does something for the local provider.
>
>
>> Maybe we only need one upgrade test, and CI can choose the most stable
>> cloud to test that on.
>
>
> I would say test on local and one CPC, maybe manual.
>
>
>>
>> --
>> Curtis Hovey
>> Canonical Cloud Development and Operations
>> http://launchpad.net/~sinzui
>>
>> --
>> Juju-dev mailing list
>> Juju-dev at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>
>
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140618/81bf7bb2/attachment-0001.html>