OK, I'll have a look on your upgrading guide and shinken code, then a talk with shinken developpers if the solution of supporting Pyro 3 and 4 according to which one is available on the system is acceptable for them.
If it is OK, - I'll port my patch to pyro 4, help you with Richard to build a test environment ; - write a patch for shinken test it with pyro 4 on my IPv6 environment and propose it to shinken developpers. Next step on August for me, when I come back from holidays. Best regards, Vincent Leloup vincent.lel...@ker-is.net Le mardi 05 juillet 2011 à 19:00 +0200, Irmen de Jong a écrit : > Hello Vincent. > > On Tue, 05 Jul 2011 09:02:38 +0200, Vincent Leloup wrote: > > Hello Irmen, > > > > As stated in the patch, it is based on revision 507 of Pyro 3. It was > > the head some days ago. > > Ah yes, I should have noticed that. Thanks. > > > > I can support you about IPv6 network but only on linux / unix. My > > knowledge about Windows is very limited. > > Well, my knowledge of Ipv6 is quite limited ;-) > I am prepared to set up a virtual network with a couple of vm's running > linux > and with a ipv6 network but I have no clue on how to do this, or if > this > is even possible on my dev pc running windows 7 on a ipv4 network. > I'm proficient with VirtualBox and Debian or Ubuntu. > Can you perhaps help with this? Or someone else? > > > > If Pyro 3 is really feature freezed, I can try to port the patch to > > Pyro > > 4 ; I don't know if code has changed so much between these two > > versions. > > Pyro4 is a different beast than Pyro3. > But, in a positive way. The code is cleaner and more modern. > The API is very similar but not backwards compatible. > See http://packages.python.org/Pyro4/upgrading.html > > Pyro3 indeed is feature frozen (only bug fixes get in). > Since a while I consider Pyro4 the only way forward for new code. > This doesn't mean there is no way to set up some form of repository for > feature patches, or perhaps even feature branches for Pyro3. > I haven't given this much thought yet, any ideas regarding this? > (the older 'third party contrib' page here: > http://irmen.home.xs4all.nl/pyro3/contrib.html > isn't really suitable for this because we're talking changes in Pyro3 > itself) > > > > I read that some features are still missing in Pyro 4 ; I can check > > if > > there are used by shinken and propose a patch against shinken to > > support > > Pyro 4 (If it is possible, I don't know how dynamic loading of > > libraries > > works in python, but it should be possible.) > > I'll be grateful if you could do this. Which version of Pyro3 are they > using now? > Again, see http://packages.python.org/Pyro4/upgrading.html for a guide. > > > > What is the better solution for you ? > > When do you think that Pyro 4 will be stable enough to be used in > > production environment ? > > It has been stable enough for production use for a while, IMO. > Pyro4's code is better than Pyro3's and it has a truckload of unit > tests > which can help to make sure any changes don't break existing behavior, > and that it works as expected on the various platforms. > > The only thing is because Pyro4 is still actively developed, there will > sometimes be small incompatible API changes. (If you are not willing to > deal > with this, stick with Pyro3. Note that the Pyro4 API has been quite > stable > for the past couple of releases anyway. And I always try to stay > backwards > compatible as much as possible.) > > Pyro3 also has some nasty problems that are not present in Pyro4 at > all, > such as mobile code troubles, which make Pyro4 a better choice) > > So the ideal solution is to introduce proper Ipv6 support in Pyro4, > including unit tests. (And a way for me to actually run them ;-). > > > > I don't know if IPv6 is used a lot, but for a monitoring tool like > > shinken, I think it's a really important feature : actually, in mys > > case, it is :) > > Yeah. I agree it would be nice if Pyro supports it out of the box. > > > Thanks for your efforts, > > Irmen de Jong > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Pyro-core mailing list > pyro-c...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/pyro-core
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
