As far as python-jsonrpc - I don't think you need it anymore and if I recall, it's not in the guide. Only pyopencl is required now.
Anyway, the pool is pretty stable unless I am poking at it with a stick, then it gets uppity... but I haven't had to poke any sticks into the pool in a while. I do need to make some adjustments to the internals of the getwork server now that we are no longer doing proportional... it's still got the proportional code running but doing nothing.
I'm also considering switching to Poolserverj when that is a bit more stable. Although if it ain't broke, I shouldn't fix it. But I always do.
Let's put it this way - I wish them the best of fortune (because BT seems to be dealing with external issues that are of a higher priority) - but my miners were running at an average of 2-3 GH/s - and that's *with* me watching like a hawk and restarting miners when necessary. BT admitted that poolserverj and other software locked up after a while (memory leak sounds normal) and needed restarting, which he didn't always get informed of.
Fair enough if external issues are the main priority. But your system is clearly stable as a rock, and if the flakiness of arsbitcoin was down to poolserverj... I'd rather you not bother unless you are satisfied that it meets your currently (obviously very high) standards.
To me - I don't care about the actual technology / language used to run the pool server - only that my electricity bill represents accepted work from the pool, and that my miners aren't sitting there 20% of the time burning kilowatts but with no work from the pool.
I'm sure that you won't deliver a half-baked solution though - doesn't look like your style. Let us all know if old configs like mine (11.04 ubuntu natty minimal, 11.6 catalyst, 2.4 APP SDK, 1.50 phoenix, various phatk kernels and a load of really shoddy catfish scripting in ruby and bash) are potentially going to be unsupported though. I've trialled the latest (AFAIK) phoenix - 1.62 - and it works but doesn't offer any performance improvements to me, nor does it change the crazy monster-stdout verbosity (I redirect phoenix output to a file and then use that to extract performance statistics, after a week it's over a gigabyte per instance), so I haven't bothered updating globally.
OTOH - my aim with the Linux Minimal build isn't to try to do any better than you - your guide works and is perfect for anyone who has 10 minutes or more shell experience. Mine is just an attempt at giving something back - all my homebrew code that starts up and stops arbitrary numbers of phoenix miners on each rig (mine tend to have 4 GPUs per logic board, but there's no limit other than ATI's), and periodically updates an html page with formatted data for each instance. Consolidating the instances to one webpage (as I do) is left to the user - it's tricky on OS X Server due to various idiosyncrasies of the apache version used, but really it's just a question of linking the HTML from each mining rig into one webpage. It works with SSI but obviously you need to be careful with security - it's simple data though with no scripting other than 'include' for each miner instance's table rows.
It won't be for everyone, but after installing my miners on full Ubuntu Desktop installs with all the patches, I was wondering why the hell I needed compiz, apparmor, and a load of fancy GUI eye candy (that *does* affect the 'first' processing GPU). I'm henceforth working on trying to get a happy, compatible miner build that starts with the Ubuntu Minimal installation. I've got a couple of GH/s lying idle whilst I faff about - hashing power that should be working for the pool - so I'm on the case...
All of my scripts are commented to hell (as has always been my style) and your guides are cited and credited, but I'll run my proposed release past you beforehand. After all, they're all effectively the same, it comes down to whether you download source and compile, use apt packages, downloaded deb packages, and/or tarballs that used to be hosted somewhere but aren't anymore. I will probably get the security-paranoid jump down my throat for potentially distributing malware... so I'll probably end up having to provide MD5 hashes for the recommended binary / deb downloads. Now AMD require a questionnaire to be answered in order to download a non-current (e.g. 11.6, which works) proprietary driver, it's not a question of scripting wget any more. And expecting new Linux users to play AMD's silly games is too much - though I'm sure that if I host the entire dependency file group (including ATI drivers) then I'll get aggro for distributing copyrighted material... sigh...