On Thu, Apr 3, 2014 at 5:10 PM, Michael DeHaan <[email protected]> wrote:
> Yeah I'm not seeing where you need this yet. > > Depends on the scale of your infrastructure, but plenty of very very large > setups are not doing this -- and really, if you are in that area, treating > cloud like cloud and using Ansible to build images is often a great option. > Just to provide another perspective, we have a use case for running remote playbooks, and are doing this this via the shell module. We really have two Ansible use cases - one is using Ansible in a "traditional" sense for provisioning servers, building images, etc. Our second use case is, I guess, a bit nonstandard. That being the configuration of on-premise server "appliances" installed in our customer's datacenters. We let customers provide configuration information - this gets saved to a local facts file, which is then used by a local playbook to apply the configuration. Sometimes this playbook is executed in a "standalone" fashion, independent of our centralized provisioning system, but sometimes it is executed remotely via another centralized playbook. -Erik -- 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/CADdM08rUcM4Hb%2BHXSmjEsfKTPBvA9qokWntr89B3LSzYjOiSdg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
