On Fri, 6 May 2016, at 09:59, nrser wrote: > that is basically what i ended up doing. it makes the workflow a pain in > the ass because i have to make changes to the playbooks on my local > machine > (connection is too slow and unstable to do much editing on the server), > commit, push, and pull on the server, but then running locally works just > fine. > > whether it's reusing connections or not, the main issue seems to be that > it > fails very easily if the connection shakes or dies. the value of software > like ansible in my opinion is the declarative nature (this should be in > the > state), which makes the playbooks idempotent and allows for reties.
mosh http://mosh.mit.edu/ is an excellent replacement for the ssh connection from your workstation to the server, to enable editing in situ. It uses udp and a predictive transfer mode so works very well over sluggish connections. I don't think it would be suitable as a replacement for ssh within ansible however, but it might cut down your editing hops at least. A+ Dave -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/1462521764.308347.599836097.5711D29F%40webmail.messagingengine.com. For more options, visit https://groups.google.com/d/optout.
