Re: Document-Driven Development: Plone Ansible Playbook
Steve McMahon <[email protected]> Sat, 20 Sep 2014 14:18:59 -0700
| Newsgroups | gmane.comp.web.zope.plone.installers |
|---|---|
| Message-ID | <CAOqzbgiEC2HHSnbcrJ=_K413f-PODKXEOrpS6EAPfwUobwXaew@mail.gmail.com> |
I had made firewalling a separate section because I thought it might be the most difficult thing to do in a general way. It also seemed possible we'd want to do the firewall work in a separate playbook. The last set of Ansible provisioning I did used the ufw module, and I found it very easy. However, I'm guessing that folks using AWS and Google Compute Engine might want to do their firewalling via AWS and GCE modules. I also suspect that many folks have firewall tastes of their own. On Fri, Sep 19, 2014 at 10:16 PM, sven <[email protected]> wrote: > Yes that is possible ! > > The reason why I ask is that I saw for example the section firewall in the > README, if we say we support deb and rpm based server I would to like the > same programs. One other point for at least deb bases systems is to make > sure to identify the OS and the version number, sometimes they change > between versions. > > Sven > > > On 09/19/2014 06:21 PM, Steve McMahon wrote: > > It seems possible to me that we could support both the deb and rpm world > on the remote server. > > We need to pick one for vagrant, though, and the latest LTS server makes > sense to me. > > On Fri, Sep 19, 2014 at 3:23 AM, sven <[email protected]> wrote: > >> Hi, >> >> Awesome !!! >> >> I assume we will base this on Ubuntu 14.04 ? >> >> BTW. I really do like the DDD approach ! :) >> >> Cheers, >> >> Sven >> >> >> On 09/18/2014 07:26 PM, Steve McMahon wrote: >> >> Hi All, >> >> I've opened a new repo https://github.com/plone/ansible-playbook that >> currently contains nothing but a first draft of documentation for a >> forthcoming Plone Ansible Playbook. >> >> Please, please, please contribute by discussing and/or editing and >> writing. I'm trying to use this document to work through the most >> fundamental questions about how this facility should look *before* we write >> much code. >> >> The doc is just a big README at the moment. Don't worry yet about >> breaking it up or getting it into good Sphinx format. Instead, think about >> it and contribute. We'll refactor later. >> >> Instead, think about questions like: >> >> What tools should be in the stack? >> >> How do we want to encourage customization? >> >> How will be handle versioning and branching going forward? >> >> I'd love for us to get this into shape by the conference so that we can >> talk about it, sell it, and incite sprinters with the doc(s) serving as our >> story. >> >> Let fly! >> >> Steve >> >> >> ------------------------------------------------------------------------------ >> Slashdot TV. Video for Nerds. Stuff that Matters.http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk >> >> >> >> _______________________________________________ >> Plone-installers mailing listPlone-installers-5NWGOfrQmneRv+LV9MX5ugtCRVl27V+i0wdF1cv0I5s@public.gmane.org://lists.sourceforge.net/lists/listinfo/plone-installers >> >> >> >> >> ------------------------------------------------------------------------------ >> Slashdot TV. Video for Nerds. Stuff that Matters. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk >> _______________________________________________ >> Plone-installers mailing list >> Plone-installers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org >> https://lists.sourceforge.net/lists/listinfo/plone-installers >> >> > > ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk _______________________________________________ Plone-installers mailing list Plone-installers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/plone-installers