My first suggestion is: Don’t deploy the CES nodes manually – way to many package dependencies. Get those setup right and the installer does a good job. If you go through and define your cluster nodes to the installer, you can do a GPFS upgrade that way. I’ve run into some issues, especially with clone OS versions of RedHat. (ie, CentOS) It doesn’t give you a whole lot of control over what it does – give it a ty and it may work well for you. But run it in a test cluster first or on a limited set of nodes. Bob Oesterlin Sr Storage Engineer, Nuance HPC Grid 507-269-0413 From: <gpfsug-discuss-bounces at spectrumscale.org<mailto:gpfsug-discuss-bounces at spectrumscale.org>> on behalf of Matt Weil <mweil at genome.wustl.edu<mailto:mweil at genome.wustl.edu>> Reply-To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org<mailto:gpfsug-discuss at spectrumscale.org>> Date: Wednesday, March 16, 2016 at 12:36 PM To: "gpfsug-discuss at spectrumscale.org<mailto:gpfsug-discuss at spectrumscale.org>" <gpfsug-discuss at spectrumscale.org<mailto:gpfsug-discuss at spectrumscale.org>> Subject: Re: [gpfsug-discuss] 4.2 installer We have multiple clusters with thousands of nsd's surely there is an upgrade path. Are you all saying just continue to manually update nsd servers and manage them as we did previously. Is the installer not needed if there are current setups. Just deploy CES manually? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160316/0c0866ee/attachment.html>