31–40 of 61 posts
> However, once we get the node.js SSH workers polished and ready for prime-time, you may run workers on your own infrastructure. Anyone who gives these people money is a fool.
Perhaps you could articulate further?
This app will suck.
There are cases where I do prefer web interfaces to command line. The AWS web console is an example of this, but for me this is a case of balancing control vs convenience. Installing the AWS libraries to use the command line is a greater PITA than the need to use the command line.
With Git, I prefer the power of the command line over a graphical client. However, in this case there is little or no convenience in the difference because I have to install Git either way.
The only usage I would be able to get out of this would be to give my non technical managers, clients, co-developers, etc a way to do deployments if I'm not available. One scenario would be for contractors to be able to setup their own dev servers. So, I can see a situation where I could use it, but it's a bit of an edge case.
Did the creators of this use any of the tools in this domain? How does this compare to mcollective/capistrano/vlad the deployer/fabric/ssh and a for loop? It's a web app, how is that superior to something CLI based? God, its Matriu AS ( http://www.kickstarter.com/projects/naterockhold/matriu-as-l... ) all over again.
When GitHub first was released, I am sure there was a skeptical group of developers who asked the same sort of questions.
Also, Matriu asked for $250,000. :)
Did the creators of this use any of the tools in this domain? How does this compare to mcollective/capistrano/vlad the deployer/fabric/ssh and a for loop? It's a web app, how is that superior to something CLI based? God, its Matriu AS ( http://www.kickstarter.com/projects/naterockhold/matriu-as-l... ) all over again.
Thanks for the feedback. Right now, since Commando.io is so young I'll admit its not the most advanced tool. However, recipes are versioned and every execution and response is logged and stored for compliance and accountability. When GitHub first was released, I am sure there was a skeptical group of developers who asked the same sort of questions. Also, Matriu asked for $250,000. :)
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.
Earlier quoted context omitted.
Thanks for the feedback. Right now, since Commando.io is so young I'll admit its not the most advanced tool. However, recipes are versioned and every execution and response is logged and stored for compliance and accountability. When GitHub first was released, I am sure there was a skeptical group of developers who asked the same sort of questions. Also, Matriu asked for $250,000. :)
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, para…
Feedback from someone that's previously (long before the devops scene exploded) looked at commercializing a system like this: Your UI should integrate monitoring and control using an actually visual interface detached from any underlying model used for state collection or implementation of state changes (because this stuff changes constantly, regardless of how much myopic VC money is thrown at it). This means instead…
Thanks for the feedback. Our goal is certainly to make a visually beautiful product. As far as floor diagrams, racks, and specific hardware, we want Commando.io to be used by everybody, including AWS, Rackspace, Linode, so building those specific features is probably over-scope. Monitoring is a market that already has some amazing companies (ServerDensity, NewRelic). The missing piece is management, provisioning, aut…
For management tools do exist, just not fancy looking but get the job done... it should be a full package; monitoring and deployment, etc etc go hand in hand.
Currently we use csshX for this sort of thing, and it does the job. It's an open source tool that opens a bunch of ssh sessions and sends each character you type to each session. You can launch it with command line args that specify the hosts you'd like to connect to and optionally the commands to run, so it's pretty easy to set up scripts that mimic the recipes in this video. If you're working with less that 20 servers at a time (about the limit of what you can read on screen at once) it's a great tool.
I think most features (and more) you mentioned in the video are already covered by the chef-server (recipes, role, ohai, search, provisioning etc), and they have large community and more thoroughly tested.
However, their webui is too simple, and in particularly not extensible - no plugin mechanism so it is difficult to add some minor feature on the top of their webui.
So I think there is a huge market for providing a better UI for chef-server, especially they are one of the leaders in the field?