<p dir="ltr">Yes! I would like these things to live under a official openstack program so there is a clear collaboration point. This should not be stack forge it should be openstack and we should aim for incubation and recognition of contributions. </p>
<div class="gmail_quote">On 06/11/2014 1:42 PM, "David Moreau Simard" <<a href="mailto:dmsimard@iweb.com">dmsimard@iweb.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">As far as monitoring is concerned, we've just had a session at the Ops summit - etherpad: <a href="https://etherpad.openstack.org/p/kilo-summit-ops-monitoring" target="_blank">https://etherpad.openstack.org/p/kilo-summit-ops-monitoring</a><br>
<br>
Definitely lots of various initiatives regarding monitoring scripts/tools that could benefit from being centralized.. at a quick glance:<br>
- <a href="https://github.com/stackforge/monitoring-for-openstack" target="_blank">https://github.com/stackforge/monitoring-for-openstack</a><br>
- <a href="https://github.com/osops/tools-monitoring" target="_blank">https://github.com/osops/tools-monitoring</a><br>
- <a href="https://github.com/sensu/sensu-community-plugins/tree/master/plugins/openstack" target="_blank">https://github.com/sensu/sensu-community-plugins/tree/master/plugins/openstack</a><br>
- <a href="https://github.com/cirrax/openstack-nagios-plugins" target="_blank">https://github.com/cirrax/openstack-nagios-plugins</a><br>
- <a href="http://packages.ubuntu.com/search?keywords=nagios-plugins-openstack" target="_blank">http://packages.ubuntu.com/search?keywords=nagios-plugins-openstack</a><br>
<br>
My personal recommendation would be that we should focus on the stackforge repository.<br>
--<br>
David Moreau Simard<br>
<br>
<br>
> On Nov 6, 2014, at 12:20 PM, Michael Chapman <<a href="mailto:woppin@gmail.com">woppin@gmail.com</a>> wrote:<br>
><br>
> Hi Operators!<br>
><br>
> I felt like OpenStack didn't have enough projects, so here's another one.<br>
><br>
> During the summit I feel like I'm repeatedly having the same conversations with different groups about bespoke approaches to operational tasks, and wrapping these in a project might be a way to promote collaboration on them.<br>
><br>
> Off the top of my head there's half a dozen things that might belong here:<br>
><br>
> - Packaging tooling (spec files/fpm script/whatever)<br>
> - (Ansible/other) playbooks for common tasks<br>
> - Log aggregation (Logstash/Splunk) filters and tagging<br>
> - Monitoring (Nagios) checks<br>
> - Ops dashboards<br>
><br>
> There's also things that *might* belong here but maybe not:<br>
><br>
> - Chef/Puppet/Ansible/Salt OpenStack config management modules<br>
><br>
> Today these are generally either wrapped up in products from various companies, or in each company's github repo.<br>
><br>
> For those of you who are still around at the design summit and don't have plans for tomorrow, how about we meet on Friday morning at the large white couch in the meridian foyer at 9am? Let's see what we can sort out.<br>
><br>
> Thanks!<br>
> _______________________________________________<br>
> OpenStack-operators mailing list<br>
> <a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br>
</blockquote></div>