cfengine-develop
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Cfengine-develop] Development plan / meeting


From: Hugo Gayosso
Subject: Re: [Cfengine-develop] Development plan / meeting
Date: Mon, 03 Mar 2003 22:44:12 -0500
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

address@hidden writes:

> Depends what you mean by monitoring. If you want a message on every
> run saying "Yes DNS is still running..."  You'll be insane within a
> few days. If you have 2000 hosts (as several cfengine users do)
> you'll be insance within a few minutes.

I don't think that any of us want that (now you understand why I am
insane :-))


> The idea behind cfengine is precisely to eliminate the administrator
> from as much as possible. Keep quiet, and keep things running..

I agree.

> > And I certainly don't see how making the ability to monitor an
> > explicit part of cfengine's feature set makes it _less_ flexible
> > and _less_ plug'n'play.  "If I've got dns configured, make sure
> > it's always running."  "If I've got a host configured, make sure
> > it checks in at least once every hour."  That kind of stuff; it's
> > all there, we just need some hooks to be able to set up what's
> > currently missing (which isn't actually much).
> 
> But this is already what happens, so I don't understand what you are saying.

Maybe what we need is recipes of real life scenarios, or "templates".

For example what I am doing in my installation is having something
like a template (I don't have it available now, so from memory) for
daemons that should be running in server:

For almost ANY daemon this is true:

a) The daemon should be configured to run in a certain runlevel.
b) The daemon should be started at boot time.
c) The daemon should be running, if it is not, it should be started.
d) The daemon should be restarted if its configuration file changes.



If we prepare a set of "guidelines" or "templates" describing this
kind of stuff it will make it easier for the newbies to start using
cfengine.

Also it will make it easier for the experts as we might even start
"standardizing" the way we configure cfengine which could lead to
better cfengine configurations.

But most important by having more newbies having results easily when
they adopt cfengine we might be able to attract more brain power to
cfengine.

Ok, I will stop now before besides being insane I will be rhetoric.

- -- 
Hugo Gayosso
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE+ZCEMMNObVRBZveYRApmzAJ4mSAvyYIVRgBHvaf4bsUYhNTk4wACfZMSE
OOZ9HCOC2XUS2NaaeNnxCJc=
=x2eY
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]