2011/2/2 nap <napar...@gmail.com>
>
> 2011/2/2 Grégory Starck <g.sta...@gmail.com>
>
>>
>> Jean :
>>
>> if we would have a shinken package tree looking like this (not so so much
>> different than the current one):
>>
>> *shinken*/ # we keep the base 'shinken' name for the shinken package
>> ofcourse.
>>
>> *objects*/ # (or "conf_objects" ?) would contain all files defining
>> all classes for all "configuration objects" widely used by the different
>> shinken daemons, like:
>> # host, service, contact, timeperiod, module(.py), etc,
>> etc.. ; well anything that can be in a Config object (and transmitted by
>> the arbiter to the others shinken daemons) I think actually
>>
>> *core*/ # would contains all "core" related code files: Satellite,
>> Daemon, Scheduler, ... modulemanager, ..., Item, ..., log, check, ... well
>> all that is really anything primary (and not contained in other subpackages
>> like objects/modules/..) needed/used by the different shinken daemons so
>> obviously.
>> ## actually they could be all left in shinken/ but having a "core"
>> subpackage with them is not more difficult..
>>
>> *daemons*/
>> ## we can have either a subpackage or python module per daemon ;
>> doesn't matter actually:
>> arbiter
>> scheduler
>> reactionner
>> poller
>> broker
>> ## this one is the most easy to do now : would just need to take
>> the *daemon.py files I just have created and rename them over there..
>>
>> *modules*/ # exactly like now but is just missing the __init__.py to
>> make it a (sub)package.
>>
>> ( soon:
>> *plugins*/ # only for shinken *own* "plugins" (I'm speaking of
>> native python plugin here (when there will be).
>> )
>>
>>
>> I actually don't see more than that.
>>
>> wdyt ??
>>
>> clearly(more than now I mean) separating "core" & "conf objects" &
>> "daemon" code seems really helpfull (already from a dev point of view but
>> also eventually for distribution packagers), at least to me.. ofcourse a
>> small care must be taken when this would be done but if it can be relatively
>> easily done why not foresee it right now ? and I do think this can be very
>> relatively easily done..
>>
>>
> Hum.... if it's more obvious for new comers why not (after all this time,
> for me it's obvious where things are, so it's hard to take a new eye on
> this). Item should go in the objects, because its the root object in fact,
> but the other dispatching seems good. I came and back to core and config
> quite a lot during coding, but why not after all.
>
> We can start with the daemon one. I do not know if a sub module is so
> useful.
>
I think it can/could be : because I was also thinking having the daemon.py
specific code be put in shinken/daemons/ cause it's not really something
purely related to shinken itself : it's a really quite common daemon
wrapper/template (that could even be used by anything else than shinken).
but i'm "playing on the words" here.. we can still see..
> Here we want to help dev to read the code and go in it easily, so another
> level is maybe too much for them.
>
I think it'll clearly help new comers ;)
For code and object, it sounds like the M and C of MVC, so why not :)
>
> For the plugin, it can be some helpers class for python plugin dev yes.
>
and for the shinken plugins that we would put directly in shinken : the most
obvious : ping / tcp / (or more when there will be)
>
> So let go and cut all of this. Thanks to both of you to make me see that
> the cutting is need :)
>
Perfect, "ls shinken/*py | wc -l" will thank you :
(master)greg@brutus:~/Documents/Projets/shinken$ ls shinken/*py | wc -l
70
(master)greg@brutus:~/Documents/Projets/shinken$
:D
actually if you can already make a list of what files should go to
"objects", and what to "core" then I can take it and try to do this split
task.. unless Hartmut/someone else want it ;)
regards,
greg.
>
>> greg.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
>> Finally, a world-class log management solution at an even better
>> price-free!
>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
>> February 28th, so secure your free ArcSight Logger TODAY!
>> http://p.sf.net/sfu/arcsight-sfd2d
>> _______________________________________________
>> Shinken-devel mailing list
>> Shinken-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Shinken-devel mailing list
> Shinken-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>
>
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
