Rolling code upgrade was never support for SMB for the reasons mention in my other email.
 
The change in 5.0 is to enforce this restriction on a code level. The SMB service will refuse to start on a protocol node, if an incompatible version is already running on another node.

Regards,

Christof Schmitt || IBM || Spectrum Scale Development || Tucson, AZ
[email protected]  ||  +1-520-799-2469    (T/L: 321-2469)
 
 
----- Original message -----
From: "Sobey, Richard A" <[email protected]>
Sent by: [email protected]
To: "[email protected]" <[email protected]>, gpfsug main discussion list <[email protected]>
Cc:
Subject: Re: [gpfsug-discuss] wondering about outage free protocols upgrades
Date: Tue, Mar 6, 2018 11:49 AM
 
Thanks for raising this, I was going to ask. The last I heard it was baked into the 5.0 release of Scale but the release notes are eerily quiet on the matter.
 
Would be good to get some input from IBM on this.
 
Richard
 

From: [email protected] <[email protected]> on behalf of [email protected] <[email protected]>
Sent: Friday, March 2, 2018 3:48:44 AM
To: [email protected]
Subject: [gpfsug-discuss] wondering about outage free protocols upgrades
 

Hi All,

               It appears a rolling node by node upgrade of a protocols cluster is not possible. Ctdb is the sticking point as it won’t run with 2 different versions at the same time. Are there any plans to address this and make it a real Enterprise product?

 

Cheers,

 

Greg

 

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

Reply via email to