Jump to: navigation, search

Difference between revisions of "Meetings/Masakari"

(Weekly Masakari team meeting)
Line 20: Line 20:
 
** [https://etherpad.openstack.org/p/masakari-recovery-method-customization recovery method customization]  
 
** [https://etherpad.openstack.org/p/masakari-recovery-method-customization recovery method customization]  
 
*** spec update in progress
 
*** spec update in progress
** Find hosts without specifying segments
 
*** Review in progress
 
**** https://review.openstack.org/#/q/topic:bp/find-segment-by-host+(status:open+OR+status:merged)
 
 
** [https://etherpad.openstack.org/p/masakari-queens-workitems Queens Work Items]  
 
** [https://etherpad.openstack.org/p/masakari-queens-workitems Queens Work Items]  
 
** Ansible support for Masakari
 
** Ansible support for Masakari
 
*** See the ML discussion http://lists.openstack.org/pipermail/openstack-dev/2017-April/115944.html
 
*** See the ML discussion http://lists.openstack.org/pipermail/openstack-dev/2017-April/115944.html
 
+
** Call Force down API when host-failure will be notified
 +
*** Current masakari will wait for 3 minutes when host-failure will be notified.
 +
The purpose of this is to wait nova-compute down.
 +
There is a possibility that using force down API instead of waiting make recovery process faster.
  
 
'''Topics below this line will not discussed in 12/5 and 12/12 meetings since samP is not available'''
 
'''Topics below this line will not discussed in 12/5 and 12/12 meetings since samP is not available'''

Revision as of 02:57, 5 December 2017

Weekly Masakari team meeting

MEETING TIME

This meeting is a weekly gathering of developers working on OpenStack Masakari. We cover topics such as release planning and status, bugs, reviews, and other current topics worthy of real-time discussion.

Agenda for next meeting

For important matters, please send mail to openstack-dev@lists.openstack.org mailing list with the prefix "[masakari]".

Meeting date: 28/11/2017

SamP will not be able to attend 12/5 and 12/12 meetings'

The purpose of this is to wait nova-compute down. There is a possibility that using force down API instead of waiting make recovery process faster.

Topics below this line will not discussed in 12/5 and 12/12 meetings since samP is not available


  • AOB
    • Migrate from launchpad to Storyboard

Previous meetings