Revision as of 05:52, 11 April 2017

Blazar weekly meeting

The Blazar project team holds a weekly team meeting in #openstack-meeting-alt:

• Tuesdays at 09:00 UTC

Next meetings

Agenda for April 11 2017

• stable/ocata branch
• Boston Summit: what to talk?
  • Blazar's session
    • Project Update - Blazar
    • Collaboration of Blazar and Promise
  • Forum sessions
    • http://forumtopics.openstack.org/cfp/details/126
    • http://forumtopics.openstack.org/cfp/details/124
• Pike blueprints status check
• AOB

Agenda for April 4 2017

• Pike blueprints status check
• Boston Summit
• AOB

Agenda for March 28 2017

• gate job
• AOB

Agenda for March 21 2017

• Ocata (0.2.0) release
• Boston Summit
• AOB

Agenda for March 14 2017

• Action items from last call
• Ocata (0.2.0) release
• Pike blueprints
• Boston Summit
• AOB

Agenda for March 7 2017

• Action items from last call

• Ocata (0.2.0) release

• Pike blueprints
  • [Discussion] Add options for on_end action: config vs. request parameter (https://blueprints.launchpad.net/blazar/+spec/on-end-options)
  • [Info] Terminate lease at any time (https://blueprints.launchpad.net/blazar/+spec/terminate-lease-at-anytime)

• AOB
  • create new Blazar_status_2017 page ?

Agenda for February 28 2017

• Summary of PTG
  • https://etherpad.openstack.org/p/blazar-ptg-pike
  • https://etherpad.openstack.org/p/Blazar_status_2016
• Deprecation rules
  • details: https://review.openstack.org/#/c/434777/
• Remaining Reviews for O

Agenda for February 14 2017

• Action items from last call
• Load to Ocata release
• Next weekly meeting
• +1 or +2 at Code Review
• Pike cycle discussion

Meeting code of conduct

• Amend the agenda before the meeting is starting, not after
• We can leave an open discussion topic at the end of the meeting
• People having reviews in progress should attend the meeting. If they can't, the ideal would be to briefly catch-up on the status before the meeting.