[sle-beta] SLE-Beta SLES12-SP3 Beta Migration - S390x

Waite, Dick (External) Dick.Waite at softwareag.com
Mon May 22 02:14:17 MDT 2017

Grand New Monday,

I updated four s390x machines this morning to SLES12 SP-3 Beta-3. No issues seen on the update or basic IVP’s

90% of my machines are virtual, so I have a “checkpoint” safety net at the last GA point.

I have found that:
zipper migration –query   run and seems to “Tidy-up” and re-build the SUSE repository environment, and then lets you know there is no action to take.

I then run:
zypper dup –details –l and this does the update from Beta-n to Beta-n+1 and so far this has been good builds…

I do have a Check Point at SP-2 GA so maybe that is not a good path for physical machines.

So now time for a bit more than basic IVP’s and of course some “KDE” updates…



From: Waite, Dick (External)
Sent: Freitag, 19. Mai 2017 14:55
To: Vincent Moutoussamy
Cc: sle-beta at lists.suse.com
Subject: RE: [sle-beta] SLE-Beta SLES12-SP3 Beta Migration - S390x

Many Thanks Vincent. Understand your reasons.

I'm happy to go from my checkpoint at SP2 GA with Migration to the new target, Beta-n or RC-n For my environment that works well and as you say we are not required to "check" a Beta-n to Beta-n+1

From: Vincent Moutoussamy [vmoutoussamy at suse.com]
Sent: 19 May 2017 12:18
To: Waite, Dick (External)
Cc: sle-beta at lists.suse.com<mailto:sle-beta at lists.suse.com>
Subject: Re: [sle-beta] SLE-Beta SLES12-SP3 Beta Migration - S390x

On 18 May 2017, at 19:07, Waite, Dick (External) <Dick.Waite at softwareag.com<mailto:Dick.Waite at softwareag.com>> wrote:


As a DUP update from beta-n to beta-n+1 is not an official update, SUSE only support a new install from beta-n to Beta-n+1, which from my point of view seems odd. If I have the configuration I want for this virtual machine it seem logical to me that I should be able to "update"... Maybe a few words on why a beta-n to beta-n+1 is an issue, maybe others would like to know too ?

Why don’t we support updating/upgrading from SLE beta-n to beta-n+x ?
Because we need the flexibility of doing important/disruptive changes to
packages, like upgrading/downgrading to different version without taking care of
supporting it.

So for instance, we can move forward with SLE Beta-n+4 without even think about
upgrading SLE Beta-n to SLE Beta-n+4 and take care of all the changes between
these versions. At the end of the day we only care about migrating from
the previous SLE to SLE Beta-n+4.

Changes between SLE Beta might not be like regular updates we make in official
SLE SP released. Since our customers might not face this kind of changes with
official SLE SP in production it seems useless to take extra care on supporting
this for our Beta Phase. And this allow us to focus on more important aspects
for the final version of the SLE SP we are preparing during the beta program.

Don’t forget that support also means to dedicated QA resources (humans and
machines) for various scenarios.

I didn't go into much details but I hope you understand our points.

Anyway as you say, I can always run a supported zypper migration from SP-2 GA to each Beta and RC and GMC

Many thanks to the team, SP-3 has gone very well to-date, lets keep the fingers crossed.

Great to hear, thanks!

Have a nice day,
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager

Software AG – Sitz/Registered office: Uhlandstraße 12, 64297 Darmstadt, Germany – Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20170522/2ce0447c/attachment.htm>

More information about the sle-beta mailing list