[prev in list] [next in list] [prev in thread] [next in thread]
List: beowulf
Subject: Fwd: [Beowulf] Configuration change monitoring
From: Walid <walid.shaari () gmail ! com>
Date: 2007-08-30 18:23:56
Message-ID: ab41db6e0708301123s3be2cac1h8c7336490049cb53 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
---------- Forwarded message ----------
From: Walid <walid.shaari@gmail.com>
Date: Aug 30, 2007 9:22 PM
Subject: Re: [Beowulf] Configuration change monitoring
To: "Robert G. Brown" <rgb@phy.duke.edu>
Hi Robert
On 8/30/07, Robert G. Brown <rgb@phy.duke.edu> wrote:
> To amplify Mark's remark a bit -- linux in general already has many
> fairly powerful tools for DOING monitoring, updates, and so on. For
> example, one can use e.g. yum, kickstart, apt, and more to install a
> "canned" node configuration and keep it up to date. It is so totally
> automatic that there is basically no need to "check for inconsistencies"
> on a node. Warewulf and several other tools also permit one to have
> rigorous control over node configuration.
Some of the inconsistencies we see is usually when one of the admin choses
the easy routes, and does changes manually to a set of nodes, and does not
update the installation files (our installations are rpm kickstart based),
others are becuase we manage quite a large variants and by mistake or
intention configurations files that are not supposed to be on cluster A
appears on Cluster B.
Monitoring tools abound, of course, ranging from things like syslog-ng
> for centralized monitoring/logging of LAN systems activity to nightly
> ... ...
> Is there something else one needs to do? Well, most cluster admins tend
> to be fairly skilled linux administrators and good at shell script magic
> or even real programming. So if one has an edge-case need that isn't
> directly met by one of the available tools, it is usually a fairly
> simple matter to hack out a script to accomplish it.
That is one reason why they want to push some commercial tools, They want
to minimize the amount of customizations that are done locally by the team,
as some writes in bash, another writes in Perl, and the other prefers
Python, in the long run there is an issue of maintaining the scripts, and
knowing which set of scripts belongs to which cluster, and what kind of
modifications are needed for new clusters,.etc all of which is documented,
but that is another story
regards
Walid
[Attachment #5 (text/html)]
---------- Forwarded message ----------<br><span class="gmail_quote">From: <b \
class="gmail_sendername">Walid</b> <<a \
href="mailto:walid.shaari@gmail.com">walid.shaari@gmail.com</a>><br>Date: Aug 30, \
2007 9:22 PM<br>Subject: Re: [Beowulf] Configuration change monitoring <br>To: \
"Robert G. Brown" <<a \
href="mailto:rgb@phy.duke.edu">rgb@phy.duke.edu</a>><br><br></span>Hi \
Robert<br><br><div><span class="q"><span class="gmail_quote">On 8/30/07, <b \
class="gmail_sendername">Robert G. Brown </b> <<a href="mailto:rgb@phy.duke.edu" \
target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)">rgb@phy.duke.edu</a>> \
wrote:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid \
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
To amplify Mark's remark a bit -- linux in general already has many<br>fairly \
powerful tools for DOING monitoring, updates, and so on. For<br>example, \
one can use e.g. yum, kickstart, apt, and more to install a<br>"canned" \
node configuration and keep it up to date. It is so totally <br>automatic \
that there is basically no need to "check for inconsistencies"<br>on a \
node. Warewulf and several other tools also permit one to have<br>rigorous control \
over node configuration.</blockquote></span> <div><br>
Some of the inconsistencies we see is usually when one of the admin choses the easy \
routes, and does changes manually to a set of nodes, and does not update the \
installation files (our installations are rpm kickstart based), others are becuase we \
manage quite a large variants and by mistake or intention configurations files that \
are not supposed to be on cluster A appears on Cluster B. <br></div><br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"><span class="q">Monitoring tools abound, of course, \
ranging from things like syslog-ng <br>for centralized monitoring/logging of LAN \
systems activity to nightly <br></span>... ...<span class="q"><br>Is there something \
else one needs to do? Well, most cluster admins tend<br>to be fairly \
skilled linux administrators and good at shell script magic<br>or even real \
programming. So if one has an edge-case need that isn't <br>directly \
met by one of the available tools, it is usually a fairly<br>simple matter to hack \
out a script to accomplish it. </span></blockquote><div><br>That is one reason why \
they want to push some commercial tools, They want to minimize the amount of \
customizations that are done locally by the team, as some writes in bash, another \
writes in Perl, and the other prefers Python, in the long run there is an issue of \
maintaining the scripts, and knowing which set of scripts belongs to which cluster, \
and what kind of modifications are needed for new clusters,.etc all of which is \
documented, but that is another story \
<br></div><br>regards<br><br>Walid<br></div><br>
_______________________________________________
Beowulf mailing list, Beowulf@beowulf.org
To change your subscription (digest mode or unsubscribe) visit \
http://www.beowulf.org/mailman/listinfo/beowulf
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic