[gpfsug-discuss] GPFS Encryption
Gareth Horton
G.Horton at bham.ac.uk
Mon Mar 26 12:25:26 BST 2018
Hi. All,
I would be interested to hear if any members have experience implementing Encryption?, any gotchas, tips or any other information which may help with the preparation and implementation stages would be appreciated.
I am currently reading through the documentation and reviewing the preparation steps, and with a scheduled maintenance window on the horizon it would be a good opportunity to carry out any preparatory steps requiring an outage.
If there are any aspects of the configuration which in hindsight could have been done at the preparation stage this would be especially useful.
Many Thanks
Gareth
----------------------
On 24/03/2018, 12:00, "gpfsug-discuss-bounces at spectrumscale.org on behalf of gpfsug-discuss-request at spectrumscale.org" <gpfsug-discuss-bounces at spectrumscale.org on behalf of gpfsug-discuss-request at spectrumscale.org> wrote:
Send gpfsug-discuss mailing list submissions to
gpfsug-discuss at spectrumscale.org
To subscribe or unsubscribe via the World Wide Web, visit
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
or, via email, send a message with subject or body 'help' to
gpfsug-discuss-request at spectrumscale.org
You can reach the person managing the list at
gpfsug-discuss-owner at spectrumscale.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of gpfsug-discuss digest..."
Today's Topics:
1. Reminder - SSUG-US Spring meeting - Call for Speakers and
Registration (Oesterlin, Robert)
2. Pool layoutMap option changes following GPFS upgrades
(Caron, Paul)
----------------------------------------------------------------------
Message: 1
Date: Fri, 23 Mar 2018 12:59:51 +0000
From: "Oesterlin, Robert" <Robert.Oesterlin at nuance.com>
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: [gpfsug-discuss] Reminder - SSUG-US Spring meeting - Call for
Speakers and Registration
Message-ID: <28FF6725-9698-4F68-BC4E-BBCD6164BB3D at nuance.com>
Content-Type: text/plain; charset="utf-8"
Reminder: The registration for the Spring meeting of the SSUG-USA is now open. This is a Free two-day and will include a large number of Spectrum Scale updates and breakout tracks.
Please note that we have limited meeting space so please register early if you plan on attending. If you are interested in presenting, please contact me. We do have a few more slots for user presentations ? these do not need to be long.
You can register here:
https://www.eventbrite.com/e/spectrum-scale-gpfs-user-group-us-spring-2018-meeting-tickets-43662759489
DATE AND TIME
Wed, May 16, 2018, 9:00 AM ?
Thu, May 17, 2018, 5:00 PM EDT
LOCATION
IBM Cambridge Innovation Center
One Rogers Street
Cambridge, MA 02142-1203
Bob Oesterlin
Sr Principal Storage Engineer, Nuance
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20180323/824dbcdc/attachment-0001.html>
------------------------------
Message: 2
Date: Fri, 23 Mar 2018 20:10:05 +0000
From: "Caron, Paul" <Paul.Caron at sig.com>
To: "gpfsug-discuss at spectrumscale.org"
<gpfsug-discuss at spectrumscale.org>
Subject: [gpfsug-discuss] Pool layoutMap option changes following GPFS
upgrades
Message-ID: <980f9a27290342e28197154b924d0abf at msx.bala.susq.com>
Content-Type: text/plain; charset="us-ascii"
Hi,
Has anyone run into a situation where the layoutMap option for a pool changes from "scatter" to "cluster" following a GPFS software upgrade? We recently upgraded a file system from 3.5.0.21, to 4.1.1.17, and finally to 4.2.3.6. We noticed that the layoutMap option for two of our pools changed following the upgrades. We didn't recreate the file system or any of the pools. Further lab testing has revealed that the layoutMap option change actually occurred during the first upgrade to 4.1.1.17, and it was simply carried forward to 4.2.3.6. We have a PMR open with IBM on this problem, but they have told us that layoutMap option changes are impossible for existing pools, and that a software upgrade couldn't do this. I sent the results of my lab testing today, so I'm hoping to get a better response.
We would rather not have to recreate all the pools, but it is starting to look like that may be the only option to fix this. Also, it's unclear if this could happen again during future upgrades.
Here's some additional background.
* The "-j" option for the file system is "cluster"
* We have a pretty small cluster; just 13 nodes
* When reproducing the problem, we noted that the layoutMap option didn't change until the final node was upgraded
* The layoutMap option changed before running the "mmchconfig release=LATEST" and "mmchfs <fs> -V full" commands, so those don't seem to be related to the problem
Thanks,
Paul C.
SIG
________________________________
IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20180323/181b0ac7/attachment-0001.html>
------------------------------
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
End of gpfsug-discuss Digest, Vol 74, Issue 45
**********************************************
More information about the gpfsug-discuss
mailing list