Versions Compared

Old Version 1

changes.mady.by.user David McBride

Saved on

compared with

New Version 2

changes.mady.by.user David McBride

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Meeting Archives: 2017/2016/2015/2014

Technical Steering Committee

Welcome to the OPNFV TSC page.

Information and materials relevant to the TSC are kept here, for information regarding OPNFV projects and releases please refer to those pages.

Technical Charter

TSC Procedures

TSC Meetings

Antitrust Compliance Notice

Logistics

When (Normally): 6:00am - 7:00am Pacific Time (13:00-14:00 UTC 14:00-15:00 UTC Find your local time).

Dec 18, 2018

Agenda

Call logistics (Zoom):

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/716473820

Or iPhone one-tap :
    US: +16465588656,,716473820# or +16699006833,,716473820# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
    Meeting ID: 716 473 820
    International numbers available: https://zoom.us/u/lWBuQ5ii


IRC irc.freenode.net

Dec 11, 2018

Agenda

Minutes

  • Approval of minutes
    • No comments - minutes approved
  • Chair Report
    • Upcoming board meeting
      • Former user (Deleted) says that OPNFV has a 15 minute slot to present to the board on Wednesday, Dec 12
    • Ongoing work on strategy at weekly tech discussion
      • 8 work items identified in strategy discussion
      • POC identified for six of the work items 
      • Frank Brockners says that the weekly technical discussion overlaps with the ONAP TSC meeting. Would it be possible to adjust the time for the weekly technical meeting? 
  • Marketing Update
  • TF Induction Review
    • Former user (Deleted) says that TF induction was iscussed at the TAC meeting last week. Voting is in progress.
    • The TAC made a recommendation on governance which was accepted.
    • Former user (Deleted) recommends supporting induction 
  • Winter holiday schedule
    • Discussion about the schedule for TSC meetings through the holidays.
    • The TSC agrees that the last meeting of the year will be on Dec 18. Our first meeting of the new year will be on Jan 8. Meetings on Dec 25 and Jan 1 are cancelled. 
  • Release update
    • The TSC votes to approve the release of Gambia 7.1 on December 14.
  • IT/Infra Update
  • Copper termination review
  • Community lab utilization
    • Trevor Cooper  says that many pods are under-utilized.
    • Former user (Deleted) says that this discussion is another aspect of our "infra evolution" objective.
    • Former user (Deleted) suggests that we continue discussion in the infra working group meeting and the weekly technical discussion.
    • Brandon Wick says that marketing can help get the message out about providing services to other communities.
  • TSC JIRA process
    • David McBride says that Former user (Deleted) had requested a process for how the TSC will use JIRA.  David reviews the proposed process with the team.
    • David McBride says that the process emphasizes that JIRA issues should come out of discussions within TSC meetings.
    • Frank Brockners and Trevor Cooper ask why we can't drive the TSC agenda, itself, using JIRA. 
    • Team agrees to continue discussing the TSC JIRA process.

Dec 4, 2018

Agenda

Minutes

  • Approval of minutes
    • No comments - minutes approved
  • MS Exception 
    • Emma Foley
    • SDNVPN team would like to add a scenario 
    • Former user (Deleted) provides background on the exception request
    • David McBride emphasizes that the MS exception simply makes the scenario eligible for release, but that it still needs to meet other release requirements.
    • The TSC agrees to the SDNVPN milestone exception 
  • Gambia 7.1 release 
    • David McBride says that there are problems with Fuel and Compass deployments and recommends delaying the release until Dec 14.
    • TSC agrees to move the release date for Gambia 7.1 to Dec 14 
  • OPNFV strategy (dmcbride, 14:18:04)
    • Former user (Deleted) describes changes to the strategy slide deck, based on feedback from TSC members 
    • Frank Brockners  asks the meaning for an "unlimited vertical" 
    • Former user (Deleted) explains that it means vertical NFV services and workloads
    • Former user (Deleted) further explains it should also include non-NFV workloads
    • Former user (Deleted) says that he would like to present the strategy to the board and get feedback 
    • Georg Kunz asks if there is sufficient detail in the strategy to have a meaningful discussion with the board 
    • Former user (Deleted) explains that we only have 10-15 minutes, so we will keep in very high level. If Board needs more details, we can set up another deep-dive session with Board for details.
    • Team further works out the final wording on slide #13, and agrees.
    • David McBride suggests a vote, but the consensus is that a #agree is sufficient.
    • The TSC approves the vision and direction expressed by slide #13 in the OPNFV Strategy and Plan as discussed in the Weekly Technical Discussion with the understanding that we will revise and adjust accordingly whenever needed, and agrees to Bin presenting it to the Board 
    • Former user (Deleted) says "I'd like to record in the minutes that I am not on board with this and that I made alternative proposals which the chairman did not allow to be discussed in the TSC meeting."
  • Budget discussion (everyone except TSC members and LF staff excused)
    • Discussion of Frank's spreadsheet as it was at the conclusion of yesterday's dedicated budget meeting.
    • The TSC agrees that Bin will contact the Board Finance Committee with a request to consider TSC budget items (community events, intern travel) that were not previously presented to the Board. 
    • The TSC agrees on the budget shown in the spreadsheet presented by Frank and discussed by the TSC on December 3 and 4. 

Dec 3, 2018 (ad hoc budget discussion)

Agenda

  • Budget
    • Review budget slide deck mailed to TSC members.

Minutes

  • Former user (Deleted) presents the revised TSC budget ask, including items unapproved by the board 
  • Frank Brockners shares a spreadsheet to help the team consider different budget scenarios 
  • Frank Brockners to share revised budget ask with the broader TSC. 
    • Frank points out that we had only 8 TSC members on the call, so we should share the changes to allow other TSC members that were unable to attend to weigh in. 

Nov 27, 2018

Agenda

Minutes

Nov 20, 2018

Agenda

Minutes

  • Approval of Minutes
    • No comments - minutes approved
  • Lightning Talk
    • TSC approves of the Barometer talk proposal for the lightning talk at the LFN Reception at Kubecon.
  • OPNFV strategy and plan
    • Strategy was presented by Former user (Deleted) over the past two Thursdays at weekly technical discussion 
    • Former user (Deleted) says that he was unable to attend the last weekly technical discussion and needs more time to review before voting 
    • Former user (Deleted) asks if the primary goal is to enable users to replicate deployment and test toolchain 
    • Former user (Deleted) shares slide from strategy presentation 
    • Former user (Deleted) asks what are the consequences of voting on this plan 
    • Frank Brockners asks whether we really need a vote.  Frank believes that it is more of an "inspiration" than a top-down plan 
    • David McBride to refresh Former user (Deleted) email thread from a few weeks ago to begin community discussion on plan
    • Frank Brockners says that we need to match what projects are capable of doing with the plan 
    • Regarding Strategic Plan, Bin points out that one critical part of TSC's role is to set up strategy and visions for the community. This is what TSC needs to play in its leadership role. So TSC is the top-down leadership role, and project's daily operation is the bottom-up execution of the project 
    • Bin further points out that we provide opportunity for community and projects to give comments, including projects' view of direction, and how and what project is capable of doing it. So the process allows projects' input 
    • Once we have vision, the next step is to define details of deliverables, i.e. what we can offer, based on resources and project's capability 
    • We target next week (Nov 27) for the vote if discussion on mailing list is mature. We allow for comprehensive discussion, and we need a date to set up the direction as the 1st milestone in order to further move towards next steps.
  • Release update
    • David McBride says that 31 projects have committed to Hunter release 
    • MS1 on Friday, Nov 23 
    • release plans on Nov 23
    • release process working group is working on evolving the release model - meets on Fridays
    • Dec 7 - MS2 - test cases 
    • Dec 7 - Gambia 7.1 release 
  • Community labs
    • Trevor Cooper  asks Whether lab resources being allocated in an appropriate way.
    • Lab resources should be allocated for the benefit of the community, not particular individuals
    • Should we put a time limit on resource allocation? 
  • AoB
    • first 30 minutes of next week's meeting will be for regular TSC business and the following 60 minutes will be dedicated to the budget discussion 

Nov 13, 2018

Agenda

Minutes

  • Approval of minutes
    • No comments - minutes approved
  • Lightning talks at Kubecon in December 
    • Format update from Heather: 
      • No slides.  This will better promote a fast paced, engaging presentation.
      • 5 minutes instead of 10
    • Brandon Wick says that in choosing a talk proposal, the TSC should consider which is most likely to be engaging to the wider Kubecon audience, not just OPNFV or LFN.
    • David McBride will send a survey to TSC members to select between the two proposals.
  • Marketing Update Brandon Wick  
  • Chair Report 
    • Waiting for board to come back with report on budget status 
    • Tungsten Fabric Induction
  • Release update 
    • Gambia 7.0 going live today 
    • Intent to participate window closes Nov 23 (MS1). Release plans also due then. 
      • 29 projects intending to participate in Hunter. Expecting 2 or 3 more. 
    • Gambia 7.1 scheduled for Dec 7 
  • Infra update 
  • AI review 

Nov 6, 2018

Agenda

Minutes

  • Approval of minutes 
    • No comments - minutes approved 
  • release update
    • David McBride says that Compass is failing single vm health check then skipping remainder of tests.  This is consistent across scenarios.
    • David McBride says that there is insufficient test feedback to evaluate Compass-based scenarios for release 
    • The TSC votes and approves the release of Gambia 7.0 on Friday, Nov 9 without the compass installer and associated scenarios.
    • The TSC votes and approves the release of the Compass installer and associated scenarios if they pass health check by Friday, based on release manager's discretion.
  • Action item review
  • Chair report
  • Other topics on the mailing list.

Nov 1, 2018 (ad hoc meeting with MWG)

Agenda

  • Description of proposed Container Networking Workshop at Kubecon (X2) in 2019 Brandon Wick
  • Discussion of benefits of a Mini-Summit vs. the proposed Container Networking Workshop

Minutes

  • Brandon Wick shares a link to a description of the container networking workshop 
  • Brandon Wick says that the plan is to hold a full-day topic-centric, not project-centric, workshop at Kubecon to engage with the CNCF/k8s communities and discuss container networking.
  • There is concern about splitting the audience as well as the high cost of maintaining 3 events: fdio summit; opnfv summit; container networking workshop
  • Brandon Wick says that if OPNFV TSC determines that mini-summit is essential, then container networking workshop would probably be dropped 
  • Former user (Deleted) proposes keeping the budget item and having OPNFV work closely with MAC to determine topics 
  • TSC to discuss workshop proposal at Nov 6 meeting and make a decision
  • Former user (Deleted) says that he likes the approach of the proposed workshop, since Apex wants to engage more with k8s 

Oct 31, 2018 (ad hoc meeting to discuss budget)

Agenda

  • Review budget line items and decide on priority
    • Note:  sensitive cost data shared prior to the meeting via email to individual members

Minutes

  • Budget
    • Frank Brockners  shares a revised spreadsheet with suggested priorities for each line item
    • Question:  is "tech marketing" an LFN or OPNFV line item?
    • Question:  is the plugfest report a shared cost with ONAP, since we're having a joint event?
    • Question:  do we need to budget for two or three plugfests, since one of the plugfests was originally scheduled for Dec, 2018, but slipped into Jan, 2019
    • When discussing line item for local meetups, Former user (Deleted) asks how the community can be made aware of these events.
    • Question:  are local meetups an LFN or OPNFV line item?
    • David McBride to get a detailed breakdown, by vendor, for the "hosting" line item
    • Question:  are interns an LFN or OPNFV line item?
    • Frank Brockners comments that, over the long term, LaaS should become a shared cost across LFN as we move to make it available to users outside of OPNFV.

Oct 30, 2018

Agenda

Minutes

  • Approval of minutes from previous two meetings
    • No comments - minutes approved
  • Agenda bashing
  • Finalize budget roll-up for the board
  • hunter schedule
    • Trevor Bramwell makes the point the schedule does not reflect the continuous process, only the stable process
      • David McBride responds that this is true, because the CD process has not yet been established and is currently being developed by the RPWG.
    • The TSC votes and approves the Hunter schedule, as presented.
    • Trevor Bramwell  and David McBride  to add release schedule to location discussed by TAC 
    • CD process will be developed in the RPWG with a goal of having a recommendation by plugfest 
  • TAC representative
    • Frank Brockners asks whether we need to elect a new TAC representative. What is the term? 
    • discussion on whether or not TSC Chair = TAC representative 
    • Former user (Deleted) doesn't believe that there is a specified term 
    • Frank Brockners reviews charter. Charter just says that we will have a representative to the TAC. It does not specify a term. 
    • The TSC votes and approves that for the time being, the TSC chair Former user (Deleted) will act as TAC representative. The TSC further agrees that they will formalize the TAC representative and determine a term of service
    • Frank Brockners proposes a JIRA for the TSC 
      •  David McBride to setup a JIRA project to track TSC action items and resolution
  • TSC plan for the coming year
  • Release update
    • David McBride proposes delaying Gambia release one week due to problems with Apex and Compass installers. 
      • Further discussion in release meeting and mailing list, followed by email vote. 
  • infra update
    • Trevor Bramwell says that updates are planned immediately following Gambia release. Will describe in more detail on the mailing list. 

Oct 23, 2018

Agenda

Minutes

  • Approval of previous meeting's minutes
    • No quorum - deferred to next week.
  • Budget
  • UCS servers
  • OPNFV Plugfest - January 8 - 11, Nokia - Saclay-Paris, FR 
    • David McBride says that this will be a 4 day event , instead of 5 days, as done in the past
    • Plugfest will be 2nd week of Jan in Saclay (Paris)
    • Co-located with ONAP DDF
    • Former user (Deleted) says that the event will be hosted by Nokia - thanks to the Nokia team for accommodating us
    • David McBride says that the planning meeting will begin Monday, October 29 
      • invitation will be sent to the mailing list
    • Former user (Deleted) requests that we setup a joint call with the ONAP project
  • IT/Infra update
    • Kernel updates pending, to be scheduled so that they do not interfere with the Gambia release
    • Trevor Bramwell will send a scheduling proposal by mail
  • Release update

Oct 16, 2018

Agenda

Minutes

  • Approval of previous meeting's minutes
    • Note: we lacked quorum for the past two meetings, so the minutes for both of those meetings were considered.
    • No comments - minutes for the past two meetings approved.
  • Budget discussion
  • Other topics deferred due to lack of time

Oct 9, 2018

Agenda

  • Approval of previous meeting minutes
  • Agenda bashing
  • Planning for Plugfest - impact on company planning/budgeting
  • Election update David McBride
    • Schedule
    • Nominees
    • How does the TSC want to handle the TSC chair vote if there is a single nominee?
      1. Single nominee is named Chair without a vote.
      2. TSC votes for either the single nominee, or re-running the nomination process.
  • Proposal to investigate replacing UCS servers with packet.net support.
  • Budget discussion
  • Release update: David McBride
    • Kickoff meeting for Release Process Working Group on Friday, Oct 12, at 6 a.m. (PST).
  • LF IT/Infra update: Former user (Deleted), 

Minutes

  • Approval of minutes
    • Deferred to next week due to lack of quorum
  • Agenda bashing
    • Qiao Fu requests that we discuss Plugfest planning.  Topic is accepted for discussion today.
  • Plugfest planning
    • David McBride and Heather Kirksey describe the status of plugfest planning.
      • A Nokia site in France has been identified and discussions are underway.
      • Date would likely be in January.
    • Qiao Fu says that plugfest planning impacts budgeting for OPNFV.
    • Former user (Deleted) asks whether other organizations are in a similar situation.
    • Heather Kirksey offers to discuss issue with any organizations that would like more information about plugfest planning.
  • Election update
    • David McBride says that the nomination period for TSC chair is nearly over and there has just been one nomination. 
    • How would the TSC like to handle the situation where there is just a single candidate for TSC chair?
    • Discussion about different ways to handle this scenario.
    • Heather Kirksey says that LF recommends running an election even in the case of a single nominee.
    • General consensus that the new TSC should update the community election procedure to handle this situation.
    • TSC agrees to add a "no confidence" option to the ballot and run the vote with whatever the nominees are by end of the nomination period.
  • Proposal to replace UCS servers
  • Budget discussion
    • David McBride refers to an email sent to the mailing list last week.
    • Former user (Deleted) asks about the schedule for the budget process.
    • Former user (Deleted) makes the point that the new TSC should weigh in on the budget, but they won't be seated for a few more weeks.
    • Former user (Deleted) asks for a summary of spending for OPNFV, so that the TSC can understand in which areas funds are currently being spent.
    • Budget discussion will continue on the mailing list and in future TSC meetings.
  • Release update
  • Infra update

Oct 2, 2018

Agenda

Minutes

  • Approval of last week's minutes
    • Deferred to next week due to lack of quorum
  • Election update
    • One week left until TSC chair nominations close on Oct 9
    • One nomination for TSC chair, so far
    • See agenda for links to election schedule and list of nominees
  • Training resource discussion
    • David McBride notes that a discussion with Former user (Deleted) at ONS about his OPNFV training session led to a discussion with Former user (Deleted) about training resources, in general.
    • Training resources are dispersed.  There is no single location to find information on all available training resources.
      • E.g., YouTube, Linux Foundation, individual projects
    • Training resources are of varying quality, age, and relevance.
    • Former user (Deleted) says that the community should be aware of existing material & content, and have a chance to review & make suggestions.
    • David McBride to collect information on available trainings and report to TSC, invite others as needed.
  • Release update
    • David McBride says that MS8 (end of formal testing) is scheduled for Oct 30.
    • Hunter release page and schedule proposal in-process.  Will be presented to the TSC later this month.
  • IT/Infra Update
    • Trevor Bramwell says that there was a Jenkins outage last weekend
      • caused by "Next Executor" plugin
      • Plugin was disabled, leading to recovery
    • Cédric Ollivier asks if problems with build servers have been addressed. Trevor Bramwell says not yet  
    • PDX contract
      • Rudy Grigar says that PDX contract is up for renewal. 
      • cost will stay the same 
      • moving from a 3 year contract to a 1 year contract
      • new contract has more flexibility to change resource capacity as needed 
      • Former user (Deleted) to contact Jonne for instructions how to handle the PDX contract extension from LFN process point of view 
    • Replacing UCS with packet.net BMaaS 
      • Benefits include improving support and reliability. Also more flexible. We can change locations, attach additional hardware (traffic gen, acceleration, etc.) 
      • We would also get rolling updates. (
      • Former user (Deleted) suggests paying for one pod for a short period for evaluation. If successful, then make a longer commitment. 
      • David McBride to prepare a request to the TSC to approve evaluation of packet.net as a replacement for the UCS hardware at PDX, including making a request to the finance committee.

Sept 25, 2018 - Cancelled

Sept 18, 2018

Agenda

Minutes

  • Approval of last week's minutes 
    • no comments - minutes approved 
  • Change in scope for next OVP release
    • email from Georg Kunz
    • Georg Kunz reviews the reasons for changing scope (first presented last week)
      • no support for Keystone API v2 
      • requires that all commercial systems support v3 
      • this is a change in the original scope, which included support for v2 and v3 
    • The TSC approves of the change in scope for the next OVP release as described here.
      • Note that wenjing also supports the vote 
  • MS exception review
    • Barometer (MS5) - Has had trouble integrating with Apex tooling 
    • AGREED: the TSC approves of MS exception for MS5/6 for the Barometer project 
    • OVN4NFV - No representative 
  • Marketing Update(
    • Brandon Wick reminds everyone of activities at ONS, including UnConference sessions 
    • Brandon Wick notes that joint plugtest/plugfest report will be published next week 
    • Brandon Wick reviews the 2019 marketing plan 
    • Review of discussion questions LFN marketing group is using to help define goals for 2019 
    • Definitions of the primary audience and explanation of how marketing traction measured 
    • Further questions for defining 2019 goals 
    • Overview of Digital and Event marketing plans for 2019 
    • Question from Trevor Cooper  about whether marketing was focusing on testing only.  Heather Kirkseywill consider rewording slide bullets.
  • Release WG
    • David is working to organize release-wg meeting. Get in touch with him if interested.
  • TSC Gathering at ONS
  • IT/Infra
    • no planned maintenance 
    • fix for company firewalls that don't accept UDP 
    • looking into build server instability 
    • people with VPN credentials will need to renew. Trevor to send instructions. 
    • ACTION: bramwelt to send email to frankbrockners with description of VM/UCS issue and credentials to access system 
    • Cisco switch support approved by finance committee 
  • TSC meeting next week during ONS
    • Frank Brockners suggests polling TSC members about whether to have a meeting next week
    • David McBride asks if anyone opposes cancelling the meeting next week 
    • The TSC agrees to cancel the Sept 25 TSC meeting.

Sept 11, 2018

Agenda

Minutes

  • Approval of previous week's minutes
    • no comments - minutes approved
  • TSC election status
    • Discussion of different options as described in email last week
    • Several comments in support of doing nothing, since the impact of the error is fairly small.
    • The TSC approves of keeping the current active contributor list and continuing the process as per today (i.e. the election period ends on Sept 25)
  • Rocket project proposal
    • Former user (Deleted) highlights a new objective in the project proposal concerning making acceleration hardware available to the community (see objective 6)
    • Frank Brockners  says that his concern was that anyone who wants to contribute, should be able to contribute and that his concern has been satisfied
    • The TSC approves of the Rocket Project proposal.
  • Lab as a Service Phase 2
  • Release Milestone Exceptions
  • Change in scope for next OVP release 
    • Georg Kunz says that OVP no longer has access to Keystone API v2 
    • This changes expectation for system under test (i.e., must support v3 instead of v2)
    • Former user (Deleted) asks whether there was a deprecation notice from the Functest project. georgk says no.
    • Former user (Deleted) and Cristina Pauna indicate no effect on their respective projects, which already support v3 
    • Former user (Deleted) suggests a 1 week review period for projects to object to lack of v2 support 
    • Georg Kunz takes an action to start thread on TSC mailing list and include slide deck presentation 
    • Former user (Deleted) requests an email vote following the review 

Sept 4, 2018

Agenda

Minutes

  • Approval of previous week's minutes
    • no comments - minutes approved
  • OVP Governance
  • Rocket project - representatives unavailable, topic deferred
  • OPNFV LaaS - representatives unavailable, topic deferred
  • Docs hacking day
  • Release update
    • Several milestone exceptions from MS5 
    • MS6 this Friday, Sept 7 
      • Events: test case implementation, preliminary documentation, branch window opens 
  • IT/Infra
    • looking into meetbot stability. Team is making some fixes. 
  • AoB
    • TSC nomination period closes this Friday, Sept 7 at 5 p.m. (PT) 

Aug 28, 2018

Agenda

Minutes

  • Approval of Minutes
    • No comments - minutes approved
  • Continuation of Rocket project review 
    • Contributor, PTL, testing strategy, starting point have been updated per last week's request 
    • Frank Brockners  questions dependency of project on resources that are not publicly available 
    • Could we define a phase 1 that does not require hardware resources, followed by a phase 2, once the project is able to make hardware resources available publicly? 
    • Former user (Deleted) asks whether we can continue discussion in weekly technical discussion meeting
    • Former user (Deleted) suggests continuing discussion to next week. Former user (Deleted) agrees. 
  • election planning
    • David McBride will continue discussion about PTL input process to the active contributor list on the mailing list 
  • TSC F2F at ONS?
    • David McBride reports 5 yes / 5 no on email responses
    • We could meet informally, instead of a formal F2F TSC meeting.
    • The TSC agrees that we will have an informal gathering of the new TSC at ONS. Other community members are welcome as well.
      • David McBride will identify a location and time at ONS and report back to the TSC.
  • Remaining agenda items postponed to next week due to lack of time 

Aug 21, 2018

Agenda

Minutes

  • Approval of Minutes
    • No comments - minutes approved 
  • Rocket Project Review
    • Rocket project proposal
    • Rocket aims to provide a framework for accelerators (FPGA, ASIC, GPU, etc) for NFV, along with testing and mesurements of effects. 
    • Rocket is evaluating current NFVs to determine which are available for acceleration and is looking to create a common API for these accelerators. 
    • Will be working with upstream communities (ex: ONAP, OPNFV Edge Cloud, Akraino, K8S) to collect requirements and determine test scope.
    • Frank Brockners asks where the Rocket project would start 
    • Frank Brockners notes that the slide deck shows a different set of contributors than the wiki page
    • Former user (Deleted) notes that the wiki page is the authoritative list. He will update the slide deck. 
    • Qiao Fu asks about the PTL. 
    • Former user (Deleted) will cleanup the list of contributors and clearly identify the PTL for the project.
    • The TSC will defer the project review vote until next week.
    • Frank Brockners asks whether Rocket hardware acceleration resources will be available to the OPNFV community. Necessary for open source.
    • Former user (Deleted) will clarify testing and starting point
  • OPNFV Lab as a Service (LaaS) vendor support
  • LaaS roadmap / expanding availability to all of LFN
    • LaaS Timeline
    • Frank Brockners says that expanding support to all of LFN will require better management of resources, since usage is already 50 - 80% of capacity.
    • Frank Brockners says that LaaS project would like blessing from TSC for LaaS 2.0 (see description in timeline)
    • The TSC decided to continue the discussion and defer agreement to next week.
      • Note that the tentative "Agree" text was inadvertently captured by meetbot.  Please ignore this "Agree" statement in the meetbot minutes, since the TSC decided to defer a decision to the following week.
  • TSC election
    • David McBride to move discussion to mailing list due to lack of time.
    • Qiao Fu notes that Oct 1 - 4 overlaps with Chinese national holiday
    • Frank Brockners says that we should have two weeks for voting 
  • Plugfest planning deferred to next week due to lack of time.
  • David McBride requests that the release update and IT/infra update be sent to the opnfv-tsc email list.

Aug 14, 2018

Agenda

Minutes

  • Approval of last weeks minutes 
    • no comments - minutes approved 
  • Cisco switch support contract
    • Need support for Switches in UNH for LaaS 
    • Support required to get access to latest software for the switches and develop requirements for v2 of the network 
    • 38 HP servers are supported, not sure about ARM servers
    • Will need to make request for budget for LaaS support to the board
    • CDW says that we have up to a year after purchase to add support (Nov) 
    • Will need to purchase support every year
    • Disscuss LaaS again at Aug 21 TSC meeting
      • Proposal to expand availability to all of LFN
      • Update on LaaS switch and server support
  • Release working group
    • To form the group we need participants and a lead
    • Looking for ~5 people to form the group 
    • David McBride to send mail to the mailing list with a call for participation 
  • Release update
    • Proposal is to push all G milestones out by 2 weeks, which will move the initial release to Nov 2.
    • Email vote will be open until 8/16 midnight PDT
    • David McBride will send out email notification 
  • Trevor Cooper reminds the team that there will be an important Cloud Native discussion at the tech discuss meeting on Thursday, Aug 16
  • Update on joint plugfest planning
    • No decisions have been made.  Currently considering a Nokia site south of Paris.
    • Heather Kirksey suggests having plugfest planning as a longer topic for Aug 21 TSC meeting 
  • IT/infra update
    • Looking for agreement to enable mode on IRC channels to only allow registered users to join
    • Reason is because spam has become a problem and bogging down channels
    • Possible to turn off the mode before meeting to avoid people being locked out
    • Trevor Bramwellemail on IRC reg
    • Registration instructions
    • The TSC agrees to change the OPNFV IRC mode to require user registration by 5 pm (PT) on Thursday, Aug 16
  • TSC election planning

Aug 7, 2018

Agenda

Minutes

  • approval of previous minutes 
    • Initially, this was deferred to next week due to a lack of quorum.  However, quorum was achieved toward the end of the meeting and the minutes were approved.
  • Review LFN marketing structure, how to get marketing resources
    • OPNFV Marketing working group wiki 
    • Brandon Wick provided an overview of the current OPNFV marketing group. 
      • Brandon will send out additional emails to opnfv-tech-discuss and tsc mailing lists to encourage additional participants
    • Lisa provided an overview on current marketing structure with MAC and per project marketing working groups
    • MAC holds a dedicated marketing budget (i.e. is more than an advisory group)
    • Budget process is outlined on slide 5 of Lisa's deck (-> need to add link for reference)
    • Outline of budgeting events since 2018
    • Budget forms being sent to projects so that 2019 budgeting can be finalized by EOY
    • Overview of cost for 2018 hackfest/meetups/dev events
    • Open questions related to budgeting, such as How do individual project participate in events not included in approved LFN event list?
  • Release update
    • proposal is to move the schedule out by 2 weeks
    • due to lack of quorum today, we'll handle things via email vote
  • Cloud Native Working Group
    • The TSC agrees to create a new cloud native working group per what is suggested on the wiki
  • Update on Keystone Demo for ONS
  • LF IT/Infra update
    • no planned maintenance
    • Trevor Bramwell is proposing to switch IRC channels to requiring registration
      • reason is to eliminate frequent spam
    • Trevor Bramwell to send info on the projected change to the entire community - asking for feedback
    • TSC will take decision on the change next week 

July 31, 2018

Agenda

Minutes

  • Approval previous meeting minutes
    • no comments - minutes approved
  • Agenda bashing
    • Georg Kunz suggests a discussion of how long to maintain CI support for previous releases. We need to consider requirements for Dovetail.
  • Cloud Native working group
    • Former user (Deleted) says that comments have been reviewed and the proposal has been updated
    • Former user (Deleted) suggests that the Kubernetes work item should be separated into separate items and refined. Former user (Deleted) agrees with Tim's suggestion.
    • Former user (Deleted) asks, how do we get the right people into the working group? 
      • Former user (Deleted) plans to approach the team members of relevant OPNFV projects to request participation in the working group
    • Former user (Deleted) suggests that new OPNFV projects should be encouraged to be Cloud Native as appropriate 
      • in this case, the Cloud Native working group could act in an advisory capacity to new projects 
    • Frank Brockners suggests that a more concrete mission for the working group be defined
      • Frank Brockners to work with task force members towards a Cloud Native WG initial mission statement to be presented in next week's TSC call
  • Update from OPNFV marketing working group
    • Former user (Deleted) asks if demo submissions are publicly available for review 
    • Frank Brockners says that OSN Days are a good opportunity to refresh and update the OPNFV message. Can we be sure to have an OPNFV agenda items for each event? 
    • Heather Kirksey reminds the team that the OPNFV working group under the MAC still exists 
  • LFN marketing structure and marketing resources
    • Presentation by Lisa Caywood
    • Out of time.  We will continue this topic with Lisa at next week's meeting.
  • Release and infra updates will be posted to TSC mailing list in lieu of presentation at today's meeting, due to the lack of time.
  • AoB(dmcbride_, 14:02:58)

July 24, 2018

Agenda

Minutes

  • Approval of previous meeting minutes
    • Minutes approved without comments
  • Agenda bashing
    • Agenda approved
  • OPNFV update to LFN Board Jul 18th Former user (Deleted)
    • https://lists.opnfv.org/g/opnfv-tsc/message/4463 - Tim's summary presentation to the board
    • Tim notes that there were only few questions asked: Key question was availability of LaaS to other communities
    • Response was that this is the plan. Relies on LaaS maturing to the level where this is possible.
    • Follow up from LF to recruit a new program manager has already happened - public description of open rec is already available
    • Heather invited TSC members to spread the word and refer good candidates
  • Status & way forward on TSC task forces Former user (Deleted)
    • 2018 Goals Working Groups
    • Could the task forces provide for a gap analysis - which might inspire incremental work? Some task forces supplied for that.
    • Question by Tim: Several task forces span multiple projects: How can conclusions from the task forces be conveyed to the working groups? We could create a new WG from the task forces? How do we coordinate? Some body for coordination is required.
    • Task forces also have upstream peers (e.g. CNCF for cloud native task force). How do we keep the link intact - and also update the corresponding OPNFV projects
    • georgk suggests to have the recommendations as Jira tickets to that they are well documented and actionable
    • frankbrockners suggests to follow Tim's recommendation to create WGs for some of the task forces - especially cloud native.
    • That would create a touch point with CNCF and also a body which could monitor/drive progress
    • timirnich echos that comment - WG sounds like the right answer at least for cloud native TF
    • timirnich adds that for other TFs different approaches might be more feasible (e.g. OPNFV edge project could help coordinate things around edge)
    • timirnich suggests to revisit the topic in the next meetings - to distill conclusions for each of the TFs. We'll start with cloud native in the next TSC meeting.
  • Release update: Trevor Bramwell
    • https://lists.opnfv.org/g/opnfv-tsc/message/4450
    • https://lists.opnfv.org/g/opnfv-tsc/message/4458
    • no decision on changing the release schedule following the issues observed
    • trozet notes that Apex deployment issues are resolved (Apex deploys with ODL). Functest issues are being worked on right now
    • plan is to revisit the set of issues and decide to eventually postpone the release next week - once david mcbride is back
    • ask to all installer teams: Report status early next week so that David can drive a decision for the next meeting
  • LF IT/Infra update: Former user (Deleted), Trevor Bramwell

July 17, 2018

Agenda

Minutes

  • Approval of previous meeting minutes
    • No comments, minutes approved
  • OPNFV update to LFN Board Jul 18th Heather Kirksey
    • Important to explicitly convey the strengths of OPNFV and the impact the project has on our upstream communities
    • Frank states that some people on the board may not know what OPNFV does, some think all we do is testing
    • Also may not understand how OPNFV can be consumed
    • Qualify challenges into 1) asks to board 2) LFN business 3) OPNFV business
    • Heather says we have highlighted compliance to the board consistently including at last meeting was addressed hence not in this presentation
  • ETSI NFV Plugtest and OPNFV Plugfest Joint Report review Heather Kirksey
    • OPNFV rules state we will publish the report within 60 days but ETSI cannot meet this deadline
    • ETSI have asked to hold off until 1st week of Sep which is later than 60 days
    • No objections recorded
  • Next OPNFV Plugfest Trevor Cooper/Heather Kirksey
    • Intend to have a joint plugfest with ONAP
    • Looking for venues that can accommodate both communities, size is around 300-400 people
    • Brian Skerry states that co-hosting gives significant logistical benefit to member companies due to overlap of participants, makes compromise on the venue worthwhile
    • Frank states we should investigate feasibility before making a final decision
  • Release update:David McBride@Trevor Bramwell
    • Frank questions whether moving to Queens is the best option
    • Going forward community should decide on time based vs tied to Open Stack release
    • Heather questions if Queens is proving difficult for installers for a particular reason
    • Would be good to understand the reason for causing delay
    • Vacation is a factor
    • See Davids email ... will look at delaying the release 2 - 4 weeks and will give an update 31 July or 7 Aug
    • Tim Rozet states ODL is a factor for Apex installer
    • Will be discussed in release meeting
  • LF IT/Infra update: Former user (Deleted), Trevor Bramwell
    • Timing of update was not well communicated, will plan for improving this aspect going forwar
    • PDX hosting contract, Trevor B will get back with quote when available
    • Quote is for contract of space in Portland Data Center (POD 1 2 4 5 and build servers)
    • Current contract ends around Sep, Trevor will report back on date contract expires
    • Question as to 1 or 3 years to renew

July 10, 2018

Agenda

Minutes

July 3, 2018

Agenda

Minutes

  • Approval of Meeting Minutes
    • Meeting minutes approved 
  • Code of Conduct Reminder Heather Kirksey
  • Approval of OVP Test Scope
    • Comprehensive overview on test scope shared by email
    • Threshold has been redueced to 5 VM pairs, which is a degredation from the previous number 
      • Raises the question on what we do in the larger scheme of where we set the threshold of expected platform work, and related to that the threshold for releases
    • Higher load levels were found on commercial platforms 
    • OVP needs approval of scope in order to have time to adapt 
      • Release expected in 1-2 months, following approval of test scope
    • Via IRC vote, the TSC approved the proposed test scope for the next release of OVP
  • OPNFV Update to the Board on Jul 18th
    • Board wants to have some better communication from projects to know what's working/what's not, and how they can help.
    • Former user (Deleted)  to prepare draft of project update to TSC and email to list 
    • Update will be reviewed next week before the TAC meeting on the 18th 
  • Update from Working Groups
    • Edge Cloud Report 
  • Release Update
    • TSC agreed to move Gambia MS3.1 from June 29 to July 9th 

June 26, 2018

Agenda

Minutes

Note: the following topics were deferred due to an extended discussion about test scope:  OPNFV store, Goal WG Updates, LF IT/Infra update

  • Approval of minutes from the previous week
    • no comments - minutes approved
  • agenda bashing
    • exception for secondary repo for barometer deferred to next week
    • added topic for test scope for different tiers of CI (Fatih Degirmenci )
  • test scope for different CI stages
  • release update
    • Gambia MS3.1 - June 29
    • Fraser 6.2 scheduled same day
      • no additional scenarios joining
      • installers look healthy, recommendation is to approve the release
    • Via IRC vote, the TSC approved the release of Fraser 6.2 on Friday, June 29
      • Note: the meetbot vote command was used incorrectly, which caused the vote count not to be tallied in the meetbot minutes.  Here are the votes as copied from the IRC screen:

        • 06:44 bjskerry: #vote +1
          06:44 XavierCosta: #vote +1
          06:44 Wenjing: #cote +1
          06:44 ttallgren: #vote +1
          06:45 bh526r: #vote +1
          06:45 fdegir: #vote +1
          06:45 timirnich: #vote +1
          06:45 trozet: #vote +1
          06:45 julien-zte: #vote +0
          06:45 Wenjing: #vote +1
          06:48 rossella_s: #vote +1

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-06-26-12.57.html

June 19, 2018

Agenda

Minutes: 

  • Previous minutes approved
  • ONS-Europe: Brandon encouraged community members to make CFP submissions for both sessions (by June 24th) and demos (by July 9th).  Heather also added that there are no quotas/reserved slots for projects, but the programming committee members can ensure there are fair representations across communities.  There are also tabs in the CFP page with details on session selection criteria.  Brandon added that the plan is for VCO 2.0 demo to be featured as part of the keynote.  
  • Release update: David noted that that MS3.0 for Gambia was last Friday (15th) with Apex still experiencing issues.  MS 3.1 is on June 29th.  On testapi, new projects were having issues adding new test cases and there maybe a resolution on this.  There will be further discussion on testapi in the Test WG meeting on Thursday.  Trevor Bramwell added that having more people reviewing patches for testapi would be helpful.
  • Updates from Working Groups: 
    • For Cloud Native, the group will come back to the TSC once there are clear action items to report on.  
    • For cross-project collaboration, Fatih noted that there are specs for ONAP and OSM integration in the repo. Suggestions were also made to provide a cross-community report out to the TAC in August. 
    • On Edge, there was a follow-up session after the Plugfest and the team is working on a recommendation that can be shared in the next few weeks
    • For OVP evolution, the focus has been on the 2H'18 release, but the team needs to have another meeting for other recommendations
    • For CD-based release the plan is to move forward with a working group
  • LF IT/Infra update: Trevor Bramwell gave a reminder on groups.io migration this Friday (22nd), and email will be delayed/queued during migration.  Intel labs move is in progress and affected PTLs will be notified by the Intel team.  There was also LaaS issues doe to thunderstorm, but should recover soon.  Aric reminded the community on proposed LDAP group changes (https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2018-May/021340.html) and will follow-up with the TSC next week for an approval.

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-06-19-13.01.html 

June 12, 2018

Agenda

Minutes: 

  • Previous two meeting minutes approved
  • Plugfest recap: Ray noted that there was a good collaboration with the ETSI community during the Plugfest and daily huddles are captured at https://wiki.opnfv.org/display/EVNT/Fraser+Plugfest+Learnings.  Heather recommended that for future co-located with event with ETSI, there'd be a better pre-planning between the two communities. 
  • Gambia release themes update: Tim Irnich shared slides that was created after the community session during the Plugfest last week.  Frank added that during the discussion with the LFN Governing Board (GB), perhaps more focus should be on OPNFV community's asks/requests to the GB. A suggestion was made to iterate over email and gather community feedback. 
  • OVP Update: Georg discussed OVP & OPNFV releases alignment plus scope of previous/next OVP releases.  Georg also wants to come back to the TSC in a few weeks for an approval of the next release of the Dovetail scope. Georg will list pointers to test cases that TSC members can review prior to approval in a few weeks. 
  • CD-based release process: Tim Irnich shared an update as captured in https://docs.google.com/presentation/d/1YURd7MAhcf2Vx-KTg7zdiavdDVTB8hnY0C2vHFLldE4/edit#slide=id.p . There was a discussion if the new process would be similar to how ONAP projects operate today.  Tim added that the proposal is a starting point and wants to start a working group to address further details.  A question was raised if there's a need to differentiate between "release" of platform vs. application and will continue the discussion next week.
  • Release update: David mentioned that that Fraser 6.2 is on June 29th and MS3.0 (June 15th)/MS3.1 (June 29th) for Gambia are upcoming that installer teams need to work towards.  
  • LF IT/infra update: Trevor Bramwell gave a reminder on Intel labs downtime and that he is working with affected project teams. 

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-06-12-13.00.html

June 5, 2018

Agenda

Minutes: 

  • Update from the Plugfest: Ray noted that there's been good collaboration with the ETSI community and slides/notes from most sessions are available at Fraser Plugfest Schedule or Fraser Plugfest Learnings pages
  • Marketing update: Nan Zhou noted that the CFP deadline for ONS-Europe is in a few weeks.  Brandon will follow-up on speaker limits/session and project specific slots.  Brandon added that the demo submission deadline is in July.  Tim Irnich took an action item to start an email discussion to encourage submissions from OPNFV community.  
  • Workgroup updates: 
    • Cloud native: Wenjing noted that one of the recommendations from the group is to produce 2 k8s scenarios targeting much easier use by downstream.  Another is to allocate a long-lasting k8s pod.  The group also recommend asking all projects to adopt k8s, service mesh, CD, etc.  There was also a discussion on Pharos to produce an edge pod with cloud native stack, and Fu Qiao added that edge pod discussion is also planned during the Plugfest this week.  There was a consensus to visit progress against recommendations on a regular (e.g. quarterly) basis.  
    • CD-based release: Tim encouraged community members to review the presentation at the bottom of CD-based Release
    • Cross-community collaboration:  Ansible roles were discussed last week and the consensus is to discuss this with the ONAP community during their developer event in Beijing
  • Release update: David McBride noted that MS3.1 for Gambia is June 15th.  In addition, Fraser 6.2 is June 29th.  For 2019 releases, Hunter is the name for H-release and Iruya is the name for the I-release
  • LF IT/Infra update: Trevor Bramwell mentioned that upgrades went well last Friday and groups.io migration is schedule for June 22nd
  • Intel labs downtime is schedule for June 14-22 as noted in https://wiki.opnfv.org/display/pharos/Intel+Lab.  

MeetBot minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-06-05-13.01.html

May 29, 2018

Agenda

Minutes:

  • Previous minutes approved
  • XCI/OpenCI update: 
    • Fatih noted that for XCI there's progress on separation between XCI framework and scenarios.  CI evolution (e.g. patchset verification, post merge, etc.) and IDF/SDF/PDF are also continuing to make progress.  Finally, a number of k8s and OpenStack scenarios are now also part of XCI.  There was also a discussion on ONAP's plans for HEAT, and Tim Irnich took an action item to reach out to Gildas in the ONAP community to get more details.  
    • On OpenCI, Fatih noted that there's an opportunity to continue CI/CD discussions across different communities in OpenCI.  At OpenDev event last week, Fatih showed a prototype demo with ODL, ONAP, and OPNFV.  Fatih encouraged people involved in Edge, Cloud Native, and testing initiatives to get involved in OpenCI discussions.
  • OpenStack Fenix project: Tapio noted that Doctor team is looking for volunteers to get involved in Fenix and there will be discussion on Thursday's weekly call.  More details can be found at https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2018-May/021311.html. 
  • Updates from 2018 Goals Working Groups: 
    • CD-based Release: Plan to make a presentation during next week's TSC.  
    • OVP evolution: Team is seeking feedback on https://etherpad.opnfv.org/p/tsc_ovp (esp. the NFV features section). 
    • Edge: The team will have hacking/report out sessions during the Plugfest. 
    • Cloud native: Following discussions during last Thursday's Technical Discussions call, the team will come back to the TSC meeting next week
    • Cross-community collaboration: Fatih noted that there was a discussion with the OpenLab team during OpenStack Summit and possibility for collaboration on LaaS. 
  • Release update: 
    • David McBride noted that Fraser 6.1 release was May 25th and artifacts have been verified and will be posted on the downloads page tomorrow.  Gambia MS2 was also Friday and David is confirming MS compliance.  Poll for H & I release names is in progress and will close on Friday (June 1st).  
    • There are a couple of milestone exceptions requests for Daisy and Qtip teams (from ZTE) in addition to Orchestra (MS1) and ONOSFW (MS0 & MS1).  The TSC agreed to grant exception requests to all 4 projects.  
  • LF IT/Infra update: Aric/Trevor Bramwell mentioned that upgrade to CentOS 7.5 will be scheduled Friday afternoon Pacific Time.  There will also be upgrade to Jenkins 2.108.  On the groups.io migration, there was also an agreement from the TSC to go ahead with the migration in the 2H of June'2018.  
  • Update on Export Administration Regulations: There was a discussion on the impact on key projects like Pharos and Releng-testresults.  Tim Irnich/Ray took an action item to reach out to the committers of the two projects and see if anyone can step up to fill in as "temporary PTLs".  

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-05-29-13.00.html

May 22, 2018

Agenda

Minutes:

  • Previous minutes approved
  • Plugfest schedule update: Ray shared the latest event schedule at Fraser Plugfest Schedule
  • Updating the inventory of unmodified/3rd-party files: There was a quick discussion on email responses from project teams on the presence of commonly used 3-party libraries.  Via IRC vote, the TSC approved inclusion of these 3rd party libraries in the OPNFV repo.  
  • Report out from the Cloud Native Working Group: The team have recommendations for several areas such as container management, container networking, micro-services support, etc. that are listed in the wiki page.  Discussion ensued and there was an agreement to have a deep dive session during Thursday's weekly call.  
  • Release update: David McBride gave a reminder that Gambia MS2 (test case documentation) is this Friday (25th).  A poll will be going out for naming H & I releases later in the week.  For MS exception reviews, David is looking for volunteers to be on the review team.  On Fraser 6.1 (May 25th), compass/fuel teams are working to resolve remaining issues and 43 scenarios are intending top participate in Fraser 6.1.  Via IRC vote, the TSC approved the release of Fraser 6.1 on May 25th.
  • LF IT/Infra update: On groups.io migration, there were questions on user passwords and attachments, and Ray took an action item to follow-up with the LF IT team.  

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-05-22-13.00.html

May 15, 2018

Agenda

Minutes: 

  • Previous minutes approved
  • Fraser launch update: Brandon mentioned that there were a number of pre-briefings with Tim Irnich and Heather and there was a good media pick up of key messages around cloud native and a good total media clip count (300). The marketing campaign helped drive traffic to opnfv.org, the software landing page, docs page, and to docs.opnfv.org). Brandon noted that most categories were roughly comparable to the Euphrates release.  Frank asked how these numbers compare to releases prior to Euphrates.  Brandon took the action item to get these numbers and post the slides on the wiki. DONE. See the Fraser rollup and release comparison slides. 
  • Updating the inventory of unmodified/3rd-party files: Ray shared the list of 3rd party files from the April license scan and there was a good discussion on why some fo these files (e.g. specialized fonts) are needed in OPNFV.  Ray noted that all PTLs are aware of presence of these files and that's why they all reside under the "3rd party" directory.  Ray took an action item to follow-up on the email thread with PTLs on why these files are needed in OPNFV.
  • LFN TAC meeting update: Tim Irnich summarized discussions from last week's TAC meeting on project representation at the LFN Governing Board (GB) and budget process.  
  • Updates from the 2018 Working Groups: 
    • CD release process: Not much progress, but this is a standing topic in the weekly release call
    • OVP: Kubi noted that the team has been working on feature priorities list for future releases (https://etherpad.opnfv.org/p/tsc_ovp) and welcome community feedback.  There will also be a session at the Plugfest.   
    • Edge: Fu Qiao mentioned that the team started polling edge related projects in OPNFV and also figuring out collaboration with Akraino.  Trevor Cooper added that there's Akraino kick off at Intel this week plus numerous edge related sessions at OpenStack next week
    • Cloud Native: Wenjing noted that the team is meeting this week to finalize their documents and will be ready to present at next weeks TSC.  Ray will reserve 15-20 minutes for the Cloud Native team next week.  
    • Cross-community: Frank noted that the team is continuing to work with CNCF and ONAP communities.  (See https://gerrit.opnfv.org/gerrit/#/c/56815/ plus https://gerrit.opnfv.org/gerrit/#/c/56895/)  
  • Release update: David McBride mentioned that that MS1 for Gambia was last Friday (11th) with 35 projects participating.  There are 14 projects participating in CD release track plus 6 participating in both CD & traditional tracks.  Both Functest & Yardstick teams have concerns about supporting the CD release track and will likely be a challenge for Gambia.  Fraser 6.1 is May 25th and TSC will need to review the release status next week.  Nominations for H & I release names are continuing this week at https://wiki.opnfv.org/display/SWREL/Future+release+name+candidates 
  • LF IT/Infra update: Trevor Bramwell noted that there is a security update related to CentOS upgrade.  This will require reboot and plan is to do this maintenance after Fraser 6.1.  Ray proposed migration to groups.io of OPNFV mailing lists and the migration will take about an hour and all the archives/email addresses will be maintained.  There was a question is user passwords will carry over to groups.io and Rudy took an action item to investigate this. 

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-05-15-13.00.html

May 8, 2018

Agenda

Minutes:

  • Previous two meeting minutes approved
  • Update on Fraser messaging: Heather noted that there were several briefings that she & Tim Irnich participated and there were positive coverage on Fraser.  Even at KubeCon, there was a lot of interest among CNCF communities around OPNFV's XCI and CI/CD work.  Will request Brandon to come back next week to provide more detailed updates on Fraser coverage
  • Reminder on Fraser release awards nomination & Plugfest:  A suggestion was made to extend the deadline for awards nomination to May 16th as many community members may be out this week.  
  • eNFV termination review: Prayson noted that there has not been any activity in the project for well over a year and there's also a new project Edge Cloud that is starting in OPNFV.  Via IRC vote, the TSC approved termination of the eNFV project.
  • Committer list for Edge Cloud: Fu Qiao shared the committers list as they are listed in Edge cloud, and the TSC members agreed on the committers list as presented.
  • Updates from 2018 Goals Working Groups: Tim Irnich noted that the CD release group will recommend forming a working group to focus on the topic.  On cross-collaboration, Fatih/Frank mentioned that the focus has been on working with ONAP and CNCF.  Tim recommended using the Plugfest for community updates/discussions on working groups.
  • Release update: Ray gave a reminder that Fraser 6.1 May 25th and for Gambia the intent to participate & project plans are due May 11th.  On release naming for H & I releases, there was a consensus to rotate through Oceania and S. America respectively.  
  • LF IT/Infra update: Trevor Bramwell suggested reboots this Friday for Gerrit & Jenkins (post-build script) plug-ins.  
  • LFN GB update slides: There was a suggestion to add caveat on LaaS to note that it's still work-in-progress and include top messaging (cloud native and mature functionalities) for the Fraser release.  

MeetBot minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-05-08-12.59.html

May 1, 2018

Agenda

Meeting minutes: 

  • Fraser release update: Brandon noted that the marketing release of Fraser will go live today including PR, Tim Irnich's blog, downloads page, info graphics, etc. around 8am PT today.  Heather expressed her appreciation for community's work and noted that Fraser messaging was well received during Fraser briefings last week.
  • Updates from 2018 Goals Working Groups: 
    • CD release: Tim Irnich mentioned that he expects a report from the CD release team to be coming shortly
    • Edge: Trevor Cooper shared that recent activities has been to survey relevant project within OPNFV and see if there are gaps, opportunities for collaboration.  Notes have been captured at https://etherpad.opnfv.org/p/tsc_edge_cloud_project_questions
    • Cloud Native: Brian Skerry noted that the group is working on several recommendations such as container management, container networking, cross-project collaboration, support for middle box, etc. 
    • Cross-project collaborations: Fatih reported that conversations have started with the ONAP community.  
  • Release update: David McBride mentioned that Fraser 6.1 date is May 25th.  For Gambia, 17 to 18 projects have expressed their intent to participate, and so far there's an even split on projects participating in traditional vs. CD release models.  David also gave a reminder that Gambia release plans should be completed by May 11th.  
  • LF IT/Infra update: On Jira federation with the LF, Thanh noted that both fd.io and ODL have already completed their federation with the LF.  There was an agreement for OPNFV to also do the federation with LF.  Trevor noted that there's a plan to upgrade JMS plug-in for Jenkins and reviewers plug-in for Gerrit this week.   

MeetBot minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-05-01-13.01.html

April 24, 2018

Agenda

Minutes:

  • Previous two meeting minutes approvedd
  • OPNFV marketing update: Nan Zhou introduced his role as a TSC liaison in the OPNFV marketing working group.  Under MAC there are several working groups including ones focused on projects such as fd.io, ODL, ONAP, and OPNFV.  Brandon gave a quick overview of Fraser messaging including increased cloud native support, new maturity on testing, carrier grade features in monitoring, service assurance, networking/dataplance acceleration, adoption at operators, etc.  The draft materials will be distributed to the TSC for review prior to launch.  Nan also added that there is also a plan to enhance the OVP web assets.
  • Creation review for Edge Cloud: Fu Qiao noted that project discussion kicked off at ONS and and the goal is to address service requirements for "Edge" (e.g. limited space/power resources, light weight management, unattended, etc.) Fu Qiao also discussed several upstream communities such as OpenStack, Akraino, ONAP, ETSI, etc. that have different Edge initiatives.  The plan is to begin with requirement analysis, then define reference platform design while working with upstream communities plus developing test strategy.  There was also a discussion that the Edge HW spec is in the context of the Pharos project.  Fu Qiao also took an action item to trim down the committers list for the project.  Via IRC vote, the TSC approved the Edge Cloud project.  
  • Release update: David McBride first discussed the MS5 Exception Review request for the SFC project on the Compass installer, and the TSC agreed to grant an exception.  David also discussed that there's been an improvement in scenario status since last week and scenarios that are not ready for 6.0 could get themselves ready by 6.1 or 6.2.  David will also be confirming with scenario owners on 6.0 readiness.  Via IRC vote, the TSC approved the Fraser (6.0) release on April 27th.  
  • LF IT/Infra update: The TSC agreed to Jira federations with other LFN projects.   

MeetBot Minutes: http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-04-24-13.00.html

April 17, 2018

Agenda

Minutes:

  • Approval of previous meeting minutes deferred until next week when Former user (Deleted) has returned.
  • Frank Brockners added "TAC meeting update" to the agenda
  • Update from each Goals Working Group:
    • Cloud Native
      • Former user (Deleted) says that draft document has been generated that describes objectives and activities of Cloud Native group
    • Collaboration
      • Frank Brockners says that collaboration team is initially focused on ONAP and LaaS
    • Edge
      • Trevor Cooper  says that notes on Edge project can be found on etherpad
      • Qiao Fu says that there is a kickoff call tomorrow to discuss project proposal
        • there will also be a discussion during the weekly community technical discussion on 04/18
      • Former user (Deleted) wonders if the OPNFV Edge project will be sufficient to drive the topics in the TSC Edge group
    • Release
      • David McBride says that this will be an ongoing agenda item for the release meeting. TSC release group may provide direction for additional or alternative meetings.
    • OVP
  • TAC meeting
    • Frank Brockners says that there was a discussion about establishing criteria for accepting projects into LFN
    • TAC wants to establish project lifecycle, which will drive how projects are managed
    • TAC repo
    • discussion about board representation for projects (e.g., OPNFV, ONAP, ODL, etc)
    • Former user (Deleted) emphasizes that TAC meetings are open to everybody
    • Former user (Deleted) says that participation in the TAC had direct impact on individual projects
  • Release update
    • David McBride provides summary of installer health and scenario status.  Discussion follows.
    • David McBride proposes slipping Fraser release schedule 1 week to April 27.  No change to point releases.  No change to Gambia.
  • IT/Infra update

Meetbot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-04-17-12.56.html

April 10, 2018

Agenda

Minutes: 

  • Approval of previous meeting minutes: Minutes of previous two meetings approved
  • Vote on the TSC Charter Update: Ray discussed updates made based on community feedback.  There was a suggestion to PDF the community elections procedures page and post it under opnfv.org.  Via IRC vote, the TSC approved the new TSC Charter and the community elections procedure reflecting OPNFV's move to merit-based TSC.
  • OPNFV 2018 goals and TSC backlog: Tim Irnich noted that a couple of work groups already started populating their wiki pages and there will be regular updates on the TSC call as a standing agenda item.  
  • Plugfest update: Ray noted that the planning page has been created and there is a group of volunteers for the programming committee.  The plan is to limit to 3 simultaneous tracks.  There was also a consensus to  investigate co-locating the Gambia release Plugfest with ONAP's developer event in December.  
  • Release update: David McBride noted that there has not been sufficient progress post stable branch.  There was an agreement to have another checkpoint on the Fraser release during Weekly Technical Community meeting on April 12th.  Intent to participate for the Gambia release will kick off on April 13th.
  • LF IT/infra update: Trevor Bramwell noted that Jira/Etherpad upgrade was successfully completed over the weekend.  

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-04-10-12.59.html

April 3, 2018

Agenda

Minutes:

  • Approval of previous minutes: due to audio issues last week, votes from the previous meeting will be re-done and approval of minutes will be done next week
    • Via IRC vote, the TSC approved MS6 exception for the Clover project.  
  • TSC Charter update reminder: Ray encouraged community members to review the TSC Charter update (https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2018-March/020787.html) prior to the vote next week
  • OPNFV 2018 goals and TSC backlog: Wenjing noted that the goal is to identify TSC owners for major activity items with the view of team report outs on a regular basis.  Wenjing also encouraged volunteers to start meeting/discussions and document progress on the wiki (Ray took an action item to create a new wiki page for this)
  • Release update: 
    • Fraser: David McBride noted that there's about 60% reporting for MS7 and is following up with other projects.  
    • Gambia: There has been discussion on having a parallel track for Continuous Delivery in addition to traditional release milestones. Fatih noted that a project can decide to participate in one or both release tracks, and there was a discussion on limiting the participation to a small number of projects in Gambia so we can figure out the details for this "parallel track"
    • Via IRC vote, the TSC approved a choice of two release procedures for the Gambia release. This will include the traditional OPNFV release process, as well as a new release process based on continuous delivery. Projects will have the choice to participate in one or both processes.  
  • LF IT/Infra update: Trevor Bramwell gave a reminder that there will be an upgrade of Jira/Etherpad this Saturday (April 7th) at 10:30am Pacific Time.  

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-04-03-13.00.html

March 27, 2018

Agenda

Minutes: 

[NOTE:  All votes from this meeting as captured in the MeetBot is to be re-done in future meetings.  Due to audio issue in the meeting room at ONS, remote TSC members were not able to fully participate in the TSC meeting.] 

  • Previous minutes approved
  • LF IT/infra update: Trevor Bramwell gave a reminder on Jira/Etherpad upgrade
  • MS6 exception review for Clover: Stephen Wong noted that the plan is to get caught up with both MS6 & MS7 by March 30 and the preliminary documentation is already complete.  The milestone exception review team also reviewed the exception request and there were no objections.  
  • Release update: David McBride noted that MS7 is this Friday (for stable branch) and there's a new process where the branch is initiated by PTLs and Trevor Bramwell has created documentations.  David aded that a new release process starting with the H-release was discussed at ONS and the proposal is to stay with the same release process for the Gambia release.  Fatih noted that it'd be good to have an avenue for projects to follow the XCI model (vs. requiring all projects to stick with the traditional release process).  There was a good discussion on creating "parallel" tracks for projects and David McBride and Fatih will propose an alternative track (following the XCI model)by the next TSC call.
  • Recap and way forward - OPNFV 2018 goals and TSC backlog: Tim Irnich noted that he wants to move the discussion forward by forming "task force" on key items on the etherpad.  Tim wants to ensure that TSC members are involved in key items but participation will be open top everyone.  Interested TSC members can add their names next to topics on the etherpad
  • OPNFV internship update: Ray gave an update on completed/on-going OPNFV internship projects and added that there's budget for internships across all LFN projects in 2018.  There's also budget for intern travel, but this is based satisfactory grade from mentors at the end of the internship.
  • AoB: Ray mentioned that new TSC charter text with merit-based composition will be distributed for review and voting will be done in ~2 weeks.  

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-03-27-16.01.html

March 20, 2018

Agenda

Minutes:

  • Previous minutes approved.  
  • TSC rep. replacement: Dave Neary will be taking on a new role and is recommending Tim Rozet to take his place.  The TSC agreed that Tim Rozet will be the new TSC representative from Red Hat for the remainder of the term.
  • TSC meeting time: Tim Irnich noted that since there will be a large contingent of TSC members at ONS next week we re-schedule the TSC meeting to 9am Pacific Time in the OPNFV Breakout room (K-Town)
  • PDF/IDF and dynamic CI introduction: Julien noted that PDF/IDF have been released for Fuel/MCP and Daisy while other installers' work is in progress. On PDF, there have been communications with all Pharos lab owners although 4 lab owners have not been responsive.   Proposed final dates for PDF creation is April 15th and June 15th for installers to use PDF/IDF.  There were also good discussions on applicability of PDF/IDF to other communities and that PDF could be extended to other non-Pharos configurations in the future. Via IRC vote, the TSC approved the PDF spec 1.0 as mandatory baseline for CI in Pharos pods and the three staged introduction time plan.  
  • Releng graduation review: Fatih noted that Releng is the first infra project going through a graduation review and project has been a community-wide effort from the beginning.  There has been good progress on scaling CI, common tooling/utilities, and XCI.  Current focous is on CI evolution, 3rd party/dynamic CI, XCI framework/scenario on-boarding.  Going forward, there's a need to work on release process improvement, scenario consolidation, 3r party CI with fd.io, investigate new tools, etc.  Via IRC vote, the TSC approved graduation of Releng as a mature project.
  • Release update: David McBride noted that MS6 was March 16th and there are still ~10 projects that have not met MS6 requirements as of today.  There's also an MS6 exception request from Clover.  David also discussed changes he wants to propose beginning with the H-release.  First, David wants to reduce the time following the OpenStack release for the OPNFV release and increase the time between MS3 and MS5. The proposal is to start the "intent to participate" to 2 weeks prior to OpenStack release and collapse MS3.1 and 3.2.  This may require dropping point release(s) for Gambia.  As time was running out, proposal is to communicate this further in the mailing list and potentially discuss at the next TSC meeting.  

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-03-20-13.00.html

March 13, 2018

Agenda

Minutes: 

  • Previous minutes approved
  • Update on LFN certification & complaince discussion: Chris Donley summarized discussion on LFN-level compliance program and stated that the goal is to be responsive to individual technical communities, be transparent, share work across communities, etc.  There would be common legal framework, infra, tool chain, etc.  However, there would be differences in each community for test plans/tools and individual TSCs would be responsible for approving test content.  The LFN-level compliance committee would be responsible for the test framework.  Chris also added that there has already been collaboration between OPNFV and ONAP on using Dovetail's framework for VNF testing.  
  • Exemption from strict API validation in Dovetail/OVP: Georg shared additional attribute examples as a follow up from the last meeting.  Trevor Cooper added that the purpose of OVP is to test platform capabilities (vs. API compliance).  Exemption will be valid for 1 year and only two exemptions are possible per product.  Via IRC vote, the TSC approved he exemption process for strict API response validation in OVP.
  • Update on Strategic work items in TSC: Tim Irnich reviewed the current draft of the 2018 Goals page.  There was a good discussion on adding more details on upstream collaboration, new initiatives, etc.

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-03-13-13.00.html

March 6, 2018

Agenda

Minutes: 

  • Previous minutes approved
  • Final check on TSC composition: There was a discussion on the TSC composition as summarized on the wiki page, and feedback from a number of people on election timeframe is to maintain the September schedule.  Ray has an action item to start working with the TSC to update the charter and come back to the TSC for a vote.
  • Exemption proposal in Dovetail for strict API validation: Georg noted that strict API validation topic has been discussed both within Dovetail team and the C&C committee.  This is related to validation in Tempest tests for Nova and the proposal is to allow Nova tests to pass if tested functionality is supported by relaxing the Strict API validation.  OpenStack had similar exemption process for about a year in 2016.  If approved, the Dovetail team will make this a service release of OVP 2018.01 and there's no proposal for an end date for the exemption process.  Georg took an action item to outline examples on the wiki or patch and will return to the TSC.
  • Strategic work items in TSC: There was a good discussion on items that have been added to the Etherpad and there were suggestions to add new items such as Edge Cloud and "OPNFV installer".  A comment was also made that there needs to be action/results beyond agreements.  The Etherpad will remain open, but a new wiki page will be created re-organize/summarize the information on the Etherpad.  
  • Release update: David McBride noted that MS5 was on March 2nd and overall there's been good compliance while he follows-up on a few scenarios.  MS6 is next Friday (March 16th) for preliminary documentation and test cases.  David also discussed pulling in MS7 (stable branch) a week and added that there has been no objections from the community (esp. installer teams).  The TSC agreed to pulling in MS7 to March 30th.
  • LF IT/Infra update: Trevor Bramwell noted that Jenkins plugin update completed last week and there are no planned maintenance.  
  • NFV Interoperability Certification Program: There was a discussion on the program and Wenjing added that MAC is aware of the program, but this is a "private" program among members.  


MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-03-06-14.01.html

February 27, 2018

Agenda

Minutes: 

  • Previous two meeting (February 13th & 20th) minutes approved
  • TSC composition, proposed metrics for active contributor: There was a discussion to focus on community contributions on Git/Gerrit/Jira/wiki while giving an opportunity for PTLs to appeal if anyone falls through the cracks based on metrics.  Rossella made a suggestion to document the appeals process.  Ray took an action item to update the TSC composition wiki page prior to the next TSC meeting.
  • LFN Developer Forum: Tim Irnich discussed that TAC representatives agreed to increase the number of plenary session slots from 12 to 20 and the TAC representatives will be grading the 33 session proposals.  Tim also encouraged community members to add topics for OPNFV breakout sessions at https://wiki.lfnetworking.org/display/LN/OPNFV+Unconference+topics+at+LFN+Developer+Forum
  • C-RAN creation review: Changming notes that one of the goal of the project is to consolidate compute resources to run radio access function in data center.  There are "sub-projects" including RAN-VNF, analysis of requirements for a shared platform for MEC and RAN use-cases, and architecture design for hardware acceleration for RAN.  There was a discussion if there are additional hardware requirements to existing Pharos labs and Changming noted that focus this year will be mostly on requirements gathering.  Via IRC vote, the TSC approved creation of the C-RAN project. 
  • Strategic work items in the TSC: Tim Irnich will be setting a separate meeting to follow-up on the email discussion on this topic prior to the next TSC call.  Tim will also share an Etherpad that community members can review and add feedback.  
  • Release update: David McBride noted that MS5 is March 2nd where Jenkins jobs need to be created for all scenarios.  For MS6 (March 16th), test cases and preliminary documentations also need to be completed.

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-02-27-13.57.html

February 20, 2018

Agenda

Minutes:

  • Approval of minutes deferred until next week due to Ray's absence.
  • Former user (Deleted)  gave a presentation on the status of LaaS, and then shared a mockup of the proposed dashboard.  
  • Former user (Deleted) led a review of the draft 2018 OPNFV goals.  Tim took an action to check with Former user (Deleted) on the timeline for goals/budget input.
  • David McBride said that Fraser has two important milestones in the next few weeks.  MS5 is scheduled for March 2, which requires scenario owners to complete scenario integration.  MS6 is scheduled for March 16, which requires implementation of documented test cases. In addition, projects are required to complete preliminary documentation.
  • Trevor Bramwell said that the Jenkins update was successfully completed.  In addition, Confluence was updated, and includes a new feature that enhances collaboration on documents.
  • Former user (Deleted) provided a recap of the TSC composition discussion.  Tim said that he would like to set the bar lower than the 50 - 100 contributions that Former user (Deleted) suggested last week.  Former user (Deleted) asserted that contribution quality should be taken into consideration, in addition to contribution quantity.  Former user (Deleted) suggested that we should run analytics on the vote to determine if the process works properly.  Bryan also said that we should consider also using meeting attendance as a metric. Agreed on minimum contribution proposal of 20 contributions.


MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-02-20-13.53.html

February 13, 2018

Agenda

Minutes: 

  • Previous minutes approved
  • TAC update: Tim gave an update from yesterday's first TAC call including TAC goals/missions, elections (GB representatives/Chair), future meetings (bi-weekly/open meetings), face-to-face meeting at ONS, process for budget requests.  Technical community budgets will be based on goals that are communicated to the LFN Governing Board.
  • LFN Developer Forum at ONS: Tim noted that a group of volunteers (incl. Dave Neary, Wenjing, Fatih, and Ray) met to start planning discussions on the developer forum.  The deadline to add plenary topic suggestions in February 23rd.  
  • OPNFV 2018 goals and budget needs: While reviewing the budget item, there was a suggestion to call out the LaaS hosting costs.  There was also a good discussion on events for the OPNFV community.  Heather added that there will be an OPNFV sub-group under the MAC (Marketing Advisory Council) and made a suggestion to focus on community goals vs. individual budget items.  
  • Release update: David McBride noted that MS5 (scenario integration + feature freeze) is coming up on March 2nd and will need to see Jenkins jobs by this date.  MS6 is two weeks later and includes preliminary documentation.
  • LF IT/Infra update: There were upgrades done to Gerrit/Confluence over the weekend.  In addition, Jenkins upgrade is ready to go after 3 weeks of testing.  The TSC agreed with moving forward with the Jenkins upgrade.
  • TSC composition: Ray shared the data on 2017 contributors across OPNFV tools including Git, Gerrit, Jira, and wiki.  There was a good discussion on using a threshold of 50 vs. 100 for a "union of contributions" across the tools.  As time was running out, suggestions were made to continue the discussion over email.  

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-02-13-14.01.html 

February 6, 2018

Agenda

Minutes:

  • Previous minutes approved
  • Update on OPNFV Verified Program (OVP): Chris Donley noted that OVP will launch today with Huawei, Nokia, Wind River, and ZTE being the first group to receive OPNFV Verified logos.  Discussion has also started on cross LFN compliance programs and there will be a bi-weekly meeting on Wednesdays starting next week. Chris is happy to include anyone interested in these meeting calls.
  • Docs Hacking report out: Sofia reported that ~20 people from 6 sites participated in Docs hacking last week and the list of work items are captured at https://wiki.opnfv.org/display/EVNT/Docs+Hacking.  Tim Irnich suggested repeating the event in the future, also for other things than docs (e.g. bug scrubbing).  
  • TSC member backfill: There is a proposal to have Trevor Copper backfill for Maryam in the TSC for the remainder of her term during maternity leave.  The TSC agreed to the proposal.
  • LFN TAC update: Tim Irnich noted that the first LFN TAC meeting is on February 12th.  There was a good discussion on potential topics including events and budget.  Ray took an action item to start a wiki page listing budget items for OPNFV technical community in the past.  Ray will also find out if TAC meetings will be open to everyone.  
  • LFN Developer Forum: There was a discussion on ONS registration discount for developers plus re-organizing Developer Forum planning pages across wiki's.  Dave Neary, Wenjing, and Fatih volunteered to help curate/review proposals for the Developer Forum.        
  • Release update: David McBride noted that MS 3.2 were completed for installers last week and MS5 (scenario integration & feature freeze) is March 2nd.  David asked community members to report any stability issues prior to MS5.  David is also working on a proposal for Gambia release process. 
  • LF IT/infra update: Aric discussed that updates to the Gerrit page to add OPNFV logo plus links for OPNFV tools will require a reboot to Gerrit during the next maintenance period and the TSC agreed to moving forward with this.

 

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-02-06-14.02.html

January 30, 2018

Agenda

Minutes: 

  • Previous minutes approved
  • TSC member backfill: Ray confirmed that a TSC member can propose an alternate/replacement that the TSC members can vote on if that's what TSC decides to do.  The TSC agreed to vote on an alternate TSC member proposed by Maryam for the remainder of her term.
  • OPNFV Verified Program (OVP) launch update: Chris Donley noted that the plan is to launch OVP on February 6th and beta participants are re-submitting their results.  Brandon added that one of the reasons for not launching this week is that there was a desire to space out news from the LFN launch last week.  Press release draft will be circulated among marketing plus C&C committee members and there will also be a blog post penned by Chris Donley.  Chris added that the community is in early stages of discussion regarding the "second release" for OVP
  • Release update: David McBride mentioned that MS3.2 (pass health check for sdn-based scenario) is this week and installer teams are on track for the milestone.  The next major milestone is MS5 (scenario integration) on March 2nd.
  • LF IT/infra update: Trevor Bramwell noted that that Jenkins server testing will continue this week.  There was also mailing list queues yesterday and this had been fixed (no mails have been lost).  Aric discussed the patch to easily identify PTLs from INFO files and that this will be discussed on Thursday's Technical Discussion call for community feedback.  The purpose of this is to only allow PTLs to update information on the TestAPI.
  • Update on Apex installer: Dave Neary discussed that Apex team would like to move towards XCI-like model (pointing to the tip of trunk) and had discussions with a number of PTLs plus David McBride.  There was a discussion that we're in the middle of the Fraser release cycle and there is a potential impact on the release.  A question was raised if the transition can wait until Fraser stable branch is cut (in case there's a big risk in moving from OpenStack Pike to Queen).  Tim Rozet added that Apex has the ability to deploy different versions of OpenStack and ODL. Versions can be supplied in the deploy settings file, and artifacts will be downloaded at deploy time from upstream. Also, upstream OpenStack Gerrit patches can be provided which will be automatically pulled in and applied during deployment.  A discussion ensued on a need to vote on a version of OpenStack (or other upstream components) for an OPNFV release.  A suggestion was made to the Apex team to come back to the TSC to report on impact to existing projects with a new approach.  In addition, there will be a separate/broader discussion on OPNFV releases going forward. 

 

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-01-30-14.00.html

January 23, 2018

Agenda

Minutes:

  • Previous minutes approved
  • Quick update: Ray gave a quick update on a plan to migrate to Zoom as a conferencing tool and planning for the Developer Forum at ONS.  Ray took an action item to clarify the registration process for the Developer Forum.  
  • TSC community member backfill: There was a discussion on a process for back filling Maryam as a TSC member when she leaves for a maternity leave.  Ray took an action item to look into the new governing documents.  
  • Scenario consolidation: Rossella volunteered to continue the work on scenario consolidation.  Rossella discussed generic vs. specific scenarios and proposed picking a generic candidate to do a POC with an installer.   One candidate is OS+no-sdn with variables for OVS, OVS-DPDK, fd.io, Barometer, HA.  Discussion ensued and there was a consensus to get started on the POC (with volunteers from installers) and report back to the TSC.  
  • Release update: David McBride noted compliance verifications have been completed for MS3.1 and MS4.  MS 3.2 (next installer health check) is February 2nd.  
  • LF IT/Infra update: No maintenance schedule, and Aric took an action item to add the OPNFV logo on the Gerrit page. 
  • OVS4NFV termination review: Dave Neary reported that the OVS4NFV project accomplished its goal as a project in OPNFV and decided in July to stop producing artifacts.  All work done in OVS4NFV has been committed upstream to OVS or OVS-DPDK.  Via IRC vote, the TSC approved termination of the OVS4NFV project.  

 

MeeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-01-23-14.03.html

January 16, 2018

Agenda

Minutes:

  • Previous minutes approved
  • Docs hacking day: Sofia announced that a Docs hacking day is planned for February 1st starting at 08:30 CET.  In addition to conference rooms in Kista (Ericsson) and Espoo (Nokia), remote participation will be possible via WebEx.  Tim Irnich encourage other community members to provide conference rooms for in person collaboration.  Ray also took an action item to create a wiki page for the the event [post meeting note: wiki page created at Docs Hacking - Q1 2018]
  • Developer Forum at ONS: Ray noted that the LFN Developer Forum is scheduled for all day Monday (March 26th) and Tuesday (March 27th) morning prior to ONS kicking off in the afternoon of the 27th.  The focus will be on cross community collaboration and when discussing proposed tracks, a suggestion was to cross post this information to all communities' (e.g. fd.io, ODL, ONAP, OPNFV, etc.) mailing lists.  Ray will also provide an update when wiki pages are setup.  
  • Release update: David McBride noted that there's a full compliance on MS4 (test framework ready) with the exception of Yardstick and he's following up with the team.  Also MS 3.1 (health check for nosdn-nofeature) is today.
  • LF IT/infra update: Trevor Bramwell noted that testing for Jenkins upgrade is in progress and will be reviewed at the next Infra WG call.  Rudy added that there will be reboots in the next few weeks as Meltdown/Specter related maintenance are performed.
  • OPNFV Verified Program (OPV): Chris Donley discussed that OVP received all necessary OPNFV Board approval and legal committee review and a heads-up will be given to the LFN Board on the OVP launch and seek approval for the OPNFV C&C Committee to continue operating to manage the OVP (the scope of the program will be limited to OPNFV).  There will be a separate discussion on the future of compliance program under the LFN.

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-01-16-14.00.html 

January 9, 2018

Agenda

Minutes: 

  • Previous two meeting minutes approved
  • LFN TAC representation: There was a discussion on TAC representation from OPNFV.  For the first 12 months, TAC members consist of Platinum designates plus representatives from each project (e.g. OPNFV, ODL, ONAP, etc.).  Tim Irnich noted that he's willing to serve as the OPNFV representative as he's interested in fostering better collaboration across LFN projects.  Via IRC vote, the TSC approved Tim serving as the TAC representative from OPNFV while he's the TSC Chair.   
  • Release update: David McBride gave a reminder on upcoming milestones.  First, MS4 (test framework ready) is January 12th and for MS3.1 (passing health check) he proposed pushing this out to January 16th as 15th is a holiday in the US.  
  • LF IT/Infra update: Trevor Bramwell noted that the Jenkins upgrade testing is in progress with pods from LF and ZTE and expects tests to continue for another couple of weeks.
  • Domino termination review: Ulas discussed that no one from the community has stepped forward to work on the project after he announced that he was stepping down as a PTL a few months ago.  There are also no other active committers/contributors to the project.  There was a good discussion on reaching out to the ONAP community to see if they can leverage Domino project's work.  Via IRC vote, the TSC approved termination of the Domino project.  
  • ONS update: Tim Irnich encouraged community members to submit proposals by the CFP deadline on January 14th.  Brandon added that when community members make submissions, they can also forward the information to pr@opnfv.org so they can track OPNFV community submissions.  There will also be an LFN booth during ONS to highlight community's work.  

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-01-09-14.01.html 

January 2, 2018

Agenda

Minutes:

  • Q3'17 projects health data: Ray presented the Q3 projects health data and noted that a number of inactive projects will be coming forward for termination reviews.  Ray noted that there's a concern with a decline in active contributors in the past few quarters and a suggestion was made to re-visit members' contributions once the Q4 data is available.  
  • Release update: David McBride reminded the community of MS3.1 on Jan. 15th (installers to pass health-check with no-sdn/no-features).  David also noted that he's also considering pulling is MS 3 dates for future releases.  MS4 (test framework ready) is also January 12th.  
  • LF IT/Infra update: Ray noted that there was another spam attack on OPNFV IRC channels and this is being investigated.
  • "Active Contributor" discussion: Bin noted that there will be a discussion during this week's Weekly Technical Discussion call to define an "active contributor" in order to move away from committers-only elections.  Dave Neary added that the goal is to have a broader constituency moving forward.  

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2018/opnfv-meeting.2018-01-02-14.00.html


Table of Contents
maxLevel3
stylenone

...