I'm going to upgrade some of the instances of RADIUS to run on HEAD, to give it some soak testing (our eduroam IdP / home and SP / visted servers) and hopefully encourage a release ;o) Before I do that, are there any thoughts on a timeline to a 3.0 release, or any cautionary notes?
Phil Mayers wrote:
I'm going to upgrade some of the instances of RADIUS to run on HEAD, to give it some soak testing (our eduroam IdP / home and SP / visted servers) and hopefully encourage a release ;o)
Yes. There are a bunch of cool features sitting in the queue, for release in 3.0.x :)
Before I do that, are there any thoughts on a timeline to a 3.0 release, or any cautionary notes?
Wait a bit for the build system to settle. :) But it seems to work for me. Alan DeKok.
On 20 Nov 2012, at 15:36, Alan DeKok <aland@DEPLOYINGRADIUS.COM> wrote:
Phil Mayers wrote:
I'm going to upgrade some of the instances of RADIUS to run on HEAD, to give it some soak testing (our eduroam IdP / home and SP / visted servers) and hopefully encourage a release ;o)
Yes. There are a bunch of cool features sitting in the queue, for release in 3.0.x :)
Before I do that, are there any thoughts on a timeline to a 3.0 release, or any cautionary notes?
Wait a bit for the build system to settle. :)
But it seems to work for me.
Eh, some of the proxy stuff is a bit explody on server down. LDAP attrmap stuff is going to change format before 3.0 is released. -Arran
On 20 Nov 2012, at 16:10, Alan DeKok <aland@DEPLOYINGRADIUS.COM> wrote:
Arran Cudbard-Bell wrote:
Eh, some of the proxy stuff is a bit explody on server down.
I thought I fixed that...
Maybe eduroam overlord Buxey can comment? IIRC he was using 3.0 in production with monit restarting the server regularly.
LDAP attrmap stuff is going to change format before 3.0 is released.
-Arran
On 20/11/12 16:05, Arran Cudbard-Bell wrote:
Eh, some of the proxy stuff is a bit explody on server down.
This has always been a pain to reproduce, too. Invariably when I got a proxy crash (on the old code) I would try to re-pro the problem by selectively making an upstream server fail, but it wouldn't crash again. Seems it was timing/state related :o( Hopefully Alan's rewrite will have quashed it; TBH part of the reason for wanting to run a pre-release is to show any bugs. I can arrange for one of our ORPS to run 3.0-pre and the other 2.2, which prevents shooting myself in the foot, but should hopefully get a bit of torture testing.
participants (3)
-
Alan DeKok -
Arran Cudbard-Bell -
Phil Mayers