Jump to: navigation, search

Difference between revisions of "Meetings/Masakari"

(Agenda for next meeting)
 
(115 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
= Weekly Masakari team meeting =
 
= Weekly Masakari team meeting =
[http://eavesdrop.openstack.org/#Masakari_Team_Meeting MEETING TIME]
+
[http://eavesdrop.openstack.org/#Masakari_Team_Meeting Click here for current meeting time and place.]
  
This meeting is a weekly gathering of developers working on [[Masakari|OpenStack Masakari]].  We cover topics such as release planning and status, bugs, reviews, and other current topics worthy of real-time discussion.
+
This meeting is a gathering of developers working on [[Masakari|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  ==
+
== Preamble ==
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: 15/08/2017 ====
+
* Roll-call
 +
* Agenda
  
* High priority items
+
== Agenda of the upcoming meeting ==
** Release (planned)
+
 
masakari 8/15
+
<pre>
masakari-monitors 8/15
+
* CI status
python-masakariclient 8/15
+
* Announcements
Minor Dependency: https://review.openstack.org/#/c/493434/
+
* Important pending reviews (important bugfixes, backports)
* Bugs (stuck/critical)
+
* Next release planning
** [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]
+
* Open discussion
* Discussion points
+
</pre>
** Application for become OpenStack oficial project: Not done yet (samP)
 
** Install guide document
 
*** Should we write installation documents for each distributions now?
 
** [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]
 
** 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]
 
** "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
 
  
 
== Previous meetings ==
 
== Previous meetings ==
 
* [http://eavesdrop.openstack.org/meetings/masakari/ All previous meetings are here]
 
* [http://eavesdrop.openstack.org/meetings/masakari/ All previous meetings are here]

Latest revision as of 06:17, 28 September 2021

Weekly Masakari team meeting

Click here for current meeting time and place.

This meeting is a 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.

Preamble

  • Roll-call
  • Agenda

Agenda of the upcoming meeting

* CI status
* Announcements
* Important pending reviews (important bugfixes, backports)
* Next release planning
* Open discussion

Previous meetings