1:30 p.m.
What/how are people monitoring their cobbler servers? particularly if
you have several.
ie, our management is very interested in how long installs take, how
many there are, who is doing them, etc. A lot of that could be gleaned
from a combination of messages, cobblerd.log and the kicklogs.
Anybody have a solution then can share?
----------------------------------------------------------------------
Jim Wildman, CISSP, RHCE jim(a)rossberry.com http://www.rossberry.com
"Society in every state is a blessing, but Government, even in its best
state, is a necessary evil; in its worst state, an intolerable one."
Thomas Paine
1:37 p.m.
On Thu, Apr 30, 2009 at 11:30 AM, Jim Wildman <jim(a)rossberry.com> wrote:
What/how are people monitoring their cobbler servers? particularly
if
you have several.
ie, our management is very interested in how long installs take, how
many there are, who is doing them, etc. A lot of that could be gleaned
from a combination of messages, cobblerd.log and the kicklogs.
Anybody have a solution then can share?
For starters, have you seen the build reporting stuff? It is in 1.6.
You might be able to do a mix of the build reporting stuff with
cobbler aclsetup to make people run cobbler as an unpriv user except
for syncs. Then edit the build report template to spit out the user
that added the system or something. It would give you a pretty email
with the info of the new system and it's information.
Just an idea
--
Jeff Schroeder
Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com
3:38 p.m.
Jeff Schroeder wrote:
On Thu, Apr 30, 2009 at 11:30 AM, Jim Wildman
<jim(a)rossberry.com> wrote:
> What/how are people monitoring their cobbler servers? particularly if
> you have several.
>
> ie, our management is very interested in how long installs take, how
> many there are, who is doing them, etc. A lot of that could be gleaned
> from a combination of messages, cobblerd.log and the kicklogs.
>
> Anybody have a solution then can share?
>
For starters, have you seen the build reporting stuff? It is in 1.6.
You might be able to do a mix of the build reporting stuff with
cobbler aclsetup to make people run cobbler as an unpriv user except
for syncs. Then edit the build report template to spit out the user
that added the system or something. It would give you a pretty email
with the info of the new system and it's information.
Just an idea
There's also "cobbler status" which uses similar triggers to log when
installs start/stop.
This doesn't track who is doing them, which would primarily something
we'd have to add .. the webapp has login info on edits, but who started
a PXE install is not really info
we can gather up since it's an external thing.
[root@localhost cobbler]# cobbler status
ip |target |start |state
10.11.231.91 |profile:F10-i386 |Thu Mar 19 17:29:44
2009|finished
127.0.0.1 |profile:profile0http:|Wed Dec 31 18:59:59
1969|finished
192.168.122.132|system:F10 |Tue Mar 24 13:02:57
2009|unknown/stalled
192.168.122.27 |system:F10A |Tue Mar 24 14:13:56
2009|unknown/stalled
Perhaps that's a start, other ideas welcome.
--Michael
5485
days inactive
5485
days old
cobbler@lists.fedorahosted.org
2 comments
3 participants
participants (3)
-
Jeff Schroeder -
Jim Wildman -
Michael DeHaan