Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
==== Minutes of Technical Community Discussion on October 15, 2015 ====

  * ''Date and Time'': 6:00am PDT / UTC 13:00, Thursday October 15, 2015
  * ''Convener'': Bin Hu (AT&T)
  * ''Participants'':
    * Al Morton (AT&T)
    * Ana Cunha (Ericsson)
    * Brian Smith (Bell Canada)
    * Bryan Sullivan (AT&T)
    * Dimitri Mazmanov (Ericsson)
    * Edgar St Pierre (EMC)
    * Howard (Zhipeng) Huang (Huawei)
    * Joe (Chaoyi) Huang (Huawei)
    * Larry Lamers (VMWare)
    * Malla Reddy Sama (DoCoMo)
    * Manuel Rebellon (Sandvine)
    * Michael Bugenhagen (Century Link)
    * Michael Melesse Damena (HP Enterprise)
    * Pasi Vaananen (Artesyn)(Stratus)
    * Stuart Mackie (Juniper)
    * Weidong Shao (Huawei)

  * Recurring PTL election

Bin (AT&T) summarized the question and discussion about recurring PTL election, and understood it "as needed". Edgar (EMC) indicated that he gave the question first, and he noticed that some other open source communities, such as OpenStack, have annual PTL election. The annual PTL election may help projects that are not progressing move forward by changing the leadership of the project. But he also thought that "as-needed" is also fine for OPNFV. Bin agreed, and said that in case that a project is not progressing, the stakeholders of the project can still take the action to re-elect PTL when needed. OPNFV is quite young, and so far we don't have issue of stale project. So let's keep PTL election "as-needed" for now. When OPNFV is getting more mature, and if we need to have annual PTL election for whatever reason, we can always revisit this topic.

All agreed.

  * Information on the recent [[:project_lifecycle_bylaws|Bylaw Amendments]] approved by the TSC and under review by legal and the board
    * Amendments included allowing up to 2 votes for member companies and affiliates.

Bin (AT&T) summarized that there was a proposal last week regarding 2 voting members of TSC from platinum members, and email discussion on this topic. It seems the proposal is aligned with community understanding, and this Bylaw Amendments.

For informational purpose, community may review the Bylaw Amendments.

  * Upstream Feature Development and Cross-Project Collaboration
    * New [[https://launchpad.net/kingbird|Kingbird]] Project Proposal in OpenStack driven by OPNFV [[:multisite| Multisite]] Project
      * [[https://blueprints.launchpad.net/kingbird/+spec/kingbird-framework| Blue Print]]
      * [[https://docs.google.com/document/d/17c8IOjegK_CDUQeDfy0Z_vN-5aahv_Xrsd70AJ8pnoE/edit#| Framework Specification]]
      * [[https://blueprints.launchpad.net/kingbird/+spec/quota-sync-api|API for Centralised Quota Management]]

Joe (Huawei) introduced Kingbird framework. He indicated that in this Kingbird framework, all jobs and results will be persisted in the Database for history review so that the Kingbird will also serve as “snapshot” of the project to some extent (especially if we have periodic jobs to collect metering/event reports from Ceilometer services which distributed in multi-region). Multiple Kingbird Job Workers will be designed and run in stateless mode, persistent data will be accessed (read and write) from the Kingbird Database through the DAL module.

Joe indicated that we will take phased approach and focus on Quota Management first, and move forward step by step.

Dimitri (Ericsson) added that Kingbird project bridges the gap between standalone OpenStack deployment in multiple regions.

Edgar (EMC) asked which OpenStack release is Kingbird targeting. Joe indicated that Kingbird ia pretty new in OpenStack community. We will follow OpenStack process and release schedule. It is tentatively targeted for M release with limited feature set, but no guarantee because of lots of unknowns, such as code repo, its own process, schedule, and gates etc. And we will do our best.

Bin asked what type of community help / support Joe needs to help Kingbird in OpenStack. Joe and Dimitri thought it might be too early in Tokyo to campaign it. Once some code are developed and more work will be done, it should be good to campaign it at OpenStack Summit in 2016.

Joe and Dimitri also suggested that it is appropriate to introduce Kingbird in OPNFV BoF in Tokyo.

Bin concluded that we should introduce Kingbird in OPNFV BoF in Tokyo. Bin will share the OPNFV BoF Etherpad with Joe and Dimitri so that they can work it out with Iben regarding agenda.

  * Project Proposal Discussion
    * Active project proposals
      * TBD

None

Meeting adjourned.
Wiki

User Tools

Site Tools

Page Tools
