It also looks like (not sure if i am right) but your worker/server has to have direct ssh access to the server. This means you basically have root access as most configuration management tools need root to administrate the server.
A web-based interface for dev-op tasks across remote servers using SSH
21–30 of 61 posts
Re: A web-based interface for dev-op tasks across remote servers using SSH
#22What is the difference to http://rundeck.org/ which can be integrated with foreman or puppet? It also looks like (not sure if i am right) but your worker/server has to have direct ssh access to the server. This means you basically have root access as most configuration management tools need root to administrate the server.
Re: A web-based interface for dev-op tasks across remote servers using SSH
#23This is my sticking point: if the power comes from the recipes, how does having a web interface help any of that? I think this is a great piece of work, but I just can't see what the advantages are over any of its competitors given that all the actual work is still being done in the same way (e.g. shell scripts).
I would add that you bring up GitHub a number of times as a comparable service, but I think that the key difference is that a number of core git features are actually implemented by GitHub (e.g. fork, log, pull) and although this all looks great it isn't the reason (IMO) why it's successful, it's because it makes a common operation easier (i.e. git repository management). I think that you would need to make common dev-op "recipes" easy to generate before the GitHub comparison is correct.
Re: A web-based interface for dev-op tasks across remote servers using SSH
#24What is the difference to http://rundeck.org/ which can be integrated with foreman or puppet? It also looks like (not sure if i am right) but your worker/server has to have direct ssh access to the server. This means you basically have root access as most configuration management tools need root to administrate the server.
(Creator of Commando.io) First time we've seen RunDeck, its been mentioned a few other times here. Investigating now.
Re: A web-based interface for dev-op tasks across remote servers using SSH
#25Earlier quoted context omitted.
(Creator of Commando.io) First time we've seen RunDeck, its been mentioned a few other times here. Investigating now.
After looking at your video it seems the main difference currently is that your recipes are versionized (which is a huge plus)
Re: A web-based interface for dev-op tasks across remote servers using SSH
#26Why not fabric? In what universe does fabric have a deep-learning curve? Good lord.
Puppet and Chef have deep-learning curve and they're the tools that can be replaced with what OP is proposing.
Re: A web-based interface for dev-op tasks across remote servers using SSH
#27God, its Matriu AS (http://www.kickstarter.com/projects/naterockhold/matriu-as-l...) all over again.
Re: A web-based interface for dev-op tasks across remote servers using SSH
#28Re: A web-based interface for dev-op tasks across remote servers using SSH
#29So, tell me - what would this tool offer over, say, RunDeck or mcollective? Why only use SSH keys? (What if I'm using LDAP across all of my machines?) I'm not trying to knock your product - I really do hope you get Kickstarter funding! But I just wanted to say that, to me, as a systems engineer, I only see a pretty interface, but not much value add over the other two products mentioned above I also feel that comparin…
(Creator of Commando.io here) - Thanks for the feedback. Commando.io is very young, and while currently only supports SSH, LDAP could easily be added. The alpha build is extremely minimal, and serves as a proof of concept. However future features are parellel execution, interactive sessions, scp transfers (maybe even Murder transfers [bitTorrent]), and provisioning. You have to think back, when GitHub first launched,…
If you missed Alex Loddengaard's "One Year, Six Products," you might want to check it out. http://alexlod.com/2012/07/10/one-year-six-products-what-ive...