Thanks to all that replied. Looks like I have some more documentation to read. Mike
On Monday, April 11, 2016 at 12:42:30 PM UTC-5, Mike Cervi wrote: > First, forgive me if my terminology is imprecise... I'm new to these tools. > Second, I work in a heavily regulated industry, and the limitations of the > design are not my doing... I'm just stuck in them. While I really > understand the urge, recommendations to alter this or that in our > Enterprise design simply won't be helpful. > Third, thanks in advance for your help. > > I am on a team evaluating orchestration tools. We want automated, > consistent builds and the ability to update, test and deploy new code. > I've read a lot of good things about Ansible, and wanted to dig a bit > deeper. My immediate concern is that it appears Ansible is strictly run > with no client side agent, and all updates are pushed from the server. In > my environment, this makes Ansible a non starter. All communication must > be initiated by the client first. Our Firewall would drop any traffic that > is not initiated by the client. > > So, is Ansible just not a practical choice for me, or is there a client > side agent/script that can be used to initiate updates from the server? > > Thanks again. > > -- 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/6ff8523d-2920-46db-bd6d-eb3411e59fd6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
