[gpfsug-discuss] GPFS update path 4.1.1 -> 4.2.3

Wed May 31 10:33:29 BST 2017

Thank you very much - that’s very helpful and will save us a lot of effort :)

Best regards,
Tomasz Wolski

From: gpfsug-discuss-bounces at spectrumscale.org [mailto:gpfsug-discuss-bounces at spectrumscale.org] On Behalf Of Achim Rehor
Sent: Tuesday, May 30, 2017 9:42 AM
To: gpfsug main discussion list
Subject: Re: [gpfsug-discuss] GPFS update path 4.1.1 -> 4.2.3

The statement was always to be release n-1 compatible. with release being (VRMF) 4.2.3.0

so all 4.2 release levels ought to be compatible with all 4.1 levels.

As Felipe pointed out below, the mmchconfig RELEASE=latest will not touch the filesystem level.
And if you are running remote clusters, you need to be aware, that lifting a filesystem to the latest level (mmchfs <fs-name> -V full)
you will loose remote clusters mount ability if they are on a lower level. in these cases use the -V compat flag (and see commands refernce for details)

Mit freundlichen Grüßen / Kind regards

Achim Rehor

________________________________

Software Technical Support Specialist AIX/ Emea HPC Support

[cid:image001.gif at 01D2DA01.B94BC9E0]

IBM Certified Advanced Technical Expert - Power Systems with AIX

TSCC Software Service, Dept. 7922

Global Technology Services

________________________________

Phone:

+49-7034-274-7862

 IBM Deutschland

E-Mail:

Achim.Rehor at de.ibm.com<mailto:Achim.Rehor at de.ibm.com>

 Am Weiher 24

 65451 Kelsterbach

 Germany

________________________________

IBM Deutschland GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Martina Koederitz (Vorsitzende), Reinhard Reschke, Dieter Scholz, Gregor Pillen, Ivo Koerner, Christian Noll
Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, HRB 14562 WEEE-Reg.-Nr. DE 99369940

From:        "Felipe Knop" <knop at us.ibm.com<mailto:knop at us.ibm.com>>
To:        gpfsug main discussion list <gpfsug-discuss at spectrumscale.org<mailto:gpfsug-discuss at spectrumscale.org>>
Date:        05/30/2017 04:54 AM
Subject:        Re: [gpfsug-discuss] GPFS update path 4.1.1 -> 4.2.3
Sent by:        gpfsug-discuss-bounces at spectrumscale.org<mailto:gpfsug-discuss-bounces at spectrumscale.org>

________________________________

Tomasz,

The statement below from "Concepts, Planning and Installation Guide"  was found to be incorrect and is being withdrawn from the publications.  The team is currently working on improvements to the guidance being provided for migration.

For a cluster which is not running protocols like NFS/SMB/Object,  migration of nodes one-at-a-time from 4.1.1 to 4.2.3 should work.  Once all nodes are migrated to 4.2.3, command

mmchconfig release=LATEST

can be issued to move the cluster to the 4.2.3 level.   Note that the command above will not change the file system level. The file system can be moved to the latest level with command

mmchfs file-system-name -V full

In other words: can two nodes, one with GPFS version 4.1.1 and the other with version 4.2.3, coexist in the cluster, where nodes have not been migrated to 4.2.3 (i.e. filesystem level is still at version 4.1.1)?

That is expected to work.

 Felipe

----
Felipe Knop                                     knop at us.ibm.com<mailto:knop at us.ibm.com>
GPFS Development and Security
IBM Systems
IBM Building 008
2455 South Rd, Poughkeepsie, NY 12601
(845) 433-9314  T/L 293-9314

From:        "Tomasz.Wolski at ts.fujitsu.com<mailto:Tomasz.Wolski at ts.fujitsu.com>" <Tomasz.Wolski at ts.fujitsu.com<mailto:Tomasz.Wolski at ts.fujitsu.com>>
To:        "gpfsug-discuss at spectrumscale.org<mailto:gpfsug-discuss at spectrumscale.org>" <gpfsug-discuss at spectrumscale.org<mailto:gpfsug-discuss at spectrumscale.org>>
Date:        05/29/2017 04:24 PM
Subject:        [gpfsug-discuss] GPFS update path 4.1.1 -> 4.2.3
Sent by:        gpfsug-discuss-bounces at spectrumscale.org<mailto:gpfsug-discuss-bounces at spectrumscale.org>
________________________________

Hello,

We are planning to integrate new IBM Spectrum Scale version 4.2.3 into our software, but in our current software release we have version 4.1.1 integrated. We are worried how would node-at-a-time updates look like when our customer wanted to update his cluster from 4.1.1 to 4.2.3 version.
According to “Concepts, Planning and Installation Guide” (for 4.2.3), there’s a limited compatibility between two GPFS versions and if they’re not adjacent, then following update path is advised:

“If you want to migrate to an IBM Spectrum Scale version that is not an adjacent release of your current
version (for example, version 4.1.1.x to version 4.2.3), you can follow this migration path depending on
your current version:
V 3.5 > V 4.1.0.x > V 4.1.1.x > V 4.2.0.x > V 4.2.1.x > V 4.2.2.x > V 4.2.3.x”

My question is: is the above statement true even though on nodes where new GPFS 4.2.3 is installed these nodes will not be migrated to latest release with “mmchconfig release=LATEST” until all nodes in the cluster will have been updated to version 4.2.3?
In other words: can two nodes, one with GPFS version 4.1.1 and the other with version 4.2.3, coexist in the cluster, where nodes have not been migrated to 4.2.3 (i.e. filesystem level is still at version 4.1.1)?

Best regards,
Tomasz Wolski

With best regards / Mit freundlichen Grüßen / Pozdrawiam

Tomasz Wolski
Development Engineer
NDC Eternus CS HE (ET2)
[cid:image002.gif at 01CE62B9.8ACFA960]
FUJITSU
Fujitsu Technology Solutions Sp. z o.o.
Textorial Park Bldg C, ul. Fabryczna 17
90-344 Lodz, Poland
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170531/cfef171d/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 7182 bytes
Desc: image001.gif
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170531/cfef171d/attachment-0004.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 2774 bytes
Desc: image002.gif
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170531/cfef171d/attachment-0005.gif>