<html><body><p><font size="2">see below.</font><br><br><font size="2" face="Arial">Steven A. Daniels</font><br><font size="2" face="Arial">Cross-brand Client Architect</font><br><font size="2" face="Arial">Senior Certified IT Specialist</font><br><font size="2" face="Arial">National Programs</font><br><font size="2" face="Arial">Fax and Voice: 3038101229</font><br><a href="mailto:sadaniel@us.ibm.com"><u><font size="2" color="#0000FF" face="Arial">sadaniel@us.ibm.com</font></u></a><br><a href="http://www.ibm.com/"><u><font size="2" color="#0000FF" face="Arial">http://www.ibm.com</font></u></a><br><i>(See attached file: opencits-d.jpg)</i><br><br><img width="16" height="16" src="cid:2__=8FBB0FEBDFEAD9EE8f9e8a93df938690918c8FB@" border="0" alt="Inactive hide details for Prasad Surampudi ---05/29/2020 05:55:20 PM---Steve, So in essence, if the minReleaseLevel is set to 5"><font size="2" color="#424282">Prasad Surampudi ---05/29/2020 05:55:20 PM---Steve, So in essence, if the minReleaseLevel is set to 5.0.x.x for a Spectrum Scale 5.0 cluster, we</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Prasad Surampudi <prasad.surampudi@theatsgroup.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">"gpfsug-discuss@spectrumscale.org" <gpfsug-discuss@spectrumscale.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">05/29/2020 05:55 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">[EXTERNAL] Re: [gpfsug-discuss] gpfsug-discuss Digest, Vol 100, Issue 34</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt><font size="2">Steve,<br><br>So in essence, if the minReleaseLevel is set to 5.0.x.x for a Spectrum Scale 5.0 cluster, we can't add any new severs with Spectrum Scale 4.x.x RPMs installed without upgrading them to Spectrum Scale 5.x.x RPMs to the cluster. Is this a correct statement? </font></tt><br><br><tt><font size="2">Steve>>> This statement is true for the local cluster. However, it is pretty simple to put the 4.2.3-X</font></tt><tt><font size="2"> client nodes(currently 4.2.3.21 is min officially recommended and only until Sep 2020)</font></tt><tt><font size="2"> </font></tt><tt><font size="2">in their own access cluster.</font></tt><br><tt><font size="2"><br>Does mmiportfs also check the filesystem version which it is importing and prevent it from importing if it is created on Spectrum Scale 4.x.x?</font></tt><br><br><tt><font size="2">I hope one of the FS experts can correct if wrong, but it would be in my mind a bug if mmimportfs didn't allow this. I know you can create new 4.2.3-X file systems in a cluster with 5.0.X minReleaseLevel and do that routinely. So, since the cluster supports lower version levels (actually I have one filesystem that is a 3.5.0.7 in a cluster that is 5.0.4.2 minReleaseLevel but obviously 3.5.0.7 wouldn't be anywhere near a recommended filesystm level but it does work fine. NOTE: that the remote cluster will not authenticate unless at a minReleaseLevel of 4.2.2.X (not a supported level) so even though the filesystem can be very back level. The remote accessing cluster has to be no more than one major version back or ahead.<br><br>On 5/29/20, 7:40 PM, "gpfsug-discuss-bounces@spectrumscale.org on behalf of gpfsug-discuss-request@spectrumscale.org" <gpfsug-discuss-bounces@spectrumscale.org on behalf of gpfsug-discuss-request@spectrumscale.org> wrote:<br><br> Send gpfsug-discuss mailing list submissions to<br> gpfsug-discuss@spectrumscale.org<br><br> To subscribe or unsubscribe via the World Wide Web, visit<br> </font></tt><tt><font size="2"><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></font></tt><tt><font size="2"> <br> or, via email, send a message with subject or body 'help' to<br> gpfsug-discuss-request@spectrumscale.org<br><br> You can reach the person managing the list at<br> gpfsug-discuss-owner@spectrumscale.org<br><br> When replying, please edit your Subject line so it is more specific<br> than "Re: Contents of gpfsug-discuss digest..."<br><br><br> Today's Topics:<br><br> 1. Re: gpfsug-discuss Digest, Vol 100, Issue 32 (Steven Daniels)<br><br><br> ----------------------------------------------------------------------<br><br> Message: 1<br> Date: Fri, 29 May 2020 17:39:59 -0600<br> From: "Steven Daniels" <sadaniel@us.ibm.com><br> To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br> Subject: Re: [gpfsug-discuss] gpfsug-discuss Digest, Vol 100, Issue 32<br> Message-ID:<br> <OF747B9ADF.668598B6-ON00258577.008141DC-87258577.00820130@notes.na.collabserv.com><br><br> Content-Type: text/plain; charset="iso-8859-1"<br><br><br> Prasad,<br><br> One of the clients I work with have several 5.0.X ESS (owning) clusters and<br> they share 4.2.3.9 file systems to remote client clusters.<br><br> The minimum release level on the 5.0.X clusters are at the version of the<br> cluster, i.e. 5.0.3 or 5.0.4 (we are in the process of getting all to<br> latest).<br><br> The key is that the clients are not part of this cluster as a node has to<br> be > minReleaseLevel to be able to join.<br><br> They are in their own (accessing) cluster which has a minReleaseLevel of<br> 4.2.3-9. This is the current (until September withdrawal) minReleaseLevel<br> that is supported in this scenario.<br><br> Don't know specifically about import but it should work as long as the<br> clients that need to mount the sub-5.0 filesystem can be in a separate<br> (remote) cluster or the client nodes are upgraded to the minReleaseLevel of<br> the local cluster.<br><br> Thanks,<br> Steve<br><br> Steven A. Daniels<br> Cross-brand Client Architect<br> Senior Certified IT Specialist<br> National Programs<br> Fax and Voice: 3038101229<br> sadaniel@us.ibm.com<br> </font></tt><tt><font size="2"><a href="http://www.ibm.com">http://www.ibm.com</a></font></tt><tt><font size="2"><br> (See attached file: opencits-d.jpg)<br><br><br><br> From: Prasad Surampudi <prasad.surampudi@theatsgroup.com><br> To: "gpfsug-discuss@spectrumscale.org"<br> <gpfsug-discuss@spectrumscale.org><br> Date: 05/29/2020 09:02 AM<br> Subject: [EXTERNAL] Re: [gpfsug-discuss] gpfsug-discuss Digest, Vol 100,<br> Issue 32<br> Sent by: gpfsug-discuss-bounces@spectrumscale.org<br><br><br><br> Jim,<br> The minimum release for 5.0.4 cluster is 5.0.4.3.<br><br> We are aware that we can't merge both gpfs_4 and gpfs_5 filesystems. Our<br> plan is to import the gpfs_4 filesystem into the Spectrum Scale 5.0 cluster<br> (with its NSDs mapped to Spectrum Scale 5.0 clusters nodes) and copy the<br> data using rsync, across fibre channel instead of ethernet to get higher<br> bandwidth.<br><br><br> On 5/29/20, 8:27 AM, "gpfsug-discuss-bounces@spectrumscale.org on behalf of<br> gpfsug-discuss-request@spectrumscale.org"<br> <gpfsug-discuss-bounces@spectrumscale.org on behalf of<br> gpfsug-discuss-request@spectrumscale.org> wrote:<br><br> Send gpfsug-discuss mailing list submissions to<br> gpfsug-discuss@spectrumscale.org<br><br> To subscribe or unsubscribe via the World Wide Web, visit<br><br> </font></tt><tt><font size="2"><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></font></tt><tt><font size="2"><br><br> or, via email, send a message with subject or body 'help' to<br> gpfsug-discuss-request@spectrumscale.org<br><br> You can reach the person managing the list at<br> gpfsug-discuss-owner@spectrumscale.org<br><br> When replying, please edit your Subject line so it is more specific<br> than "Re: Contents of gpfsug-discuss digest..."<br><br><br> Today's Topics:<br><br> 1. Re: Importing a Spectrum Scale a filesystem from 4.2.3<br> cluster to 5.0.4.3 cluster (Carl Zetie - carlz@us.ibm.com)<br><br><br> ----------------------------------------------------------------------<br><br> Message: 1<br> Date: Fri, 29 May 2020 12:25:46 +0000<br> From: "Carl Zetie - carlz@us.ibm.com" <carlz@us.ibm.com><br> To: "gpfsug-discuss@spectrumscale.org"<br> <gpfsug-discuss@spectrumscale.org><br> Subject: Re: [gpfsug-discuss] Importing a Spectrum Scale a filesystem<br> from 4.2.3 cluster to 5.0.4.3 cluster<br> Message-ID: <C3494A35-F482-4E3D-B71D-AD7B3D9B02B1@us.ibm.com><br> Content-Type: text/plain; charset="utf-8"<br><br> On a non-technical note, I wanted to remind everybody that if you?re<br> doing a migration and you need to temporarily run both systems, IBM<br> licensing allows you to do that without ceremony or formality, for up to 90<br> days under a thing called the ?Temporary Additional Use Policy?. You don?t<br> need to register, ask beforehand, etc. Just go ahead.<br><br> If you need the additional usage for more than 90 days, contact your<br> seller and we?ll figure something out.<br><br> Regards<br><br><br><br><br> Carl Zetie<br> Program Director<br> Offering Management<br> Spectrum Scale<br> ----<br> (919) 473 3318 ][ Research Triangle Park<br> carlz@us.ibm.com<br><br> [signature_398516855]<br><br><br> -------------- next part --------------<br> An HTML attachment was scrubbed...<br> URL: <<br> </font></tt><tt><font size="2"><a href="http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20200529/010f20c4/attachment.html">http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20200529/010f20c4/attachment.html</a></font></tt><tt><font size="2"><br> ><br> -------------- next part --------------<br> A non-text attachment was scrubbed...<br> Name: image001.png<br> Type: image/png<br> Size: 69558 bytes<br> Desc: image001.png<br> URL: <<br> </font></tt><tt><font size="2"><a href="http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20200529/010f20c4/attachment.png">http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20200529/010f20c4/attachment.png</a></font></tt><tt><font size="2"><br> ><br><br> ------------------------------<br><br> _______________________________________________<br> gpfsug-discuss mailing list<br> gpfsug-discuss at spectrumscale.org<br><br> </font></tt><tt><font size="2"><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></font></tt><tt><font size="2"><br><br><br><br> End of gpfsug-discuss Digest, Vol 100, Issue 32<br> ***********************************************<br><br> _______________________________________________<br> gpfsug-discuss mailing list<br> gpfsug-discuss at spectrumscale.org<br> </font></tt><tt><font size="2"><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></font></tt><tt><font size="2"><br><br><br><br><br> -------------- next part --------------<br> An HTML attachment was scrubbed...<br> URL: <</font></tt><tt><font size="2"><a href="http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20200529/0c6df3be/attachment.html">http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20200529/0c6df3be/attachment.html</a></font></tt><tt><font size="2"> ><br> -------------- next part --------------<br> A non-text attachment was scrubbed...<br> Name: graycol.gif<br> Type: image/gif<br> Size: 105 bytes<br> Desc: not available<br> URL: <</font></tt><tt><font size="2"><a href="http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20200529/0c6df3be/attachment.gif">http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20200529/0c6df3be/attachment.gif</a></font></tt><tt><font size="2"> ><br> -------------- next part --------------<br> A non-text attachment was scrubbed...<br> Name: opencits-d.jpg<br> Type: image/jpeg<br> Size: 182862 bytes<br> Desc: not available<br> URL: <</font></tt><tt><font size="2"><a href="http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20200529/0c6df3be/attachment.jpg">http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20200529/0c6df3be/attachment.jpg</a></font></tt><tt><font size="2"> ><br><br> ------------------------------<br><br> _______________________________________________<br> gpfsug-discuss mailing list<br> gpfsug-discuss at spectrumscale.org<br> </font></tt><tt><font size="2"><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></font></tt><tt><font size="2"> <br><br><br> End of gpfsug-discuss Digest, Vol 100, Issue 34<br> ***********************************************<br><br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><tt><font size="2"><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></font></tt><tt><font size="2"> <br><br></font></tt><br><br><BR>
</body></html>