Awesome, I might give it a shot then. Finally, as per stallion, for node connections how are you doing that? For example the master says create vps 0259 or something like that, how does it talk to the "slave" nodes.
You should poke around the newer firmwares as well, not just CI. CI, while feature complete, doesn't have its core developers anymore. They went off to do their own thing and only really commits bug fixes and such. Granted, CI's expandable enough that you can write quick functions to supply whatever you're missing.
For communication we use good old HTTPS. We originally planned to use a nodejs daemon with probably XMPP for communication, but in the end we were going to blow too much time remaking the wheel for no reason. It works quickly and keeps us within languages we're all accustomed to.
We run a lightweight webserver on each node that also runs a codeigniter instance. The biggest thing we needed was node side sanitizing of all data. Solus has shown what happens when you don't sanitize what gets sent to you, even in a supposed 'safe environment'. Solus' node side (did, or at least used to) take everything it was told and passed it right to the CLI via SETUID bins. This means if you fed it a $CTID param of "100;dd if=/dev/zero of=/dev/sda", it runs the DD as root.
We had done a basic audit on Solus a few years ago and I was screaming about their poor coding practices since their big "LOL we removed BW rate limiting without telling you. Sorry about the overages!". They proceeded to try to SQL inject Stallion 1.
EDIT - fixing tense.
Francisco
