Jump to: navigation, search

Difference between revisions of "Octavia/Weekly Meeting Agenda"

(Meeting 2014-08-27)
Line 9: Line 9:
 
** 1 haproxy process per listener, or 1 haproxy process per loadbalancer
 
** 1 haproxy process per listener, or 1 haproxy process per loadbalancer
 
* Discuss where haproxy config should be rendered (on controller, or on Octavia VM).
 
* Discuss where haproxy config should be rendered (on controller, or on Octavia VM).
 +
* Discuss ideas for increasing project velocity
 
* Review prioritized action items list, look for volunteers for high-priority items
 
* Review prioritized action items list, look for volunteers for high-priority items
  

Revision as of 08:51, 27 August 2014

Meeting 2014-08-27

Agenda

  • Review action items from last week
    • Review German's benchmarks related to 1 haproxy process per listener, or 1 haproxy process per loadbalancer
    • Ready to accept v0.5 component design?
    • Ready to accept Brandon's initial database migrations?
    • Any other action items with progress to report
  • Poll for consensus on:
    • 1 haproxy process per listener, or 1 haproxy process per loadbalancer
  • Discuss where haproxy config should be rendered (on controller, or on Octavia VM).
  • Discuss ideas for increasing project velocity
  • Review prioritized action items list, look for volunteers for high-priority items

Meeting 2014-08-20

Agenda

  • Revisit some basic features of LBaaS Object model and API:
    • Should 'loadbalancer' be the only root object
    • Get consensus on whether we allow child objects to be shared
      • Should we allow sharing of pools by L7 policies within a single Listener parent?
  • Get consensus on initial project direction implementation detail: One haproxy instance per loadbalancer, vs one haproxy instance per listener?
    • Volunteers to run benchmarks?
  • Decide what else needs changed in v0.5 design before it can be approved and implementation work started: https://review.openstack.org/#/c/113458/
  • Decide where to document semi-arbitrary "get consensus on" decisions so we don't end up revisiting them more frequently than necessary, and so new-comers can get up to speed on the the decisions and reasoning behind them if and when these get revisited at some much later date.
  • Discuss action items for team members for next week / coming weeks
    • Do we want to build off what is in gerrit, get v2 rolling github, wait for neutron-labs?
    • Creating the skeleton code/interfaces for Octavia development
    • Begin work actually writing implementations where it makes sense
    • Review this after it's updated post meeting: https://review.openstack.org/#/c/114671/

Meeting 2014-08-13

Agenda

  • Discuss future of Octavia in light of Neutron-incubator project proposal.
  • Discuss operator networking requirements (carryover from last week)
  • Discuss v0.5 component design proposal: https://review.openstack.org/#/c/113458/
  • Discuss timeline on moving these meetings to IRC.


Meeting 2014-08-06

Agenda