Re: [Shinken-devel] broker failure, pyro replacement
Status: Beta
Brought to you by:
naparuba
From: nap <nap...@gm...> - 2013-07-03 07:47:03
|
On Mon, Jul 1, 2013 at 3:00 PM, nap <nap...@gm...> wrote: > > [...] > The http-branch remove Pyro, I switch to an http connexion (wsgi module > for listening connexion, with some threads and locks), and pycurl for http > connexion to other daemons. I'm still fixing some timeouts things here and > here, but the main idea is OK. It will be possible to add HTTPS connexions, > and even to reverse-proxy some distant daemons if you want (like a unique > nginx that will reverse schedulers+poller connexions for a realm). > > So in the 2.0 (won't be 1.6 ;) ) there won't be any Pyro problems (and I > hope no http ones :p ). > > > Hi, If you are curious, you can have a closer look at the http-core branch, I just commit https://github.com/naparuba/shinken/commit/8de0bf998fa6cd393650b619fe2e48d27b8a3bcfthat change the http client lib from requests to pycurl and add a real thread for the http daemon. It should be good enough for a testing environment. I'm currently working on the httpS part, and when it's done, I'll give my help to Romain Forlot on the split conf branch. The main 2.0 features will be quite ready then :) Jean |