<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">I suggest option A.<o:p></o:p></p>
<p class="MsoNormal">We are facing a similar transition and are going with a new cluster and then 4.x cluster to 5.x cluster migration of existing data. An extra wrinkle for us is we are going to join some of the old hardware to the new cluster once it is free
of serving current data.<o:p></o:p></p>
<p class="MsoNormal">Main reasoning of the new cluster for us is to be able to make a fully V19+ filesystem with sub-block allocation.<o:p></o:p></p>
<p class="MsoNormal">Our understanding from talking to IBM is that there is no way to upgrade a pool to be SBA-compatible, nor is it advisable to try to create a new pool or filesystem in same cluster and then migrate (partially because migrating between filesystems
within a cluster with afm would require going through nfs stack afaik).<o:p></o:p></p>
<p class="MsoNormal">Option B would be much less work and work fine if you are not concerned with things like sub-block allocation that can’t be gained easily with an in-place upgrade.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal">Chris<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black"><gpfsug-discuss-bounces@spectrumscale.org> on behalf of Mark Bush <Mark.Bush@siriuscom.com><br>
<b>Reply-To: </b>gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br>
<b>Date: </b>Friday, March 29, 2019 at 12:11 PM<br>
<b>To: </b>"gpfsug-discuss@spectrumscale.org" <gpfsug-discuss@spectrumscale.org><br>
<b>Subject: </b>[gpfsug-discuss] A net new cluster<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">So I have an ESS today and it’s nearing end of life (just our own timeline/depreciation etc) and I will be purchasing a new ESS. I’m working through the logistics of this. Here is my thinking so far:<o:p></o:p></p>
<p class="MsoNormal">This is just a big Data Lake and not an HPC environment<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Option A<o:p></o:p></p>
<p class="MsoNormal">Purchase new ESS and set it up as a new cluster<o:p></o:p></p>
<p class="MsoNormal">Remote mount old cluster and copy data (rsync or AFM)<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Option B<o:p></o:p></p>
<p class="MsoNormal">Purchase new ESS and set it up to join the old cluster same filesystems<o:p></o:p></p>
<p class="MsoNormal">Evacuate old NSDs and expel Old nodes<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Option C<o:p></o:p></p>
<p class="MsoNormal">Purchase new ESS and set it up as a new cluster<o:p></o:p></p>
<p class="MsoNormal">Point all new data to new cluster and age out old cluster over time (leverage TCT or Archive)<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Any/All feedback welcome<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Mark<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure
under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication
in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you.
<o:p></o:p></p>
</div>
<hr>
<div style="font-size:7.5pt; font-family: arial; font-style:normal; font-weight:normal; ">
This message is for the recipient’s use only, and may contain confidential, privileged or protected information. Any unauthorized use or dissemination of this communication is prohibited. If you received this message in error, please immediately notify the
sender and destroy all copies of this message. The recipient should check this email and any attachments for the presence of viruses, as we accept no liability for any damage caused by any virus transmitted by this email.</div>
</body>
</html>