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. On Friday, May 6, 2016 at 3:44:32 PM UTC+8, Johannes Kastl wrote: > > On 05.05.16 08:21 nrser wrote: > > > i can hold an ssh terminal open with the server no problem... what's > going > > on here? is ansible creating a new connection for every task? can i make > it > > just hold one connection open and use that? can i make it retry a few > times > > if it can't connect? > > Just an idea: SSH to the server, start screen and then apply the > playbook with target localhost. > > I think ansible is using connection multiplexing to avoid having to > open new connections for each task. Why it does not work in your case? > No idea. > > Johannes > > > -- 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/67ec5efe-6f41-4be5-99ba-e920a8bc6919%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
