<html xmlns:v="urn:schemas-microsoft-com:vml" 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:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="FR-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">IMO, you should keep storhaug and maintain it. At the beginning, we were with pacemaker and corosync. Then we move to storhaug with
the upgrade to gluster 4.1.x. Now you are talking about going back like it was. Maybe it will be better with pacemake and corosync but the important is to have a solution that will be stable and maintained.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">thanks<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Renaud</span><span style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:#4D4D4D"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">De :</span></b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> gluster-users-bounces@gluster.org [mailto:gluster-users-bounces@gluster.org]
<b>De la part de</b> Jim Kinney<br>
<b>Envoyé :</b> 30 avril 2019 08:20<br>
<b>À :</b> gluster-users@gluster.org; Jiffin Tony Thottan <jthottan@redhat.com>; gluster-users@gluster.org; Gluster Devel <gluster-devel@gluster.org>; gluster-maintainers@gluster.org; nfs-ganesha <nfs-ganesha@redhat.com>; devel@lists.nfs-ganesha.org<br>
<b>Objet :</b> Re: [Gluster-users] Proposing to previous ganesha HA cluster solution back to gluster code as gluster-7 feature<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">+1!<br>
I'm using nfs-ganesha in my next upgrade so my client systems can use NFS instead of fuse mounts. Having an integrated, designed in process to coordinate multiple nodes into an HA cluster will very welcome.<o:p></o:p></p>
<div>
<p class="MsoNormal">On April 30, 2019 3:20:11 AM EDT, Jiffin Tony Thottan <<a href="mailto:jthottan@redhat.com">jthottan@redhat.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p>Hi all,<o:p></o:p></p>
<p>Some of you folks may be familiar with HA solution provided for nfs-ganesha by gluster using pacemaker and corosync.<o:p></o:p></p>
<p>That feature was removed in glusterfs 3.10 in favour for common HA project "Storhaug". Even Storhaug was not progressed<o:p></o:p></p>
<p>much from last two years and current development is in halt state, hence planning to restore old HA ganesha solution back<o:p></o:p></p>
<p>to gluster code repository with some improvement and targetting for next gluster release 7.<o:p></o:p></p>
<p>I have opened up an issue [1] with details and posted initial set of patches [2]<o:p></o:p></p>
<p>Please share your thoughts on the same<o:p></o:p></p>
<p>Regards,<o:p></o:p></p>
<p>Jiffin <o:p></o:p></p>
<p>[1]<a href="https://github.com/gluster/glusterfs/issues/663"> https://github.com/gluster/glusterfs/issues/663</a><o:p></o:p></p>
<p>[2] <a href="https://review.gluster.org/#/q/topic:rfc-663+(status:open+OR+status:merged)">
https://review.gluster.org/#/q/topic:rfc-663+(status:open+OR+status:merged)</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><br>
-- <br>
Sent from my Android device with K-9 Mail. All tyopes are thumb related and reflect authenticity.<o:p></o:p></p>
</div>
</body>
</html>