Re: [Nagios-devel] New Nagios implementation proposal

[Guest]

On Dec 9, 2009, at 2:50 PM, Flyinvap wrote:

> Le Wed, 9 Dec 2009 12:12:20 -0600,
> Marc Powell a =E9crit :
>=20
>> know, Ethan doesn't even know or use Python at all. You are asking
>=20
> And what about taking some concepts from shinken and using their in =
next
> nagios versions ? in python, c, c++ or anything else the developers
> want.

That's not what was proposed but may be encumbered, depending on how =
Gab=E8s Jean proceeds and under what license. He has contributed very =
useful code before, particularly the circular parent check logic useful =
for large installations so I think that he certainly has things he can =
contribute conceptually and code-wise. As a user with a large =
installation, I am personally very interested in any changes/additions =
that improve the performance or capabilities for large installations and =
fully appreciate the desires expressed by him to implement them. =
Proposing a complete re-write in a completely different language and =
asking it to just be accepted might not be the best path.

>> In the end, it's Ethan's decision but I see your project as living on
>> it's own, similar to Icinga, promoting 100% nagios compatibility, but
>> a completely different implementation none-the-less.
>=20
> Jean proposed a new implementation for nagios, not a fork, doesn't he =
?

If you re-implement something in a language that the current developer =
does not use, then that is a fork, unless the current developer =
relinquishes control/responsibility or agrees to switch to that =
language. Do you know how good Ethan's python coding is, or even if he =
can at all? To the best of my knowledge whether he can proficiently code =
in Python is an unknown.

> Is the fork the only solution ?

I think that if Python is the language of choice for the proposed =
'reimplementation', then yes, that would be _my_ opinion unless Ethan is =
fully on board with it and fully involved. I think if the concepts can =
be integrated into the current codebase, then that's a different thing.

> icinga is not enough ? Is Nagios XI the only future of nagios ?

I don't know and I have no say. Those were just my thoughts and opinions =
from an end-user perspective with an eye to the time, work and =
intellectual investment Ethan has in the current code. I do believe that =
a wholesale replacement of the official nagios with a Python re-write is =
going to be very very unlikely.

--
Marc






This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]