> 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.
A web-based interface for dev-op tasks across remote servers using SSH
11–20 of 61 posts
Re: A web-based interface for dev-op tasks across remote servers using SSH
#12dev-ops for me also includes provisioning - and based on " ... you can use shell, perl, ruby, node.js ..." I don't see a strict system for that in place.
(Creator of Commando.io here) Commando.io is extremely early, and while no such provisioning features are built yet, they are certainly in the pipeline. The beta users will dictate features and direction.
> Commando.io is extremely early
Yes, and I think it's great, that people seem to be already interested in it on kickstarter.
Just one thought, but I'm far from a dev-ops expert. I worked with Chef and Puppet in the past, looking at salt now. There are two large benefits for me in dev-ops: 1) automation and 2) documentation - and still, chef, puppet and salt have quite some rough edges. And those are mostly command line tools - I just can't see, how a UI oriented system could simplify things and could come near those. But then again, I'm mostly thinking idempotent provisioning - for monitoring and similar, a web-frontend is a great plus.
Re: A web-based interface for dev-op tasks across remote servers using SSH
#13Why not fabric? In what universe does fabric have a deep-learning curve? Good lord.
But, but, but, those other guys got a million dollars!
Re: A web-based interface for dev-op tasks across remote servers using SSH
#14Feedback 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, automation of servers within a web-interface.
Re: A web-based interface for dev-op tasks across remote servers using SSH
#15[deleted]
Re: A web-based interface for dev-op tasks across remote servers using SSH
#16> 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?
Re: A web-based interface for dev-op tasks across remote servers using SSH
#17I'm not sure if I'd want anyone touching my servers who thought that fabric had a 'steep learning curve'. That just sounds irresponsible.
Founder of NodeSocket, creator of Commando.io here. The steep learning curve was geared at Chef and Puppet, but wanted to list some other popular options.
I guess what I mean is, simplifying server access is great and it looks like you are doing that well. However, I guess I don't like the idea of marketing it because the other automated methods are too hard to learn; market it because it is convenient and provides a nice interface. Just my 2 cents.
Re: A web-based interface for dev-op tasks across remote servers using SSH
#18Earlier quoted context omitted.
Founder of NodeSocket, creator of Commando.io here. The steep learning curve was geared at Chef and Puppet, but wanted to list some other popular options.
I guess what I mean is, simplifying server access is great and it looks like you are doing that well. However, I guess I don't like the idea of marketing it because the other automated methods are too hard to learn; market it because it is convenient and provides a nice interface. Just my 2 cents.
Thanks, agree need to work on marketing and positioning.
Re: A web-based interface for dev-op tasks across remote servers using SSH
#19Feedback 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…
I agree with most of these suggestions: the one thing that can land you all the toughest customers in this market is a user experience that is unquestionably better than Vim ;)
Re: A web-based interface for dev-op tasks across remote servers using SSH
#20Our company uses a combination of Capistrano and Puppet. It is actually pretty easy to get going with Capistrano and Puppet if you are comfortable with Ruby. Our Capfile specifies the server recipe which is propagated to Puppet using Environment Variables. The whole operation is easy to understand, and very little learning curve required.
We do the same, except we've started phasing out Capistano because it's model doesn't fit well with Tomcat. Once you have your keys distributed everywhere via Puppet, it trival to use your favorite scripting language to just SSH around and run commands.
This just doesn't seem like its so hard a problem that I need a cloud based solution.