This same thing came up at the mid-cycle Ops meet up at RAX in August.  There 
wasn't much action that came from it, but we did set up a new org in GitHub for 
collecting this type of common stuff:  https://github.com/osops
The ops tools session going on now ( http://sched.co/1nfHWk3 ; 
https://etherpad.openstack.org/p/kilo-summit-ops-tools ) are discussions along 
these same lines, too.

Mike




From: Michael Chapman <wop...@gmail.com<mailto:wop...@gmail.com>>
Date: Thursday, November 6, 2014 at 12:20 PM
To: OpenStack Operators 
<openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>>
Subject: [Openstack-operators] Proposal for an 'Operations' project

Hi Operators!

I felt like OpenStack didn't have enough projects, so here's another one.

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.

Off the top of my head there's half a dozen things that might belong here:

 - Packaging tooling (spec files/fpm script/whatever)
 - (Ansible/other) playbooks for common tasks
 - Log aggregation (Logstash/Splunk) filters and tagging
 - Monitoring (Nagios) checks
 - Ops dashboards

There's also things that *might* belong here but maybe not:

 - Chef/Puppet/Ansible/Salt OpenStack config management modules

Today these are generally either wrapped up in products from various companies, 
or in each company's github repo.

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.

Thanks!
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to