On Thu, Aug 11, 2016 at 9:02 AM, Jóhann B. Guðmundsson
<johannbg(a)gmail.com> wrote:
Administrator are bound to the limit of their ( already existing )
infrastructure so you cannot bind the community to Ansible since then you
will have excluded participation from those administrators that are running
puppet or chief in their infrastructure and I have yet to see what incentive
administrators will have to participate in the server WG as an result of
this. In the CM upstream communities they will just create their playbooks,
manifest and or recipes that will fit their infrastructure and use case
perfectly as opposed to using a predefined one with a boxed solutionin
which they *always* will have to tweak one way or another to be able to
implement it in their infrastructure.
That's one of the great things about Ansible in particular.
Administrators are specifically not bound to use it in exclusion to
anything else since it's completely agentless. If you want to deploy
our predefined role using Ansible, and then further customize it (with
Puppet, Chef, BladeLogic, vi, or whatever tools you might want to use
:D) then that's perfectly OK from a technical perspective, and I think
that's a pattern that we need to support. Ideally, all the
customization that one needs would be built into the role with
extra_vars that you define when you run a playbook, but in spite of
our best intentions, there's sure to be something that we miss.