[op5-users] Ninja backend and architecture

[Andreas Ericsson]

Hendrik Baecker wrote:
> Andreas Ericsson schrieb:
>> Hendrik Baecker wrote:
> 
>> However, since the various components are neatly separated and there's
>> supposed to be an API to retrieve data, it will be possible to write
>> a file-based API as well. We won't do that initially, but if someone
>> else picks up the ball I'm sure we'll help keep it rolling.
>>
> A quickstart (almost quick&dirty is welcome) guide for your ninja design
> would be great to help to pick up the ball.
> Something like a: "If you would do <this> to be on the site, do <that>
> in kohana in <those> files."
> Just a few hints how you would like to see your concept during coding.
> 

This is Per territory, I think. I haven't actually touched the GUI at all
yet, since I've been busy working on Merlin. I'll need the same type of
documentation you do though, so I'm sure something will have to be written
down fairly soon (we're doing a bugfix release this week, but on monday
it's business as usual again).

>>> I would appoligize to be straight forward, but I think everyone want's
>>> to have a new WebUI but only middle up to huge environments will benefit
>>> from merlin.
>>> I were realy excited to contribute to ninja,
>> Awesome to hear! :)
>>
>>> but I fear the merlin
>>> dependency as another failuresource in the nagios workflow.
>>>
>> Not so awesome to hear :-/
>> Have some faith in my mad coding skills ;-)
>>
> Oh no! Not in your coding skills - but you now that Merlin was a
> magician with his own, not transparent for everyone, ways of acting? ;)
> 
> To keep the track of the brittish saga: There are some other cool names
> like Mordred or Morgan le Fay - some possible names for Ninja? :D
> 

But.. but... Mordred and Morgan (or Morgana) were evil! We're basically
nice (and stylishly black with shiny toys ;-))

> I guess I have to start a test run with merlin to get a better thinking
> of what it is doing. When I see it below my own fingers I bet I will
> spent some kudohs ;)
> 

It's fairly straightforward. If you think of it as a module that inserts
Nagios events into a database, you're not too far off. The problem with
having only the module and nothing in between is that Nagios hangs while
the module is working. Hence the middle step here, and since Merlin
already handled event transports just fine, we decided to use that.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.