=============================================== #openstack-meeting-4: OpenStack Ansible Meeting =============================================== Meeting started by b3rnard0 at 16:00:09 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-04-09-16.00.log.html . Meeting summary --------------- * Agenda & rollcall (b3rnard0, 16:00:37) * LINK: https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting (b3rnard0, 16:00:47) * Blueprints (b3rnard0, 16:10:52) * LINK: https://blueprints.launchpad.net/openstack-ansible/+spec/implement-ceilometer (b3rnard0, 16:11:01) * LINK: 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) * Milestones (b3rnard0, 16:33:43) * LINK: https://launchpad.net/openstack-ansible/+milestone/10.1.3 (b3rnard0, 16:35:12) * Open discussion (cloudnull, 16:43:32) * LINK: https://bugs.launchpad.net/openstack-ansible/+bug/1442239 (BjoernT, 16:43:40) * LINK: 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) * 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) Meeting ended at 17:00:35 UTC. People present (lines said) --------------------------- * cloudnull (46) * odyssey4me (39) * b3rnard0 (24) * BjoernT (13) * openstack (13) * d34dh0r53 (6) * andymccr (5) * Sam-I-Am (3) Generated by `MeetBot`_ 0.1.4