looks like the API pieces will be a key area in consideration for a
core redo, I guess it would fall under a thread worker as modeled out
in the diagram I sent out recently.
I'm keen to hear where and how these ideas will impact a core redo and
where/how we'll need to accommodate that when planning for the core
redo.
other than that, my comments are that I like the way key pieces are
being compartmentalized and each piece meant to do a few functions
well.

---------- Forwarded message ----------
From: Christoph Maser <[email protected]>
Date: Sun, Aug 8, 2010 at 9:07 PM
Subject: Big picture

Hi team

I sat down and painted a rough overview of my view on icinga components
and how I think they should interact. Have a look at the attached Ooo
Draw file. Some comments on that:

The orange marked API parts all together should be considered "the API"
and should be an internal API wich is in full or in parts exported via
some standard technology (e.g. SOAP, XMLRPC, whatever. Expressed by the
fat arrows).

I did not put it in the diagram to prevent cluttering, but it is quite
clear that all orange marked API parts must have direct read access to
the central object store.

What did became quite clear to me while painting this is the fact that
an event manager is the central component, not the scheduler.

Another point I did express in this design is to drop state keeping from
any external database. So ndo/ido in this design is downsized to a mere
log-storage for reporting.

Completely missing is configuration handling.

So these are my ideas, what about yours? Please comment and/or modify.

Attachment: Icinga Components.odg
Description: application/vnd.oasis.opendocument.graphics

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
icinga-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/icinga-devel

Reply via email to