Re: [Cfengine-develop] Development plan / meeting

[Hugo Gayosso]

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

"Luke A. Kanies" <address@hidden> writes:

> I like the idea of a constantly running cfagent, and rather than one that
> works in passes, like now, I'd like one that set alarms on all work.  You
> may want to check your process table every 5 minutes, because it's
> lightweight and very important, but only check file permissions every
> hour, because it takes more time and is less likely to cause service
> outages.
> 
> So, each feature is built like a plugin, and each plugin supports an alarm
> setting, with support for a default.  The cfagent starts by parsing all of
> the config files, and probably running each plugin once.  Then, it sets
> each plugin's alarm (including the plugin that updates cfagent's config),
> and when that alarm goes off the plugin runs again.

I agree.

> But you still need a way to figure out who's in charge of reporting if a
> host is down.  That should be pretty easy:  whoever cares.  For services
> other than infrastructure services (dns, ntp, etc.), most hosts are only
> contacted by peers providing the same services and by downstream hosts who
> require those services.  At the same time, most hosts again only contact
> peers, and upstream servers providing required services.
> 
> So, you just have every host care about its peers (or some subset; if a
> host has 100 peers, than that's a waste of effort) and upstream servers,
> and pass any important events around when something changes.

This resembles what I described in a previous message under the "Are
you ok?" title, so it is good that we agree.



> Do the rest of the people interested in cfengine development feel
> that way, or, like me, do most people feel that some significant
> change is necessary?

I think that we need to define the specific role that cfengine plays
in a fully autonomic infrastructure, depending on this role are what
kind of changes are needed.

Maybe we need to define what an "autonomic infrastructure" is, in
short, a infrastructure that self-configures, self-monitors and
self-heals, if we read what IBM says, they also include
self-optimizing.


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

iD8DBQE+ZBfoMNObVRBZveYRAu8hAJ9EHrMMjSmtClQ9Oww8f1fN5+LkbgCfRH/o
hxB2EXQjzbA3VH1aN0CkZd8=
=sN53
-----END PGP SIGNATURE-----