[Openstack-operators] [puppet] OpenStack Puppet Modules Usage Questions
matt at mattfischer.com
Thu Jun 25 17:34:28 UTC 2015
This was my action from the puppet meeting this week, so here's my
I discussed this with Tom Fifield. He has no objections to us using the
operators list like that and in
addition he has enabled tags with a new topic called [puppet] so that folks
could sub/ignore it.
Here's his message:
>Just had a look in the mailman settings, and topic filtering was off.
>So, I turned it on and made a new topic "[puppet]".
>Now, it is possible to subscribe to the ops ML and only get mails about
>puppet by following this guide:
>... but, was that what you actually wanted? If your question was just
>"is it OK to use [puppet] in subject lines and where is the wiki page
>where these things are listed like for the dev list?" The answer is of
>course, and there just isn't a wiki page at the moment :)
On Tue, Jun 16, 2015 at 8:27 AM, Jonathan Proulx <jon at jonproulx.com> wrote:
> On Mon, Jun 15, 2015 at 7:46 PM, Richard Raseley <richard at raseley.com>
> > As part of wrapping up the few remaining 'loose ends' in moving the
> > modules under the big tent, we are pressing forward with deprecating the
> > previously used 'puppet-openstack at puppetlabs.com' mailing list in favor
> > both the openstack-dev and openstack-operators lists with the '[puppet]'
> > tag.
> > Usage of the openstack-dev list seems pretty straight forward, but we
> > to confirm with the broader community that this list
> > was the appropriate venue for Puppet and OpenStack related usage
> > Any objections to this model?
> I think makes perfect sense especially as other ops related working
> groups are starting to use this list in a similar [tagged] way.
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-operators