Well, to repeat - how does this compare to tools in the domain? Why are you opting for a web interface driven approach over a command line interface?
Why are you opting to build the entire thing from scratch instead of using an existing orchestration tool and building an interface to that? Wouldn't that save you time and money?
I've most recently hammered on mcollective, and it can easily support multiple users, parallel requests, full auditing of all requests and responses, authorization, server discovery, etc. There's all your advanced features, already implemented.
In regards to the interface, our thought is this is what is currently missing from other tools in the domain. Imagine if GitHub had build just their API first without their interface. A fully RESTFul API with shell wrappers (node.js, python, perl) will come with time.
Why are you opting to build the entire thing from scratch instead of using an existing orchestration tool and building an interface to that? Wouldn't that save you time and money?
I've most recently hammered on mcollective, and it can easily support multiple users, parallel requests, full auditing of all requests and responses, authorization, server discovery, etc. There's all your advanced features, already implemented.