Jump to: navigation, search

Difference between revisions of "Octavia/Weekly Meeting Agenda"

(Agenda)
Line 15: Line 15:
 
**** create_load_balancer, update_load_balancer, delete_load_balancer, create_listener, etc
 
**** create_load_balancer, update_load_balancer, delete_load_balancer, create_listener, etc
 
*** Option 4: Do nothing, the current situation is acceptable
 
*** Option 4: Do nothing, the current situation is acceptable
 +
* Align Octavia user API with neutron-lbaas's API
  
 
== Meeting 2015-05-13 ==
 
== Meeting 2015-05-13 ==

Revision as of 21:44, 26 May 2015

Meeting 2015-05-27

Agenda

  • Announcements
  • Static Code Analysis
    • Decide on having a tox environment to do this check or we don't do it at all
  • How to solve tightly coupled drivers (compute, network, amphora)
    • Example: Amphora driver needs information from neutron, but in a true loose coupling, it wouldn't call neutron it would either get the information it needs passed into it or it would call the network driver's interface.
      • Option 1: All information needed is passed into the driver methods as data models
        • Will require a lot of extra data models
      • Option 2: Drivers are allowed to call other driver types (compute, network, amphora)
        • Will require more methods in each driver, specifically retrieval methods.
      • Option 3: One driver to rule them all! Ocean boiling (better to do it now than later)
        • Compute, Amphora, and Network removed in favor of a single more generic interface.
        • create_load_balancer, update_load_balancer, delete_load_balancer, create_listener, etc
      • Option 4: Do nothing, the current situation is acceptable
  • Align Octavia user API with neutron-lbaas's API

Meeting 2015-05-13

Agenda

Meeting 2015-04-29

Agenda

Meeting 2015-04-22

Agenda

Meeting 2015-04-15

Agenda

Meeting 2015-04-08

Agenda

  • Announcements
  • Brief progress reports
  • Summer Midcycle for LBaaS/Octavia
    • Extend and invite FWaaS amd VPNaaS?
  • Confirm API Server vs. Controller Worker database updates
  • Review what still needs to be completed for the end to end demo
  • Should Octavia use tempest or Rally for integration tests? - 2
  • Open Discussion

Meeting 2015-04-01

Agenda

  • Announcements
  • Brief progress reports
  • How should a Octavia dev/test environment look like - 2
    • Run octavia components as single screens
  • Should Octavia use tempest or Rally for integration tests?
  • Open Discussion

Meeting 2015-03-25

Agenda

Meeting 2015-03-18

Agenda

  • Announcements
  • Brief progress reports
    • Neutron LBaaS V2 Octavia Driver
    • Networking Driver
  • Open Discussion

Meeting 2015-03-11

Agenda

  • Announcements
    • Quick Recap of RUG demo
  • Brief progress reports
  • Discuss AmphoraDriver: Now with agent API having some legs should we keep our double strategy ssh & REST
  • Open Discussion

Meeting 2015-03-04

Agenda

Meeting 2015-02-25

Agenda

Meeting 2015-02-18

Agenda

  • Brief progress reports
  • python setup.py install fails
  • amphora-haproxy driver
  • Future of this meeting
  • Open Discussion

Meeting 2015-02-11

Agenda

  • Brief progress reports
  • Demo Octavia in Neutron LBaaS Talk
    • Amphora Driver
    • Network Driver
    • Deploy Worker
  • Open Discussion

Meeting 2015-01-28

Agenda

  • Brief progress reports
  • HealthMixin in amphora driver (mwang)
  • Open Discussion

Meeting 2015-01-21

Agenda

  • sbalukoff stepping down as PTL
  • Team discussion (dougwig)
  • Brief progress reports
  • Open discussion

Meeting 2015-01-14

Agenda

  • Brief progress reports
  • Closing in on an alpha release
  • Summit talk proposals
  • Open Discussion

Meeting 2015-01-07

Agenda

  • Brief progress reports
    • controller implementation
    • amphora api
    • operator api
    • what else?
  • To tightly couple interfaces with taskflow or to not (german & blogan)
    • We should still use taskflow in the layer that calls the driver, and if driver implementers want to use taskflow then that is their perogative.
  • Open Discussion

Meeting 2014-12-10

(It's anticipated that this will be a short meeting so folks can get back to the Neutron meet-up.)

Agenda

  • Octavia hack-a-thon next week (reminder)
  • Brief Progress reports
  • Open Discussion

Meeting 2014-12-03

Agenda

Meeting 2014-11-19

Agenda

  • Octavia hack-a-thon in December
  • Progress reports
    • operator-api (blogan)
    • network-driver-interface (blogan)
    • appliance-api (sbalukoff and davidlenwell)
    • base-image creation (johnsom)
    • TLS data security (rm_work)
    • compute driver interface (amiller and TrevorV)
    • controller
  • Other reviews Needing Attention ( https://review.openstack.org/#/q/stackforge/octavia+status:open,n,z )
  • Open Discussion

Meeting 2014-11-12

Agenda

Meeting 2014-10-29

Agenda

  • Announcements and updates
  • Reviews Needing Attention ( https://review.openstack.org/#/q/stackforge/octavia+status:open,n,z )
  • Octavia hack-a-thon in December (sbalukoff)
  • Discussion with API working group (jaypipes)
  • Progress reports
    • operator-api (blogan)
    • appliance-api (sbalukoff and davidlenwell)
    • network driver and neutron implementation (dougwig)
    • base image (johnsom)
    • amphora-driver-interface (xgerman)
    • compute-driver-interface (amiller)

Meeting 2014-10-22

Agenda

  • Announcements and updates
  • Reviews Needing Attention ( https://review.openstack.org/#/q/stackforge/octavia+status:open,n,z )
  • Logging requirements discussion (jorgem)
  • Progress reports
    • operator-api (blogan)
    • appliance-api (sbalukoff and davidlenwell)
    • network driver and neutron implementation (dougwig)
    • base image (johnsom)
    • amphora-driver-interface (xgerman)
    • compute-driver-interface (amiller)

Meeting 2014-10-15

Agenda

  • Neutron LBaaS FLIP Update
  • Reviews Needing Attentions
  • Usage requirements
  • Progress Reports
    • operator-api (blogan)
    • appliance-api (sbalukoff)
    • network driver and neutron implementation (dougwig)
    • base image (johnsom)
    • amphora-driver-interface (xgerman)
    • compute-driver-interface (amiller)

Meeting 2014-10-08

Agenda

Meeting 2014-10-01

Agenda

  • Quick update on "Octavia" trademark
  • Review progress on action items from last week
  • From blogan: Neutron lbaas v1 and v2 right now creates a neutron port before passing any control to the driver, we need to decide how Octavia is going to handle that
  • Discuss any outstanding blockers
  • Review status on outstanding gerrit reviews
  • Review list of blueprints, assign people to specific blueprints and/or tasks

Meeting 2014-09-17

Agenda

  • Review progress on gerrit reviews and blueprints

Meeting 2014-09-10

Agenda

  • Discuss: Use storyboard instead of launchpad for blueprints?
  • Vote on whether haproxy.cfg should be rendered in the amphora or the amphora driver
  • Vote on whether we should keep meetings in IRC or move back to webex
  • Discuss use of Pecan, WSME, and jsonschema for the API

Meeting 2014-09-03

Agenda

  • Briefly discuss Octavia/Non-arbitrary Decisions wiki page
  • Briefly discuss v0.5 component design under review, Brandon's initial database migrations, push for consensus on that.
  • Get consensus on name of "thingy" doing the load balancing (VM / appliance / device / strategy / toaster / whatever)
  • Discuss where haproxy config should be rendered (controller, driver, or Octavia VM / appliance)(Driver, of course.)
  • Discuss DB model around loadbalancer VIPs in relation to different front-end topologies and how be to represent these abstractly
  • Discuss blueprints here, look for volunteers: https://blueprints.launchpad.net/octavia/

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.


Previous meeting logs