[gpfsug-discuss] Support for TLS 1.3 to work with SKLM

[Alec]

I'm not sure what it costs.. but I can say for sure that if it's properly
leveraged the money it saves on hardware can be exceptional.

I don't know how to put a value on a technology that has remained the best
solution for so long... We haven't had to reengineer anything to remain top
dog on so many metrics (availability, throughput, enterprise standards,
backups, failover, etc....)

So don't think about the line item cost think of the cost per user, gb,
Gbps, whatever makes you happy to pay it.

｡⁠◕⁠‿⁠◕⁠｡

Alec


On Tue, May 23, 2023, 5:29 PM Ryan Novosielski <novosirj at rutgers.edu> wrote:

> We looked into it, but couldn’t afford the licenses. As it stands now, our
> “standard” licenses (or the Lenovo equivalent — data management, or data
> access? I forget) are apparently about to double in price. Glad to hear
> that if something changed in that area, it works well.
>
> On May 23, 2023, at 17:23, Alec <anacreo at gmail.com> wrote:
>
> For those who don't use GPFS encryption.  I can say the GPFS version is
> fantastic.  Our write performance was nominally faster due to the
> compression of encryption I suppose. But it works flawlessly and at speed.
>
> Alec
>
> On Tue, May 23, 2023, 4:51 PM Ryan Novosielski <novosirj at rutgers.edu>
> wrote:
>
>> Thanks!
>>
>> We don’t use encryption, which is I suppose why I was unfamiliar. Happy
>> to vote for it though.
>>
>> On May 23, 2023, at 16:31, Alec <anacreo at gmail.com> wrote:
>>
>> For GPFS encryption we use an IBM SKLM (Key Server) and it uses SSL
>> certificates for that communication.  The SKLM server needs to provide /
>> use TLS 1.3 SSL to pass our security standards but GPFS doesn't state it
>> will support that.
>>
>> Alec
>>
>> On Tue, May 23, 2023, 3:25 PM Ryan Novosielski <novosirj at rutgers.edu>
>> wrote:
>>
>>> There’s very little detail there. Can you elaborate on what this is
>>> actually for/where it is used in GPFS?
>>>
>>> --
>>> #BlackLivesMatter
>>> ____
>>> || \\UTGERS,
>>>  |---------------------------*O*---------------------------
>>> ||_// the State  |         Ryan Novosielski - novosirj at rutgers.edu
>>> || \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~
>>> RBHS Campus
>>> ||  \\    of NJ  | Office of Advanced Research Computing - MSB
>>> A555B, Newark
>>>      `'
>>>
>>> On May 22, 2023, at 23:16, Alec <anacreo at gmail.com> wrote:
>>>
>>> Hello we are being asked to support TLS 1.3 in our configuration.
>>>
>>> Can I ask that folks upvote this RFE to help get it addressed?
>>>
>>>
>>> https://ibm-sys-storage.ideas.ibm.com/ideas/GPFS-I-964
>>>
>>> Alec
>>> _______________________________________________
>>> gpfsug-discuss mailing list
>>> gpfsug-discuss at gpfsug.org
>>> http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
>>>
>>>
>>> _______________________________________________
>>> gpfsug-discuss mailing list
>>> gpfsug-discuss at gpfsug.org
>>> http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
>>>
>> _______________________________________________
>> gpfsug-discuss mailing list
>> gpfsug-discuss at gpfsug.org
>> http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
>>
>>
>> _______________________________________________
>> gpfsug-discuss mailing list
>> gpfsug-discuss at gpfsug.org
>> http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
>>
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at gpfsug.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
>
>
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at gpfsug.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20230523/de0bb05e/attachment.htm>