Re: proposed changes to lvsd, nanny, pulse: seeking advice
Marek Grac <[email protected]> Wed, 21 Jul 2010 11:37:59 +0200
| Newsgroups | gmane.linux.redhat.piranha |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============5051818119101315363==
Content-Type: multipart/alternative;
boundary="------------010606080703030008070107"
This is a multi-part message in MIME format.
--------------010606080703030008070107
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi,
On 07/20/2010 06:58 AM, Fred Clift wrote:
>
> Hi. My company is using lvs and we've noticed a few issues. We have
> at least one local patch, and plan on making several more.
>
> I cribbed and slightly modified an internal wiki page about our
> proposed changes and bugs.
>
> In particular there is at least one verified bug in lvsd (mis-indexed
> re-read of config file), some missing features (as the documentation
> implies, or is missing -- pulse re-reading the config file, doesn't
> pay attention to the status of it's child lvsd), nanny doesn't check
> it's arguments carefully and may unexpectedly exit etc.
>
> For a full detailed description of all the issues we've found, and for
> our proposed solutions, please see:
>
> http://clift.org/fred/lvs/lvs.html
>
I will check it.
> I have a couple of questions. First, can you direct me to the process
> for submitting patches for lvs/pulse/nanny, and second, are there
> other known issues with these programs that we might likely trip
> over? In particular are there nanny options that currently are
> arguably non-valid parameters (cause immediate nanny exit) -- for
> example, a timeout of 0 is one. Are there others?
>
> Anyway, I'd appreciate anyone's feedback on our proposed changes and
> the patch submission process.
>
>
Please create a bug in bugzilla.redhat.com (components ipvsadm &
piranha). Currently there are two long-term open bugs 'LVS do nothing
when VIP is down' and failure to start nanny kill all running nannies
(mentioned in follow-ups; patch was discussed before and yes it works).
Piranha is now part of fedora, so there is place to put upstream changes
and create packages for other distro if needed. Piranha will work with
SELinux as can be seen in RHEL6 beta (Fedora / RHEL5 will be ready
soon). There is git repo with upstream available:
http://git.fedorahosted.org/git/?p=piranha.git
Patches to this repo does not have to pass RH processes (also no real
QA) but it can be flexible enough.
m,
--------------010606080703030008070107
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Hi,<br>
<br>
On 07/20/2010 06:58 AM, Fred Clift wrote:
<blockquote
cite="mid:D2F744D05ED19D45A4A7757F49274A8B03AFF160@IAD-WPRD-XCHB01.corp.verio.net"
type="cite">
<meta http-equiv="Content-Type"
content="text/html; charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]-->
<div class="WordSection1">
<p class="MsoNormal">Hi. My company is using lvs and we’ve noticed a
few issues. We have at least one local patch, and plan on making
several
more.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I cribbed and slightly modified an internal wiki
page about
our proposed changes and bugs.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In particular there is at least one verified bug
in lvsd (mis-indexed
re-read of config file), some missing features (as the documentation
implies,
or is missing – pulse re-reading the config file, doesn’t pay
attention to the status of it’s child lvsd), nanny doesn’t
check it’s arguments carefully and may unexpectedly exit etc.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For a full detailed description of all the
issues we’ve
found, and for our proposed solutions, please see:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a moz-do-not-send="true"
href="http://clift.org/fred/lvs/lvs.html">http://clift.org/fred/lvs/lvs.html</a><o:p></o:p></p>
</div>
</blockquote>
I will check it.<br>
<br>
<blockquote
cite="mid:D2F744D05ED19D45A4A7757F49274A8B03AFF160@IAD-WPRD-XCHB01.corp.verio.net"
type="cite">
<div class="WordSection1">
<p class="MsoNormal">I have a couple of questions. First, can you
direct me
to the process for submitting patches for lvs/pulse/nanny, and second,
are
there other known issues with these programs that we might likely trip
over? In particular are there nanny options that currently are
arguably
non-valid parameters (cause immediate nanny exit) – for example, a
timeout of 0 is one. Are there others?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Anyway, I’d appreciate anyone’s feedback on our
proposed changes and the patch submission process.<o:p></o:p></p>
</div>
<br>
</blockquote>
Please create a bug in bugzilla.redhat.com (components ipvsadm &
piranha). Currently there are two long-term open bugs 'LVS do nothing
when VIP is down' and failure to start nanny kill all running nannies
(mentioned in follow-ups; patch was discussed before and yes it works).<br>
<br>
Piranha is now part of fedora, so there is place to put upstream
changes and create packages for other distro if needed. Piranha will
work with SELinux as can be seen in RHEL6 beta (Fedora / RHEL5 will be
ready soon). There is git repo with upstream available:
<a class="moz-txt-link-freetext" href="http://git.fedorahosted.org/git/?p=piranha.git">http://git.fedorahosted.org/git/?p=piranha.git</a> <br>
<br>
Patches to this repo does not have to pass RH processes (also no real
QA) but it can be flexible enough. <br>
<br>
m,<br>
<br>
<br>
</body>
</html>
--------------010606080703030008070107--
--===============5051818119101315363==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Piranha-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/piranha-list
--===============5051818119101315363==--