#openstack-meeting-4: OpenStack Ansible Meeting

Meeting summary

1. Agenda & rollcall (b3rnard0, 16:00:37)
   1. https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting (b3rnard0, 16:00:47)
   
   
2. Blueprints (b3rnard0, 16:10:52)
   1. https://blueprints.launchpad.net/openstack-ansible/+spec/implement-ceilometer (b3rnard0, 16:11:01)
   2. http://docs-draft.openstack.org/76/168976/1/check/gate-os-ansible-deployment-specs-docs/845ff17//doc/build/html/specs/kilo/tunable-openstack-configuration.html (cloudnull, 16:15:10)
   
   
3. Milestones (b3rnard0, 16:33:43)
   1. https://launchpad.net/openstack-ansible/+milestone/10.1.3 (b3rnard0, 16:35:12)
   
   
4. Open discussion (cloudnull, 16:43:32)
   1. https://bugs.launchpad.net/openstack-ansible/+bug/1442239 (BjoernT, 16:43:40)
   2. https://wiki.openstack.org/wiki/Bugs#Status according to this the triaged status should be used when "The bug comments contain a full analysis on how to properly fix the issue" which we are not really doing. Just want clarification as to how we're using the Triaged status (d34dh0r53, 16:50:27)
   3. d34dh0r53: https://wiki.openstack.org/wiki/Bugs#Status according to this the triaged status should be used when "The bug comments contain a full analysis on how to properly fix the issue" which we are not really doing. Just want clarification as to how we're using the Triaged status (b3rnard0, 16:52:00)

Action items

1. (none)

People present (lines said)

1. cloudnull (46)
2. odyssey4me (39)
3. b3rnard0 (24)
4. BjoernT (13)
5. openstack (13)
6. d34dh0r53 (6)
7. andymccr (5)
8. Sam-I-Am (3)