Difference between revisions of "Meetings/Masakari"
< Meetings
(→Meeting date: 15/08/2017) |
(→Agenda for next meeting) |
||
| Line 10: | Line 10: | ||
* High priority items | * High priority items | ||
| + | ** Release (planned) | ||
| + | masakari 8/15 | ||
| + | masakari-monitors 8/15 | ||
| + | python-masakariclient 8/15 | ||
| + | Minor Dependency: https://review.openstack.org/#/c/493434/ | ||
* Bugs (stuck/critical) | * Bugs (stuck/critical) | ||
** [https://bugs.launchpad.net/masakari/+bugs?search=Search&field.importance=Critical&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress Critical bugs] | ** [https://bugs.launchpad.net/masakari/+bugs?search=Search&field.importance=Critical&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress Critical bugs] | ||
Revision as of 03:51, 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
- Release (planned)
masakari 8/15 masakari-monitors 8/15 python-masakariclient 8/15 Minor Dependency: https://review.openstack.org/#/c/493434/
- Bugs (stuck/critical)
- Discussion points
- Application for become OpenStack oficial project: Not done yet (samP)
- 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
