<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;">Thank you for the detailed answer Andrew.
<div>I do understand that anything above the posix level will not be supported by IBM and might lead to scaling/other issues.</div>
<div>We will start small, and discuss with IBM representative on any other possible efforts.</div>
<div><br /></div>
<div>Regards,</div>
<div>Lohit</div>
</div>
<div name="messageReplySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;"><br />
On May 15, 2018, 10:39 PM -0400, Andrew Beattie <abeattie@au1.ibm.com>, wrote:<br />
<blockquote type="cite" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #1abc9c;">
<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10.5pt">
<div dir="ltr">Lohit,</div>
<div dir="ltr"> </div>
<div dir="ltr">There is no technical reason why if you use the correct licensing that you can't publish a Posix fileystem using external Protocol tool rather than CES</div>
<div dir="ltr">the key thing to note is that if its not the IBM certified solution that IBM support stops at the Posix level and the protocol issues are your own to resolve.</div>
<div dir="ltr"> </div>
<div dir="ltr">The reason we provide the CES environment is to provide a supported architecture to deliver protocol access, does it have some limitations - certainly</div>
<div dir="ltr">but it is a supported environment. Moving away from this moves the risk onto the customer to resolve and maintain.</div>
<div dir="ltr"> </div>
<div dir="ltr">The other part of this, and potentially the reason why you might have been warned off using an external solution is that not all systems provide scalability and resiliency</div>
<div dir="ltr">so you may end up bumping into scaling issues by building your own environment --- and from the sound of things this is a large complex environment. These issues are clearly defined in the CES stack and are well understood. moving away from this will move you into the realm of the unknown -- again the risk becomes yours.</div>
<div dir="ltr"> </div>
<div dir="ltr">it may well be worth putting a request in with your local IBM representative to have IBM Scale protocol development team involved in your design and see what we can support for your requirements.</div>
<div dir="ltr">
<div> </div>
<div>Regards,</div>
<div>
<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt">
<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt">
<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt">
<div dir="ltr" style="margin-top: 20px;">
<div style="font-size: 12pt; font-weight: bold; font-family: sans-serif; color: #7C7C5F;">Andrew Beattie</div>
<div style="font-size: 10pt; font-weight: bold; font-family: sans-serif;">Software Defined Storage - IT Specialist</div>
<div style="font-size: 8pt; font-family: sans-serif; margin-top: 10px;">
<div><span style="font-weight: bold; color: #336699;">Phone:</span> 614-2133-7927</div>
<div><span style="font-weight: bold; color: #336699;">E-mail:</span> <a href="mailto:abeattie@au1.ibm.com" style="color: #555">abeattie@au1.ibm.com</a></div>
</div>
</div>
</div>
</div>
</div>
</div>
<div> </div>
<div> </div>
<blockquote data-history-content-modified="1" data-history-expanded="1" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #e67e22;">----- Original message -----<br />
From: valleru@cbio.mskcc.org<br />
Sent by: gpfsug-discuss-bounces@spectrumscale.org<br />
To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br />
Cc:<br />
Subject: Re: [gpfsug-discuss] SMB server on GPFS clients and Followsymlinks<br />
Date: Wed, May 16, 2018 12:25 PM<br />
<div name="messageBodySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;">Thanks Stephen,
<div> </div>
<div>Yes i do acknowledge, that it will need a SERVER license and thank you for reminding me.</div>
<div> </div>
<div>I just wanted to make sure, from the technical point of view that we won’t face any issues by exporting a GPFS mount as a SMB export.</div>
<div> </div>
<div>I remember, i had seen in documentation about few years ago that it is not recommended to export a GPFS mount via Third party SMB services (not CES). But i don’t exactly remember why.</div>
<div> </div>
<div>Regards,</div>
<div>Lohit</div>
</div>
<div name="messageReplySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;"><br />
On May 15, 2018, 10:19 PM -0400, Stephen Ulmer <ulmer@ulmer.org>, wrote:
<blockquote style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #3498db;" type="cite">
<div>Lohit,</div>
<div> </div>
Just be aware that exporting the data from GPFS via SMB requires a SERVER license for the node in question. You’ve mentioned client a few times now. :)
<div>
<div>
<div>-- <br />
Stephen<br />
<br />
</div>
</div>
<div>
<blockquote style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #d35400;" type="cite">
<div>On May 15, 2018, at 6:48 PM, Lohit Valleru <<a href="mailto:valleru@cbio.mskcc.org" target="_blank">valleru@cbio.mskcc.org</a>> wrote:</div>
<div>
<div>
<div name="messageBodySection">Thanks Christof.<br />
<br />
The usecase is just that : it is easier to have symlinks of files/dirs from various locations/filesystems rather than copying or duplicating that data.<br />
<br />
The design from many years was maintaining about 8 PB of NFS filesystem with thousands of symlinks to various locations and the same directories being exported on SMB.<br />
<br />
Now we are migrating most of the data to GPFS keeping the symlinks as they are.<br />
Thus the need to follow symlinks from the GPFS filesystem to the NFS Filesystem.<br />
The client wants to effectively use the symlinks design that works when used on Linux but is not happy to hear that he will have to redo years of work just because GPFS does not support the same.<br />
<br />
I understand that there might be a reason on why CES might not support this, but is it an issue if we run SMB server on the GPFS clients to expose a read only or read write GPFS mounts?</div>
<div name="messageSignatureSection"><br />
Regards,<br />
<br />
Lohit</div>
<div name="messageReplySection"><br />
On May 15, 2018, 6:32 PM -0400, Christof Schmitt <<a href="mailto:christof.schmitt@us.ibm.com" target="_blank">christof.schmitt@us.ibm.com</a>>, wrote:
<blockquote style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #34495e;" type="cite">
<div dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:9pt">
<div dir="ltr">> I could use CES, but CES does not support follow-symlinks outside respective SMB export.</div>
<div dir="ltr"> </div>
<div dir="ltr">Samba has the 'wide links' option, that we currently do not test and support as part of the mmsmb integration. You can always open a RFE and ask that we support this option in a future release.</div>
<div dir="ltr"> </div>
<div dir="ltr">> Follow-symlinks is a however a hard-requirement for to follow links outside GPFS filesystems.</div>
<div dir="ltr"> </div>
<div dir="ltr">I might be reading this wrong, but do you actually want symlinks that point to a file or directory outside of the GPFS file system? Could you outline a usecase for that?</div>
<div dir="ltr"><br />
Regards,</div>
<div dir="ltr">
<div dir="ltr" style="font-family:Arial;font-size:10.5pt">
<div dir="ltr"><br />
<font size="2" face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif"><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif">Christof Schmitt || IBM || Spectrum Scale Development || Tucson, AZ<br />
<a href="mailto:christof.schmitt@us.ibm.com" target="_blank">christof.schmitt@us.ibm.com</a> || <a dir="ltr" href="tel:+1-520-799-2469" target="_blank" x-apple-data-detectors="true" x-apple-data-detectors-result="2" x-apple-data-detectors-type="telephone">+1-520-799-2469</a> (T/L: <a dir="ltr" href="tel:321-2469" target="_blank" x-apple-data-detectors="true" x-apple-data-detectors-result="3" x-apple-data-detectors-type="telephone">321-2469</a>)</font></font></div>
</div>
</div>
<div dir="ltr"> </div>
<div dir="ltr"> </div>
<blockquote data-history-content-modified="1" dir="ltr" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #2ecc71;">----- Original message -----<br />
From: <a href="mailto:valleru@cbio.mskcc.org" target="_blank">valleru@cbio.mskcc.org</a><br />
Sent by: <a href="mailto:gpfsug-discuss-bounces@spectrumscale.org" target="_blank">gpfsug-discuss-bounces@spectrumscale.org</a><br />
To: gpfsug main discussion list <<a href="mailto:gpfsug-discuss@spectrumscale.org" target="_blank">gpfsug-discuss@spectrumscale.org</a>><br />
Cc:<br />
Subject: [gpfsug-discuss] SMB server on GPFS clients and Followsymlinks<br />
Date: Tue, May 15, 2018 3:04 PM<br />
<div name="messageBodySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;">Hello All,
<div> </div>
<div>Has anyone tried serving SMB export of GPFS mounts from a SMB server on GPFS client? Is it supported and does it lead to any issues?</div>
<div>I understand that i will not need a redundant SMB server configuration.</div>
<div> </div>
<div>I could use CES, but CES does not support follow-symlinks outside respective SMB export. Follow-symlinks is a however a hard-requirement for to follow links outside GPFS filesystems.</div>
</div>
<div name="messageSignatureSection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;"><br />
Thanks,
<div>Lohit</div>
</div>
<div name="messageReplySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;">
<div> </div>
</div>
<div><font size="2" face="Default Monospace,Courier New,Courier,monospace">_______________________________________________<br />
gpfsug-discuss mailing list<br />
gpfsug-discuss at <a href="http://spectrumscale.org" target="_blank">spectrumscale.org</a><br />
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target="_blank">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></font></div>
</blockquote>
<div dir="ltr"> </div>
</div>
<br />
_______________________________________________<br />
gpfsug-discuss mailing list<br />
gpfsug-discuss at <a href="http://spectrumscale.org" target="_blank">spectrumscale.org</a><br />
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target="_blank">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></blockquote>
</div>
</div>
_______________________________________________<br />
gpfsug-discuss mailing list<br />
gpfsug-discuss at <a href="http://spectrumscale.org" target="_blank">spectrumscale.org</a><br />
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target="_blank">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></div>
</blockquote>
</div>
</div>
_______________________________________________<br />
gpfsug-discuss mailing list<br />
gpfsug-discuss at spectrumscale.org<br />
<span><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target="_blank">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></span></blockquote>
<div> </div>
</div>
<div><font size="2" face="Default Monospace,Courier New,Courier,monospace">_______________________________________________<br />
gpfsug-discuss mailing list<br />
gpfsug-discuss at spectrumscale.org<br />
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target="_blank">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></font></div>
</blockquote>
<div> </div>
</div>
</div>
<br />
_______________________________________________<br />
gpfsug-discuss mailing list<br />
gpfsug-discuss at spectrumscale.org<br />
http://gpfsug.org/mailman/listinfo/gpfsug-discuss<br /></blockquote>
<div></div>
</div>
</body>
</html>