Difference between revisions of "Meetings/Masakari"
< Meetings
Dinesh.bhor (talk | contribs) (→Meeting date: 08/08/2017) |
|||
| Line 7: | Line 7: | ||
For important matters, please send mail to [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev openstack-dev@lists.openstack.org] mailing list with the prefix "[masakari]". | For important matters, please send mail to [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev openstack-dev@lists.openstack.org] mailing list with the prefix "[masakari]". | ||
| − | ==== Meeting date: | + | ==== Meeting date: 15/08/2017 ==== |
* High priority items | * High priority items | ||
| Line 18: | Line 18: | ||
** [https://review.openstack.org/#/c/469029/4/masakari/engine/drivers/taskflow/host_failure.py@191 Should the 'error' instances be only stopped after recovery or stop and reset to 'error' again?] | ** [https://review.openstack.org/#/c/469029/4/masakari/engine/drivers/taskflow/host_failure.py@191 Should the 'error' instances be only stopped after recovery or stop and reset to 'error' again?] | ||
** [https://etherpad.openstack.org/p/masakari-recovery-method-customization recovery method customization] | ** [https://etherpad.openstack.org/p/masakari-recovery-method-customization recovery method customization] | ||
| − | ** | + | ** How do we find hosts if we forget the relational of segments-hosts? |
| + | *** I heard a opinion, "It will be hard to find hosts if operator forgets the relational of segments-hosts." What do you think about it? | ||
| + | **** Should we create new API? | ||
| + | **** Or, Should we implement it by combination of existing APIs as a new masakari CLI's feature? | ||
| + | **** Or, should not we deal it? | ||
** [https://etherpad.openstack.org/p/masakari-pike-workitems Pike work Items] | ** [https://etherpad.openstack.org/p/masakari-pike-workitems Pike work Items] | ||
** "masakari-manage db purge": support for purging notification records | ** "masakari-manage db purge": support for purging notification records | ||
Revision as of 03:04, 15 August 2017
Contents
Weekly Masakari team meeting
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: 15/08/2017
- High priority items
- Bugs (stuck/critical)
- Discussion points
- Application for become OpenStack oficial project
- Install guide document
- Should we write installation documents for each distributions now?
- Should the 'error' instances be only stopped after recovery or stop and reset to 'error' again?
- recovery method customization
- How do we find hosts if we forget the relational of segments-hosts?
- I heard a opinion, "It will be hard to find hosts if operator forgets the relational of segments-hosts." What do you think about it?
- Should we create new API?
- Or, Should we implement it by combination of existing APIs as a new masakari CLI's feature?
- Or, should not we deal it?
- I heard a opinion, "It will be hard to find hosts if operator forgets the relational of segments-hosts." What do you think about it?
- Pike work Items
- "masakari-manage db purge": support for purging notification records
- AOB
- Ansible support for Masakari
- See the ML discussion http://lists.openstack.org/pipermail/openstack-dev/2017-April/115944.html
