Anuket Project

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 455 Next »

 

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.

TSC Policy

TSC Charter

TSC Meetings

Logistics

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

Please use the same GoToMeeting logistics below

May 16, 2017

Agenda

Call logistics (GoToMeeting):

  • Please join my meeting from your computer, tablet or smartphone at https://global.gotomeeting.com/join/798898261
  • You can also dial in using your phone.
    • United States +1 (626) 521-0010
    • Australia (Long distance): +61 2 8355 1030
    • Austria (Long distance): +43 7 2088 1033
    • Belgium (Long distance): +32 (0) 28 93 7001
    • Canada (Long distance): +1 (647) 497-9371
    • Denmark (Long distance): +45 69 91 89 21
    • Finland (Long distance): +358 (0) 942 41 5770
    • France (Long distance): +33 (0) 182 880 159
    • Germany (Long distance): +49 (0) 692 5736 7208
    • Ireland (Long distance): +353 (0) 14 845 982
    • Italy (Long distance): +39 0 693 38 75 50
    • Netherlands (Long distance): +31 (0) 208 080 208
    • New Zealand (Long distance): +64 9 925 0481
    • Norway (Long distance): +47 21 54 82 21
    • Spain (Long distance): +34 911 82 9890
    • Sweden (Long distance): +46 (0) 852 500 179
    • Switzerland (Long distance): +41 (0) 435 0167 65
    • United Kingdom (Long distance): +44 (0) 20 3713 5010
  • Access Code: 798-898-261

IRC irc.freenode.net

May 9, 2017

Agenda

Minutes:

  • Previous minutes approved
  • CVP update:
    • Wenjing gave an update on activities from the Plugfest.  The Dovetail test cases have been tested with different open source stacks and also one commercial one at the Plugfest.  Test case requirements docs have also been merged in gerrit at gerrit.opnfv.org/gerrit/#/c/33771.  Wenjing added that the goal is to complete the test scope drafts by May 16th.  The TSC will then have two weeks for review prior to vote/approval (targeting May 30th). 
    • Bryan noted that Refstack test case requirements docs maybe available (e.g. https://refstack.openstack.org/#/guidelines)
    • Wenjing added that test outputs are available on testresults.opnfv.org
    • Tim Irnich mentioned that Dovetail tests are based on the test cases that are used in OPNFV release testing, so they have been run many times and are also running regularly in the CI
    • Bryan made a suggestion that there should to be a dry run of the Dovetail test suite among active participants in OPNFV.
    • There was a good discussion on expanding the committer ranks of Dovetail.  Among the Dovetail team, there has been a discussion if there should be a limit of one committer per member organization.  Via IRC vote, the TSC voted against limiting the number of committers in the Dovetail project from each company to one.
  • Danube/Euphrates update: David McBride noted that Danube 2.0 was released last week, and Danube 3.0 is scheduled for June 8th. 

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-05-09-14.04.html

May 2, 2017

Agenda

Minutes:

  • Previous minutes approved.
  • OPNFV Summit update: Brandon noted that summit speakers were notified and schedule published last week.  Out of 177 submissions, ~60 presentations were approved.  Still confirming POC, Design Summit, and Ideas Nest sessions.  Keynote sessions will be announced in the next few weeks,  and Brandon encouraged everyone to register and book their travels.  If track chairs have any feedback on the Hubb tool, they can send an email to events@opnfv.org.
  • TSC composition discussion: Tapio summarized discussions during the Plugfest and noted that there were other discussions such as how the TSC meetings should be organized going forward in addition the composition of the TSC members.  Plan is to continue the discussion in Beijing during the Summit and Tapio took an action item to start a wiki page to continue the discussion/collaboration on the topic.
  • OPNFVDOC update: Jack noted that we need a strategy for website (www.opnfv.org), wiki (wiki.opnfv.org), user documentation (docs.opnfv.org) and we should get input from EUAG, marketing, and technical communities. Brandon noted that he can share the proposal with marketing and EUAG communities.  
  • Danube/Euphrates planning and activities: Danube 2.0 is scheduled for this week and the plan is for the 2.0 downloads pages to go live on Friday (May 5th).  The status on the Danube status pages shows the current status of the scenarios, but testing is still ongoing.  Scenario owners will make the final call on the scenario release.  Via IRC vote, the TSC approved the Danube 2.0 release.  
  • Creation review for NFVbench: This is designed to run in production environment for measuring performance of NFVi.  NFVbench runs traffic through a number of service chains, then provides feedback on network performance.  There were discussions if there should be further investigation into leveraging other projects and if the name accurately describes the project.  Via IRC vote, the TSC approved creation of the NFVBench project.

 

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-05-02-14.00.html

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-05-02-14.51.html

April 25, 2017

Agenda

Minutes:

  • Previous minutes approved
  • Updates from the Plugfest & Design Summit update: There were 76 people from 21 companies attending the first day of the Plugfest.  There were good breakout sessions on infra, testing, plus OPNFV deployment on numerous hardware platforms during the Plugfest.  Planning page for the Design Summit is Beijing Design Summit Schedule and people are encouraged to start adding breakout sessions on the wiki page.
  • The Forum at OpenStack Summit: Ildiko discussed the Forum session on Wednesday during OpenStack-Boston and encouraged community members to participate in session planning (https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration) 
  • TSC composition discussion: Tapio mentioned that there will be a discussion on the TSC composition during the Plugfest/Hackfest.  There was a good discussion if committers are right constituents elect TSC members,   service provider representation on the TSC, if the role of TSC would change with a new composition, etc.
  • Danube/Euphrates planning and activities: David McBride noted that 40 projects have declared intent to participate in Euphrates and MS1 is May 2nd.  Danube 2.0 is due May 4th (Thursday) and the daily huddle will start on May 1st.  David took an action item to send out a recommendation for testing/documentation dates for Danube 2.0.  
  • Creation review for Multi-Access Edge: Bryan wants to postpone the creation review as he looks to recruit more project contributors (e.g. from more than 2 companies) and is not concerned about not being part of the Euphrates release.  Bryan will also reach out to the ENFV project team. 

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-04-25-14.00.html

April 18, 2017

Agenda

Minutes: 

  • Previous minutes approved
  • April 7th Board meeting report out: Tapio noted that during the Board members only part of the meeting, there were report outs from the Marketing Committee and Audit & Finance Committee.  There were also discussions on 2017 Goals and OPNFV value proposition
  • Danube/Euphrates planning and activities: David McBride gave a reminder on Danube 2.0 scheduled for May4th and pushing out the intent to participate date for the Euphrates release to accommodate next week's Plugfest.  The Danube retrospectives will also continue during the weekly release meeting.  
  • Graduation review: Ray summarized previous discussions on graduation reviews at the last hackfest and past TSC meeting.  Frank noted that removing an integration review maybe premature as we still don't have any projects that have gone through graduation reviews.  There was also a good discussion on the need for metrics for graduation review and there was a concern that metrics are somewhat arbitrary and could be gamed.  There was also a consensus that having graduated projects would provide a baseline for graduation reviews.  
  • Monthly support for readthedocs: Ray proposed paying $50/month to readthedocs for support.  Chris Price and Aric added that having a paid support would give us branding opportunities and priority support.  Via IRC vote, the TSC approved $50/month spending for readthedocs.  
  • New installer project creation discussion: In the past few weeks, there's been good discussion on new installer projects.  Participants from testing/feature projects noted that additional installers create more requirements for their projects.  However, there were also concerns that installer projects should not have a different criteria for creation reviews.  Bryan Sullivan made a suggestion to create a wiki/etherpad page on community resource requirements from new installer projects.  Points were also made that there are community resource requirements for all projects (not just installer projects) and no mandate for feature projects to support all installers. 

 

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-04-18-14.01.html

April 11, 2017

Agenda

Minutes:

  • Previous minutes approved
  • Board meeting readout: Tapio noted that the official meeting summary from the Board Secretary will be going out shortly and noted that today's summary will focus on the joint meeting with the TSC.  The April 7th meeting started with ONS feedback and harmonization activities across LF networking projects.  This was followed by updates from the Certification & Compliance Committee and the End User Advisory Group.  During the TSC update there was also a brief discussion on mapping EUAG pain points with OPNFV projects.  
  • Dovetail update: Wenjing discussed meeting with the LF IT team during ONS on infrastructure requirements.  There is also a plan to test the Dovetail SW at the Plugfest.  Wenjing added that community help is needed in (a) testing the Dovetail software, (b) documentation (Jira ticket DOVETAIL-352), and (c) test case review.  Test case (plus test strategy) will be presented for TSC review after the Plugfest.  
  • Danube/Euphrates planning and activities: David McBride noted that Danube 2.0 is scheduled for May 4th.  For Euphrates, 39 projects so far have expressed interest to participate.  There was a discussion on pushing out the Euphrates MS1 (release planning) date to accommodate community members attending Plugfest.  There was a concensus to move the MS1 date to May 2nd while not making any changes to MS2.  David took the action item to update the Euphrates schedule to reflect the new MS1 data.  
  • Community awards: Ray reminded community members to send nominations for Danube release awards by April 17th (Monday)
  • Plugfest/Design Summit update: 
    • Ray gave a quick update on the Plugfest and noted that ~90 people from over 25 organizations have registered for the event.  Proposed agenda for the week is also available.
    • For the Design Summit, a planning page has been created.  There will be 3 rooms available during the Design Summit and the proposal is to limit presentation sessions to Day 1 and devote Day 2 to project team meetings/breakouts.  
  • Scope expansion OpenRetriever: Xuan notes that the proposal is to bring NGVS's proposed activities into OpenRetriever (unikernel and scheduler were not part of the original project scope).  New committers will also be added to OpenRetriever and the plan is to work with both OpenStack and bare metal (with containers).  Juju will be used as the installer and potentially Compass.  Via IRC vote, the TSC approved the scope expansion for OpenRetriever.  

 

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-04-11-13.59.html

April 4, 2017

Agenda

Minutes:

  • Previous minutes approved
  • Danube/Euphrates planning and activities:
    • Danube release: Brandon Wick provided an update on Danube 1.0 release outlining the new streamline software page, press release, blog post, social media posts, etc.  Brandon encouraged community members to amplify Danube messaging via social channels and at ONS.  There was a consensus to have a Danube post-mortem discussion on April 11th during the weekly release meeting.
    • David McBride noted that there are no changes to milestone dates for Danube 2.0/3.0 and Euphrates.  Danube 2.0 is schedule for May 4th and Euphrates MS0 closes on April 24th.  
  • TSC+Board meeting: Tapio walked through the slide deck that covers Danube/Euphrates updates, CI/CD discussions, projects health metrics, etc.  There will also be a discussion with the EUAG tomorrow (Wed) on mapping pain points with projects in Euphrates.  
  • Scenario descriptor: Uli shared the status of scenario descriptor and noted that the plan is to come back to the TSC for approval when patches are finalized for the descriptor file. There are outstanding discussion items such as specifying minimum versions of upstream, single OpenStack using different minor versions, etc. that will be discussed at the Plugfest/Hackfest.  Tim Irnich noted that having a single file would be a key value for "feature projects" and will streamline work with installers.  
  • Additional Git repositories: Fatih noted that each OPNFV project gets a single git repo today, but a number of projects created GitHub repo's for upstream work.  Some projects may also benefit from logical splits vs. having a large/single repo.  A proposal is a pilot of additional repos with Apex & Releng projects and will come back to the TSC with findings in 2-3 weeks.
  • There was a good discussion on challenges posed to the community resources with the number of installer projects and installer project proposals.  There was a consensus to have more follow-up discussions during the next weekly technical community call on April 6th.

 

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-04-04-13.59.html

March 28, 2017

Agenda

Minutes: 

  • Previous minutes approved
  • Danube 1.0 status: David McBride presented the scenarios status as of March 27th and noted that Apex/Compass/JOID installers are doing well and Fuel is showing improvement.  David also noted that it would be up to the scenario owners to decide whether their scenarios are ready for release or not.  David added that based on his analysis as of March 27th, about 18 scenarios look ready for release.  Several participants noted that more scenarios could be added to the list as there have been more improvements since the previous day.  If the community agrees to a release on March 31st, JIRA tickets will need to be wrapped up by 29th, documentation completed on the 30th, and labeling will be done on the 31st.  Via IRC vote, the TSC approved the Danube 1.0 release date of March 31, 2017.
  • OPNFV Summit Update: Brandon noted that the Summit CFP deadline has been extended to April 10th @11:59pm PT.  There are 20 track chairs in the programming committee and speakers will be notified on April 25th and schedule to be published on April 27th.  Heather added that for ONS next week, there will be a Hackathon on Monday with a developer reception the same evening plus several other OPNFV related activities during the week.  
  • EUAG pain points: Steven presented the list of pain points that the EUAG members complied and prioritized based on what EUAG members thought was feasible for Euphrates.  EPIC statements have also been developed for key pain points.  Steven added that another EUAG survey is planned to gather additional feedback and there will also be more discussions on EUAG-TSC interactions including at ONS next week.  
  • Dovetail update: Wenjing shared the latest status on Dovetail.   Wenjing also discussed SUT, test strategy draft, what will be collected in test DB, test case requirements, etc. and encouraged community members to contribute/provide feedback to test case reviews.  Dovetail release is targeted for Danube 1.0 + 3 months.  During the Plugfest tools validation, test case selections, etc. are also planned during the week.   

 

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-28-14.00.html

March 21, 2017

Agenda

Meeting Minutes:

  • Previous minutes approved
  • Creation review for SampleVNF: Kannan noted that the samplevnf project is to create a repository of sample VNFs to help VNF benchmarking and NFVi characterization with real world traffic.  The project team also addressed questions on Apache 2.0 licensing and that all source code (no binaries) will be available on OPNFV repos. The Sample VNFs will consist of several VMs and can be used for load testing the virtual infrastructure.  The project team is also planning to look at service chaining in the future.  Via IRC, the TSC approved creation of the SampleVNF project.
  • Creation review for VINA:  Koren noted that the VINA project addresses assurance and monitoring for VIM and the focus will be on monitoring, visualization, monitoring, root cause analysis, etc.  There was a good discussion on relationships with other projects in OpenStack e.g. Ceilometer, Vitrage, etc. Via IRC, the TSC approved creation of the VINA project.
  • Danube planning and activities: David McBride noted that less than 1/2 of the Danube 1.0 target scenarios have been deployed and a few projects like ONOSFW and Bottlenecks are still working through issues.  There was a consensus that more time is needed for troubleshooting in general and documentations, so it's premature to make a decision on Danube 1.0.  
  • OpenDaylight (ODL) release timing: Colin Dixon noted that release timing for ODL has not always worked with OPNFV and ODL community is considering moving to twice a year release cycle.  Suggestions were made on (1) 3-month gap between ODL and OPNFV or (2) ODL line up with OpenStack and then OPNFV come some time after that.  As time was running out, there was a consensus to continue the dialog on mailing lists/Weekly Technical Community call/ONS.

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-21-13.59.html

March 14, 2017

Agenda

Minutes:

  • Previous minutes approved.
  • Internship update: Ray provided an update on the Internship program and noted there are currently two projects that are looking for interns.  Ray encouraged community members to post new internship projects as summer vacation period for students in many countries are approaching.  Also going forward, recommendation is to have start internship projects at the beginning of each quarter (e.g. January, April, June/July, September) to streamline administrative tasks and avoid end of the year holidays in December.
  • Danube/Euphrates planning and activities
    • David McBride presented the proposed milestones timeline for Euphrates and noted that FDS team will be experimenting with a more flexible release schedule for their project during Euphrates release.  If other projects are interested in flexible release schedule, they can join the next Infra WG call on March 20th.  Via IRC vote, the TSC approved the Euphrates timeline.
    • David also discussed the Artifact versioning starting with Euphrates.  The proposal is to go with numeric-only versioning such as 5.0.0 (Euphrates 1.0) , 5.1.0 (Euphrates 2.0), 5.2.0 (Euphrates 3.0), etc.  There was a discussion if there should be both release name & number versioning in documentations and the OPNFVDOCs team took the action item to discuss this in their next meeting.  The TSC also agreed to start using the numeric artifact versioning in Euphrates.  
    • David also reviewed the latest milestone exception proposal and noted that the new exception process proposal will be effective starting with Euphrates.  The TSC agreed to adopt the new exception process and make evaluations as the process is used.  
  • Joint TSC/Board meeting agenda/presentation: Tapio reviewed the Board agenda and looked for volunteers for Cross Community CI (XCI) and Devops topics.  Tapio/Ray will follow-up with volunteers to start working on the presentation.  
  • Bamboo creation review: Donald Hunter noted that Bamboo will be leverage PNDA, which provides a platform for analytics applications. Bamboo team already had discussions with other testing projects such as QTIP & Functest on future collaboration opportunities.  Beyond OPNFV testing projects, there maybe other opportunities with projects such as Barometer.  Via IRC vote, the TSC approved the creation of Bamboo project.
  • Plugfest update: Ray provided a quick update on Plugfest and encouraged everyone to register and book hotels early as there are many events in Paris the week of April 24th.  Also planning info. can be found at Plugfest - Danube Release

 

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-14-14.00.html

March 7, 2017

Agenda

Minutes:

  • Previous minutes approved.  
  • OpenStack Forum: Kathy Cacciatore and Tom Fifield gave an overview of OpenStack Forum starting at OpenStack Summit in Boston. The Forum will be used to gather end user requirements for future releases (e.g. Queen release) at the Summit and OPNFV community members are encouraged add ideas/topics to https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV. 
  • ONS Update: ONS is taking place during the first week of April and there will be a Hackathon on Monday.  On Thursday, OPNFV has a 1 hour time slot to give a project update.  In the "S3 demo" area, there is a plan to showcase LaaS and Pharos dashboard.  On a related note, for the OPNFV Summit, the CFP is open and there is a call for track chairs.  (You can still volunteer for track chair if you are not attending the Summit, but please note this when you apply for a track chair)
  • Graduation reviews: There was a discussion if the "Integration State" (and the integration review) is necessary in OPNFV.  Also a question was raised if all "feature" projects need to be upstreamed within a short period or if they can "stay" in OPNFV long-term.   Ray will be soliciting volunteers to wrap up the discussion on mailing lists.  
  • OPNFV Infra/CI & CD Roadmap: David explained that the CI system consists of the POD hardware (described by the POD description file) and scenarios.  The ultimate goal of the evolution is to do dynamic allocation of scenarios to pods (targeting the F-release in Spring'2018).  This requires that all installers support running the installer in a VM so the jumphost does not need to change.  David also shared shared various CI evolution activities for proposed Euphrates milestones.  Uli added that the scenario descriptor template will be reviewed after the scenario lifecycle document.  
  • Danube/Euphrates planning and activities
    • MS7 (stable branch) is this Friday
    • David shared the proposed milestones for Euphrates.  MS0 will start on March 27th, and Euphrates 1.0 is targeted for late September.  There was a good discussion on pros/cons of different release models a consensus to postpone the voting of Euphrates milestones until next week.  

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-07-14.59.html

February 28, 2017

Agenda

Minutes:

  • Previous minutes approved
  • On-going items: Tapio provided a reminder on project proposals for VINA/Bamboo/sampleVNF plus E-release naming survey.  There's also a Dovetail planning etherpad
  • Community awards: Ray summarized the proposal that was sent out via mailing lists.  There was a consensus to go with the new release-based community awards program.
  • doc.opnfv.org update: Sofia discussed the migration to readthedocs and is looking for agreement on the Docs structure as can be found on docs.opnfv.org today.  Sofia added that project teams have been asked to restructure their repo's under /docs but the content should auto-populate in docs.opnfv.org. There was a discussion that it may make sense to divide the documentation for developers and users.  There was also a suggestion that the documentation page should use descriptive names like "functional testing" or "performance testing" instead of project names.  Frank noted that restructuring the documentation maybe difficult since OPNFV is deployed with scenarios today.  There was a consensus to continue with the currently proposed docs structure for the Danube release but can visit other options in the future such as a separate page for developer documentation.
  • OpenStack PTG readout: Jose summarized Interop WG meetings in Atlanta where he had a chance to discuss NFV reference test cases with the OpenStack community.  A comment was made that having a developer focused event was also helpful.  Bryan also discussed RefStack that includes features that are common in public OpenStack clouds but do not include all OPNFV relevant features
  • Danube/E-release planning: 
    • David McBride shared the data on Danube MS6 compliance.  Two requirements for MS6 are test case implementation and preliminary documentation.  Many projects have yet to report on MS6, so David requests PTLs to send the latest data if this hasn't been done.  
    • For E-release timeline, David noted that the proposal is to maintain 1.0/2.0/3.0 releases as was communicated on mailing lists.  The E-release timeline vote plus CI/CD evolution will be on the agenda for next week.  
  • Graduation reviews: There was a quick discussion on graduation reviews and Tapio noted that this is another mechanism for community recognition.  As time was running out, discussions will continue next week.

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-02-28-15.00.html

February 21, 2017

Agenda

Minutes

  • Previous minutes approved.
  • End user Advisory Group survey discussion: Steven Wright gave an overview of the survey results from January and noted that many are using OPNFV (although not yet in production).  Many respondents also noted that they'd like to see projects like DPACC and Pinpoint being part of future releases.  There was a discussion on how End user feedback can be provided for future releases (starting with the E-release), and Brandon noted that key pain points (e.g. interoperability, real-time performance monitoring & fast fault detection, resiliency at scale, etc.) may be a good starting point for this.  There was a consensus to bring the pain points topic back to the TSC in the next few weeks.
  • Danube/E-release planning and activities: David McBride noted that MS6 was on February 17th and he's in process of evaluating compliance.  The MS7 (stable branch) is March 10th.  David added that E-release discussion/feedback is on-going and the plan is to come back to the TSC next week for a vote on the E-release timeline.
  • OPNFV Architecture: There was a good discussion on evolving the OPNFV Colorado architecture diagram (on https://wiki.opnfv.org/) vs. looking at OPNFV architecture from a new/different angle.  There was a consensus that for the evolution of the Colorado architecture diagram, the LF team can take a first cut at it, and for a new architecture diagram, face-to-face sessions at upcoming events such as ONS or Plugfest/Hackfest maybe a better approach.

 

MeetBot Minutes 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-02-21-14.59.html 

February 14, 2017

Agenda

Minutes

  • Previous minutes approved.
  • Committer removal discussion: Ray discussed the proposed change to the TSC Charter and noted that this requires approval by the Board.  More details on (e.g. when TSC needs to be notified) can be added to the Committer Removal wiki page.  Via IRC, TSC approved proposed updates the TSC Charter to simplify the committer removal process as outlined here.  
  • Pod descriptor file: Jack noted that patches are all done and ready to be merged for the next phase.  The descriptor file will be used for the Danube release and Jack will be working with Pharos lab owners.
  • Cross Community CI (XCI): Fatih provided an update on activities from the past several months and noted that XCI activities includes working with OpenStack, ODL, fd.io, Open-O with the goal of installing upstream code from master and providing faster feedback.  For OpenStack, good progress has been made with the Bifrost team (for Ansible) and for ODL prototype has concluded.  
  • Danube planning and activities: For MS5, 17 projects are now compliant and 8 are not compliant.  MS6 is this Friday (Feb. 17th).  David also discussed proposed E-Release milestones.   There was a good discussion on dot releases (e.g. flexibility with dot releases and providing opportunities for updates vs. people having an impression that there are separate milestone dates (e.g. MS5/MS6) for dot releases).  David took an action item to continue the dot release conversation via email.  Ray also has an action item to start the naming process for the E-Release.
  • OPNFV Architecture: Tapio discussed the current draft and noted that more contents are needed for certain sections like MANO.  There was a consensus to also continue the discussion on Thursday's Weekly Community call
  • Other: February TSC update to the Board

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-02-14-15.00.html

February 7, 2017

Agenda

Meeting Minutes:

  • Previous minutes approved
  • Board meeting update: Tapio noted that the last Board meeting was focused on CVP discussions and several agenda topics including the TSC update was not covered.
  • Termination review for PolicyTest: Bryan discussed that the PolicyTest project never took off since formation and a number of committers are no longer part of the OPNFV community.  Some of the future work will likely be done in other projects such as  Copper. Via IRC vote, the termination of PolicyTest was approved by the TSC.
  • Committer removal: Ray describe the current process per the TSC Charter, where the PTL can request from the TSC a permission to remove a committer.  Some of the PTLs thought that requiring TSC approval maybe too burdensome.  Discussion ensued on PTLs only providing notification to the TSC, having a review period, etc.  Ray took an action item to draft a new text in the TSC charter and circulate via mailing lists.  Morgan also brought up the issue of committers who are not active for 6+ months. Ray noted that the LF team plans to publish a regular (~every 6 months) report of inactive committers for projects and share the report with the PTLs.
  • Danube planning and activities: David McBride noted that for MS5, 13 projects are compliant/8 non-compliant/5 unreported.  MS6 is also coming up on February 17th.  David added that comparison with previous releases are difficult as he's being more strict on milestone compliance.  There was a good discussion if there needs to be a better evaluation for MS3 (OpenStack integration).  Next, David discussed the milestone exception process and noted that this is something that will start with the E-release.  As time was running out, there was a consensus to continue the conversation in other meetings.  
  • Project creation review for SNAPS-OO: Randy gave an overview of the project proposal and noted that some of the libraries have already been used by other projects such as Apex and Functest.  The code is Apache-2.0 and the plan is to migrate the code to OPNFV repo.  Via IRC vote, TSC approved creation of the SNAPS-OO project.  

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-02-07-15.00.html 

January 31, 2017

Agenda

Minutes:

  • Previous minutes approved
  • Termination reviews
    • Prediction: Uli discussed the current state of the Prediction project (collection of data for fault analysis).  There are unfortunately no resources to continue working on the project and no other OPNFV projects are dependent on Prediction.  Via IRC vote, the termination of Prediction was approved.
    • Inspector: Luke discussed the Inspector project and noted that the original PTL is no longer part of the community and no one else in the community is interested in stepping up to lead the project.  In addition, there has been no project activity since creation.  Via IRC vote, the termination of Inspector was approved
  • TSC update to the Board: Tapio noted that during the Board meeting, the plan is to follow-up on action points (e.g. architecture discussion, Danube & E-release priorities, etc.) and the update on Milestone 5.  There will also be slides-only update on Cross community CI activities, projects, and other community activities.
  • Testing dashboard on Bitergia: Morgan discussed that Test WG is working on a common dashboard for all testing projects and met with Bitergia at OpenStack-Barcelona and discussed if they can help develop/maintain the new testing dashboard.  This will allow the testing community to focus on testing (vs. building dashboards).  The cost of the development is $8k and the proposal is to have TSC cover 1/2 of the cost out of the TSC budget.  The development will start in Q2'2017.  The TSC agreed to spending $4k to help develop the testing dashboard.
  • Danube planning and activities: David McBride notes that Milestone 5 was January 27th and he's still collecting status from PTLs.  Out of 26 projects, 7 passed/5 has not passed/14 have not reported.  Milestone 6 is February 17th.  David gave a reminder that if people have new projects in mind for the E-release the time to propose projects is now.  

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-31-15.02.html

January 24, 2017

Agenda

Meeting Minutes

  • Previous minutes approved
  • OPNFV Ambassadors Program: Brandon Wick notes that the pilot has started for the OPNFV Ambassadors program. The term of ambassadors is 2 years and they will be representing OPNFV at various events, webinars, etc.  Ambassadors' time commitment isn't meant to be taxing beyond what many community members are already doing. 
  • Danube priorities: Morgan highlighted changes from the previous meeting and noted that this is focused on "community priorities".  For example, there is now a shorter version of text for MANO priorities.  There was an agreement to adopt the current version of the document and and move forward with E-release priorities.  Morgan took an action item to further develop the E-release priorities and also look for opportunities to have face-to-face discussions at future events.  Will also look for incorporating End User Advisory Group feedback for the E-release.  
  • Danube release planning and activities: David noted that MS5 is this Friday (Jan. 27th).  Jack Morgan added that the Pharos lab owners may not necessarily know the individual project status in their Pharos PODs  and recommend checking with individual PTLs.  David also checking with the OPNFVDOCs team on documentation requirements for MS6.  
  • Quarterly Awards: There was a good discussion on moving recognitions to after each release (plus rewards at the Summit) vs. continuing with Quarterly Awards.  Morgan noted that it would also be good to recognize interns for their work.  Ray took an action item to continue the discussion over the mailing list. 

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-24-14.59.html

January 17, 2017

Agenda

Minutes

  • Previous minutes approved
  • Meetings page on wiki.opnfv.org: Ray notes that recent changes in https://wiki.opnfv.org/display/meetings allows project teams to update meeting information on one location.  There was a consensus to try out the new meeting page approaches and see if there are further areas for improvement going forward.
  • Dovetail update: Wenjing provided an update on the Dovetail project and noted that focus has been on testing NFVi + VIM for each OPNFV release.  The Dovetail team is in the process of reviewing test cases and dependencies.  Tests will be reviewed in Gerrit and project teams/Test WG will be notified when new test cases are added.  There was also a good discussion on possible "fabrication" of results and the Dovetail team will have more discussion on detailed trace and un-modified output.  The next steps for the Dovetail are to report out to the Test WG on January 19th and come back to the final TSC review/approval on February 14th.  
  • Quarterly projects health metrics: Ray presented the draft Q4 report showing projects activities in terms of commits, JIRA tickets, and wiki.  There will be a review period of few weeks to allow community members to provide feedback/suggestions.
  • Danube priorities finalization: Morgan noted that additional inputs from the MANO WG and Dovetail have been added to the Danube priorities wiki page.  On "community priorities", Morgan noted that these are items that are important for more than 2-3 projects.  As the time was running out, discussion will continue via mailing lists and the next call.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-17-14.59.html 

January 10, 2017

Agenda

Minutes

  • Previous minutes approved
  • Brandon Wick gave a preview of the new opnfv.org site that is scheduled to go live on January 16th.  Key goals were simpler navigation, more visually compelling site, etc.  There will be a section to highlight projects and will welcome community contributions.  Brandon welcomes feedback on the new site are welcome after it goes live
  • Scenario consolidation: Uli discussed the scenario consolidation opportunities as captured in https://wiki.opnfv.org/download/attachments/6823941/Scenario%20Consolidation%20Danube%20v1.pptx?version=1&modificationDate=1483971812000&api=v2. Uli noted that there are currently 58 scenarios for the Danube release.  There was a good discussion on HA vs. Non-HA scenarios and Uli suggested that one possibility is to have Non-HA as development scenarios that are not part of the release.  There was a consensus to continue the HA vs. Non-HA discussion during Thursday's Technical Community call.    Tim Irnich also noted that as a scenario reaches a certain maturity level, it could be a good candidate for consolidation.  Uli also noted that he will also reach out to ODL community members to investigate additional consolidation opportunities.
  • Danube planning and activities: David McBride noted that due to migration at Intel labs, a large number of projects have been impacted for the MS5 work.  David is proposing a new dates for MS5 (Jan, 27th) and MS6 (Feb. 17th).  No changes are being recommended for MS7 (stable branch) and Danube release dates.   Morgan noted that there's will likely be an impact on testing projects as integration period is compressed.  The TSC approved moving Danube's MS5 and MS6 dates to Jan. 27th and Feb. 17th respectively.
  • Tech discuss forum trial (based on Discourse): Ash discussed a need for a better tool vs. mailing list/Gerrit for community discussions.  There was a question if the Discourse tool can be integrated with email (e.g. for notifications, subscription, etc.), and Ash took an action item to investigate email integration.  
  • Meeting page on wiki.opnfv.org: Ray & Mark Beierl discussed the progress on cleaning up the wiki meetings page (https://wiki.opnfv.org/display/meetings).  A clean up has been made to remove duplicate meeting information from the main vs. individual meetings pages.  Mark noted that there's a further opportunity to create calendars in individual project meeting pages that can be aggregated in a "master" calendar.  This provides an opportunity to further reduce duplication of content and the inconsistencies we currently have.  Ray/Mark took an action item to continue the discussion on the mailing list.   
     

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-10-14.59.html

January 3, 2017

Agenda

Minutes:

  • Previous minutes approved
  • Next Plugfest/Hackfest: Ray discussed options for the next Plugfest/Hackfest in April.  Orange has a facility available in Paris during second week of April, and they also have another facility in Lannion that is available in the 2H'April.  There were some concerns that the Plugfest/Hackfest will be between ONS (first week of April in Santa Clara) and the OpenStack Summit-Boston (in May) and this may have an impact on attendance.  Ray took an action item to have a follow-up conversation with Jamil/Morgan at Orange.  
  • Follow-up on Common Configuration Files: Jack outline the common configuration file for Pharos pods (https://gerrit.opnfv.org/gerrit/#/c/23727) and review of the patch requires further discussion relating to at what stage different configurations are provided.  Jack took an action item to follow up with Tim Rozet and others in the community on this topic.
  • Proposal for docs.opnfv.org: Aric outlined that our current documentation process is to create HTML artifacts and store them. This requires manual handling for versions and manual support of the toolchain.  The docs team proposes to use readthedocs to handle versioning and a publishing toolchain.  The proposal includes establishing the URL docs.opnfv.org to point to the implemented solution and the theme is being updated to provide an OPNFV theme.
  • Follow-up on Danube priorities: Morgan noted that no edits/feedback were added to the wiki page (https://wiki.opnfv.org/pages/viewpage.action?pageId=8686146) since the last discussion on the TSC call prior to the holidays.  Morgan also added that lot of activities identified on the wiki page (e.g. for opnfvdocs) have already started.  Morgan described that that this priorities list can provide input to the OPNFV Board and the community about what we are focusing on and potentially help newcomers understand our community direction.  Brian Skerry noted that there are inconsistencies on the page regarding the proliferation of scenarios that should be corrected on the page.  The TSC agreed on the overall direction on Danube priorities as captured on Danube priorities. Morgan also took an action item to convert the final version in PDF and send to the opnfv-tech-discuss mailing list.  
  • Danube planning and activities: David McBride reminded the community that MS5 (scenario integration & feature freeze) is January 12th.  There are no new updates from the Movie project on MS2 and David also added that the Moon project may have difficulty meeting MS5.  On the Fuel issue for Colorado, the problem has been resolved upstream and the workaround is no longer necessary.  

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-03-14.59.html

December 20, 2016

Agenda

Minutes

  • Previous minutes approved
  • Purchasing a new switch for LF POD 4 & 5: Rudy re-capped his previous email on the topic.  The total purchase price including the switch, support (for 3 years), and shipping is under $5,500.  The LF team is also familiar with the product.  The TSC agreed to move forward with the purchase.  Rudy will also check if existing cables (for the current 1GBE switch) can be used for the new switch.   
  • Project creation review for Rescuer: Howard and Leon presented the project proposal.  The project's aim is to deal with application data loss and the initial focus will be data protection on the VIM.  There were questions if the project is just protecting OPNFV data/metrics that is collected, and the response was that the goal is to go beyond test data/metric protection and provide a generic recovery service.  There were also suggestions to start doing the initial work (e.g. for gathering requirements/use cases) under the HA project plus recruit additional committers from other companies/organizations.  The project team agreed to start their work as part of the HA project in the next 3 months and come back to the TSC for creation review after the Danube release.   Edgar took an action item to coordinate a conversation with the HA team.  
  • Scenario consolidation: Since time was short, Uli suggested postponing the discussion to the next TSC call.
  • Danube planning and priorities: David McBride noted that there's no update from Movie & Orchestra projects on Milestone 2.  Upcoming milestones in January are MS 5 (scenario integration and feature freeze on Jan. 13th) and MS 6 (test cases implemented/preliminary documentation/stable branch open on Jan. 26th).  
  • Call for expertise from ETSI to identify gaps between ETSI NFV requirements and Open Stack APIs: Gergely and Pierre discussed the Call for Expertise from ETSI to identify gaps between OpenStack APIs and two ETSI specs.  The deadline to volunteer is January 26th and more details can be found in this document.  
  • Compliance/Verification Program document follow-up: Ray noted that the CVP document was sent to TSC members only as this is not a public document.  The feedback from the TSC was due by 5pm Pacific Time on December 14th.  Chris Donely collated feedback from TSC and End User Advisory Group prior to sending the program document  (along with action items/plans) to the Board.  
  • There will be no TSC meeting next week, and regular calls will resume on January 3, 2017.

 

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-20-15.00.html

December 13, 2016

Agenda

Minutes

  • Previous minutes approved
  • TSC meetings around the holidays: TSC meeting will be held on December 20th, but will be cancelled for December 27th.  Regular meetings will resume on January 3rd.  The weekly release meeting will follow the same pattern as the TSC meeting. 
  • December Board meeting update: Tapio provided an update from the December 8th Board meeting.  The TSC budget has been approved and as a result of the Compliance/Verification Program (CVP) discussion, the latest CVP documentation was sent to TSC members for feedback by 5pm Pacific Time on December 14th.  
  • Plugfest/Hackfest wrap-up: Ray noted that there were 70 attendees from 23 organizations at the Plugfest/Hackfest.  There will also be a Plugfest whitepaper with a target date of late January'2017.  
  • Colorado + Danube planning and activities: David McBride noted that Colorado 3.0 released last week.  Upcoming milestones for Danube are Scenario integration and feature freeze (MS5) and test cases implemented/preliminary documentation/stable branch open (MS6).  David is also following up on Movie and Orchestra teams for MS2 and Compass and Daisy teams for MS3.  
  • Danube priorities discussion: Morgan noted that main priorities identified for Danube are CI, Testing, and documentation.  The placeholder theme/tagline suggested by Morgan for Danube is "Real CI Ready".  There is also a section on future releases (after Danube), and community members are encouraged to contribute to the page.  A comment was made that release priorities discussions should start sooner and a question was raised what is the impact of priorities decision.  Morgan noted that one of the impact could be on milestones definitions (e.g. with additional criteria) or resource requests could be made to the Board.  There was a consensus to give community members ~2 weeks to review and have TSC to vote on the priorities on January 3rd.  
  • Common configuration file and scenario naming: Uli discussed the goal of common configuration files and noted that an agreement was reached on common configuration files during the Plugfest/Hackfest.  There were suggestions of doing a proof-of-concept for validation plus looking at what the OpenStack community is doing.  Jack also noted that the pod descriptor file is on Gerrit and asked for community feedback.  This will again be revisited on the January 3rd TSC call.  There was also a quick discussion on scenario consolidation, and as time was short the discussion will resume next week.  
  • Project Proposals OpenRetriever: Xuan presented the proposal that aims to create a platform to manage containers and VMs (and also allow VNFs to run on a set of containers/VMs).  Of three modes to integrate container with OpenStack, the OpenRetreiver team is proposing to use Container Orchestrator Engine with Kubernetes and OpenStack-Newton.  OpenRetriver will not participate in the Danube release, but there will be development activities in the next few months.  Via IRC vote, the TSC approved project creation for OpenRetriever.  

 

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-13-14.59.html

December 6, 2016

Agenda

Minutes:

  • Previous minutes approved
  • A new sysadmin from LF Rudy Grigar was introduced to the community
  • 2017 events plan: Brandon Wick shared the tentative 2017 events plan.  3 major events for the technical community are Plugfests (with co-located Hackfests) and the Design Summit.  The target for the next Plugfest is late April'17 and Orange (France) is the potential host.  There was a good discussion on IETF participation, and suggestions were made to look into hackfest/hackathon opportunities with MEF and BBF.  
  • Updates from the Plugfest: As of Tuesday morning, 60 people from 21 companies are attending the Plugfest exceeding the numbers from the first Plugfest in May.  
  • December Board meeting agenda: Tapio shared the draft presentation for the December Board meeting when he will be giving updates on Colorado/Danube releases, action items for OPNFV Architecture and Danube priorities, etc.  There was a good discussion on the proliferation of scenarios and one proposal to reduce the number of scenarios is to merge the HA and non-HA scenarios.  
  • Colorado + Danube planning activities: Colorado 3.0 software downloads page is scheduled to go live on December 8th.  For Danube, a few projects are behind on MS2 milestone and David McBride is following up with PTLs.  David is also working with the Daisy installer project team as that installer has an impact on other projects such as Escalator.
  • New switch for LF POD 4 & 5: There was a suggestion to also provide support costs for switches and the LF team will come back with an update.  

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-06-15.00.html

November 29, 2016

Agenda

Minutes:

  • Previous minutes approved.
  • Plugfest/Hackfest update: Ray gave a reminder that the registration deadline for Plugfest/Hackfest is December 1st.  In addition, ETSI Plugtest will be in January and OPNFV member companies are encouraged participate.  There was a consensus to discuss future collaboration with ETSI after their Plugtest event.
  • Proposed Developer Collaboration budget: Ray gave an overview of the proposed budget for 2017.  Most items are similar to the previous year with some increases in items such as internship to accommodate more interns.  There are new spending items such as Documentation Consultant and Travel Assistance.  There was a question on Travel Assistance and Ray noted that this is for interns and other key people from industry/upstream communities.  There was a good discussion on OPNFV events plan in 2017 and Ray suggested inviting Brandon Wick to future TSC call to provide an update.
  • Goals and Vision for the Danube release: Morgan discussed progress so far from various working groups (e.g. Infra & Testing ).  Tapio took an action item to start a wiki page on Danube priorities and a group including Tapio, Morgan, Uli, Dave Neary, Rosella, and Cecilia will work on priorities for the Danube release with the target of mid/end of December.  
  • Colorado + Danube planning and activities: Dave noted that there are milestones for Colorado (wrap-up test/docs for 3.0) plus Danube (installer/OpenStack integration) this week.  For Colorado 3.0, the goal is to have the software downloads page updated by December 8th.  
  • Meetings discussion: There was a good discussion on setting up a single recurring meeting for each technical project GotoMeeting accounts plus cleaning up the meetings wiki page.  Ray took an action item to give community members a 2-3 weeks advance notice on single recurring meetings and start looking at meetings wiki page clean-up opportunities.  There was also a good discussion on staying with Pacific Time vs. using UTC for scheduling meetings and Ray will start another email discussion on this topic. 

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-11-29-14.58.html 

November 22, 2016

Agenda

Minutes:

  • Previous minutes approved
  • Hackfest/Plugfest update: Ray noted that the registration deadline for the Plugfest/Hackfest is December 1st.  So far 70+ people are registered representing ~25 companies/organizations.  Three companies are brining hardware plus at least three more companies are making their hardware available remotely.  Uli made a suggestion that Hackfest sessions could be scheduled Tuesday-Thursday so that people that are participating in the Hackfest-only can avoid traveling on weekends.  
  • Common configuration file and scenario naming: Jack noted that more time is needed to gather community feedback on the topic and there could be a session during the Hackfest.  The current discussion can be found at https://gerrit.opnfv.org/gerrit/#/c/23727. 
    Frank made a suggestion that it may be a good idea to get agreements from all installer project PTLs before coming to the TSC, but Uli noted that not all installer maybe able to implement the proposal right away.  
  • Goals and vision for Danube: Morgan started an etherpad on the topic, and so far the discussion have taken place at the Test WG and other WGs are encouraged to start/continue the conversation.  There is an action item for the TSC to provide an update to the Board during the December Board meeting.  
  • Colorado + Danube release planning: David McBraide notes that the test milestone for Danube is today plus Colorado 3.0 is release coming up on December 5th and he will be following up with some of the PTLs.  David also discussed the recent survey on OpenStack releases to be used for upcoming OPNFV releases and there is a consensus from the PTLs that Danube should be based on OpenStack-Newton.  Via IRC vote, the TSC agreed that the Danube release will be based on OpenStack-Newton.  David also added that the Daisy team is reporting issues with CI integration so projects dependent on Daisy should plan accordingly.  Scenarios participating in Colorado 3.0 should be reflected in https://wiki.opnfv.org/display/SWREL/Colorado+Scenario+Status.
  • JIRA Federation: Aric noted that there is no documentation on JIRA Federation so it is difficult to make any progress on federation between OPNFV and fd.io.  Aric took an action item to contact Atllassian to make an inquiry on JIRA federation including work scope & costs (if any).
  • There was a discussion on setting up a single recurring meeting in two GoToMeeting accounts and making it easier to make meeting updates on the wiki page (sometime requires making updates in 4 different places).  Ray took an action item to continue the conversation on the mailing list.  

 

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-11-22-14.58.html 

November 15, 2016

Agenda

  • Approval of previous meeting minutes
  • Agenda Bashing
  • Goals & vision for the Danube release - Unknown User (mrichomme)
  • Colorado + Danube planning and activities - David McBride
    • OpenStack - Ocata release

Meeting Minutes

  • Previous minutes approved
  • Unknown User (tapiotallgren) announces that Colorado 2.0 download page is live
  • Goals and Vision for Danube release
  • Release planning
    • Discussion about which versions of OpenStack will be integrated with OPNFV Danube and "E-release"
    • Proposal is:
      • OPNFV Danube to be  based on OpenStack Newton (current release)
      • OPNFV E-release to be based on OpenStack Pike
      • OpenStack Ocata would be skipped
    • David McBride has sent a survey to the project leads.  Please complete by Nov 21, noon (PST)
    • Unknown User (jose.lausuch) says that the Functest project has committed to supporting OpenStack Newton for the OPNFV Danube release cycle.
    • There is a reference to the OPNFV upstream project roadmap.  However, it does not appear to have been updated.
  • Meeting scheduling
    • There is some confusion about meeting times.  
      • PST vs. UTC
      • Interference between meetings when using a shared GTM account
    • Unknown User (blsaws) proposes a single always-available meeting per account
    • Action to David McBride to propose a solution

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-11-15-15.00.html

November 8, 2016

Agenda

Meeting Minutes

  • Previous minutes approved
  • Plugfest/Hackfest update: Lincoln noted that members from 15+ organizations have registered for the Plugfest and 5 companies will provide hardware resources (4 on-site and 1 remotely via VPN).  An update has been made to the planning page and participants are encouraged to add/schedule topics.  There was a good discussion on what information can be shared after the event without violating the Rules of Engagement (ROE) and the general consensus was that hackfest-related discussions and outcomes can be shared publicly.
  • Graduation reviews and discussions: Ray proposed to continue this conversation in person when community members get together for the Plugfest.  Ray took an action item to schedule and add it to the plugfest/hackfest planning page.
  • Common configuration file and scenario naming: Jack summarized the discussion that started in Barcelona and noted that the current scenario naming convention needs to be improved.  So far there has not been a lot of feedback/objections from the community on proposed items in Gerritt.  Questions were raised if this really is going to be scalable going forward especially when similar attempts in the past have not been successful.  There was also a discussion if an approach should be taken to force people to adopt this convention in order to be part of Danube.  Jack took an action item to collect additional feedback and come back to the TSC in two weeks with a proposal.  
  • Goals & vision for the Danube release: Morgan went over his draft presentation and discussed the need to better articulate OPNFV both internally and externally.  There was a good discussion on if we are giving up on building a reference platform and the desire to continue the discussion via mailing list.  

 

MeetBot Minutes

November 1, 2016

Agenda

Meeting Minutes:

  • Previous minutes approved
  • Ray gave a quick reminder to the community that the Summer Time ended this Europe this past weekend and the Daylight Saving Time ends in N. America this coming weekend, so people need to adjust meeting times accordingly.
  • Board meeting update: Tapio gave an update from the October 28th Board meeting.  The meeting kicked off with an update from the End User Advisory Group before proceeding with the joint TSC-Board meeting.  First a sample project health metrics were discussed, then Bryan Sullivan presented an update from the MANO Working Group.  Tapio led the discussion on the OPNFV Architecture, and there is an action item to discuss goals and vision for the Danube release as a follow-up to the architecture discussion in the December Board meeting.  Chris/Frank discussed collaboration opportunities with other networking projects in the LF (e.g. fd.io, ODL, etc.) and they will be starting conversations with the Boards of other projects to come back to OPNFV with a proposal.  During the Certification & Compliance Committee report out, there was a consensus that there needs to be better alignment with other testing projects.  For the Strategic Planning Committee, a decision was made to dissolve the committee.  Other discussions were on OPNFV values & goals plus membership engagement.  On the OPNFV architecture, there was a good discussion on getting to the next level of detail and how the community can collaborate on this.  Tapio took an action item create a wiki page to start and will make an announcement on the mailing list.
  • Termination review for Resource Scheduler (RS): Mingjiang discussed the original motivation for RS but noted that it has not been active since during the Brahmaputra release.  So far no coding/documentation work has been done and a better home for this project maybe OpenStack.  Via IRC vote, the TSC approved terminating the Resource Scheduler project.  
  • Graduation reviews: Ray noted that as OPNFV matures we should turn our attention to graduation reviews for our mature projects like functest and pharos.  All projects in OPNFV today are in an "incubation phase" and some of our projects would seem to qualify for graduation reviews.  The process for the graduation review is outlined in the Project Lifecycle page, and there was a discussion on what it means for a project to be in a "mature" stage.  Ray took an action item to continue this discussion on the mailing list.
  • Colorado + Danube planning and activities: David McBride notes that there was a discussion last week to postpone the Colorado 2.0 release to November 10th.  One of the scenarios planned for 2.0 is dependent on Fuel and the the Fuel team needs more time.  There is also a possibility of including an fd.io scenario with the delay.  There will be no changes to the Colorado 3.0 release.   The TSC acknowledged pushing the Colorado 2.0 release date to November 10th.  For Danube, Milestone 1 was last week and 34 projects have submitted their release plans.  The Movie project team expressed their intent to participate 2 days after the deadline, but the TSC had no objections to this.  There was a quick discussion on intercepting OpenStack-Ocata (scheduled for late Feb'17) by delaying the Danube release.  Ray took an action item to start a discussion on Ocata and the community's interest in OpenStack's Project Teams Gathering (PTG).  

 

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-11-01-14.00.html

October 25, 2016

Agenda

Minutes

  • Previous minutes approved
  • Colorado + Danube planning and activities: 
    • David noted that at this point we have 2 scenarios for Colorado 2.0 but neither seem to have documentations associated.  In addition, test result for the SFC isn't fully clear (whether it's good or bad) and ONOS scenario doesn't include Yardstick results.  David took an action item to follow-up with PTLs on the status of both scenarios.  There was a consensus to approve Colorado 2.0 release pending follow-up with PTLs by 5pm CET on October 26th and David will update the TSC via email.  
    • There was a discussion on keeping both 2.0 and 3.0 releases for Danube and beyond and the consensus that the overhead is low for maintaining monthly releases.
    • On Danube, David is still awaiting on 8 projects for Milestone 1 documentation.
  • SFQM change in project scope/name: Maryam noted that previously the focus of the SFQM project has been on networking traffic.  One of the starting activities under the new scope is to develop collectd plugins.  The project team has also started planning for the Danube release and the committers for the project will remain the same.  On the new name, there was a consensus for Barometer.  Via IRC vote, the TSC approved the scope change and Barometer as the new project name.  
  • Discussion on merging existing projects: There was a question on how project teams can propose merging two existing projects (e.g. KVMFORNFV and OVSNFV).  The consensus was that a proposal should be posted the proposal on mailing list for 2 weeks prior to coming to the TSC for approval.  
  • Contribution Guidelines: Morgan noted that an additional section on license & copyright has been added to Contribution Guidelines and comments/feedback on the page are welcome.  
  • MANO WG report out: Bryan reviewed the latest material posted at https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111  

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-10-25-05.00.html

October 18, 2016

Agenda

 

Minutes:

  • Previous minutes approved
  • Tapio noted that there is a termination review request for the RS project and the 2-week review period starts now.
  • OpenStack-Barcelona: 
    • There was a discussion on moving the TSC call next week to morning hours in Europe since lot of people will be at the OpenStack Summit, and there was an agreement to have the TSC meeting start at 7am CET followed by the release meeting at 8am CET.
    • The topics (with owners) for the joint TSC-Board meeting are
      • Current state of MANO activities and projects in OPNFV (Bryan Sullivan)
      • Project health/Community metrics (Ray/David McBride)
      • TSC Activities and Scope (Tapio)
      • OPNFV's role in fostering synergies across networking projects (Chris Price/Frank)
    • OPNFV at OpenStack: Ray notes that there is still need for volunteers at the OPNFV Booth.  There is also a joint reception with OpenDaylight on Tuesday evening and people need to RSVP.  
  • Quarterly awards: Ray reminded the community that the nomination for the Q3 awards closes at 5pm Pacific Time on Friday.  
  • Colorado + Danube planning: David McBride noted that Colorado 2.0 is scheduled for next week and so far only 2 out of 6 scenarios for 2.0 are showing up on the Functest dashboard.  For Danube, 40 projects have expressed intent to participate and roughly half of those projects have planning complete for the M1 milestone.  There was a suggestion to review which projects are passing the M1 milestone next week.
  • Mirroring OPNFV repo in Github (read-only): Aric noted that there is a Gerritt plug-in that enables mirroring of OPNFV repo in Github.  Bryan Sullivan suggested including a README file in the Github repo to provide additional context.  There was an agreement to move forward with the read-only OPNFV repo in Github.
  • noha scenario types: Bryan notes that we need a noha scenario for developers and establishing a starting point for engaging with the OPNFV community.  There was also a suggestion that noha scenarios document HW setup where the testing was done.  Jack Morgan took an action item to start a wiki page under Pharos so the community can continue this discussion. 

 

MeetBot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-10-18-14.00.html

October 11, 2016

Agenda

Minutes

  • The community welcomed the new TSC Chair Tapio Tallgren.
  • Previous minutes approved
  • Board meeting report out: Tapio provided an update from the Board meeting and noted that the C&C report out included the status of the Compliance/Verification Program (CVP) which will be presented to the Board in Barcelona.  There was also a discussion that the CVP and the Dovetail test suites will also be presented to the TSC and there will be no further action from the TSC until after C&C Committee's presentation to the Board.  There was a marketing committee update focused on the Colorado launch and a discussion around OPNFV's potential roles in better collaboration/efficiency across different networking projects in the LF.  
    • There was a good discussion on topics for the joint TSC-Board meeting on October 28th.  Tapio discussed proposed topics such as MANO-related projects, TSC activities & scope, OPNFV architecture, etc.  There was concern that MANO discussion maybe premature, but Heather noted that this was one of the discussion topics that the Board was interested even if there are no concrete accomplishments to-date.  Also, on the architecture, Frank made a suggestion to have further discussion on this during the weekly Technical Community call prior to the Board meeting.  Ray took an action item to summarize the joint TSC-Board topics and send to mailing lists.  
  • Colorado & Danube release planning: David McBride noted that 39 projects have expressed their intent to participate in Danube so far.  Colorado 2.0 is scheduled for October 27th and "daily" stand-up meetings have started.  There was a question on which projects will not be participating in Danube.  David noted that so far only Cperf & Dovetail confirmed they will not be participating in Danube and David took an action item to start a new wiki page on the Danube release. 
  • OPNFV at OpenStack-Barcelona: Ray discussed OPNFV's planned activities at the OpenStack Summit and encouraged community members to contribute updates to the wiki page and volunteer to sign up for the OPNFV booth in the expo hall. 

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-10-11-13.59.html

October 4, 2016

Agenda

Minutes

  • Previous minutes approved
  • TSC Chair election is on-going and the community members thanked Chris Price for a job well done as a TSC Chair over the past two years
  • Recap from OpenDaylight Summit: On Thursday there was a good discussion on Dovetail & VNF Onboarding during the OPNFV meetup.  There was also a session with the OpenDaylight Community focused on release alignment and testing collaboration between ODL and OPNFV.  
  • Managing private keys in OPNFV: Luke noted that there have been multiple private keys stored in repositories for some projects which is generally not considered a good practice.  Ash added that reasoning for including keys is to facilitate automation, but there may be better ways of achieving automation which the security group will further investigate.  Ash also developed a tutorial to help people onboard activities in a more secure fashion and Ash took the action item to post the tutorial presentation on the Security working group wiki page.  Luke also asked for volunteers from the community to help with this effort and the security team meets weekly on Wednesdays at 14:00 UTC.
  • Danube development and CI/CD process: Fatih discussed the CI evolution and outlined that there have been some additions to the post-merge job as part of the promotion process.  Experiments will be done with Fuel & Apex and Fatih is looking for help with other installers.  There are discussions on-going with testing teams about using a similar framework and Morgan noted benefits of test promotion as a tool to facilitate onboarding test cases into test frameworks.  
  • OPNFV October Board meeting: Chris shared his presentation for the Board meeting and topics to be covered are Colorado/Danube releases, updates from the ODL Summit, and joint Board-TSC meeting in Barcelona.
  • Colorado + Danube planning and activities
  • Colorado + Danube planning and activities: David McBride describes that there are already over 30 projects that expressed their intent to participate in Danube.  Release planning is ongoing for Danube and a new template will be presented for discussion during the upcoming release meeting.  
  • OpenStack-Barcelona plans: Brandon noted that the Doctor project will be featured during the keynote on Day 1 and OPNFV will be featured in 7 sessions during the week.  OPNFV will also have a booth in the Expo area with demos and there will be a sign-up for booth volunteers.  There will also be meetings for the OPNFV End User Advisory Group and Board meeting (TSC members invited to join the Board meeting in the morning).  Ray took an action item to start the OpenStack planning page.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-10-04-13.59.html

September 27, 2016

Agenda

Minutes

  • Previous minutes approved
  • Colorado launch: Heather discussed Colorado launch assets (e.g. landing page, press release, blogs, social media) in addition to press briefings.  Heather noted that coverage has been positive and congratulated the technical community for an on-time release.
  • Technical Community Elections: Ray noted that the Committer Board election has kicked off and will close at 5pm on Friday (September 30th).  TSC Chair nomination period will also close on Friday.
  • IETF 97 in Seoul, Korea: Heather outlines that we are interested in participating in the IETF Hackathon to bring topics that we want to develop in OPNFV that we could collaborate with the IETF community.  For the Hackathon, we'd need volunteers from the community to facilitate the development of the topic and to run the Hackathon on site at the IETF event.  Some of the potential topics could be SFC, IPv6, BGP & VPN, FD.io and VPP, vsperf and security.  Frank added that the focus of the Hackathon should be on producing demonstrable code in ~24 hours.  Ray took an action item to start a page for IETF97 planning.
  • Colorado & Danube planning and activities: 
    • David McBride noted that Colorado 2.0 release date is October 27th with Colorado 3.0 schedule set for December 5th.  Tapio noted that the Colorado 3.0 date actually falls during the week of the Plugfest, and there will be a further discussion on Colorado 3.0 in the release meeting.  
    • For Danube, the proposal is to open the call for participation for Danube and leave it open for about a month to give community members an opportunity to join (incl. those not familiar with OPNFV release process).  So new project proposals will need to be approved and then declare an intent to participate in the next month.  In addition for Danube, the stable branch window will be about 6 weeks.  Via IRC vote, the TSC agreed to start the Danube release process with proposed milestones and a planned release date of March 27th.
  • Joint Board-TSC meeting on October 28th: Chris reminded the TSC members about the joint meeting with the Board during the OpenStack Summit.  Chris will begin soliciting topics for the meeting.
  • Meetup at the ODL Summit: Ray noted that OPNFV members are invited to join the ODL Community in the main Developer Design Forum room for an hour long discussion on Carbon/Danube planning at 9:30am on Thursday.
  • External repositories: There was a discussion on creating a read-only OPNFV repo in Github as the Github interface is more user friendly and well known.  Ray took an action item to create a wiki page for external repo questions/concerns. 

 

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-09-27-13.59.html

September 20, 2016

Agenda

Minutes

  • Previous minutes approved
  • Technical community elections : A reminder that nomination periods are open both for the Commiter Board & TSC Chair election
  • JIRA Federation: Frank explained the benefits of being able to relate to upstream communities using JIRA Federation as you'd be able to relate to and link across issues in OPNFV and upstream projects.  The TSC agreed to start a trial between OPNFV and fd.io an Frank will report back to the TSC on the status.
  • Non-Apache-2.0 license for the Moon project: Ruan described his work in the Moon project where they use identity federation across OpenDaylight and OpenStack.  The Moon team developed some ODL code under EPL 1.0 license (5 new files & 5 modified files) that is under review, but they have not been merged in ODL yet.  The Moon team is requesting to have Non-Apache-2.0 codes in the OPNFV repository until they get accepted upstream.   The OPNFV Legal Committee will also be reviewing the request from the Moon project.  The TSC has no objections to the proposal from the Moon project team.
  • Colorado planning and activities: David noted that there are 24-28 scenarios that have indicated their intention to release for Colorado 1.0.  Morgan added on test results chart, scenarios with scores above 80% are likely to be stable but there could be documented limitations.  Sofia also noted that on documentation front there are still some inconsistencies and missing documents.  There was a good discussion on release readiness based on documentation issues.  Ray took an action item to setup a 30 minute TSC call at 7am Pacific Time on September 21st.  
  • OPEN-O Developer's Event on September 26th (Bellevue, WA): Marc discussed the Open-O developer event next Monday between 16:30 - 18:30 right across the street from the OpenDaylight Summit and encouraged participation from the OPNFV community.

 

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-09-20-14.00.html 

September 13, 2016

Agenda

Minutes

  • Previous minutes approved
  • Update from the September OPNFV Board meeting: Chris noted that the technical community budget for Q4'2016 has been approved and the next TSC chair will have a chance on developing the budget for the new fiscal year in 2017.  Ray also has an action item to come back to the TSC to give an update on the Q4 budget.
  • Meetup at the OpenDaylight Summit: Ray encourage community members attending the ODL Summit to list their names on the Thursday meetup planning page.  It'd also be good to identify ODL community members we want to invite for the Carbon release discussion (9am) and topics for the open time slot at 11am-noon.  
  • Colorado planning and activities: 
    • David McBride first discussed the Danube release milestones.  David noted that JIRA gating will be used for Danube, and there is also on-going discussion around stable branch window.  
    • For the Colorado release, 14 scenarios are now release ready and further 10 scenarios are approaching stability.
    • There was a discussion on different artifacts for ARM vs. x86 architecture and consensus that ARM will have its own ISOs so their artifacts will need to be accommodated accordingly.  
  • Project health metrics: There was a good discussion on the metrics including the purpose.  There were comments that metrics can help evaluate projects activities and identify outliers or ones that need community's help.  The metrics would also be a good input in the context of project lifecycle assessment.  
  • External repo's: Ray noted that an agenda item for an extended discussion on licensing is planned for future Technical Community call in early/mid October.  There was a good discussion that a "non-governed" repos should be allowed as a short-term solution for example for upstream forks.  There may need to be a distinction between different types of external repos (e.g. ones that are closely reviewed for licensing info. vs. ones that are more informal).  There was a question if it'd make sense to have a separate "folder" for upstream codes in OPNFV and Ray noted that a proposal is forthcoming with some of the OPNFV projects that have upstream forks.  
  • Mailing list discussions: Ray discussed proposals for new mailing lists as opnfv-tech-discuss is getting too congested.  Bryan Sullivan asked for a clarification on upstream mailing lists and Ray noted that this is to facilitate discussions with upstream communities (e.g. OpenStack, OpenDaylight, etc.) without requiring upstream community members to subscribe to OPNFV mailing lists.  The TSC agreed to the creation of new mailing lists for working groups and upstream communities.  

 

MeetBot Minutes 

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-09-13-13.59.html

September 6, 2016

Agenda

Minutes

  • Previous minutes approved
  • New TSC members were introduced.  Rosella Sblendido is a TSC rep from SUSE and five new Committers-at-Large TSC members are Bin Hu, Fatih Degirmenci, Hongbo Tian, Morgan Richomme, and Jack Morgan
  • License scan update: Scott Nicholas gave an update on the latest license scan.  PTLs have been contacted if there were questions, and a quick response/action would be appreciated.  Scott also noted that there's a room for improvement in including license information at the file-level (vs. directory-level) and license files should have a .txt extension.  
  • Confluence/wiki tracking on Bitergia: Ray noted that wiki contribution tracking is something that has been discussed in the community and Bitergia has now added support for Confluence.  There is an opportunity to add Confluence/wiki tracking on Bitergia's OPNFV dashboard for $3k, and there is a room in the current budget to pay for this.  Via IRC vote, the TSC approved $3k spending for adding wiki tracking from Bitergia.
  • September OPNFV Board meeting: Chris shared his draft presentation and he will be going over Colorado update, D-release planning, community elections, and other community updates during the Board meeting.
  • Technical community elections
    • Committer Board (Announcement: Sep. 6/Nomination Sep 13 - 23/Election Sep 26 - 30/Result: Oct. 3)
    • TSC Chair (Announcement: Sep. 12/Nomination Sep 19 - 30/Election Oct. 3 - 7/Result: Oct. 10)
  • OPNFV Intern program update: Ray shared learnings from 5 interns in OPNFV this year.  There was a discussion on the part-time internship option and the consensus was to keep this option along with a traditional full-time internship.  
  • Colorado planning and activities: David McBride noted that Colorado 1.0 release date of September 22nd is fast approaching.  The Functest dashboard shows a small number of "green" scenarios plus the scenario wiki page is showing 6 or 7 scenarios that are not yet ready.  Frank added that for many of the scenarios, the failure may actually be due to one test case.
  • Harmonized configuration for OPNFV: Carlos notes that the doctor project requires certain platform configurations to function.  However, the project team found that this was not possible across all installers for Colorado.  There is a need for a common set of behaviors that allow features to be deployed on all scenarios.  Julien asked if Genesis should be a vehicle to achieve common configurations across installers.  Frank noted that there was limited participation in genesis to harmonize these items and thus stood down from the Colorado release.  Jack Morgan added that the Infra WG has been looking at this from the physical infrastructure perspective that can lead to alignment on installers.  Jack took an action item to work on this topic.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-09-06-13.59.html

August 30, 2016

Agenda

Minutes

  • Previous minutes approved.
  • Toronto Hackfest report out: Chris reported activities from Q3 Hackfest discussions including Coloraro milestone review, mailing list proposals, Dovetail update, etc.  Most discussions are captured in the wiki or on mailing lists.
  • Plugfest update: Lincoln reported that four companies are registered for the Plugfest so far and planning/preparation are being done on the Plugfest wiki.  Ray added that plan is to organize a number of "tracks" during the Plugfest and the (co-located) Hackfest could be one of the tracks.  Everyone participating in the Plugfest (incl. Hackfest) will be required to accept the Rules of Engagement during registration.   Ray asked if there are any concerns with co-locating the Hackfest with the Plugfest and no concerns were raised.  
  • Colorado planning and activities: David McBride noted that deployment figures have not changed significantly in the past week (around 50% are deploying successfully and some scenarios remain inactive).  In addition, a large number of scenarios are not passing all test cases.  Also, there are a large number of Colorado 1.0 issues that may not be resolved in time and these require PTL's attention.  Frank made a suggestion to develop a features/scenarios increment report for Colorado (vs. Brahmaputra) and David took an action item to work on this.  
  • D-release activities: D-release naming activities have kicked off and the voting will start on September 5th.  David gave an overview of a proposal for the D-release schedule, and the projected release date would be March 27, 2017 (https://wiki.opnfv.org/display/SWREL/D-Release)
  • A reminder on the timeline for upcoming elections:
    • Committer-at-Large elections to the TSC (Nomination closes Aug. 19th/Elections Aug. 22 -  Sep. 2/Results: Sep. 6)
    • Committer Board (Announcement: Sep. 6/Nomination Sep 13 - 23/Election Sep 26 - 30/Result: Oct. 3)
    • TSC Chair (Announcement: Sep. 12/Nomination Sep 19 - 30/Election Oct. 3 - 7/Result: Oct. 10)

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-08-30-13.58.html

August 23, 2016

Agenda

Minutes

  • Previous minutes approved.
  • Technical community elections: Ray noted that the committer-at-large election has started and the voting will close on September 2nd (Friday)
  • CII badging update: Sona discussed that OPNFV community has achieved the CII security badge, but work should continue to improve the security in OPNFV.  Luke noted that the security team plans to work with each of the projects to do a security audit of individual projects and provide recommendations for improvement.  Luke asks projects to read the security audit planning etherpad and provide feedback.  There was also discussion on adding "security audit" as one of the release milestones.
  • Project health metrics: There was an action item from the TSC meeting on June 28th to work on establishing metrics for projects to help identify active or struggling projects in OPNFV.  The intention is to develop metrics to help measure projects' activities so that we can identify projects that may need help from the community plus highlight projects that are working well.  Ray has an action item to start a wiki page on project health.   
  • Project lifecycle review and process development: After Colorado, there will be a number of projects that would have participated in multiple OPNFV releases and there is a need to start a discussion on criteria for projects to go beyond incubation.  Dave Neary asked the purpose of a graduation review and if projects have been held back by being in the incubation stage.  Uli and Prakash also noted that we should also consider different criteria for different types of projects for these reviews.  Chris Price noted that a purpose of graduation reviews would be for a community recognition of projects that are doing well, and also communicating project's maturity outside of OPNFV.  
  • Colorado planning and activities: David McBride noted that the stable branch creation milestone has been accomplished for Colorado.  The  infra team is creating Jenkins jobs for Colorado branch and there will be patches pending on gerrit.  David added that the next milestone is test completion in mid-September and that Jira cleanup needs to be done prior to the release.  David McBride has the action item to establish Colorado 2.0 and 3.0 milestones plus start the D-release planning activites.  
  • AoB:
    • Next meet-up will be at the ODL Summit in September and there will be a session on Thursday morning with the ODL community to discuss the ODL Carbon release.
    • D-release naming: Ray has the action item to start the process for naming of the D-release. 

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-08-23-13.00.html

August 16, 2016

Agenda

Minutes

  • Previous minutes approved
  • Next week's TSC call: Since the Hackfest kicks off in Toronto next Tuesday (Aug. 23rd), Ray proposed shifting both the TSC and Colorado release meetings an hour earlier.  Ray will send out an email soliciting further feedback from the community to ensure that the changes are not detrimental.
  • Technical community elections: The TSC agreed to extend the nomination period to ~2 weeks in lieu of discussions/debates on mailing lists.  For the Committer-at-Large TSC election, Frank asked if it'd be possible to also extend the voting period as many are out on vacation in August.  Since there were no objections, the community will follow the following timelines for upcoming elections
    • Committer-at-Large elections to the TSC (Nomination closes Aug. 19th/Elections Aug. 22 -  Sep. 2/Results: Sep. 6)
    • Committer Board (Announcement: Sep. 6/Nomination Sep 13 - 23/Election Sep 26 - 30/Result: Oct. 3)
    • TSC Chair (Announcement: Sep. 12/Nomination Sep 19 - 30/Election Oct. 3 - 7/Result: Oct. 10)
  • Colorado planning and activities: David McBride noted the documentation milestone was yesterday and the stable branch window will remain open until next Monday (Aug. 22nd).  There was good discussion on clarification of projects' participation in the release and a consensus to continue this discussion on the release meeting.  There was also feedback from the Armband team that currently there is no good way to provide status per hardware architecture for scenarios.  Jack Morgan took an action item to discuss long term planning around hardware architectures and scenario compatibility during the Infra WG meeting.  David also has the action item to work with Sofia and Morgan on how to document and capture the results of the hardware testing for colorado.
  • Orchestra project creation review: Guiseppe noted that the initial scope of the project is to focus on vnf testing and deployment.  The Orchestra team has already begun working with models, functest, install tools teams and others.  There are also plans to work with Doctor and Promise teams for fault management and resource reservation.  Via IRC vote, the TSC approved project creation for Orchestra.  

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-08-16-13.59.html

August 9, 2016

Agenda

Minutes

  • Previous minutes approved
  • OPNFV Board meeting recap: Chris Price noted that there was a discussion with the Board on the reporting status for Colorado release and the Board approved the proposal to add 5 Committers-at-Large TSC members.  Also, Board resolutions affecting OPNFV Bylaws will be published going forward. The title of the President for the OPNFV Board will be changed to the Vice Chairperson.  
  • Committer-at-Large elections to the TSC: There was a discussion on dealing with more than 2 individuals being elected from same member organizations and alternates.  The TSC agreed that it is up to individual organizations to decide which two individuals are represented in the TSC.  For alternates, the TSC does not want to enforce who can be alternates but in cases when there are more than two members from the same organization, only two of the votes will count.  The TSC also agreed that the election result is valid for that election only and can not be used to fill vacancies in the future (e.g. when someone steps down).  Chris Price took an action item to update the elections wiki page.  Ray also reminded everyone of the Friday deadline for nominations.
  • TSC meeting schedule: The TSC agreed to postpone this discussion until after the new Committer-at-Large TSC members are elected.
  • Colorado planning and activities: David gave a reminder that the documentation milestone is on August 15th.  For stable branch, there will be a window that will last a week starting with Milestone 9.  David also noted that some projects are forking upstream code, but did not know how to contribute back upstream and is help PTLs work with upstream communities.  
  • Opera project creation review: Opera will initially focus on the integration of Open-O NFVO, a VNFM based on Juju, and an OpenStack based VIM. TOSCA and HEAT will be the primary target interface models.  The project team will start with a vCPE use case for its work and the plan is to participate in the OPNFV D-release.  The project team still needs to investigate which scenarios would be used and how they would interact with installer projects.  Via IRC vote, TSC approved project creation for Opera.  

 

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-08-09-13.59.html

August 2, 2016 

Agenda

Minutes

  • Previous minutes approved
  • OPNFV Board meeting topics: During the Board meeting on Augst 4th, Chris will discuss Colorado update, Committer-at-Large election, and Community Events.  If there are any feedback on the presentation material, please let Chris know prior to the meeting.  
    • For future TSC meetings after the Committer-at-Large election, Brian Skerry asked what the new quorum count will be and if Community TSC members can name alternates.  Brian took the action item to start a discussion on TSC alternates on mailing lists.  Another item that needs clarification is how to limit TSC seats to 2 per member organization when more than 2 are elected, and Chris took the action item to clarify this  on the wiki page.    
  • October-January budget amendment and activities: Ray noted that the OPNFV fiscal calendar will be shifting to January - December in 2017 and there will be a "transitional budget" for October - December'2016.  For IT, there will be additional spending for new staff and switches for newly donated hardware.  
  • Committer Promotions: There was a discussion of allowing gerritt reviews to be used for committer promotions (in addition to email votes).  Via IRC vote, the TSC approved the use of gerrit for committer promotion as described on the Committer Promotions wiki page.
  • Colorado planning and activities: 
    • David McBride noted that project reporting has improvevd significantly since last week.  Also, the the Scenario table in the wiki page is sortable by different columns.  
    • Uli explained that the steps to Colorado release will be the same as for Brahmaputra and that he has updated the process and described it for Colorado miletsones.  There was a good discussion if every project needs to follow the stable branch handling at the next milestone.  David McBride took the action item to follow-up on this discussion to understand any impact on the release schedule or if would be possible to allow exceptions.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-08-02-13.59.html

July 26, 2016

Agenda

  • Discussion around adoption of Phase 1 of CI evolution for Colorado
  • Joint discussions with the OpenDaylight Community at the ODL Design Summit - Unknown User (rpaik)

Minutes

  • Previous minutes approved
  • CII Badging update for OPNFV: Sona provided an update on the CII badging activities and one remaining issue is using MD5 as was found in releng.  Work is on-going to resolve this and Aric owns the JIRA ticket for this issue.  Sona noted that instead of MD5, sha2 could be a better option.  Sona and David McBride took the action item to resolve issues with MD5 based cryptographic algorithms in Colorado time frame. 
  • Community TSC member election: Chris reviewed the election process as captured in the wiki.  Ray added that the list of committers as of August 1st will be used for the election.  Via IRC vote the TSC approved the election process as outlined in Community Election Procedure
  • Colorado planning and activities: David presented his analysis of risk levels of projects participating in Colorado.  David noted that some projects are not reporting their status to the wiki page, and projects that are either missing milestones or reporting put themselves in a high risk category.  David added that JIRA ticket handling (e.g. closing tickets, using common versions and tags, etc.) is also an issue for many projects.  For scenarios, reporting has also been lacking on the scenario status wiki page.  For high risk projects, David has already been in communication with the PTLs.  Gerald asked what would be the next steps if projects are not able to recover their status, and David responded that when the situation is clear for high risk projects he will come back to the TSC to ask for a decision as to the projects remaining in Colorado if necessary.  
  • Discussion around adoption of Phase 1 of CI evolution for Colorado: Unknown User (trozet) noted that he's concerned about the Jenkins job structure change in Phase I that may have an impact on the Colorado release.  In addition, Apex has a different job structure vs. other installer projects.  After some discussion, there was a consensus that the TSC does not object to allowing Apex to defer alignment of job structures as long as we secure that the we can achieve phases 3 and 4 of the CI evolution in the D release.
  • Joint discussions with the OpenDaylight Community at the ODL Design Summit: Ray noted that the OpenDaylight Community proposed having a session during their September Design Summit (on Thursday) to discuss the ODL Carbon release and needs from OPNFV.  At a nominal cost, OPNFV will be able to get a meeting space to meet with the ODL community.  Ray will setup a planning wiki page with logistical information.  

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-26-14.00.html

July 19, 2016

Agenda

Minutes

  • Previous minutes approved
  • Alternating time slots for TSC meetings: Feedback from community members in Asia is that the current TSC meeting time is inconvenient for many people in the region (e.g. 10pm in China, 11pm in Japan, etc.).  Suggestions were made to continue the discussion on the mailing list or create a poll if needed.
  • GoToMeeting accounts for project team meetings: Ray provided an update on the 2nd GoToMeeting account that was created in May.  Ray took an action item to re-send the announcement email from May to opnfv-tech-discuss.
  • Q3 Hackfest: Ray noted that the Hackfest registration page is up and encouraged community members to add breakout topics on the Planning page. There was a discussion on organizing a joint breakout session with Dovetail and C&C members at the Hackfest.  
  • Colorado planning and activities: David McBride discussed the test implementation milestone on July 15th and noted that 24 projects have not reported for milestone 7 yet (Releases Colorado Projects).  David took the action item to update the overall reporting pages by next week and will be following up with the PTLs.  

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-19-14.00.html

July 12, 2016

Agenda

Minutes

  • Previous minutes from June 28th & July 5th approved
  • SPC Working Group:  
    • Ulrich Kleber shared his presentation on the Polestar working group proposal.  The working group's goal is to help get alignment on OPNFV community wide vision and calls for cross-project participation.  There was a discussion if the working group membership is open (like other working groups in the technical community) and that it'd be preferable to have more participation from non-Platinum member organizations.
    • OpenStack Operators Telecom/NFV Working Group: Uli notes that this new group meets bi-weekly on IRC on Wednesdays at 8am Pacific Time and encourages OPNFV community members participation.  Uli also added a reminder that there are 2 days remaining for submitting session proposals for OpenStack Summit in Barcelona.  
  • Abandoning old patch sets in Gerrit: Unknown User (agardner) noted that there is a request to remove a patch set if it is not touched for 6 months.  The patch will go into an "abandoned" state.  The TSC agreed to move patches that have not been updated for more than 6 months into "abandoned" state. 
  • Colorado planning and activities: David McBride reminded everyone that the test implementation milestone (M7) is this Friday (15th) and this reflects moving out the milestone a week.  David noted that he does not expect this to have an impact on the overall release schedule.  TSC agreed to pushing out the M7 milestone by a week.  David also gave an assessment of "yellow" for the release as not all projects are completely aware of the release milestone/schedule.  
  • Q3 Hackfest: Unknown User (rpaik) noted that the next Hackfest will be at a venue close to the LinuxCon-North America and encouraged community members to post breakout session proposals the Planning page.  More details will be sent out as soon as venue, registration details, etc. are finalized.  
  • Project creation review: Unknown User (lukehinds) noted that the security scanning functionality is already part of Functest as of 3-4 weeks ago.  Also, the latest version of the OpenSCAP will be used in the project.  The project will continue to be embedded in Functest, but will now have a separate repository.  Via IRC vote, the TSC approved creation of the Security Scanning project.  

MeetBot Minutes
http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-12-13.58.html 

July 5, 2016

Agenda

Minutes

  • Approval of previous meeting's minutes deferred until Ray returns.
  • Unknown User (kunzmann) requested that the topic of the Feature Freeze milestone (July 1) be added to the agenda.  Unknown User (christopherprice) requested that this topic be deferred to the Release Planning meeting in the next hour.
  • Fatih Degirmenci described the proposal for the evolution of OPNFV CI
    • Details here.
    • Motivation for change is stability of current system and the time to debug.
    • Using a tiered approach would likely reduce the time it takes to isolate a bug.
    • Validating scenarios in a virtual environment before testing on bare metal would help to preserve resources.
    • Some concern was raised about the timing of the changes.  We need to avoid impacting Colorado, so most changes should wait until the D-release cycle.
    • Proposal to implement changes in two phases: (1) low impact changes during Colorado release cycle; (2) higher impact changes early in D-release cycle.
  • Committer at Large (CAL)
    • Unknown User (kunzmann) suggested that we need to document a common definition of this term
    • The plan is to restrict nominees to existing committers.  Unknown User (dneary) raised a concern about this.
    • Who should vote?  Unknown User (dneary) suggested that voters should include, at a minimum, all committers.
    • How many? 
    • Voted on "Does the TSC agree to include 5 committer TSC seats for the 2016/2017 term?"  Approved.
    • Voted on "Does the TSC agree to start the committer election process on the 8th of August?"  Approved
  • Colorado Release
    • David McBride reminded the team that the Feature Freeze milestone was Friday, July 1.  In addition, the Test Case Implementation and Scenario Integration milestones are this week.
    • David McBride told the team that three projects that had previously expressed intent to participate in the Colorado release have voluntarily withdrawn from the release:
      • Escalator
      • Resource Scheduler
      • Policy Test
      • Escalator will likely participate in a future release; however, the other two projects will probably not.
      • David McBride also said that there seems to be no process for projects to withdraw.  These projects were identified by David based on discussions with the PTLs.
  • Ran out of time to discuss the SPC working group and the QTIP project.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-05-13.59.html

June 28, 2016

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • OPNFV Design Summit & Summit report out - Brandon
  • OPNFV Plugfest and ETSI Plugtest follow up - Pierre
  • OPNFV Board meeting report out - Chris
    • SPC Working Group
    • TSC structure and technical Governance
    • Infrastructure Working Group
      • Infra resource request
  • Project structure, scope and coordination discussion - Chris/All
    • Working groups
    • Project overlap
    • "Less Active" projects
  • Colorado planning and activities - David
  • AoB

Minutes

  • Previous minutes approved
  • OPNFV Design Summit & Summit report out: Brandon noted that the Summit Recap page is available and there were 620 attendees from 35 coutries at the Summit.  Attendance at the Design Summit was over 300, which is an increase from last year.  The full Summit report will also be available in a few weeks.  Videos from the Summit should be posted on the Summit Recap page in the next few days, and Brandon encouraged everyone to complete the Attendee survey.
  • OPNFV Plugfest and ETSI Plugtest follow-up: Pierre noted that ETSI plans to list OPNFV as a "Supporting Open Source Project" for the ETSi Plugtest.  OPNFV member organizations that are also members of ETSI can bring OPNFV Platform to the Plugtest.  It was also determined that a co-located event between OPNFV and ETIS will not be possble this time.
  • OPNFV Board Meeting report out
    • SPC Working Group: SPC (Strategic Planning Committee) is a board committee and wants to reach out to the wider technical community via a Working Group.  Uli noted that there was a meeting during the Design Summit and will be sending a note to mailing lists to solicit others who are also interested in participating in the Working Group.  
    • TSC structure and technical governance: Chris Price mentioned that he presented the same set of slides from the last TSC meeting to the Board, and the feebdack from the Board was to execute on "Committer-at-large" elections for the TSC as noted in the TSC Charter.  
    • Infrastructure Working Group: The request was made to the Board to add 2 Full-time people at the LF (release engineer & system administrator) to improve support for the OPNFV community.  This will allow the Infra WG community members to focus on improvements (vs. daily upkeep).
  • Project structure, scope and coordination discussion: There are a number of projects that have not been active or staffed by a single company and has not been able to attract new contributors.  There was a good discussion on different metrics to determine the health/status of projects.  Brian Skerry and Tapio agreed to meet after their vacations to continue evaluating this topic.  
  • Colorado planning and activities: David McBride provided an update from meetings with project teams during the Design Summit.  David also noted that the feature freeze milestone on July 1st will provide clarity on which projects are demonstranting the ability to be part of the Colorado release.  

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-06-28-13.58.html

June 21, 2016

The TSC Meeting during the OPNFV Design Summit will be at 8-9am CET.  Room Potsdam III at InterContinental Berlin will be available for the meeting.   

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • Update on the TSC Charter to reflect the OPNFV Code of Conduct - Ray
  • Report out from the Design Summit - Ray/Chris 
  • Colorado planning and activities - David
  • MANO working group discussion 
    • Establishing a working group to coordinate among projects relating to MANO.
  • Joint TSC Board meeting preparation:
    • Engagement with the SPC - Uli K
    • C&D release planning - David
    • Infrastructure WG report out - Fatih D
    • Bitergia roadmap - Ray & Dave N
    • TSC Governance discussion for the joint Board-TSC meeting - Chris
  • AoB

Minutes

  • Previous minutes approved
  • Update on the TSC Charter to reflect the OPNFV Code of Conduct: Ray noted that the OPNFV Board approved the new TSC Charter reflecting the new Code of Conduct.  
  • Design Summit report out: Over 300 people attended the first day and there will be several co-located events on Day 2.
    • Q3 Hackfest: The next OPNFV Plugfest will take place during the week of December 5th, and Ray proposed having a Q3 Hackfest at LinuxCon NA (Toronto) and a meet-up at OpenDaylight Summit (Seattle).  The TSC agreed to holding the Q3 Hackfest co-locate with LinuxCon.
  • Colorado planning and activities: David McBride has been working with the infrastructure team at the Design Summit to work through release activities.  In general, the infrastructure is looking good for Colorado, but a pod for ARM will be added to support ArmBand activities. 
  • MANO Working Group: Chris Price noted that the MANO working group could be looking at things like common interfaces and work on cross coordination. There was a discussion if a charter is required for the Working Group, but existing Working Groups in OPNFV (e.g. security, infrastructure, testing) do not have charters that were approved by the TSC.  The TSC agreed that the establishment of the MANO Working Groups would be a good idea.  Prakash will come to the Technical Community meetings for further discussions.
  • Joint Board-TSC meeting
    • David McBride prepared slides for the C&D releases and will send out to mailing list for feedback.  Uli is working on the SPC interaction presentation and noted that the SPC is interested in forming a working group to address long term planning and community themes
    • TSC governance: Chris Price suggested that options for the TSC composition includes maintaining the current setup (with committers at large); phased migration to an elected TSC; migrate to a fully merit-based TSC.  There was a discussion on potential tradeoffs when Platinum members do not automatically get a TSC seat, concerns about the TSC size (e.g. for achieving quorum), ensuring non-Platinum member classes are represented, etc.

 

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-06-21-06.00.html

June 14, 2016

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • Next week's TSC meeting - Ray
  • Joint Board-TSC meeting in Berlin - Updates
    • TSC governance - Chris
    • Engagement with the SPC - Uli K
    • C&D release planning - David
    • Infrastructure WG report out - Fatih D
    • Bitergia roadmap - Ray & Dave N
  • Design Summit update - Ray 
  • Colorado planning and activities - David
  • Project creation review
  • MANO working group discussion - Chris (may need to postpone)
    • Establishing a working group to coordinate among projects relating to MANO.
  • AoB

Minutes

  • Previous minutes approved
  • Next week's TSC meeting will be at 8-9am CET on June 21st.  Room Potsdam III at InterContinetal Berlin will be available for anyone interested in participating in person.  
  • Joint Board-TSC meeting: Ray noted that TSC members can join the joint meeting around 10am on June 24th.  Chris Price has an action item to start an email discussion on the TSC governance.
  • Design Summit update: Ray noted that the latest schedule is available at Berlin Design Summit.  In case you have not scheduled your breakout sessions, you can can still add sessions to the planning wiki page.  Heather added that there will be TV screens throughout the venue during the week for soccer fans.  
  • Colorado planning and activities: David McBride discussed triage process for JIRA issues and there will be a breakout session to discusss this topic during the Design Summit.  The latest release schedule and milestones were also discussed and these are available at https://wiki.opnfv.org/display/SWREL/Colorado. Frank noted that there are no separate feature freeze dates for 2.0 and 3.0 releases. There was a question on documentation completion date and David responded at the date is aligned with the stable branch creation.   Frank also made a suggestion to add a note that test results will not be part of the documentation completion in mid-August.  Via IRC vote, the TSC approved the OPNFV Colorado schedule.  
  • Project creation review: Zhijiang discussed key highlights of Daisy4NFV such as multicacst, automatic deployment, containerized OpenStack services, configration template, etc.  One of the concerns expressed is that a new installer will add new scenarios, and add strain to CI and testing teams. Zhijiang sees this as a flaw in the scenario process which we should address. There is also a plan to add a new CI pod at ZTE for testing.  There was a good discussion on the need to investigate resource issues on scale testing and requirements for OPNFV test project teams.  Via IRC vote, the TSC approved the project creation for Daisy4NFV.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-06-14-13.59.html

June 7, 2016

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • ETSI PlugTest Plan - Pierre Lynch
  • Joint Board-TSC meeting in Berlin - Chris
    • TSC governance - Chris
    • Engagement with the SPC - Volunteer
    • C&D release planning - David
    • Infrastructure WG report out - Volunteer
    • Bitergia roadmap - Ray/Volunteer
  • Design Summit update- Ray 
  • Colorado planning and activities - David
  • Project creation review
  • AoB

Miniutes 

  • Previous miniutes approved
  • ETSI Plugtest plan: Pierre Lynch provided an update on plans for the ETSI Plugtest.  The Plugtest will focus on interoperability over standard interfaces, and the HIVE tools will be used for remote testing.  Test case proposals need to be submitted to ETSI for approval prior to the event.  ETSI team would like OPNFV to participate in the Plugtest and potentially coordinate with OPNFV Plugfest.  The first ETSI Plugtest will likely be in January'17 and the planned frequency is still TBD.  Chris Price noted that one possibility out of the 2nd OPNFV Plugfest is to identify scenarios that OPNFV can bring to the ETSI Plugtest.  Ray took an action item to call for volunteers from the technical community to have discussions with ETSI Plugtest team (likely in conjunction with the OPNFV C&C Committee).  
  • Joint Board-TSC meeting in Berlin: Chris Price discussed topics for the joint Board-TSC meeting and asked for volunteers to lead some of the topics in the meeting.  Uli volunteered to take the lead on SPC engagement, Fatih volunteered for the Infrastructure WG readou, and Ray will work with Dave Neary on the Bitergia roadmap.
  • Design Summit update:  Ray noted that selected Design Summit sessions are now listed at Berlin Design Summit.  Ray also mentioned that he will be working with community members to create a single table that shows the schedule of all lecture-style sessions plus breakouts.  
  • Colorado planning and activities:  David McBride noted that he completed his action item of establishing a clear stable branch date (August 15, 2016).  Rather than voting on the Colorado release plan during the meeting, Chris Price took an action item to write a concise vote text on the Colorado plan and execute the vote via e-mail this week.
  • Project creation review: Zhijiang Hu presented the proposal for Daisy Nfv, and noted that Daisy4nfv introduces Kolla to speed up deployment and atomic upgrades.  The plan is to be ready by the D-release.  Number of people commented that there are a lot of similarities with other installer projects and there maybe opportunities for collaboration.  Chris Price also noted that he intends to raise the question of infrastructure usage for installer projects as a topic for consideration on this week's Infra WG call.  The review for the Daisy4nfv project will resume in the weekly Technical Discussions call and/or the next TSC meeting.  

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-06-07-13.59.html

May 31, 2016

Agenda

Minutes

  • Previous minutes approved.  
  • Joint Board-TSC meeting in Berlin: Current optics are TSC governance and SPC interactions.  Other possible topics are Bitergia roadmap and Infrastructure WG report out.  Chris Price has the action item to continue developing the agenda for discussion with the technical community.
  • OPNFV Code of Conduct: Ray described a proposed 1-sentence update to the Section 1 of the TSC Charter to reflect the community Code of Conduct.  Via IRC vote, the TSC approved the Code of Conduct and propose the identified changes to the TSC Charter.  Ray has the action item to review the changes with the OPNFV Legal Committee prior to presenting it to the Board.  
  • Colorado planning and activities: The PTLs reached a consensus on a code freeze date of August 15th (with a proposed release date of September 22nd).  Frank noted that OpenDaylight-Boron will not code freeze by August 15th and this may have impact on a number of scenarios.  David McBride took the action item to update the project release diagram with the code freeze date and definition.  
  • SFC project scope adjustment: Brady notes that the scope change is to add VNF manager and in future releases MANO-based orchestrator.  There were a number of questions on Tacker, and Brady noted that the plan is to use Tacker for Colorado as VNF manager (but not to develop/test Tacker).  Via IRC vote, the TSC approved the scope change for the SFC project.
  • VNF Event Stream creation review: Alok/Bin discussed the project proposal.  The scope includes a common event data model, platform support for generating the event stream, development of an event collector (for MANO components) to consume the event stream.  Via IRC vote, the TSC approved project creation.  

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-05-31-14.00.html

May 24, 2016

Agenda

Minutes

  • Previous minutes approved
  • Purchasing additional memory for LF PODs: Fatih asks if memory on 2 jump servers plus 4 standalone servers can be upgraded from 32GB to 128GB for better performance and deplyments.  Via IRC vote, TSC agreed to purchasing additional memory for 6 servers in the LF data center.  
  • Joint Board-TSC meeting in Berlin: Ray mentioned that TSC will be invited to join the Board meeting in Berlin around 9:30am CET for a 3-4 hour session.  Ray encouraged the community to make suggestions on agenda topics for the joint meeting.  
  • OPNFV Code of Conduct: Gerald made a suggestion that the names of the LF staff (Heather & Ray) for the email alias conduct@opnfv.org should be listed on the Code of Conduct page.  Ray will also propose an update to the TSC Charter to reflect the OPNFV Code of Conduct.  
  • Berlin Design Summit Update: Ray noted that a 3rd room has been added for the Design Summit.  One room will be reserved for plenary sessions and presentations while the other two will be used for project team breakouts/hack sessions.   People can plan breakout sessions at [ARCHIVED] Berlin Design Summit Project Breakouts and Hacking.  
  • Colorado planning and activities: David discussed that the community is approaching consensus on the relese and a community survey for key points will resolve toward a final schedule.
  • Review of OPNFV Support models: There was a good discussion on current support tools (e.g. AskBot & opnfv-users mailing list).  Aric suggested another possible tool from Atlassian https://www.atlassian.com/software/confluence/questions.  
  • Options for the OPNFV Plugfest: There was a good discussion on possible Plugfest dates considering a packed events schedule in Q4'2016.  Trevor noted that logistical requirements/efforts for Plugfest hardware should not be underestimated.  Ray will start an email discussion this week and propose ideas on Plugfest/Hackfest in 2H'2016.  

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-05-24-14.00.html 

May 17, 2016

Agenda

Minutes

  • Previous minutes approved
  • 3rd party Open Source Software dependencies: Ray shared the wiki page (Licensing in OPNFV) that has details on the process for obtaining OPNFV Board approval for non-Apache v2 licenses if this is necessary.  Scott outlines that the best way for the OPNFV to upstream code to source projects is via contributions to those projects' repositories directly.  The LF team periodically performs license scans but if community members want to ask/raise issues ahead of time, please contact Ray or Scott Nicholas
  • May OPNFV Board meeting: Chris reminded everyone that this is the last board meeting before the joint Board-TSC meeting in Berlin.  Chris also reviewed his slides on TSC Governance based on community feedback and noted that there is a perception that the OPNFV TSC is "pay-to-play".  Chris also added that his preference is for project teams to be consensus-driven with a minimal guidance from the TSC. 
  • Committer removals: Maryam mentioned that the inactive committers have not submitted any patches or attended any meetings in the past 6 months. Via IRC vote, the TSC approved removing committer rights for chenjinzhou@huawei.com, randy.wang@huawei.com, challa@noironetworks.com, tgraf@noironetworks.com from the VSPERF project.  
  • Annual Awards: Ray outlined the process for 2016 Annual Awards.  A suggestion was made to name the Award after Margaret Chiosi (our previous Board President).  
  • Plugfest readout: There were more than 40 people at the Plugfest including 3 from non-member companies.  Learnings from the Plugfest will be discussed at the Design Summit and a whitepaper is also in the works.  

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-05-17-13.59.html

May 10, 2016

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • OPNFV Summit update - Brandon
  • Budget update - Ray
  • Report out from the OPNFV Plugfest - Ray
  • OPNFV Working Groups - Chris
  • Colorado planning and activities - David
  • AoB

Minutes

  • Previous minutes approved
  • OPNFV Summit Update: Brandon notes that Summit schedule is now available at https://www.eventscribe.com/2016/OPNFV/aaSearchByDay.asp?h=Full%20Schedule&BCFO=P|G. OPNFV member and Summit sponsor organizations have discount codes that can be used for registration.   Design Summit will take place on June 20th & 21st an email on Design Summit proposals can be found at http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2016-May/010389.html. There will also be a 1/2-day "orientation session" on Sunday (June 19th) that will be free of charge.  Project Track/Project Theater is planned during the Summit, and Ray will be sending an email update out to PTLs.  
  • Developer Collaboration budget: The technical community is trending well in terms of the budget.  However, Ray/Heather noted that the community could be spending more on interns and encouraged adding more internship project proposals at Intern-projects-page. 
  • Plugfest report out: Ray noted that the Plugfest is off to a good start with good representation from install and test projects.  The goal is to publish a whitepaper to summarize the learnings after the Plugfest.  Ray will also post a daily summary of activities at Plugfest (Brahmaputra)
  • OPNFV Working Groups: Chris Price noted that the Infra Working Group had the first meeting last week.  There has been questions on if decisions can be made in Working Groups, and Chris encouraged decision making within working groups but TSC can help if any guidance is needed.  Dave Neary added that communication across stakeholders is needed when projects make decisions that affect other projects.  Fatih reminded everyone that the Infra Working group is an open group and others are welcome to join.  There was a general consensus that  working group for Infra & Testing seem to be working well and maybe a good way to utilize community’s time.  
  • Colorado planning and activities: David McBride mentioed that the focus of the weekly release meeting should be on reporting and coordination.  Also, milestone definitions is approaching a steady state for Colorado and release projects in general.
  • AoB: Bryan Sullivan mentioned that the OpenDaylight Summit CFP has closed and asked for OPNFV's plans at the ODL Summit in September.  Ray added that OPNFV is a Silver sponsor at the ODL Summit and it maybe worth organizing a me/hackfest.   Ray/Chris Price took an action item to update the events page on the wiki. 

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-05-10-14.00.html

May 3, 2016

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • Highlights from the OpenStack summit - All
    • Quick read-out on; statistics, infra, project teams.
  • Design Summit update - Ray
  • OPNFV Technical Governance Discussion  - Chris
  • Colorado planning and activities - David
  • Colorado infrastructure cross project initiatives
    • RelEng: Jenkins Jobs refactoring  Unable to render Jira issues macro, execution error.
    • Genesis: Common configuration  Unable to render Jira issues macro, execution error.
    •  Pharos: Compliance  Unable to render Jira issues macro, execution error.  and Tooling  Unable to render Jira issues macro, execution error.
  • AoB

Minutes

  • Previous minutes approved
  • Highlights from the OpenStack Summit: Chris Price noted that there was a meeting with the OpenStack infra team on Friday and is trying to make connections with the OPNFV infrastructure team to start collaboration.  Uli/Bryan noted that there is definitely good synergy between & relationship between the two communities.  Ildiko also noted that many OpenStack members came to OPNFV sessions to learn how to collaborate with OPNFV.   Dave Neary shared feedback from OpenStack that OPNFV should approach them with a problem and collaborate with them on a solution (vs. telling them what to do).  
  • Design Summit Update: Ray Paik encourgaged community members to post session proposals at Design Summit session proposals page by May 27th.  Ray also took the action item to send a mail to mailing lists for a "call for volunteers" to help with Design Summit planning.  During the main Summit, there will also be a "Project Track" so that project teams can present an overview/update on their projects.
  • OPNFV Technical Governance Discussion: In addition to discussions on mailing lists, people can send private feedback to community-feedback@opnfv.org if anyone is uncomfortable with doing it in public mailing lists.
  • Colorado planning and activities: David McBride noted that the project team is continuing to work on the details of the milestones for Colorado and people can participate in detailed discussions during the weekly release meeting (following the TSC call).
  • Colorado infrastrucuture cross project initiatives: There was a discussion on starting a wiki page to document these infrastructure-related initiatives.  Chris Price took an action item to reach out to the infra-related teams to help establish a common wiki page.  Ray also suggested that interns may be a good resource for these initiatives.  

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-05-03-14.00.html 

April 26, 2016

Agenda

Minutes

  • Previous minutes approved
  • Colorado planning and activities: David McBride notes that an email was just sent with updates on projects participating in Colorado release.  Milestone refinement is on-going and there was also good discussions on the schedule at OpenStack Summit.  Chris Price added that it'd be good to have a discussion on improving Documentation for the Colorado release and this could be discussed in other meetings (e.g. Thursday's Technical Community call).  
  • Brahmaputra 3.0 update: Chris Price mentioned that scenarios counts are expected to increase for 3.0 and the labeling should be completed by Thursday (28th).  
  • OSCAR project termination review: Stuart notes that announcement on project termination was sent out 2 weeks ago and no work has been done for OSCAR since project creation.  There's also no impact on any other OPNFV projects.  The TSC approved project termination via IRC vote.
  • Code of Conduct: Ray discussed the current draft of the Code of Conduct (CoC) on the wiki.  Dave Neary asked what happens when there is a poor behavior and what the recourse is.  There was a discussion of having people from the LF plus select members of the community helping with resolutions.  Mike Dolan added that LF typically has a 4-step process, starting with talking to the community members in question, then (if issues are not addressed) with their management, finally in the community, and step 4 is exclusion.  Getting to step 4 is very unusual and indicates a serious problem.  Dave Neary, Chris Price, Ray, Ash, Uli, Jonas Bjurel, and Ildiko volunteered to finalize the Code of Conduct for review at a future TSC call.
  • Design Summit planning: Ray discussed the outline for Design Summit in Berlin.  Chris Price asked if it would make sense to also have project team meetings/hacking on Day 1 plus move some of the presentation sessions to Day 2 so there's a consistent format over both days.  Ray will start a wiki/etherpad page so that people can propose Design Summit sessions.  Dave Neary made a comment that it'd be better to have more interactive sessions (vs. one way presentations).  There will likely be call for volunteers to help review session proposals on the wiki/etherpad.  
  • AoB: Sofia outlines that the Docs team is working on documentation template for Colorado and is looking for community feedback.  Uli made a suggestion that documents should be structured to address the user and the project structure we have today may not be best serving our consumers.  

 

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-04-26-14.00.html


April 19, 2016

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • Board meeting report out - Chris 
    • OPNFV technical governance discussion - Prodip Sen
  • brahmaputra.3.0 update - Chris
  • Colorado planning and activities - David
  • Code of Conduct discussion
  • Upcoming Events and planning - Ray
    • EVNT
    • TSC Meeting on "OpenStack Tuesday" 09:00 central Austin time.
  • Community metrics
  • AoB

Minutes

  • Previous minutes approved
  • Board meeting report out 
    • Chris Price summarized the Board meeting discussions from April 14th.  
    • Next, Prodip gave an update on Board discussion around technical governance and areas for improvement.  Prodip discussed uniqueness of OPNFV and areas where OPNFV can take a leadership role across NFV.  There is also a desire to have a merit-based approach in OPNFV to reward and promote those who are contributing strongly to the technical community.  Prodip asked for feedback from the TSC and community on the topics/feedback presented in the slides and how we can improve our technical structure and governance.  A question was raised how feedback was gathered to-date, and Prodip noted that these were independent feedback and thus the desire to reach out to the sider community.  On NFV industry leadership, Prodip noted that such leadership is desired to broker architectural discussions within OPNFV (e.g. on MANO, Forwarding, etc.).  On the merit-based TSC, there was a discussion that many open source communities have elected committees and this may also be a good way to attract more developers.  Bryan made a suggestion that any move to a new structure needs to have a clear plan and done methodically. The topic will be re-visited in future TSC calls.  
  • Brahmaputra 3.0 update: Chris Price noted that 3.0 is on track for labeling at the end of this month.  A question was raised if another dot release is planned for May, and Chris noted that it looks like most scenarios will make the 3.0 release but can have another conversation next week.
  • Colorado planning and activities: David McBride mentioned that the community wants to have more granular milestones that better capture the development flow toward the release.  Also, the community has agreed to roll the scenario and release planning project discussions back into the weekly release meetings and scenarios/scenario owners are being captured on the wiki (https://wiki.opnfv.org/display/SWREL/Colorado+scenario+inventory+and+dependencies).  David also noted that we are behind on some of our early milestones but catching up and bringing our activities into alignment for Colorado.  David also mentioned that he is close to producing an updated schedule for Colorado.  
    • There was also a board discussion on release cadence/interval as there has been a lot of stress in the community to meet the 6-month cadence.  Brian Skerry added that the cadence in his view is not the issue, our processes and activities should be evaluated to limit the effort of addressing the release activity. Dave Neary noted that the value of the OPNFV community is not in the releases that we produce.  Margaret encouraged the technical community to provide feedback/recommendation to the Board on release cadence.  Chris Price took the action item to start a discussion on the mailing regarding release cadence and Dave Neary has the action item to start a mailing list discussion on whether OPNFV should continue to do releases.  
  • Upcoming events and planning: Ray mentioned that the EVNT wiki page will be further updated shortly, and some of the key upcoming events are OpenStack-Austin, OPNFV Plugfest, OPNFV Summit (plus the Design Summit).  The Design Summit planning will start next week and looking for volunteers to help with programming.  
  • Community metrics: Dave Neary discussed that the metrics should be driven by desired goals and outcomes of the community.  There is also interest from  OpenStack to capture NFV metrics.  Dave took an action item to investigate if a meeting could be setup with OpenStack community next week in Austin.  

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-04-19-14.01.html

April 12, 2016

Agenda

 

Minutes

  • Previous minutes approved
  • Trevor Bramwell introduced himself as another sysadmin resource from the Linux Foundation
  • Wiki post-mortem: There has not been a lot of feedback on the wiki migration on the wiki page and people thought more feedback would be helpful.  Dave Neary suggested having a call to discuss feedback and took an action item to setup a call.
  • Colorado planning and activities: David McBride reports that Milestone 2 passed on April 8th and about 20-30% of projects are reporting "red" for Colorado.  Colorado timelines are under discussion and testing teams have indicated that they need between 12-16 weeks post freeze (including integration/test/docs) to complete the release.
  • Colorado test coordination and planning: Trevor outlines the expansion of test project and scenario growth creates a challenge for the testing teams to coordinate criteria for a release.  Trevor recommended that projects should look to contribute to the test projects which would be reported and documented in a common and consistent manner.  Fatih added that there is a need to reduce overlap and focus our efforts to maximize the effectiveness of our efforts to validate and prove the platform.  Fatih recommended that test project PTLs should drive this forward.
  • Dedicated mailing lists and GTM accounts for project teams: 
    • Frank discussed a need for a separate mailing list for the fd.io project and a discussion on if there is a good case for making an exception.  In general, there was a consensus on not having separate mailing lists for each project.  The TSC agreed to creating a separate mailing list for fd.io
    • GTM accounts: Frank outlined issues with coordinating GTM sessions across multiple project calls and Ray noted that there is a budget for getting a couple of additional GTM accounts if needed.  Ray has an action item to propose a solution to the conference infrastructure on the list and invest in additional accounts as needed.  
  • Board dialogs from the Collaboration Summit: Chris Price summarized board dialogs from the Collaboration Summit.  One of the discussion topics with the OpenStack Board was tracking developer contributions.  
  • Upcoming board meeting report: Chris Price went over the TSC report out topics that he plans to cover during the upcoming board meeting on April 14th.  

MeetBot Minutes

April 5, 2016

Agenda

Minutes

  • Previous minutes approved
  • Tapio asked about the latest on OpenSAF and Chris Price noted that plan is to have a discussion in the OPNFV Legal Committee before coming back to the TSC
  • OPNFV Security group actions for Colorado: Luke discussed the Google Form (http://goo.gl/forms/fy15794sA8) that was sent out to Project Leads for the Colorado release.  This is a questionnaire to collect information for the LF's Core Infrastructure Initiative badging program.  Uli pointed out that many people will have issues with Google forms and Luke took the action item to find alternative ways (e.g. wiki) to collect the information.
  • Brahmaputra 2.0 update: Chris Price noted that labels are now in place for projects that are participating in Brahmaputra 2.0.  
  • Brahmaputra 3.0 update: The release plan for Branhmaputra 3.0 can be found at https://wiki.opnfv.org/display/SWREL/3.0.release.plan
  • Colorado planning and activities; David McBride noted that he's been working with project leads to establish a health metrics for projects.  He will also be proposing milestones that incorporate more details with development activities.  Scenario–as a vehicles for integration and deployment–will also be incorporated into the Colorado release plan earlier.  Proposed (draft) intent to participate in a release can be found at https://wiki.opnfv.org/display/SWREL/3.0.release.plan
  • Wiki migration update: Mark Beierl presented that redirect services for sustaining links are in place and is tracking incoming traffic to correct links when needed.  Mark also noted that no pages or attachments have been lost in the migration and asked ti file tickets to the OPNFV helpdesk if there are remaining issues.  Mark also took an action item to start an email discussion on metadata and Confluence configuration.  There was also a consensus on forming a "curation group" within the community to help maintain the wiki on an on-going basis.  
  • TSC Policy Update: Ray noted that there were no feedback from the Board members on the TSC Policy update proposal (https://wiki.opnfv.org/display/meetings/Tscpolicydraftjan2016) and a new diagram will be added based on the latest ETSI architecture diagram.  Via IRC Vote, TSC approved amendments to the TSC Policy document.  

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-04-05-14.00.html

March 29, 2016

Agenda

Minutes

  • Previous minutes approved
  • Introduction to the fd.io project - Ed Warnicke presented that fd.io is the fast data I/O project that was recently formed and intends to provide a datapath forwarding platform based on the VPP project that enabled simple integration of forwarding control functions and encapsulations.  The first release is planned for June, 2016 and fd.io presentation materials can be found at https://wiki.fd.io/view/Presentations
  • Brahmaputra.2.0 readiness: Chris noted that there are no scenario updates for Brahmaputra 2.0, but there are improvements in testing and documentation.  More scenario updates are expected for Brahmaputra 3.0
  • Wiki migration update: Mark mentioned that there have been issues with the namespace plugin to allow us to address the new wiki pages the same way as it was with Dokuwiki.  In addition, internal links  on the new wiki structure have been done using external links which were not automatically migrated.  Work is on-going to address these issues and requesting community to help.  Also, work is being done via the LF infrastrucuture to resolve incorrect links from Google searches.  An update will be provided to the community within the next 24 hours.  
  • Project creation review:
    • FDS project proposal: Frank discussed the new project proposal to incorporate the fd.io forwarder to OPNFV.  The project will involve collaboration with upstream projects such as OpenDaylight and OpenStack.  There will be a focus on scenario composition with VPP as the forwarding software.  Via IRC vote, the TSC approved the project creation.
  • Infrastructure requirements and improvements: Chris summarized discussion during the OPNFV Hackfest regarding the utilization of existing hardware (vs. purchasing more equipments).  Trevor also noted that purchaing the hardware is the easy part and the bigger challenge is the personel required to support the hardware.  It is also imprtant to follow defined processes for Pharos labs.  

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-03-29-14.00.html

March 22, 2016

Agenda

Minutes

  • Previous minutes approved
  • Project creation review for NetReady: Georg noted that the project name has been changed to Netready to better reflect the scope of the project. Also, there were no future discussions or inputs around the project scope. Via IRC vote, the TSC approved the project creation.
  • Hackfest update: Ray provided a quick recap from the Hackfest. Ray will also send out a follow-up note to gauge community's preference for hackfests in 2H'2016.
  • Board meeting update: There was a feedback from the board to investigate if more hardware is desired for testing/release activities and this conversation started during the Hackfest.
  • Wiki migration update: Migration to Confluence will commence on Friday (25th) morning Pacific Time and the wiki will be unavailable for a few hours.
    • Request was made to the Wiki migration team to ensure that external links to wiki pages are all functional ASAP post migration.  
  • Project creation review for Domino: Prakash presented the project proposal and noted that Domino is a label-based publication/subscription system. Interactions with other OPNFV project such as Models and Parsers were also presented in the project proposal page. Via IRC vote, the TSC approved the project creation.

MeetBot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-03-22-14.00.html

March 15, 2016

Agenda

Minutes

  • Previous minutes approved
  • Project creation review
    • OpenSAF - Jonas Arndt presented the history of the OpenSAF project. In response to question if OpenSAF addresses other markets besides telco/carriers, Jonas noted that there has been military applications, but the focus is on carrier networking. Jonas also added that the OpenSAF foundation will dissolve and the license will change to Apache-2 after the April release. There were questions on the license change-Jonas added that OpenSAF is the sole owner of the copyright-and Ray Paik took the action item to discuss the license issue with the legal team. There was also a discussion on hosting code development projects in OPNFV and Dave Neary will start this discussion on the mailing list.
    • NFV Ready Networking Services: Georg presented the project proposal and the goal of the project is to work with upstream communities to evaluate NFV use cases in the context of cloud networking. There was a good discussion if the work can be under existing projects and on the project scope. Suggestions were also made to change the project name. Georg took the action item to continue the discussion on the mailing list.
  • IETF 95 - Charles Eckel (eckelcu@cisco.com) discussed the upcoming Hackathon at IETF 95 in Bueno Aires and IETF's recent focus on code. OPNFV will also be hosting Bits'N Bites in Buenos Aires.
  • Marketing update: Brandon provided a quick marketing update including OPNFV's activities at ONS, CFP for OPNFV Summit that is open until the end of the month, Plugfest website/registration, and start of the OPNFV Meetup program.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-03-15-13.59.html

March 8, 2016

Agenda

Minutes

  • Previous minutes approved
  • TSC Meetings in Summer time transitions: With Daylight Savings/Summer times starting in the US, Europe, etc. there will be changes in meeting times for different timezones. TSC meetings will stay at 7-8am Pacific Time.
  • Board agenda & TSC update: Chris Price shared his slides for the board meeting that included TSC Policy update, Brahmaputra update and C-release planning.
  • Brahmaputra 2.0 planning: Daily release meetings are continuing to be held at 6:30am Pacific Time, and Chris Price will send a reminder to the mailing list on the daily meetings.
  • Release C planning: Ash Young noted that having projects sign-up and begin recording our state for the C-release should be done quickly. Ash also added that project on-boarding is a key item and took the action item to send a mail to the mailing list to kick start the process. There was a consensus on starting the C-release work as soon as possible and having a one-month planning phase. Via IRC vote, the TSC approved establishing the C-release activity immediately with a release cadence of 6 months.
  • ONOSFW project remaining: Ash Young described that there is a confusion on the name ONOSFW and there is also a trademark issue. Ash also confirmed that this is a simple name change and there is no change in the project scope. Via IRC vote, TSC approved the project name change to NETWORKFW.

 

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-03-08-15.00.html

March 1, 2016

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • Brahmaputra release recap/update
    • Pending scenario stability activity - Debra
    • Brahmaputra stable handling - Morgan/(Fatih/Uli)
    • Communication and web launch - Brandon/Ray/Heather
  • Release C Planning - Chris/All
  • AoB

Minutes

  • Previous minutes approved
  • Brahmaputra release recap/update:
    • Debra outlines that the teams are focused on troubleshooting scenario's that were not in a completely "release ready" state for Brahmaputra. Also, some of the limitations may not be solved in the B release timeframe and may be documented limitations
    • Morgan notes the need to establish a methodology for handling C release activities in parallel with B-stable handling. The current assumption is that we will work only on Master and stable/Brahmaputra and tag the releases as they are ready on stable/Brahmaputra. Uli added that we are not doing stable releases, but only stabilizing scenarios. There was a discussion that there is a need to secure resources for stable handling of stable/Brahmaputra once the scenario's are in a stable state while other resources are assigned to the C-release. Octopus/Releng teams have the action item to work with the design teams to establish a resource plan for stable handling for Brahmaputra 2.0 plus document stable branch handling and labeling for stable/Brahmaputra on the release wiki page.
    • Brahmaputra marketing launch: Heather described various marketing assets that went live earlier in the morning such as the press release, blog post, software downloads page, Brahmaputra landing page, etc.
  • Release C planning
    • Chris Price discussed Immediate activities for release planning.. There were discussions on dates (e.g. a month later than the original target), inter-project dependencies, integration/testing, etc. Chris took the action item to start a discussion on the mailing list to iterate on the wiki page.
    • Release C naming: Ray still collecting nominations and the plan is to send out a poll on March 3rd. A question was raised on guideline for release names, and there was a discussion that there is no strong desire/reason to impose restrictions on release names.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-03-01-15.00.html

February 23, 2016

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • Brahmaputra release update - Chris/Debra
  • Release C Planning - All
  • AoB

Minutes

  • Previous minutes approved
  • Brahmaputra release update:
    • Number of scenarios are ready for release (e.g. Apex/ODL-L2, Compass/ODL-L2, Compass/ONOS, Compass/NOSDN, Fuel/NOSDN, Fuel/ODL-L2, Fuel/ONOS, etc.) There are also projects that have not yet reached a stable scenario (e.g. NFVOVS, KVM4NFV, SFC, BGP-VPN, Doctor, etc.)
    • There was a good discussion on scenarios that are deploying successfully, but have known limitations. The TSC agreed that scenarios with known limitations can be release on Feb. 25th with limitations documented. (These scenarios need to be reproducible) The OPNFVDOCS team has the action item to work with the deploy and test teams to clarify and fully document the state of each scenario. Aric/Debra/Octopus team also took the action item to ensure that the release tagging process is well understood for the project leads. Tagging must be done by Wednesday for all projects.
    • Ray discussed updates on the software downloads page. The main download page will have links to deploy tools and users will be taken to a separate page that include software and documentation for each deploy tool. The main page will also have links to composite docs and a link to the release documentation page which will contain all project documentation.
    • Heather raised the question on the terminology for release iterations. Frank suggested "Release Additions", and there were no objections to the term.
  • Release C Planning:
    • Ray took an action item to start a mailing list conversation for the C-release naming
    • C-release brainstorming Etherpad started
    • There was a good discussion on learnings from the Brahmaputra release such as resource issues on the back-end (e.g. for testing, CI, documentation, etc.), and with Pharos and install teams. There is also a need to identify early on how many projects will be involved and what impact they will have on integration, testing, and infrastructure. Shifting requirements late in the release cycle is also something that needs to be avoided. Another concern that was brought up was that the OPNFV community is not setup to provide adequate support across multiple versions of upstream projects.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-02-23-15.00.html

February 16, 2016

Agenda

Minutes

  • Previous minutes approved
  • Wiki update: Aric noted that once you login with LFID, people should be able to edit the wiki. If there are still issues, please let Aric know.
  • Committer removal for Releng: Fatih confirmed that there has been no objection from Releng committers to removing Victor Laza as a Releng committer. The TSC approved the committer removal via IRC vote.
  • Brahmaputra release update: Debra provided the latest on Brahmaputra. Number of scenarios are working (e.g. few Compass and Fuel scenarios are ready for release), but troubleshooting is on-going for issues such as ODL L-3. Debra will update the wiki with the latest status (incl. documentation of identified issues).
  • Plugfest/Dovetail update: Hongbo presented the latest on the May plugfest Logistics and the Dovetail project. Bryan Sullivan added that there's on-going discussion in ETSI regarding various certification programs and will provide suggestions/ideas to the Dovetail team.
  • Project creation review for Information Modeling: Bryan discussed the proposal and mentioned that the project is intended to collect information on data modeling, show best practices, and and then collect references to tools. Goal is to provide conduit to SDOs so they can interact with OPNFV through our tools. Suggestions were made to add new committers from HPE & Huawei as was discussed in email threads. The project creation was approved via IRC vote.
  • Project termination review for LSOAPI: Kevin discussed reasons for project termination listed on the project wiki page. Dave Neary asked if this is an area that needs to be worked on beyond the Brahmaputra release, and Kevin responded that the problem can now be worked on in ODL (e.g. for the Boron release). There was also a discussion that validation of the use case can be moved to other OPNFV projects such as SDNVPN. The TSC approved project termination via IRC vote.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-02-16-14.59.html

February 9, 2016

Agenda

Minutes

  • Previous minutes approved
  • Change Request for TSC approval of OpenDaylight Beryllium uplift: There was a discussion on taking OpenDaylight Beryllium due to blocking issues with Lithium. Tapio raised the question if there are any dependencies on dlux and none were noted. The TSC approved to support OpenDaylight Beryllium in Brahmaputra via IRC vote.
  • Brahmaputra release date and content: Chris discussed two scenarios outlined in https://etherpad.opnfv.org/p/steps_to_brahmaputra. For scenario 2, there was a discussion that some thought should be given to what can be included in Stable Releases. Comments were also made that the community may want to investigate creating a new lightweight release process for stable releases (post Brahmaputra). There was a consensus forming around scenario 2, and the TSC voted to set the Brahmaputra release date to February 25th with incremental stability releases.
  • TSC Policy document update: Brian Skerry presented the updates on the TSC Policy document following the removal of initial scope constraint on OPNFV. A block diagram from page 14 of https://www.etsi.org/deliver/etsi_gs/NFV/001_099/002/01.02.01_60/gs_NFV002v010201p.pdf will be added to the new TSC Policy page. Also, there was a consensus to remove "..., additional architectural functional blocks, ..." above the block diagram. The TSC agreed to move forward with the proposed text and will approve it once we have received feedback from the Board. Ray has the action item to update the text on the wiki page.
  • OPNFV Hackfest update: Ray noted that the focus of the upcoming hackfest will be on project breakouts and plenary session will be limited to 3-4 hours on the first day Hackfest Etherpad (https://etherpad.opnfv.org/p/Q1'2016_Hackfest). Will also have additional discussions during the Community Call on Thursday.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-02-09-14.59.html

February 2, 2016

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • License scan update - Scott Nicholas
  • Brahmaputra status update - Debra
  • Brahmaputra release date and content discussion - Chris
    • Vote: Shall the TSC set the final release date for Brahmaputra to agreed_date? (-1, 0, +1)
  • TSC Policy document update - Brian Skerry
  • Update on Q1'2016 Hackfest at ONS (March 14-15) - Ray
    • Planning Etherpad (https://etherpad.opnfv.org/p/Q1'2016_Hackfest)
  • Update on Brahmaputra PlugFest planning and activities - Hongbo and team
  • AoB

Minutes

  • Previous meeting minutes approved
  • License scan update: Scott mentioned that another license scan will be done after the code freeze on Friday and individual project teams will be contacted if there questions/issues. Scott also added that if it is not possible to add license information in a file (e.g. for images, binaries, etc.), you can put a license file in a directory. For projects that require files with non-Apache v.2 license, a 3rd party OSS dependency questionnaire will be sent to be filled out by project teams. For documentation, Ray added that Creative Commons license should bs used as noted in the Documentation section of OPNFV Coding Guidelines. opnfvdocs team took an action item to work with the projects to ensure we have the right licensing in our documents. Finally, Scott added that if a file has an incorrect license it can be flagged as a bug, but one needs to be sure they have the rights to change the license of the file prior to making any corrections.
  • Brahmaputra status update: Debra noted that troubleshooting is on-going after code freeze. Some scenarios (e.g. Compass, JOID) have begun to stabilize, but for others more runs are needed to establish a stable trend. There was a good discussion on the latest proposal for a schedule captured on https://etherpad.opnfv.org/p/steps_to_brahmaputra. Morgan added that having all project teams use the same CI solution will make it easier to track & predict what is happening (e.g. on https://build.opnfv.org/ci/view/OPNFV%20Platform%20CI%20-%20Alternative%20View/). The consensus was that the community will likely have more confidence in setting the release date in about a week’s time. The TSC agreed to postpone setting the release date until next TSC meeting when more information will be available.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-02-02-14.59.html

January 26, 2016

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • Brahmaputra status update - Debra
  • Brahmaputra release date and content discussion - Chris
  • Update on Q1'2016 Hackfest at ONS (March 14-15) - Ray
    • Planning Etherpad (https://etherpad.opnfv.org/p/Q1'2016_Hackfest)
  • AoB

Minutes

  • Previous minutes approved
  • Brahmaputra status update: Debra noted that currently there are 24 scenarios planned and 15 of them are installing successfully. Other scenarios have not been deployed and still working through known issues. On testing, both Functest & Yardstick are working through issues. Morgan also added that there are issues with vPing & vIMS. Currently, there is no scenario that is able to be run according to the release requirement of four successful runs (Compass is closest). Consensus that the community is about three weeks behind on meeting the Milestone E requirements (people are still working towards code freeze in many cases). The community also had to deal with the delay in CI lab resources as many were not available until early January.
  • Brahmaputra release date and content discussion: There was a good discussion on staying with the time-based approach for the release vs. moving to a more content-based approach (where a release date would be set based on achieving targets for scenarios). Community also learned in the past few weeks that testing required more time than originally anticipated. There was a consensus to create a new schedule with reasonable milestones in order to set a target release date. The TSC decided to postpone the target release date of Brahmaputra via IRC vote.
    • After the vote, there was a discussion on the definition of code freeze and Chris Price took the action item to start this discussion on the mailing list and vote on the code freeze date.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-01-26-15.00.html

January 19, 2016

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • Brahmaputra update - Debra
  • Brahmaputra release marketing plan - Brandon/Jill
  • Q1'2016 Hackfest at ONS (March 14-15) - Ray
    • Planning Etherpad (https://etherpad.opnfv.org/p/Q1'2016_Hackfest)
  • OPNFV Board meeting update - Chris
  • TSC Policy document update - Brian Skerry
  • ETSI NFV Modeling Workshop summary - Bryan Sullivan
  • AoB

Minutes

  • Previous minutes approved
  • Brahmaputra update: Debra reported that code freeze for installers (e.g. Fuel, Compass4nfv) postponed for a few days due to hardware issues over the weekend. Major challenge now is to stabilize testing suites and test results for the scenarios. Some projects have decided to work in a post-install process to relieve the requirement to support a tested Brahmaputra scenario. Frank added that the TSC will need to determine next week how strict we are on maturity and conformance as we approach the final release date for scenarios that are struggling with stability.
  • Brahmaputra release marketing plan: Brandon Wick reported that the marketting team is preparing their content for going live on Thursday the 4th, pending a go/no-go decision by the TSC on February 2nd. A new Brahmaputra landing page will also be added to opnfv.org. Jill Lovato also discussed press release, blog post, and social media campaign. Jill also wants to include quotes from project leads in the Brahmaputra PR campaigns. Frank asked how much lead time the marketing team would need for release marketing, and Brandon noted that the 2 day buffer is there to allow for any fluctuation.
  • Q1'2016 Hackfest at ONS (March 14-15): Ray started a Hackfest planning etherpad (https://etherpad.opnfv.org/p/Q1'2016_Hackfest) and encourages everyone to add suggested topics on the etherpad.
  • Board meeting update: Chris went over the The January Board meeting summary that was sent out by Wenjing (Board Secretary). During the TSC update, Chris Price communicated to the board that the goal is to stay with the time-based release schedule for Brahmaputra.
  • TSC Policy document update: Brian Skerry provided an update on the TSC Policy document and suggested doing final edits over the mailing list before voting at the TSC meeting next week.
  • ETSI NFV Modeling Workshop summary: Bryan Sullivan provided an update from his participation at the workshop (http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2016-January/007651.html). Bryan also discussed his plan to incubate a project that evaluates interfaces from SDO's and how they are able to be applied to OPNFV (and our upstream communities) including evaluating any divergences.
  • AoB: Ray gave a reminder that an email has been sent to project leads if there were either missing or non-Apache v.2 license information in project repos. A request to address these issues as soon as possible.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-01-19-15.00.html

January 12, 2016

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • OPNFV Board Update - Chris
  • Q4'2015 Quarterly Awards - Ray
  • Project life cycle update - Ildiko/Frank
    • OPNFV Projects
    • Frank would like to vote for the implementation of this description:
      • Vote to approve the new project lifecycle document (+1, 0, -1)
  • TSC report out for the January Board meeting - Chris
  • Brahmaputra update - Debra
  • C-release milestones discussion
  • AoB

Minutes

  • Minutes for December 22, 2015 & January 5, 2016 approved
  • OPNFV Board update: The January OPNFV board meeting agenda was posted in Board agenda email, and Chris Price shared the TSC update slides that will be included in the board deck.
  • Q4'2015 Quarterly awards: Ray noted that it is time to start the quarterly awards process for Q4'2015. There was some concern that people that are new to the community may not be getting the recognition with the current process. Ray to start a discussion on the mailing list to collect community feedback.
  • Project life cycle update: Frank/Ildiko summarized the updates to the document and recent discussions in the community. There was a consensus that further iteration on the document will likely be necessary for latter stages like Integration. The TSC approved the latest project lifecycle document via IRC vote (with 13 votes in favor).
  • Brahmaputra update: Work is on-going to resolve Pharos issues in order to have a stable infrastructure. Testing is also constrained due to issues with deployment scenarios and this is being addressed. Scenario freeze date has been pushed out to January 15th to allow more features into Brahmaputra. Debra is also driving towards test tools, installers, and infrastructure projects freeze by January 19th. TSC should have the necessary information by the next TSC call (January 19th) to make an informed decision on the release.
  • C-release milestone discussion: There was a discussion on the need to clarify milestones for the C-release.
    • The following people volunteered to help Debra with this activity Uli, Fatih, Edgar, Ildiko, Trevor, Tim Irnich, and Frank Brockners.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-01-12-14.59.html

January 5, 2016

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • License scan for Brahmaputra - Ray & Scott Nicholas
  • Brahmaputra update - Debra
    • Release readiness team, to provide steering and the TSC with recommendations, with Ray and Debra
  • AoB

Minutes

  • Minutes for December 15, 2015 approved. Approval for the December 22nd minutes deferred to next week.
  • Confluence migration: Aric reported that the universal migration tool from Atlassian is no longer available and is looking for community help to structure the new wiki. Bryan Sullivan, Mark Beierl, and Chris Price volunteered to help with the work.
  • Alan Sardella also starts this week as a Technical Marketing Manager for OPNFV.
  • License scan for Brahmaputra: Scott Nicholas reported the outcome of the recent license scan and not all projects are following the best practice of including licensing information in files (and not just having a license file in each directory). Scott and Ray will be reaching out to project leads if there's missing license information or if there's a-non Apache 2 license. Scott also added that investigation on license for binary files is still on-going. Scott/Ray will also share the license scan data with files that are missing license or has non-Apache 2 license.
  • Brahmaputra update: Debra reminds everyone that the deadline for Milestone E (code freeze and establishing the stable branch) is today. Debra presented the idea of a "release group" that can evaluate release readiness. There was also a good discussion on Brahmaputra Scenarios. The preference is to ensure that key groups like functest, Pharos, yardstick, releng, installers, scenario leaders, etc. are represented in the "release group".

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-01-05-15.00.html

December 22, 2015

Agenda

Minutes

  • Updates from the December board meeting: There are two new member to OPNFV. SUSE joined as Platinum and CENGN is the first Associate member. There was also a report out from the Strategic Planning Committee on MANO discussions. For future board meetings, agenda will be published and also a summary of the board meeting will be shared publicly.
  • Brahmaputra update: There are issues with a jump host at Intel labs, so not all PODS are available. There was also a discussion on the need to include development testing on Pharos infrastructure earlier in the release cycle.
  • AoB: Need to discuss the "release readiness team" during the next TSC call.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-12-22-14.59.html

December 15, 2015

Agenda

Minutes

  • Previous minutes approved
  • OPNFV internship program proposal: Ray presented the proposal for OPNFV internship. This is a year around program with options for either 3-month or 6-month project. The mentors will be responsible for posting the project proposal, selecting, and managing the intern. Thus the availability and dedication of mentors will be key to the success of the intern project. The community is asked to provide additional feedback via mailing list or wiki.
  • Brahmaputra update: Debra has been focused on working with the community on CI/Genesis/test infrastructure activities. There was also a call on plug-in development which was identified as a gap. There was a question if there is a summary of the features available for all installer in Brahmaputra and they can be found at https://git.opnfv.org/cgit/genesisreq/tree/docs/sources/system-requirements.rst and https://git.opnfv.org/cgit/genesisreq/tree/docs/sources/ux-requirements.rst. Uli added that we do not yet have a stable base for our testing projects to further develop stability in the test suites. There was also a discussion on availability of PODs for installers/CI/testing/releases, and more detailed discussion will continue on Pharos calls.
  • Review and comments on the API workshop material: Bryan Sullivan will be representing OPNFV at the API workshop, and the goal of his presentation is to communicate our desire to collaborate with SDO' performing interface modeling and specification. Bryan is soliciting feedback/input from the community especially on some technical areas.
  • Methods of publishing requirements work with our release: Uli noted "requirements" documents we release should receive a proper review. However, adding them to the documentation tree would not require a huge effort. There was also a discussion that requirements documents are living documents.
  • Project Creation Review
    • OVN for NFV project proposal: The goal of this project is to align on NFV requirements and contribute upstream to OVN. There was a question on what additional capabilities are provided by OVN, and Vikram noted that OVN provides an alternative method of implementing existing features and distributes network control elements. In response to questions regarding OVSNFV project, Vikram noted that objectives of OVN and OVSNFV projects are different, but the intention is to work with OVSNFV team. Via IRC vote, project creation was approved for ovn4nfv (+1: 8 votes, 0: 4 votes, -1: none as shown on IRC log)
  • Updates from the December board meeting: postponed to future meeting as time was running out

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-12-15-14.59.html

December 8, 2015

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • Action points
    • Plugfest working group e-mail - ChrisPriceAB
    • Q1 Hackfest poll - rpaik
  • Removal of OPNFV's initial scope constraints - Chris
  • Brahmaputra milestone D report - Debra
  • TSC meetings rest of the year
    • 15th, 22nd, 29th Dec
    • 5th Jan
  • OPNFV input at Jan 13-14 ETSI NFV-ISG Inter-SDO Information Modeling Workshop - Bryan
  • Artifact page updates, approval of budget - Chris
    • Vote to approve the budget allocation to improve the artifacts page for Brahmaputra. (+1, 0, -1)
  • Methods of publishing requirements work with our release - Chris
  • TSC input for the Board meeting Thursday 10th Dec
  • Project Creation Reviews
  • AoB

Minutes

  • Previous minutes approved
  • Action points
    • Plugfest working group e-mail: Chris Price sent an email to the mailing list seeking volunteers for the upcoming Plugfest.
    • Q1 Hackfest poll: The poll was close between Collab Summit (18):ONS (15). There was a good discussion on whether it makes sense to have two separate meetings or one meeting at one location. Via IRC vote, the TSC agreed to have the Q1 Hackfest co-located with ONS (week of March 14th, 2016).
  • Removal of OPNFV's initial scope constraints: Prodip Sen gave an update to the technical community on the board's decision to remove initial scope constraints. Prodip noted that most of the concerns were around the timing and not necessarily on removing the constraints. There was a feedback that the technical community would like more transparency and discussion around important topics like the scope. The community also discussed if the TSC Policy document needs to be updated with the removal of scope constraints, and there was a general consensus that an update is need. Dave Lenrow and Brian Skerry have the action item to start a workgroup and propose an amendment of the TSC policy for TSC review.
  • Brahmaputra milestone D report: Debra shared the Milestone D report plus projections for Milestone E. Some of the concerns approaching Milestone E are CI unknowns, installer interactions, resource issues, etc. Chris Price noted that one of the learnings from Brahmaputra is that there is a need for more detailed information on milestone criteria.
  • TSC meetings rest of the year: There will be TSC calls on December 22nd & January 5th. NO meeting on December 29th.
  • OPNFV input at Jan 13-14 ETSI NFV-ISG Inter-SDO Information Modeling Workshop: Bryan Sullivan sent out emails to mailing lists regarding the workshop and Bryan is looking for community to provide input from OPNFV as he is developing the presentation.
  • Artifact page updates, approval of budget: There was a discussion on revamping the current artifacts page and Fatih has an action item to start discussing the new artifacts page design on mailing lists. Via IRC vote, TSC approved the budget for the new artifacts page.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-12-08-14.59.html

December 1, 2015

Agenda

Minutes

  • Previous minutes approved
  • Milestone D update: Debra noted that milestone D reports are looking good, but projects are reporting issues as they work towards Milestone E. Debra will also reach out to project leads for 1-on-1 discussions.
  • Plugfest support: Certification & compliance committee wants to have plugfest events following each release. First one is targeted for March-June timeframe after the Brahmaputra release. Chris Price noted that a working group (for testing/integration) is needed to support plugfests. Chris Price/Wenjing will send a note to the mailing list to start the conversation on the Plugfest working group
  • Q1'2016 Hackfest LF Collab-Summit vs. ONS discussion: There was a good discussion on co-locating the Q1 hackfest at either the LF Collab Summit (Lake Tahoe) or ONS (Santa Clara). Ray Paik took the action item to send out a poll to gauge community preference.
  • OPNFV security initiative: Luke described LF's Core Infrastructure Initiative (CII) badge program and how many of the items in the program provides a recommended framework to help OPNFV focus on security as a community. There was a good discussion on impact of upstream components and how the program applies to an integration project like OPNFV. There was a consensus in the TSC for the OPNFV security group to pursue the CII badge program.
  • Pharos LF & Community lab use for Brahmaputra release processing: Fatih explained that there will be resource constraints for Brahmaputra testing if we constrain the release testing to be done only in the LF labs and would like to take advantage of capacity in community Pharos labs. There was a good discussion on which community labs can provide the capability and the need to re-purpose some of the developmental labs for release testing. Using community lab resources also gives the community to demonstrate portability of OPNFV. The TSC agreed to allow the use of Pharos community labs for release testing.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-12-01-14.59.html

November 24, 2015

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • Milestone D update - Debra
  • Project lifecycle discussions
    • Update on progress with project creation WiKi - Ildiko & Dave
    • Project scope adjustments - Uli
    • Process for archiving projects - Chris
  • OPNFV Plugfest, needs and support - Chris/Wenjing
  • Wiki migration plans - Aric/Mark/Ray
    • Setup a Confluence instance: 1 week
    • Get approval on the open source license: 1 week
    • Initial migration of Dokuwiki pages to Conflunce (using Universal Wiki Converter): 1 week
    • Confluence page is up for community review/feedback (both Dokuwiki & Confluence pages will be available during the review period): 2 weeks
    • Complete migration to Confluence and archive Dokuwiki pages (archived dokuwiki pages will be available for 6 months)
  • Finalize the review of the Board f2f and discussions - Chris
  • AoB

Minutes

  • Previous meeting minutes (from the past two meetings) approved
  • Milestone D update: Debra notes that she will prepare a list of questions for projects participating in Brahmaputra and will this will be listed on the wiki page.
  • Project lifecycle discussions: Ildiko provides updates on updates being made to project proposals wiki page and needs the project lifecycle page to be updated. Ray Paik responds that the update is in progress and should be updated soon. There was a discussion on the Word template of the project proposal and the consensus was to remove the Word template and continue using the Wiki template.
  • Project scope changes: There was a discussion on what needs to be done when project's scope changes post creation. The consensus was to have project teams notify the TSC of the scope change and the TSC reserves the right to discuss/review the scope change. There was also a suggestion that changes in the project should be well documented in the project wiki page.
  • Process for archiving projects: There was a discussion on how a project maybe archived when the project has no active members. Also, when dormant projects are listed on the wiki this may cause misconceptions on OPNFV's activities. So far, two dormant projects have been identified, and Ray Paik contacted the project teams regarding archiving those projects.
  • Finalize the review of the Board f2f and discussions: Uli raised the concern that a major changes in the technical aspect of the project as a result of board discussions should be discussed in the technical community. Chris Prise raised the point that board discussions are not public information so this is not always easy. Discussion ensued, and Uli made a request that in the future Chris Price ask for more time to the board in order to collect more input from the technical community.
  • Wiki migration plans: The community is generally in agreement with the proposed timeline, however, the request is made to start the migration process post December 1st (Brahmaputra milestone D).

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-11-24-14.58.html

November 17, 2015

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • Design Summit & OPNFV Summit re-cap
  • Update on the Technical Community budget proposal
    • Establishing and on-boarding and training working group
  • Brahmaputra artifact and release update and agreement
  • OPNFV Project Life Cycle changes and amendments to Bylaws & TSC Charter
  • Four additional Cisco UCS servers at the LF Lab
  • AoB

Minutes

  • Minutes to be reviewed next week as it was posted late
  • Design Summit & OPNFV Summit re-cap: There was good energy & attendance at the design summit (200+ attendees). If you have any feedback on the design summit, you can add to the etherpad at https://etherpad.opnfv.org/p/2015_Design_Summit_feedback.
    • OPNFV Summit attendee demographics:
      • Member (72%) vs. Non-Member (28%)
      • North America (78%) EMEA (12%) APAC (10%)
  • Update on the Technical Community budget proposal: The OPNFV approved the technical community budget proposal on November 13th. Work can now start on new programs such as on-boarding and internship programs.
  • Brahmaputra artifact and release update and agreement:There was good discussion around How feature projects and deployment projects will participate in Brahmaputra. Chris Price took the action item to continue the discussion on the mailing list.
  • OPNFV Project Life Cycle changes and amendments to Bylaws & TSC Charter: The board approved amendments to bylaws and the TSC Charter with the streamlining of the project life cycle. Feedback from the board was that there is a proliferation of many projects and new projects may want to investigate joining existing projects. There was discussion on the need to re-visit metrics on how projects progress from incubation to mature and if changes are needed for project creation. Frank took the action item to begin working on establishing the metrics and evaluation criteria for project progression post Brahmaputra. Dave Neary and Ildiko will also work on clarifying expectations on project creation with the recent amendments
  • Four additional Cisco UCS servers at the LF Lab: New servers are now available in the LF lab and the infrastructure will now be reconfigured to provide 2 POD's for deployment and 2 stand alone servers for nested deployments as well as providing build machines for jobs. Trevor took the action item to update the Pharos page to reflect the changes in the LF lab.
  • Bryan noted the need for the install scripts to amend functionality to the common Genesis deployment. This creates and opportunity to invest in community crowd sourcing for developing and maintaining component integration scripts.

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-11-17-14.59.html

November 10, 2015

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • Latest from the Design Summit & OPNFV Summit
  • OPNFV Software License - Scott Nicholas
  • Brahmaputra artifact governance and expectations
  • AoB

Minutes

  • Previous minutes approved
  • Latest from the Design Summit & OPNFV Summit: Design Summit has been well attended with good energy. Some of the areas for improvement are room sizes, availability of whiteboards, video streaming, and confusion on room reservations (wiki/etherpad/whiteboards)
  • OPNFV Software License: Scott noted that the having the license information in a file (vs. a directory) is a good practice and should continue. There were questions on if the information on OPNFV Coding Guidelines is accurate and how to handle gif/jpeg/binary files. Ray has an action item to investigate these questions with Scott and report back to the technical community.
  • Brahmaputra artifact governance and expectations: Dave Neary noted that he wants Brahmaputra to be based on at a minimum patches that are accepted upstream. However, Frank mentioned that this may not always be possible due to the large cross project dependencies in OPNFV and adds that install teams are concerned about the amount of last minute work that might come up. PTL's have the action item to provide your requirements are into the genesis requirements by November 13th. Frank and Chris Price will also put a concrete proposal together on release contents

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-11-10-15.00.html

November 3, 2015

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • OpenStack reflections and information sharing - Debra
  • Design Summit & OPNFV Summit - Heather/Ray
  • Brahmaputra artifact governance and expectations
  • Upcoming OPNFV Board meeting topics
    • Board / TSC Dinner - Thursday evening
    • Formal approval of bylaw project lifecycle amendments
    • OpenSAF
    • Brahmaputra update - Debra/Chris
    • Pharos updates - Morgan/Chris
  • AoB

Minutes

  • Previous minutes approved
  • OpenStack reflections and information sharing: Debra created an etherpad to collect information from sessions of interest to OPNFV and can be found at https://etherpad.opnfv.org/p/Tokyo_Summit_Sessions_of_Interest. Community members are encouraged to add notes to the etherpad.
  • Design Summit & OPNFV Summit: Ray noted that there will be whiteboards at the design summit so that project teams can update their breakout sessions real time. Also the latest schedule can be found at http://events.linuxfoundation.org/events/opnfv-summit/program/schedule. Debra is also planning to have 1-on-1 sessions with PTLs. Ray will also schedule a meeting room (plus coffee/breakfast) for the TSC meeting at 7am on Tuesday (Nov. 10th).
  • Brahmaputra artifact governance and expectations: There was a good discussion on different approaches. There is a view that some level of stability needs to be provided by upstream communities. Another possibility is to introduce "experimental" features that are not published in upstream communities. There was also a desire to allow OPNFV community to push ahead and publish their work in OPNFV releases. The consensus was to have further discussions on this topic during the design summit and Chris Price has the action item to schedule this session.
  • Upcoming OPNFV Board meeting : Chris outlined TSC report out topics for the upcoming board meeting on November 13th.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-11-03-14.59.html

October 26, 2015

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • Overview of the Developer Collaboration Budget Items for Oct'15 - Sep'16 - Ray
    • Focus on on-boarding and community enablement. (I know it's not a real word)
    • Additional Items?
  • Design summit planning and desires
  • OpenStack activities and intentions for the week
  • AoB

Minutes

  • Previous minutes approved
  • Overview of the Developer Collaboration Budget Items for Oct'15 - Sep'16: Ray discussed the proposed budget items that are pending Board approval. Chris Price added that additional infrastructure for the LF Lab is not included in the budget and will be handled as a separate budget request to the board on an as needed basis. The community is also encouraged to provide feedback on the proposed on-boarding topics
  • Design Summit: Day 1 will start with plenary sessions and then tutorials/breakouts in the afternoon. There will be more breakouts/unconference sessions in Day 2.
  • Application of security patches: The CI team will propose an update to the stable branch procedures around incorporating upstream security patches.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-10-26-07.58.html

October 20, 2015

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • TSC meeting times (PST) during Autumn - Ray
  • Committer removal - Frank/Chris
    • Acknowledge resignment of Arnaud Morin as committer on OpenSteak and Genesis (Arnaud's resignment message)
    • Committer removal processes - Chris
    • Committer removal requests:
      • Octopus committer removal request: e-mail.
        • Shall the TSC remove Palani Chinnakannan (pals@cisco.com) as committer on the octopus project? (+1, 0, -1)
        • Shall the TSC remove Sudha Kumari (sudha.kumari@hp.com) as committer on the octopus project? (+1, 0, -1)
  • OpenStack Summit + Quarterly/Annual Awards- Ray
  • Pharos lab update - Trevor
    • Discussion on pre-requisites for using community labs for the purpose of parallelizing Brahmaputra release activities.
  • Overview of the Developer Collaboration Budget Items for Oct'15 - Sep'16 - Ray
  • AoB

Minutes

  • Previous minutes approved
  • TSC meeting times: Just a reminder that Daylight Savings Time ends in Europe next week and in N. America the following week. This will shift the TSC meeting times an hour later for many countries in Asia starting on November 3rd.
  • Committer removal:
    • There was a good discussion on how to deal with inactive committers and there was a consensus on the following text "An approval by the project's committers to remove the committer in question from the project, i.e. no objections." Via IRC vote, the TSC approved the committer removal process.
    • Committer removal requests for Octopus: The TSC agreed to removing Palani Chinnakannan from the committer list. Sudha Kumari is interested in continuing as Octopus as committer.
  • OpenStack/Awards update:
    • See OPNFV activities at OpenStack-Tokyo at https://etherpad.opnfv.org/p/OpenStackTokyo
    • A reminder that Quarterly Awards nomination closes tomorrow and there'll be a separate nomination for the Annual Awards. For the annual awards, eligible voters will be limited to opnfv-tech-discuss subscribers with a Linux Foundation ID.
  • Pharos lab updates: Trevor discussed pre-requisites for using community labs for the purpose of parallelizing Brahmaputra release activities. All project leads have the action item to provide relevant information for the Brahmaputra release to the Pharos team. Relevant wiki pages are:

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-10-20-13.56.html

October 13, 2015

Agenda

Minutes

  • Previous minutes approved
  • MEF Hackathon at GEN15 conference: James Kim (CableLabs) presented the MEF LSO Hackthon (Nov. 16-18 in Dallas). Code developed during the hackthon will be contributed to OPNFV & OpenDaylight. Registration information is available at http://www.cvent.com/events/lso-hackathon/event-summary-a2385ae659154b37a48da813d8a561f5.aspx
  • OpenSAF introduction and discussion: Jonas Arndt (HP) gave an overview of OpenSAF. Jonas noted that OpenSAF looked at use cases such as HA for NFVs and HA as a Service. There is also a plan to move from LGPL 2.1 to Apache 2.0 licensing. Companies currently involved in OpenSAF are HP, Ericsson, Oracle, etc. Jonas is proposing to bring OpenSAF under OPNFV (in addition to proposing projects with OPNFV). There was a consensus to continue the discussion on the mailing list and Chris Price took the action item to provide an update to the OPNFV Board (esp. on potential issues with scope, location of code, etc.)
  • Demo theater & design summit update: Community members are encouraged to sign up for project overview sessions at the demo theater etherpad page. Design Summit will have parallel tracks for tutorials and project breakouts, and you can add session proposals on the design summit etherpad. For both the demo theater & design summit, the deadline to sign up is October 23rd. Ray took an action item to send out a sample schedule for the design summit so people can gauge how many additional sessions can be accommodated.
  • Community election process: There was consensus on the overall process, and a good discussion on the publication of results. For the next few elections, there was a consensus to publish the results on opnfv-tech-discuss mailing list if all nominees agree. The TSC voted to approve the new community election process via IRC vote.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-10-13-13.57.html

October 6, 2015

Agenda

Minutes

  • Previous minutes approved
  • Strategic Planning Committee: Chris Donley discussed the need to address OPNFV end-users in Brahmaputra with a theme of "lab-ready". The mapping of identified capabilities vs. projects participating in Brahmaputra was also presented. Chris Donley also mentioned that the release cadence and iterative development was viewed as more important than feature completeness. The Strategic Planning Committee (SPC) will be happy to facilitate community support for resource shortages. SPC will also look into 2 release out moving forward and also try to return to the TSC with feedback earlier in the planning cycle (e.g. prior to Milestone C).
  • TSC update to the board: Chris summarized the TSC update to the board, which included community elections, project lifecycle updates, Brahmaputra milestone C, and Pharos update.
  • Community Lab readiness for Brahmaputra: There was a good discussion on the desire to have additional servers for the CI team in the LF lab and agreement to request additional funding to the board. There was also a discussion on the need to have more Pharos labs available to the community. The Pharos team have the action item to identify labs that intend to participate in Brahmaputra and be part of the CI pipeline.
  • OPNFV release artifacts: There was a voting on the preference for release artifacts, and the Genesis team will take the TSC members' preference into consideration. The "Install script per installer" received the most votes.
  • Release maintenance: There was also a vote on the preference for release maintenance, and "Latest and stable branch maintenance" received the most votes.
  • Wiki tool decision: Ray noted that the preference from the community was to migrate to Confluence. After a vote, the TSC agreed to migrate the wiki tool to Confluence.
  • OpenStack Tokyo: OPNFV' activities are listed at https://etherpad.opnfv.org/p/OpenStackTokyo and community members are encouraged to volunteer at the OPNFV booth. Ray will also follow-up with TSC members if re-scheduling the TSC call that week to Monday at 17:00 local time will work.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-10-06-13.59.html

September 29, 2015

Agenda

Minutes

  • Previous minutes approved
  • Release artifacts: Frank summarized options discussed to-date on what OPNFV releases. The concern is that the current approach requires a significant effort. Discussion ensued and Chris Price took an action item to start the email vote on the mailing list for the TSC members to state their preference.
  • Arno SR1 status: Frank noted that there are issues remaining with the CI pipeline, so SR1 will not be ready today. The TSC agreed to the delay of SR1 to enhance stability.
  • Brahmaputra milestone C: Debra reports that as of the TSC call, 38 projects have reported for Brahmaputra. No projects are reporting Red, while some projects have concerns around resourcing or dependencies (but are non-blocking). The TSC agreed to pass Milestone C for Brahmaputra.
  • Election processes and improvement opportunities: Dave Neary presented some of the feedback received after our previous round of community voting. Dave suggested "Active Technical Contributor" (vs. committer) for board representation and discussion ensued on the definition of Active Technical Contributor. Dave took and action item to lead a community discussion on what an Active Technical Contributor means and propose a concrete proposal for running future elections for the TSC to vote on next week.
  • Upcoming "meet-ups"
    • SDN/OpenFlow World Congress (Düsseldorf): Heather proposed a community dinner among mini-summit participants in lieu of a larger meet-up.
  • Wiki tool: Ray took an action item to request a vote on the TSC mailing list for the community's opinion on migrating to Confluence.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-09-29-13.58.html

September 22, 2015

Agenda

  • Previous meeting minutes
  • Agenda Bashing
  • Report on the OPNFV Board meeting - Chris
  • Bylaw amendment discussion -Ildiko
  • Election processes and improvement opportunities - Chris
  • Jira training provided and costs - Ray
  • Brahmaputra update - Debra
    • Milestone C readiness & Jira update
    • Milestone C project reporting process
    • Milestone C TSC decision process - chris
  • OPNFV release artifacts discussion - Frank
    • Update including WiKi & relevant threads

Minutes

  • No objections/comments on previous meeting minutes
  • Report on the OPNFV Board meeting: Chris gave a summary of the OPNFV Board meeting on September 14th including the report out from the Strategic Planning Committee
  • Bylaws amendment discussion: The proposal is to remove top-level projects and the nomination of a nominal number of community members to the TSC (vs. all top-level project leads). Via IRC vote, the TSC approved the changes and making the proposal to the board.
  • Election processes and improvement opportunities: Suggestions so far has been publicity of nomination statements, use of mailing lists, and publication of results. The discussion was postponed to next week.
  • Technical community budget overview: Ray made a proposal for the Year 2 budget (incl. "developer collaboration" for the technical community), and this still needs board approval. In addition to budget items we had in Year 1 (e.g. hackfests, awards, infrastructure maintenance, community analytics, etc.) newly proposed items are for ambassador/user group programs, training materials, internship program, etc. Training materials such as those on Jira that were recently developed and posted will be paid for from the proposed training budget. Ray took an action item to create a wiki page for the Developer Collaboration budget items.
  • Brahmaputra milestone C: Debra outlines that many projects are actively working with Jira, and work is on-going on solving tooling options. Debra will be opening IRC on Thursday to track project reporting on IRC for milestone C readiness and the IRC will remain open until Friday. The TSC will review milestone C and decide pass/no pass on milestone C during next week's TSC call

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-09-22-13.59.html

September 15, 2015

Agenda

Minutes

  • Ray Paik suggests to have minutes posted by 17:00 Pacific Time on Thursdays to allow for feedback/questions. Ray also proposes that if there is no feedback by the next TSC call, the minutes can be considered accepted. The TSC agreed that this proposal to allow 5 days for review prior to the minutes being accepted automatically is acceptable.
  • Bylaw amendment review: Ildiko summarized the community member discussion on amendment to the Project Lifecycle and the Bylaw. Major changes include removal of the top level project, adjustment of the bylaws to remove TSC seat s for top level project leads. Frank Brockners proposed that adding a cap to the size of the TSC may be a good idea. Discussion ensued and consensus was that another call was needed for further discussions.
  • OPNFV release
    • Artifacts: Frank took an action item to provide a summary of our option for release artifacts in a wiki so that an informed decision can be made in a future TSC call.
    • Installer integration guidelines:
  • Elections for TSC Chair & Committer Board Member:
    • TSC Election closes at noon Pacific Time on September 15th
    • Committer Board Election
      • OPNFV Committers Sep-14-2015 Rev2: Updated version to include new IPv6 committers voted last week.
      • Ray notes that three nominations have been received and nomination statements and links for the vote will be sent out to all committers on September 16th. Voting will close at noon Pacific Time on September 23rd.
  • Project creation review (tentative)
    • Project: StorPerf - Storage Performance Benchmarking for NFVI: Edgar described that the project plans to create a stand alone performance testing solution for storage. Following the first phase the plan is to integrate the tool with qtip and yardstick projects. "storperf" name will also be used for Jira and Git. Project creation was approve via IRC vote.
  • OPNFV wiki tool: Ray summarized the results from the poll for wiki tool preferences. Confluence received the most votes (10), but there was a concern that the number of people voting was low (23) considering the size of the community. There was a consensus to get additional data on the number of active wiki contributors and conduct another poll on the wiki tool.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-09-15-13.59.html

September 8, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Managing the communities proliferation of project meetings: dneary & tnadeau
  • Upcoming OPNFV elections
    • TSC Chairperson nominations & next steps
    • Committer election, clarification for nominations & next steps
  • Community lab Pharos integration and CI processes report/discussion
  • OPNFV release, artifact discussion
  • OPNFV Support review and next steps
  • Project creation review:

Minutes

  • Upcoming Elections
    • TSC Chair: Received two nominations and voting will start on September 8th and will close at Noon Pacific Time on September 15th.
    • Committer Board: Propose postponing the election process by a week so that PTL can make updates to the committers lists.
  • Managing the communities proliferation of project meetings: Dave Neary/Tom Nadeau notes that real time meetings are not a productive method to apply in open source projects and would like to see more discussions take place asynchronously. Discussion ensued on universal access to IRC, desire for real-time meetings for early stage projects, need to encourage PTLs to have IRC-based meetings, etc.
  • Community lab Pharos integration and CI processes report/discussion: Uli notes that activity is ongoing around the use of Pharos labs for octopus, but there's a need for community lab representatives in Pharos meetings. Trevor also added that he would like to see more direction around pharos planning and lab federation. Uli requests all TSC members who have labs involved in Pharos should ensure the labs are represented in Pharos meetings.
  • OPNFV Support review and next steps: Chris Price noted that most requests/questions on opnfv-users mailing lists have been answered by 2 people within a day. However, there is a concern that this is probably not scalable.
  • Project creation review:
    • ARM Band: Bob notes that the goal of ARMBand is to integrate and support the use of ARM in the Brahmaputra release. The project has identified a number of OPNFV project they will need to work with including CI & deploy projects, integration of ARM-based labs into Pharos, etc. The project creation was approved via IRC vote.
    • Pinpoint: Adi explains that the project will focus on fault correlation on the OPNFV platform. There is also an invitation for community members to join the project. The project creation was approved via IRC vote.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-09-08-13.59.html

September 1, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Upcoming OPNFV elections
    • TSC Chairperson elections
    • Committer election to the board
    • Board elections
  • OPNFV design summit in November
    • overview of tracks and activities
    • CFP and programming of the design tracks
  • TSC 2016 Events Schedule
  • OPNFV release, artifact discussion
  • postponed OPNFV Support review and next steps
  • Weekly Brahmaputra release project meeting outline
  • Project creation review:

Minutes

  • Upcoming OPNFV elections: First election is for the TSC chair that is open to TSC members. Second is the Committer Board elections that is open to all committers in OPNFV. Nominations open for both elections starting today. Chris Price took the action item to add the topic of Committer Board elections to Thursday's Tech Discuss call.
  • OPNFV Design Summit: OPNFV Summit planning is done and speakers have been notified. Some talks were moved to the Design Summit which is in early stages now. See Design Summit Etherpad. OpenDataPlane & OpenDaylight will also co-locate their hackfests during the OPNFV Design Summit.
  • TSC 2016 Events Schedule; Heather discussed the tentative plans for 2016 that is captured at https://wiki.opnfv.org/start?&
  • Linux Foundation Data Center: Another router is needed (~$US 1,500) so additional vlans can be added without downtime. The TSC approved the purchase via IRC vote.
  • Weekly Brahmaputra release project meeting: Debra will run a weekly meeting following the TSC call on Tuesdays.
  • Project creation review:
    • SDN distributed routing and VPN: The project intends to address extending VPN's in the datacenter. The project will be done in collaboration with the related bgpvpn project in OpenStack and supported implementations in SDN controllers to make sure that the functionality can be integrated on the OPNFV reference platform for the Brahmaputra release and onwards. The committer list needs to be updated for the project. The project creation was approved via IRC vote.
    • Controller Performance Testing: There is a need to establish a project that performs performance testing of controllers in real hardware deployments for SDN controllers. There will be participation from the upstream ODL performance testing project, and hopes to work with other SDN controller teams. The project creation was approved via IRC vote.
    • dovetail Project: The project will work under the guidance of the OPNFV C&C Committee. The project creation was approved via IRC vote.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-09-01-13.59.html

August 25, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • OPNFV Event overview: Heather
    • mini-summit / meet-up - Dusseldorf
    • OpenStack / IETF update
    • OPNFV Summit update
  • postponed: OPNFV Support review and next steps: Chris
  • postponed: OPNFV release, artifact discussion & decision: Chris
  • Weekly Brahmaputra release project meeting: Tuesday 8:00am - 9:00am Pacific Time (15:00-16:00 UTC): Frank
  • Project creation review:

Minutes

  • Previous minutes approved
  • OPNFV events overview:
    • SDN OpenFlow World Congress: CFP running for the mini-Summit. Also exploring technical community meeting in Düsseldorf and will need local people's help with this.
    • OpenStack Tokyo: No OPNFV Day due to space constraints. Exploring a community dinner plus ~1/2 day meeting. Heather will create an Etherpad page to coordinate the "meet-up"
      • There is also an IETF hackfest on the weekend after the OpenStack Summit
    • OPNFV Summit
      • Currently reviewing CFP submissions: There were 131 submissions and expect ~25% acceptance rate. There may be some combining of topics and also planning on a "demo theatre" area for project-focused sessions
  • Weekly Brahmaputra release project meeting: Frank presented the idea to use the 1 hour after the TSC call for Brahmaputra release planning. This means that the Technical Community call will remain on Thursdays.
  • Project creation review:
    • PolicyTest: The project defines system-level tests which exercise network policy scripts. Focus is on infrastructure policy and not orchestration. The project creation was approved via IRC vote.

MeetBot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-08-25-14.00.html

August 18, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • OPNFV Arno SR1 date setting: Frank
  • OPNFV Brahmaputra Release
    • Scenario discussion: Chris/Debra
    • Decision on Brahmaputra date: TSC
  • OPNFV release, stable support discussion & decision: Chris
  • OPNFV release, artifact discussion & decision: Chris
  • Project creation review:

Minutes

  • OPNFV Arno SR1 date setting: Frank presented the Arno SR1 planning information captured in the OPNFV Arno SR1 page. The target release date will be September 29th with code freeze on the 15th. There was a discussion that the list of bugs will captured in release documentation (plus there is also a Jira list). The SR1 plan was approved by the TSC via IRC vote.
  • Brahmaputra release: There was a good discussion on two release date options of Nov’15 or Feb’16. The Feb’16 release will likely include ODL-Li and OpenStack-Liberty. Plus with a 5-month offset with OpenStack, will likely be working with a more stable version of OpenStack. Frank points out that a November release would be OpenStack-Kilo & ODL-Li. Chris Price also added that even with the Feb'16 release, year-end holidays mean 4 effective months from the Liberty release to Feb'16. The TSC voted for the Feb'16 release of Brahmaputra via IRC.
  • OPNFV release, stable support discussion & decision: Inconclusive discussion ensued on the topic, outlining the challenges of maintaining a release as compared to supporting consumers of OPNFV. Chris will raise the topic on the mailing list.
  • OPNFV release, artifact discussion & decision: Dave Neary noted that producing a release ISO was difficult in Arno and will be further complicated in Brahmaputra with multiple installers and component choices. Dave Neary will raise the topic on the mailing lists.
  • Project creation review:
    • Edge NFV: James outlines that the project intends to enable the utilization of edge compute capability in the OPNFV infrastructure, and the focus of EdgeNFV project is on the compute node. James has also been in communications with the LSO team and does not foresee conflicts between EdgeNFV & LSO projects. The project creation was approved via the IRC vote.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-08-18-13.58.html

August 11, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • OPNFV Project classification discussion: Ildiko
  • OPNFV Support review and next steps: Chris
  • OPNFV Brahmaputra Release discussion
    • Upstream release strategy
    • OPNFV Packaging discussion
    • Bramaputra release process and target release date
      • Report and discussion
      • Decision
  • Project creation review (tentative):

Minutes

  • Previous minutes approved
  • OPNFV Project classification discussion: Ildiko led a discussion on a proposal to combine the project types in the OPNFV project lifecycle document into a single project type. Projects would include needed combination of documentation, development, needed integration and testing and is reflective of the way the projects are working in OPNFV today. Ildiko also proposes re-classification of project types to; Continuous Build and Integration, Continuous Deployment and Testing & New Requirements and Features. There is also no need for a "top-level" project. TSC agrees to continue development of these proposals and there will be a community activity to revise documents such as Project Lifecycle, TSC Policy, Bylaws, etc. and bring to the TSC for review at a later date.
  • OPNFV Brahmaputra Release discussion: Debra mentions that based on feedback received so far, there is limited dependency on OpenStack Liberty which makes a December release a viable (with OpenStack Kilo). Discussion ensued if the community is comfortable with being “behind” on OpenStack release if we stay with June/December cadence (installer support & testing will likely require ~2 months post OpenStack release). Debra also shared the Brahmaputra release page (Releases Brahmaputra Release Plan) with the definition of the release theme "Lab Readiness". A suggestion was made to agree on dates for Milestones A/B/C next week.
  • Project creation review:
    • Project Name: Genesis: Frank noted that the genesis project intends to work across the installer projects to create a common set of requirements for the installers to comply to during the release. The project will also work with component teams to facilitate the integration of new components into the installers. Frank also added that governance details are still in draft and will evolve. The project creation was approved via IRC vote.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-08-11-14.00.html

August 4, 2015

Agenda

Minutes

  • Previous minutes approved
  • Joint Board-TSC meeting report out: agenda covered were (1) C&C Committee report out (2) Strategic Planning committee report out (3) Brahmaputra release planning (4) resource needs
  • Open Daylight Summit & OPNFV Hackfest report out: The hackfest included an awards, a panel with key OpenDaylight developers, and a session with ETSI NFV ISG Thursday morning. The rest of the hackfest was dedicated to tracks with good break-out sessions on Thursday afternoon and Friday.
  • Brahmaputra planning read-out: Debra will set up 2 weekly calls (EMEA & APAC timezones friendly) with project leaders to work through Brahmaputra planning and activity. Debra will also post the Brahmaputra planning presentation on the wiki
  • TSC meeting length: Based on votes from TSC members, the consensus is to reduce the TSC meeting length to 1 hour. The TSC agreed to reduce the meeting length to an hour starting in 2 weeks.
  • Project creation reviews:
    • OpenContrail Virtual Networking for OPNFV: Stuart Mackie (Juniper) described the use of the OpenContrail controller and OVR to provide the networking component of the OPNFV platform. A suggestion was made to remove the versions from the upstream releases in the proposal. Project creation was approved via IRC vote.
    • OpenSteak Installer: Arnaud Morin (Orange) outlined the strategy for the installer is to keep it very simple and streamlined. The installer is based on ubuntu, relying only on upstream puppet modules and foreman. Project creation was approved via IRC vote.
  • AOB: A question was raised if there is a need to validate all deployments on the LF infrastructure for Brahmaputra. Chris Price took the action item to clarify the relation between the Brahmaputra release process and various labs.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-08-04-14.00.html

July 28, 2015

Agenda

Minutes

  • Meeting is shortened to 1 hour and will focus on project reviews.
  • Project creation review:
    • Project Proposals Bottlenecks: The project provides a framework for identifying coarse and fine-grained OPNFV system level performance including identification of performance bottlenecks. The project will work with Qtip and other performance-related OPNFV projects. The project creation was approved via IRC vote.
    • OpenSteak Installer: No one was available from the project team
    • Other two projects have not passed the 2 week review period.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-07-28-13.59.html

July 21, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Action item follow-up
    • Evolving project categories: Ildiko & Ray Nugent
    • New structure for TSC calls: Dave Lenrow
  • Release planning - status review: Debra
  • Joint Board-TSC meeting agenda (July 27th): Ray
  • Open Daylight Summit & OPNFV Hackfest: Ray
  • Project creation review (tentative):
    • Compass Based OPNFV Installer Project Proposal
    • Open vSwitch for NFV

Minutes

  • No objections raised on the minutes of the previous meeting, however no quorum for approval
  • Evolving project categories: Ildiko started discussion on the mailing list and discussion on requirements & development projects is planned during the hackfest.
  • Release planning: Debra discussed projects for Brahmaputra that we will not release without/working plan/at risk/outside of plan. Debra will post an editable document on the wiki for feedback.
  • Joint Board-TSC meeting agenda: Ray presented the agenda for the meeting on the 27th and they are C&C committee report out, strategic goals for OPNFV, Brahmaputra planning, resource needs/gaps. The meeting is only for board & TSC members (or named alternates)
  • Open Daylight Summit & OPNFV Hackfest: Still looking for volunteers for the OPNFV Kiosk. Please sign-up at https://etherpad.opnfv.org/p/OPNFV_Kiosk_at_ODL_Summit. The latest agenda for the hackfest can be found at https://etherpad.opnfv.org/p/OPNFV_at_ODL. A couple of items are still TBD so some of the sessions may shift but will be sorted out during the hackfest.
  • Project creation review (tentative):
    • Compass Based OPNFV Installer Project Proposal: Weidong (Huawei) presented the proposal. A suggestion was made to update the list of committers. Also, when asked if there's a dependency on the new Genesis project, Weidong responded that their intention is to be part of Genesis and will reflect that on the wiki. The project creation was approved via IRC vote.
    • Open vSwitch for NFV: Mark (Intel) presented the proposal and noted that there's no intention to fork OVS. It is an upstream OVS project initially focused on enabling kernel and user space OVS deployments in the OPNFV platform. The project creation was approved via IRC vote.
  • New structure for TSC calls: Currently the TSC meeting is 2 hours long with a mixture of informational discussions and decision making. Proposal was to shorten to 1hr and focus on decision making. Ray will send out a SurveyMonkey poll to gauge TSC members' preference.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-07-21-14.02.html

July 14, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Action Item follow-up
    • Requirements projects development process: Ildiko, Uli
  • Request for formal approval to allow CI/CD Pipeline to support script and ISO deploy methods.
  • Support for OPNFV hardware @LF data center: Trevor/Ray
  • Quarterly Awards: Ray
  • Project creation review (tentative)
  • AOB

Minutes

  • Previous minutes approved
  • Requirements project development process: Ildiko noted that requirements projects should have end-to-end coverage from use cases to implementation. There will be a breakout session at the upcoming Hackfest and Ildiko will look for new requirements projects to test out the new approach being discussed. The current proposal includes (1) Evolution of the current project categories (2) Process for requirements projects, but further discussions should focus on (2). Ray Nugent & Ildiko took the action item to start a separate discussion on evolving project categories.
  • Request for a formal approval to allow CI/CD Pipeline to support script and ISO deploy methods: This was what was done for Arno, but it is too early to decide what the packaging options would be for Brahmaputra.
  • Support for OPNFV hardware @LF data center: LF support is limited to bare metal hardware support (cabling, power, network connectivity, etc.) and theres a need for additional infrastructure support from the community. More information available at Linux Foundation Infrastructure Support Process
  • Quarterly awards: Send your nominations to Ray Paik by Noon Pacific Time on July 15th. Ray will send email to TSC members for voting.
  • Proposals to split the current TSC calls to 1 hour of TSC (for decision making) plus 1 hour of technical discussions. Dave Lenrow took the action item to bring this discussion to the mailing list.
  • Project creation review:
    • Apex: This is a continuation of the Foreman work that was done as part of BGS and will include fixes for Foreman for Arno SR1 and a new installer (RDO manager) for Brahmaputra. Contact Tim Rozet if you're interested in being committer/contributor to the project. The project creation was approved via IRC vote.
    • Release Engineering: This is to formalize the already ongoing work for "OPNFV infrastructure" across various projects. releng repo exists already and was instrumental for Arno. The project creation was approved via IRC vote.
    • Connectivity Services LSO: This is requirements project for API on OpenDaylight controller to drive MetroEthernet Services. ODL is just the initial focus of the effort and API could also apply to other controllers. There was a discussion that this may be a good project to test the new approach for requirements projects and Ildiko will contact Kevin @CableLabs. The project creation was approved via IRC vote.

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-07-14-14.00.html

July 7, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Action Item follow-up
    • Requirements projects development process: Ildiko, Uli
    • Pharos plans: Trevor
  • Test strategy overview - Trevor
  • Volunteers for OPNFV Kiosk @OpenDaylight Summit: Heather/Ray
  • Quarterly Awards: Ray
  • Project creation review (tentative)
  • AOB

Minutes

  • Action Item follow-up
    • Requirements projects development process: Vacation period is making it difficult to gather inputs. There is a session planned at the upcoming hackfest
  • Test strategy overview: Trevor discussed the current set of testing and related projects that can be found at Testing page. The page includes information related to coverage of component testing, platform functional testing, and performance testing, etc. Tables listed under “Test Category” show areas where test coverage is lacking. Test & Releases” table shows plans for the Brahmaputra release. Morgan added that description of tools for testing will be developed (esp. for new projects). Also, Functest demo has been recorded and and will be posted on the OPNFV channel by Brandon.
  • Pharos overview & plans: Trevor explains that Brahmaputra plans for Pharos are still WIP (e.g. specifications, compliance checklists, dashboards, etc.). Trevor will post his presentation on the wiki.
  • OPNFV Kiosk at the OpenDaylight Summit: We want to have the booth staffed by community members. Ray will setup an Etherpad page for people to sign-up for 2 hour shifts. [Etherpad is now available at https://etherpad.opnfv.org/p/OPNFV_Kiosk_at_ODL_Summit] If we can not put together a demo in time for the ODL Summit, this will be an informational booth with collaterals.
  • Quarterly awards: Send your nominations to Ray. Award winners will be voted by the TSC (e.g. SurveyMonkey). More information on OPNFV awards can be found at http://lists.opnfv.org/pipermail/opnfv-tsc/2015-April/000709.html
  • Project creation review:

June 30, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • OPNFV lab utilization email - Chris
  • Stable Release proposal - Uli
  • Release 2 planning: Debra
  • Agenda for the TSC & Board joint meeting on July 27th @CableLabs: Chris Price
    • C&C Committee report - Wenjing
    • Release 2 planning - Debra
    • Resource needs/gaps - TSC
    • Strategic goals/vision for OPNFV - All
  • OPNFV Kiosk @OpenDaylight Summit - Heather
  • OpenStack Summit in Tokyo - Heather
  • Action Item follow-up
    • Requirements projects development process: Uli
    • Pharos plans: Trevor
  • Project creation review:
  • AOB

Minutes

  • Previous minutes approved
  • OPNFV Lab utilizations: Chris discussed a proposal to configure one of the PODs to provide an infrastructure for continuous bare-metal deploy and test with the 2nd POD providing infrastructure for various jobs including build, test & virtual deploys when we work with pushing patches and merges. The TSC agreed to have the octopus and pharos teams reconfigure the LF lab to provide build infrastructure on one of the POD's The Pharos team has the action item to provide lab configuration accordingly. The Octopus team has the action item to enable CI pipeline to utilize one build POD and one deploy POD.
  • Arno stable release proposal: Uli described the approach for working with the Arno stable release branch and asked for feedback to be provided directly to Uli so that he can incorporate them on Stable release wiki page. TSC agreed to use the documented stable release plan for the Arno stable branch. Uli will also migrate the wiki page to RST format in the Octopus repo.
  • Release 2 planning: Debra discussed Brahmaputra planning activities. For milestones & timelines, Debra explained that once milestones A & B are set, subsequent milestones can be defined. Also, inclusion in the Brahmaputra release is open to any projects until Milestone C. The was also a suggestion that further dependencies such as deployment tools should be included in the upstream schedule slide.
  • Agenda for the joint board & TSC meeting on July 27th: Proposed agenda was reviewed without comment
  • OPNFV kiosk @OpenDaylight Summit: OPNFV will have a kiosk at the ODL summit and need community volunteers to help staff the kiosk.
  • OpenStack Summit Tokyo: Heather discussed that we have another opportunity for an OPNFV Day at the upcoming OpenStack Summit. The OPNFV Day maybe on Tuesday or Wednesday this time.
  • Project creation review for kvm for nfv: Jun Nakajima presented the project proposal. There was a suggestion to select a single project category. When asked about licensing of KVM vs. OPNFV, Jun responded that the goal is to submit patches in the KVM repo. The project creation was approved via IRC vote.

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-06-30-13.59.html

June 23, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Release 2 naming: Ray
  • Bitgeria contributor analytic tool: Ray
  • OPNFV Hackfest planning (July 30-31): Ray
  • CFP for the OPNFV summit: Heather
  • Committer roles & forge author identity: Chris Price
  • Release planning: Debra
  • TSC & Board joint meeting July 27th Santa Clara: Chris Price
  • Action Item follow-up
    • Requirements projects development process: Uli
    • Pharos plans: Trevor
  • Project creation review:
  • AOB

Minutes

  • Previous minutes approved
  • Release 2 Naming: The winner is Brahmaputra. Other contenders were Bourne, Bode, Beam, and Beppu.
  • Hackfest: Planning started with discussion among planning volunteers. Suggestion was made to involve Phil Robb & Colin Dixon from ODL to coordinate topics. Also Thinh Nguyenphu (ETSI NFV EVE WG chair) made a suggestion to reach out to the TST to explore collaboration opportunities as ETSI also has a meeting during the same week in San Jose.
  • Bitergia tool: Ray discussed that Bitergia came highly recommended from OpenStack & CloudFoundry and can track developer contributions in code, reviews, wiki, etc. There was a discussion on privacy concerns that LF team can investigate.
  • CFP for the OPNFV Summit: Heather reminded the community that the Call for Papers (http://events.linuxfoundation.org/events/opnfv-summit/program/cfp) is open. The CFP will close in early August. Should also encourage upstream communities to participate.
  • Committer roles and forge author identity: The purpose of allowing forge is to help project teams be more agile (e.g. when author is away, for very simple fixes, etc.). The TSC agrees to allow forge author identities on respositories for 3 months and then re-evaluate. Aric has the action item to enable this in repo's
  • Action item follow-up:
    • Requirements project development process: Uli reports that the work is ongoing, but nothing new to report yet
    • Pharos plans: Trevor reports that meetings for LF infrastructure support & testing strategy are being scheduled
  • Security group report: Luke discussed the idea of the idea of performing a security audit of a deployed Arno platform. The activity will help identify any issues and establish some best practices for OPNFV. In addition, this will allow the team to do a dry run of the vulnerability management process being defined by the security group. Will need a lab and some volunteers for the audit. Luke has the action item to create a proposal for the audit activity as a project.
  • Project creation review for OpenContrail Quickstart: Stuart Mackie presented the proposal and noted that this is a start-up project to help get hands-on experience and create visibility. There was a good discussion on why a project is needed for this effort vs. creating a wiki page. Stuart agreed that he will create a wiki page for the work and make it available as a developer resource (vs. creating a project).

June 16, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Arno marketing update: Brandon
  • OPNFV@ONS report: Heather
  • OPNFV Hackfest (July 30-31): Ray
  • TSC & Board joint meeting July 27th Santa Clara.
  • Action Item follow-up
    • Requirements projects development process: Uli
    • Pharos plans: Trevor
  • Arno Retrospective overview: Heather/Ray/Debra
  • Stable release discussion
    • Stable release strategy and allowed content
  • Progression of BGS/Genesis
  • Project creation review:
  • AOB

Minutes

  • Previous minutes approved
  • Arno marketing update: Brandon provided update on site statistics since Arno launch. 300% increase in opnfv.org traffic. The Arno download page viewed 3800 times since launch with 700 ISO downloads (split evenly between ISO images) plus 3400 downloads from documentation links.
  • OPNFV @ONS: Heather discussed the tutorial and dev track on Monday. Two panels are also planned for Thursday.
  • OPNFV hackfesk @OpenDaylight Dev Forum: Our hackfest will be a track at the OpenDaylight Dev Forum on July 30-13 in Santa Clara. Registration details can be found at Hackfest Etherpad. Ray will also send an email to the lists to start a planning committee.
  • Joint Board/TSC face-to-face meeting: Session planned in the afternoon of July 27th (Monday) at CableLabs in Sunnyvale, CA. Chris has the action item to send an email to the TSC mailing list to start discussing potential topics for the joint board/TSC meeting.
  • Action item follow-up
    • Requirements projects development process: Uli scheduled a meeting on June 17th on this topic
    • Pharos plans: Trevor discussed that the team is in the process of formulating a vision for Pharos for release 2 and beyond. Infrastructure management and tooling for managing the deploy environment are areas that need further development. Trevor will schedule a separate Pharos meeting for this topic.
  • Arno retrospective: Material and notes available at Arno Retrospective wiki page.
  • Stable release: There was a good discussion on if there is a need & resource available to do a stable release. Consensus among the TSC is that a stable release should not include stepping a release version of our component pieces (e.g. stable release should not update OpenStack from Juno to Kilo)
  • Progression of BGS/Genesis: Frank followed-up on his email (http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2015-June/003094.html) that outlined potential evolution of BGS. Frank mentioned that continuous integration and common user experience are some of the key goals. When discussing project structure, Frank added that the contribution will be open to anyone but he was trying to have a limited number of committers.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-06-16-13.55.html

June 9, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • AP Follow up:
    • Ray also has the action item to create a "opnfv-users"mailing list for the community-based support.
      • List created, release doc ready to be patched with correct address
    • Uli has the action item to recruit a team from the requirements project community to further develop/update the requirement projects development process.
    • Chris Price took the action item to start the discussion on the support structure on mailing lists.
      • Thread started, TSC consensus indicated structure would form as activity emerged
    • Dave Neary has the action item to provide a release map for upstream communities as input in to the B-Release planning.
    • Pharos team to present lab definitions and tracking in a future TSC meeting.
  • Project activities (per project):
    • Refresh of committer and contributor lists for projects
    • Arno lessons learnt
    • Jira clean-up and R2 planning
  • Toolchain/workflow:
    • Documentation management in gerrit DOCS-33
    • Branching and patching arno/stable OCTO-xx
  • Scheduling the Arno retrospective session: Chris Price/Heather
    • Community and collaboration
    • Project and planning
    • Infrastructure and tools
  • Release 2 planning discussion: Debra Scott
  • Project creation review:
  • AOB

Minutes

  • Previous Minutes approved
  • AP follow-up
    • opnfv-users mailing list will be populated with everyone on the TSC mailing list
    • Uli will organize the meeting to discuss the requirements project development process.
    • Trevor will present the Pharos plans to the TSC
  • Project activities
    • Refreshing committer/contributor lists: Aric mentioned that he has the list of all contributors and will notify the project leads on who have been granted access.
  • Toolchain/workflow
    • Chris made a request for the community to help improve the documentation process in DOCS-33. Also a reminder that anyone can comment on Jenkins tickets.
    • Branching and patching arno/stable OCTO-xx: There was a good discussion on where bugs should be solved for arno/stable (in main or in the maintenance branch) and if any features should be added to arno/stable. Uli & the Octopus team has the action item to define the intention for our maintenance branch arno/stable and our methods for working with it
  • Arno retrospective session: Consensus to have the session on June 11th 6-7:30 am Pacific Time. Ray created an Etherpad page at https://etherpad.opnfv.org/p/Arno_retrospective
  • Release 2 planning
    • Debra shared her learnings/observations so far and mentioned that she heard a lot of feedback around scope creep, roles & responsibilities, communication, and dependencies. This creates a need for detailed scheduling (incl. project dependencies) and a change management process. Debra also added that project plans should provide a method for prioritization of the features and activities in order to schedule our activities.
    • Debra is also looking for a plan for project guidance in Release 2 planning and will be reaching out to project leads for help.
  • Project creation review:

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-06-09-14.01.html

June 2, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Introducing Debra Scott (OPNFV Release Manager): Heather
  • Arno Project plans & tracking
    • Release activities - flag raising: All
    • Release process, labeling and artifact cutting: Uli
    • Arno landing page review: Brandon
    • Technical whitepaper: Chris
  • Arno support: Chris Price
  • WiKi structure & Layout
    • /projects
    • /developer
    • /community
    • /security
    • /documentation
    • /releases
  • Development process/project categories: Chris
  • OPNFV Release 2 "marquee feature" discussion
  • Release 2 planning
  • AOB

Minutes

  • Previous minutes approved
  • Introduction of Debra Scott: Debra is the release manager for OPNFV and will work with the community to establish our release processes and shepherd our projects through future OPNFV releases.
  • Arno project plans and tracking:
    • Documentation: Needs to be finalized tonight/tomorrow morning
    • BGS: Team is is working to address three remaining issues prior to the release
    • Functest: There have been discrepancies in executing testing when altering the platform. Morgan adds that all issues are known and able to be defined and documented.
    • Octopus: Prepared a release procedure to be reviewed
  • Release process, labeling and artifact
    • Release process is documented at OPNFV Process to prepare the release
    • Want to go through steps outlined in the wiki page above on Wednesday (June 3rd) in preparation for the release on Thursday. (Release PR is planned for 8am Eastern Time on June 4th)
    • TSC agrees to use arno.2015.1.0 as our release tag
    • TSC also agrees to use stable/arno as our stable branch
  • Arno support: Consensus that support offered for OPNFV is community-based support, with no sla's associated.
    • Ray also has the action item to create a "opnfv-users"mailing list for the community-based support.
    • Frank also noted that bugs are to be reported on Jira.
    • There was a good discussion on the need for a community manager to help with user support activities and wiki content management.
  • Development process/project categories: There was a good discussion on the need to review both development process & project categories. The consensus was to postpone this discussion after the Arno release.
  • Release 2 "marquee" features: Good discussion on theme/marquee features for release 2 and three suggestions were Policy, Service Function Chaining, and High Availability + Fault Management.
  • Release 2 planning

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-06-02-13.59.html

May 26, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • OpenStack summit activity summary: Heather
  • OPNFV Board meeting summary: Chris Price
  • Project Approvals - committer and contributor check only.
  • Requirements projects and next steps: Uli
  • Arno Project plans & tracking
    • Release tagging and maintenance structure
    • Release activities - flag raising
  • Release 2 planning
    • Working on the development process
    • Release dates and upstream dependencies
    • Topics to cover for Release 2 development
  • AOB

Minutes

  • Previous minutes approved
  • OpenStack Summit update: OPNFV Day & reception were both well attended on Day 1. Heather Kirksey/Chris Price/Jim Zemlin also led the OPNFV discussion at the OpenStack board meeting on May 17th.
  • OPNFV board meeting: Chris presented discussed some of the Arno learnings with the board but also mentioned that the technical community will have to do a formal post-mortem. The board will be having a discussion on major themes/features for Release 2 and will follow-up with an interactive discussion with the TSC on the topic.
  • Project Approvals - committer and contributor check only.
  • Requirements projects: Uli reports that requirements projects cannot be seen to be finished until the requirements are implemented, but this is not reflected in the Project Lifecycle document. Uli has the action item to recruit a team from the requirements project community to further develop/update the requirement projects development process. (Ildiko Vancsa, Bryan Sullivan, and Gerald Kunzmann volunteered to be on the team)
  • Arno project plans & tracking:
    • Release tagging & maintenance: There was a good discussion on if there's a need for a maintenance branch or if we want to do stable releases at all. Providing some stability to our consumers and standing behind our release is important for our credibility. There was an agreement on the need to support and potentially provide stable releases on the Arno release with a minimum maintenance effort. Chris Price took the action item to start the discussion on the support structure on mailing lists.
    • Flag raising: Morgan reported that the full testing sequence will likely contain some errors at Arno release however will be able to explain them.
  • Release 2/B-release planning: There was a discussion if OPNFV Release 2 can support OpenStack Liberty, and there was an agreement that TSC would like to accommodate OpenStack liberty in our B-release planning. In addition to OpenStack, ONOS, OpenContrail, ODL, Open vSwitch, and DPDK are other upstream communities we need to factor in for the next release. Dave Neary has the action item to provide a release map for upstream communities as input in to the B-Release planning. The community will review project release map of upstream communities prior to setting the date for the B-release.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-05-26-13.58.html

May 19, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • OPNFV Release Manager role & update
  • OPNFV Day @ OpenStack overview
  • OpenStack summit activity summary
  • Arno Project plans & tracking
    • Release readiness report
    • Release readiness discussion
  • Release 2 preparation and planning
    • Post-Arno evaluation and lessons learned session planning
    • Release 2 scope and activity discussions
  • OPNFV Board topics
  • Project Approvals (Tentative)
  • AOB

Minutes

  • Previous minutes approved
  • OPNFV Release Manager: Debra Scott has been hired as a release manager for OPNFV and will start on June 1st. She will start helping us with release 2 planning.
  • OpenStack: Heather reminded everyone that an email was sent out on Sunday (May 17th) with recommended sessions at the OpenStack Summit (http://lists.opnfv.org/pipermail/opnfv-tsc/2015-May/000843.html)
  • Arno project plans and tracking:
    • opnfvdocs: Chris updates that a lot of people are still heads down on Arno work and need to find time to edit documentation. Chris again asks for community to help with reviewing documents (Arno Release Documentation)
    • Octopus: Nothing new to report. In a ready state.
    • Pharos: In a ready state apart from needing to complete the documentation.
    • BGS: Status available at https://wiki.opnfv.org/meetings/bgs?&. Auto-deploy on both PODs are working, but still need bootable ISO. See test cases 1-3 in the earlier link that still needs work.
    • The TSC has agreed (via IRC vote) to set a target release date of June 4th for the Arno release, the Arno team has approximately 2 weeks to complete release activity.
  • Release 2 preparation & planning: There was a discussion on having a post-mortem session after the Arno release. Chris also noted that simultaneous release process needs to be defined and will be a learning process for the community. Dave Neary made a suggestion of identifying a marquee features for release 2 would be helpful (e.g. service function chaining, performance/functional testing, carrier-grade, etc.).
  • TSC update to the Board: Chris discussed that a couple of topics that will be raised to the board include
    • Need for updates development process
    • Project definitions and classification
  • Project Approvals
    • inspector: There was a discussion that the list of committers/contributors need to be updated/completed before TSC votes on project approval. Juan has the action item update the committer and contributor list and the project proposal will come back for vote only next week.
    • Juju OPNFV Infrastructure Deployer: Similar to the Inspector project, Artur has the action item to update the committer/contributor list and JOID will come back next week for a vote only. There was also a good discussion on how BGS will evolve post-Arno.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-05-19-13.54.html

May 12, 2015

Agenda

Minutes

  • Previous minutes approved.
  • TSC meeting next week: Consensus to keep the meeting during OpenStack Summit. If anyone can secure a room during the TSC call, please let Chris Price know.
  • Arno project plan & tracking:
    • BGS: Deployments & testing on-going on both POD's @LF. Troubleshooting on functional testing in progress.
    • Octopus: Automatic deployment continuing on POD2, but not yet integrated on POD1. Tests can be triggered automatically, but not completely ready.
    • Functest: Errors being worked through and the number of failed tests are going down on a daily basis.
    • Pharos: Pharos spec is being defined in the release documentation and working to make these documentations accurate and to improve the quality of the documentation.
    • Documentation: Release docs are being captured at Arno Release Documentation. Request to the community to review and provide feedback on documentation.
  • Requirements project document approvals and next steps: Uli presented the OPNFV project lifecycle and led the discussion on the process for requirements project documents. There was a consensus that a simultaneous release process needs to be established. Chris Price made a suggestion for requirements projects owners to review the current process and bring proposals to the TSC.
  • NFV World Congress report & OpenStack Summit: NFV World Congress was well attended and approximately 1/3 of attendees came through the OPNFV mini summit. The latest schedule for OPNFV Day is available at https://www.openstack.org/summit/vancouver-2015/schedule/
  • Project creation review:
    • Moon OPNFV Security Management System: Ruan He presented the proposal for Moon that use a realtime mechanism to mitigate the security risk with having a one hour trust window for a provided security token. The project creation was approved via the IRC vote.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-05-12-13.59.html

May 5, 2015

Agenda

Minutes

  • Arno Project plans & tracking:
    • Documentation making good progress. There was a consensus not to timestamp documentation as documentation would then be tied to a specific release. Octopus team also have the action item to add a lab integration documentation in the Arno release.
    • BGS: Work still in progress to move Fuel work from Ericsson lab to the LF lab. There was a discussion that in the LF Lab, we need auto-deploy to work, hooked up to Jenkins, and required Functest tests are passing. There are still uncertainties to make a decision on the Arno release date. Ray to setup another Release Readiness meeting on Thursday (May 7th).
  • WiKi content management: There was a discussion on the importance of maintaining wiki content for accuracy. Pharos team to present lab definitions and tracking in a future TSC meeting.
  • Update on OPNFV Day at the OpenStack Summit: All breakout sessions in the afternoon has been identified and the latest is available at https://etherpad.opnfv.org/p/Vancouver_OpenStack. This will also be posted on the OpenStack Summit webpage.
  • Project proposal & creation review checklist: Chris Price's reminder that the TSC voted against requiring proposal review in the Technical Community calls but encouraged people to take advantage of input at the Technical Community meeting. Chris/Bin/Ray has the action item to return to the TSC meeting with an updated proposal.
  • Requirements project document approvals and next steps: postponed to next week.
  • Project creation review:
    • Re-visit ONOS Framework (ONOSFW): Mike Young continued his presentation from last week. There was a suggestion for additional committers from other companies, and Daniel Smith (Ericsson) volunteered. The project creation was approved via the IRC vote.
    • OPNFV Service Function Chaining: Brady Johnson presented the proposal. This project will create a link between OpenDaylight and OPNFV, and one of the goals is to allow OpenDaylight to create Service Function Chains across OPNFV Network Functions. The project creation was approved via the IRC vote.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-05-05-14.02.html

April 28, 2015

Agenda

Minutes

  • Previous minutes approved
  • Uli suggests discussion on requirement projects document approval and further proceeding in the next TSC meeting
  • Arno project plans & tracking:
    • Pharos: Awaiting finalization/documentation of LF HW POD deployments. Current estimate is a "couple of days" of work to complete Arno work.
    • BGS: Good progress made to get things deployed on LF HW, but still work to be done.
    • Octopus: Documentation progressing. Automatic build working. Automatic deploy pending BGS work
    • Functest: Manual installs of tools (Rally, Robot) available. Documentation in progress. Rough estimate is a "couple of days" to have smoke tests available. vIMS still pending and not sure how much time is required to be completed.
    • Documentation: Lot of progress and team can help with converting proprietary file formats (e.g. MS Word). Suggestion was made to create an dashboard of what is required for the documentation project and Iben took the action item to create one on the wiki. Iben also took an action item to schedule a documentation happy hour" where people (esp. project leads) can meet on IRC and get their docs questions answered.
    • There was a consensus was that the community is still not able to define a more precise target release date for Arno.
  • Updating Section 7 of the TSC Charter: A consensus was reached on the following text. "For internal project decisions where no consensus can be reached, a majority vote among all Committers of the project via +1 voting should be used. A simple majority voting should be used for decisions within the TSC at which a quorum is present, unless otherwise required."
  • OPNFV Day @OpenStack Summit: There was a discussion on breakout sessions in the afternoon and a suggestion was made to limit to 2 parallel breakout sessions. Possible topics are IPv6, multisite, Doctor, SFC, VNFFG, etc. Dave Neary/Heather/Ray to schedule an IRC session to continue working on the agenda for OPNFV Day.
  • Project Approvals:
    • Project Proposal & Creation Review Checklist: Bin made a suggestion that the order of project review should be based on the "maturity" of proposals vs. when they were first submitted. This will be brought back to the TSC meeting next week after further discussions/feedback on the mailing list.
    • Yardstick: This project proposes a test framework, including test cases and test stimuli, to verify the infrastructure compliance when running VNF applications. The project creation was approved via IRC vote.
    • OPNFV Service Function Chaining: No one from the project team was available to present the proposal.
    • ONOS Framework (ONOSFW): The project addresses integrating an SDN controller of choice based on a target applications or use cases within the OPNFV defined NFVI and VIM framework. There was a good discussion on installers, build, etc. As time was running out, consensus was to continue the creation review discussion next week.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-04-28-13.59.html

April 23, 2015

Agenda

  • Arno Project plans & tracking
    • Release readiness report
    • Release readiness discussion

Minutes

  • The latest Arno tracking information can be found at Release Readiness for Arno: Status and Plan
  • The current estimate for release date is about 2-4 weeks from today
  • Project leads need to evaluate the impact of the OpenStack Summit on resource availability leading up to Arno release. There was also consensus that release should not be scheduled during the week of the OpenStack Summit. There was a discussion of going with OpenStack Kilo for Arno, but the consensus was this will significantly change the scope of Arno.
  • Will not set a new release date today, but the TSC will review a new release date on a weekly basis
  • Contact Heather if you need help with messaging at the NFV World Congress.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-04-23-13.31.html

April 21, 2015

Agenda

Minutes

  • Previous minutes approved
  • Arno Project plans & tracking
    • BGS: ISO images are ready, not deployed in an automated way, hardware configuration not yet complete. BGS team meeting daily for status updates.
    • Octopus: Octopus readiness pending configuration of hardware in the LF lab, but documentation is ready and scraped to the wiki. CI scripting for testing not confirmed yet.
    • Updates from Functest still pending
    • Documentation: Final release structure to be completed. Documentation team has the action item to to construct a consolidated presentation of release documentation.
    • Release readiness:
      • LF Hardware configuration is still on-going. There was a discussion that a reasonable approach may be to set a release date of one week after we have successful manual deployments
      • Consensus that we will not be able to release Arno on April 23rd. Project leads to craft a concise plan of action for Arno and will have another TSC meeting on April 23rd to discuss the new release date.
  • Arno marketing/messaging update: Heather indicates the marketing team will now have some work to do now that the release date has slipped pending a TSC decision.
  • OpenStack discussion: Heather asks for feedback on the room set-up during the OPNFV Day at the OpenStack Summit. The current proposal is to use a fishbowl style set-up in the morning. In the afternoon, use a smaller breakout style set-up to focus on specific topics.
  • Open Access update: Aric provided an update that Jira is now also open to the public. Will open Gerrit after Arno is released to save any collateral interruptions
  • Updating Section 7 of TSC Charter: There was a discussion on updating two sentences in Section 7 of the charter. Will continue the discussion over the mailing list and ratify during next week's meeting.
  • Project creation review:
    • Multisite Virtualized Infrastructure: Howard Huang (Huawei) presented the proposal, which is based on the ETSI NFV phase 1 work. There is a need in upstream communities to enable this functionality which are intended to be addressed in the requirements project. The project creation was approved via the IRC vote.
    • Escalator: Jie Hu (ZTE) presented the proposal, which intends to address the needs of operators for system upgrade. The project creation was approved via the IRC vote.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-04-21-14.00.html

April 14, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • New committers for BGS & Octopus
  • OPNFV Compliance & Certification Committee
  • Arno marketing update
  • Budget discussion on hoodies
  • Open Access
  • Arno Project plans & tracking
    • RC1 report and update on RC2
  • Project Approvals
  • AOB

Minutes

  • Previous minutes approved
  • Committer update process: There was a discussion that votes on committer updates need to be captured in minutes/email. Frank asks what is meant by "a majority vote". For example, is it majority among all committers or majority of those who actually voted? The consensus was majority of all committers and Ray has the action item to propose a new language for Section 7 of the TSC Charter.
  • OPNFV Compliance & Certification (C&C) Committee: Heather discussed the board approval of forming a C&C Committee. There will be representatives from board, TSC, and marketing committee. For TSC members interested in volunteering, please email Heather.
  • Arno marketing update: There was a good discussion on the release diagram. Heather mentioned that all feedback for OPNFV & Arno overview slides (i.e. slides 1 & 2) have been incorporated and the updated version will be posted on the wiki. Please send feedback if there are any technical inaccuracies.
  • Hoodies: Ray discussed ordering new hoodies for upcoming technical gathering at the OpenStack Summit. Since we're ordering a larger quantity and higher quality hoodies, this will require ~20% of the remaining TSC initiatives budget. There was a consensus among TSC members that this is a worthwhile investment to raise awareness among developers and agreed to move forward with the purchase.
  • Open access to OPNFV tools: Iben outlines that the ability of external parties to review our patches and contributions is inhibited since you can not access OPNFV repo's without an LF account. Aric will investigate and report back to the TSC with options for enabling open read-only access to Gerrit.
  • Arno project plan & tracking: Due to delays in LF hardware availability, RC1 was not fully passed. Deploy scripts and auto testing scripts are available in repositories now, documentation templates are now available. For LF hardware, still waiting on an adaptor that is due to arrive this morning Pacific Time. Fatih reports that once the LF hardware is available, there will be a 1-day lead time required to have the jobs set up and connected. For Functest, scripts and structures are in place in the repo. Intel lab access for Jenkins has been resolved.
  • Project approvals: Chris reminds the community that request for creation review must happen via an email to the TSC. Also when your projects are approved, please list them on the main wiki page under approved projects.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-04-14-14.00.html

April 7, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Linux Foundation data center hardware update - Konstantin
  • Release diagram update - Craig
  • OPNFV board meeting update to the TSC - Chris
  • OPNFV meeting tools and logistics - Frank
  • OPNFV award program review and approval - Ray
    • Awards committee
  • Arno Project plans & tracking
    • RC0 report and update on RC1
  • Project Approvals
    • Vote on VIM Northbound Model and Interface - vimnbi
  • AOB

Minutes

  • Previous minutes approved
  • OPNFV Hardware update at the LF Data Center: There have been some delays as purchasing of additional network & power connectors was necessary. Konstantin expects the hardware to be available for a dry-run by the end of this week (and ready for Jenkins setup early next week). Konstantin asks that if you need access to the OPNFV hardware, send your request to Chris Price, Trevor Cooper, or Frank Brockners. Since we will not be able to run RC1 activity on LF hardware, Frank will work with the Ericsson team to try to run RC1 activities in the Ericsson lab
  • Release diagram: Heather reviewed the draft release diagrams. There was a lot of discussion on "roadmap" slides. First, there was a consensus to drop the word "roadmap" and a preference to only include open source projects that are in the project pipeline. Will continue the discussion to the mailing list and will have the latest draft posted on the wiki. Please send any feedback/comment on release diagrams by Friday this week (April 10th).
  • OPNFV meeting tools and logistics: Frank reported that OPNFV have too many meetings that require audio and suggests some of the projects move to IRC-only meetings to see if this can become a default option for OPNFV meetings.
  • Award program: Ray discussed the proposal that was previously sent to the mailing list. For quarterly & "MVP" awards, the consensus is open nominations & voting. There can be a nomination/awards committee to help review & short-list nominees. Ray to write-up a final proposal for TSC approval.
  • Arno project plans & tracking:
    • Documentation: Toolchain in place, connecting it to Jenkins and getting templates in place
    • BGS: Teams are working on deployment scripts for Arno
    • Octopus:Automatic builds are ready, dependent on hardware at the LF datacenter.
    • Functest: The functest suites can be run manually in the intel labs. The vPing test cases are working but some issues in the pods. Morgan will reach out to the Ericsson lab with tools needed for tests on Thursday.
  • Project Approvals
    • Vote on VIM Northbound Model and Interface - vimnbi: The project has been renamed to Model Oriented Virtualization Interface and other questions were answered/clarified offline. The project creation was approved via the IRC vote.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-04-07-13.58.html

March 31, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • OPNFV videos & recordings - sharing and storing
  • OPNFV communications tools and meeting methods
  • Summit travel planning and registration etc...
  • OPNFV functest project issues:
  • Development process and guidelines discussions
    • Project scope adjustment processes
    • Project committer approval processes
    • Requirements project structures and key artifacts
  • Arno and OPNFV release graphic
  • Arno release candidacy planning
    • Arno RC process description
    • Release candidate reporting meeting
  • Arno Project plans & tracking
    • bootstrap
      • RC0 readiness report
    • octopus
      • RC0 readiness report
    • function test
      • RC1 readiness report
    • documentation
      • RC1 readiness report
  • Project Approvals
    • Re-visit VIM Northbound Model and Interface - vimnbi
    • OPNFV Documentation project - opnfvdocs
  • AOB

Minutes

  • Previous minutes approved
  • Video & recordings: OPNFV YouTube channel to be used for posting training/tutorial contents and will look for ways to organize marketing vs. technical contents. There's issue accessing YouTube in China so alternatives will need to be investigated by the LF team.
  • OPNFV communication tools & meeting methods: Frank Brockners mentions that there are issues with using GoToMeeting due to increase in the number of meetings and audio quality. Consensus to form a separate team to investigate options (incl. doing more meetings via IRC). Frank, Ray Nugent, Bryan Sullivan, Iben, and Dave Lenrow will meet and report back to the community.
  • OpenStack summit update: Find the latest on the Summit at OpenStack Summit Etherpad. Heather also encourage everyone to contribute ideas to the Etherpad page. In general, event information (incl. registration, post meeting notes, etc.) will be available on the events Etherpad page at https://wiki.opnfv.org/ as it was done for our two events in February.
  • Functest: There is an urgent need to add 6 new committers to the project. Trevor has the action item to get current committers to approve adding the new committers. As a rule, project leads need to communicate committer changes (showing votes in IRC, email, etc.)
  • OPNFV & Arno release graphic: Heather, Ray, and Brandon will meet with Craig (from LF' Creative Service team) will meet later in the day to discuss the release graphics. There was a meeting on Friday (March 27th) to explore several different options and proposed diagrams from Frank does a good job of capturing the OPNFV overview and Arno.
  • Arno release candidate (RC) planning: There was an agreement to run the RC meeting via IRC on the Thursday at 07:00 AM Pacific time
  • Arno Project plans & tracking
    • BGS team to reach consensus prior to Thursday for RC0 reporting
    • Octopus team expect to be ready for RC0
    • Functest: currently running on Jenkins in different labs
    • Documentation: Expect ~100 person hours of work
  • Project Approvals
    • OPNFV Documentation project - opnfvdocs describes all the required elements for a release. The project creation was approved via the IRC vote.
    • Re-visit VIM Northbound Model and Interface - Chris Price asks if renaming the project to "Service Oriented VIM Northbound Model and Interface" makes sense. There were also other questions on scope and implementation. As we were running out of time, the consensus was to post questions on the mailing list and the TSC meeting will be used for voting only (i.e. no further discussions) next week.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-31-13.56.html

March 24, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • OpenStack community status
  • Arno release candidacy and final release activities
    • Candidacy schedule and validation
    • Release Artifacts
    • Labeling & distribution
  • Arno and OPNFV release graphic
  • Arno Project plans & tracking
    • bootstrap
      • Release readiness and timing for candidacy activities
    • octopus
      • Lab readiness
    • function test
      • Scope and automation status
    • documentation
      • Release 1 documentation scope
      • Utilizing a technical writer for bootstrapping Arno documentation
  • Project Approvals
    • Re-visit VIM Northbound Model and Interface - vimnbi
  • AOB

Minutes

  • Previous minutes approved
  • OpenStack community status: Dave Neary updates the community that blueprint reviews have been occurring on Thursday's Technical Community calls. Goal is to develop the blueprints to a point where we are ready to add them to the upstream gerrit for further discussion and review. Blueprints to be reviewed by the community should be handled through https://wiki.opnfv.org/community/openstack. We're targeting Liberty which will be released in October of 2015. Dave Neary is the main contact person for the OpenStack activity and will update the wiki page accordingly.
  • Arno release activities: Chris Price proposes weekly release candidate (RC) activities leading up to April 23rd. RC scope needs to be agreed up on during the next TSC meeting (March 31st).
    • Release vehicle will include:
      • ISO image (from BGS)
      • Documentations for user guide (from BGS), test scenarios (from FuncTest), and hardware guide (from Pharos)
    • Automatic testing will not be part of the release vehicle/artifacts
    • Arno release diagram: Chris presented his proposal for the release diagram. There was a good discussion on the target audience, if we also need to address future plans/vision, etc. Ray took the action item to schedule a separate call to discuss the release diagram later in the week.
  • Arno project plans
    • BGS: High level schedule for Arno. Need to define the stable installed networking state of the get_started_system_state wiki page
    • Octopus: Work needs to be done with the functest team to identify structure/triggers
    • Functest: The goal is to have each of the toochains run autonomously by Jenkins. Status of test automation (incl. details for different installers)

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-24-14.00.html

March 17, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • OPNFV Ambassadors program establishment: Prathima
  • Marketing committee update: Brandon
  • Update on OPNFV hardware @LF data center: Konstatin
  • Vancouver OpenStack Summit update: Heather
  • Update on the Release 1 naming: Ray
  • Follow up onboarding activities: Fatih
    • Development tool training, Jira, Gerrit, Git, Jenkins
  • Project plans & tracking
    • bootstrap
    • octopus
    • function test
    • documentation
      • Utilizing a technical writer for bootstrapping release one
  • Project Approvals
    • VIM Northbound Model and Interface - nemo
  • AOB

Minutes

  • Previous minutes approved
  • OPNFV Ambassadors program: Prathima introduced the Ambassadors program for technical speaking opportunities. More program details will be posted on the wiki. In the mean time, please email Ray or Prathima (pramesh@linuxfoundation.org) if you are interested in volunteering
  • Marketing committee update: Brandon provided update from MWC and plans for upcoming events such as NFV World Congress, Open Networking Summit, and OpenDaylight Summit. A suggestion was made to post event recaps on the wiki (similar to February Meetup & Hackfests).
  • OPNFV Hardware: Konstantin reported that all servers have been racked, but have a list of questions for the community. Suggestion was made to send the list of questions to mailing lists and setup a follow-up call later this week.
  • OpenStack Summit (Vancouver): Heather provided the latest on OpenStack Summit. The current plan is to have an OPNFV Day on Monday with a reception in the evening (post booth crawl). On Wednesday/Thursday, will participate in Telco WG Design Summit where blueprints will be discussed. OpenStack Summit Etherpad
  • Release 1 naming: Ray reported that the winner is Arno. Also a reminder not to include release names in the codebase in case if we have any issues in the future (using them in the filename is OK).
  • Developer tools training: Fatih has training material in place and the session will be ~2 hours long and will cover OPNFV Developer Tool Info, OPNFV Developer Workflow, and live Hands-on session.
  • Project plans & tracking:
    • BGS: BGS project is working on defining the commonalities across the final system states after the multiple installers
    • Octopus: Reviewed scripts from the Fuel team yesterday. Looking forward to running in Jenkins after issues are worked out.
    • Functest: Trevor communicating with Palani if he’s still interested in being a project lead. Also mentioned that a better coordination with Ci & BGS teams are needed. Uli suggested having a rep from Octopus join the Testing team meeting on Thursday.
  • Documentation update: Iben proposes using git for documentation. There are 2 areas to work on. One to write the documentation for Arno and another to establish a documentation process. Iben will schedule a meeting to discuss a potential process for documentation.
  • Project proposal review for VIM Northbound Model and Interface: Tianran Zhou (Huawei) presenting the proposal. The goal is to provide consistent/intuitive northbound interfaces for VIM. There were a lot of questions on scope, collaboration with ETSI, etc. and as time was running out consensus was to re-visit this proposal at the next TSC call (after possibly having another review on Thursday's Technical Discussions call).

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-17-14.01.html

March 10, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Update from the board f2f
  • Hack-fest planning and updates
  • Follow up- Development tool training, Jira, Gerrit, Git, Jenkins
  • Update on OPNFV hardware @LF data center
  • Update on the Release 1 naming
  • Discussion on awards programs for the OPNFV technical community
  • Project plans & tracking
    • bootstrap
    • octopus
    • function test
    • documentation
  • Project Approvals
  • AOB

Minutes

  • Previous minutes approved
  • Update from the face-to-face board meeting: Chris provided an update form the board meeting. One of the topics that the TSC will have to discuss in the near future is the topic of certification or compliance testing
  • Hackfest planning: Discussion on-going with the OpenStack community (esp. the Telco working group) on options for collaboration in Vancouver. There was also a discussion on if there is a need for a "standalone" OPNFV Hackfest as the next two planned hackfests are co-located with upstream projects (e.g. OpensStack & ODL). The consensus was to stay with the current plan and re-evaluate later in the year if necessary.
  • Development tools training: Aric has posted content on the wiki https://wiki.opnfv.org/developer, but some recorded sessions would be helpful. Ray has the action item to see if there are existing training materials @LF. Fatih/Iben/Aric will also build recorded training materials.
  • OPNFV Hardware: Ray provided a quick update on OPNFV hardware @LF data center. Delivery has been made to the data center and the team in currently doing inventory of items. Will invite Konstantin to the TSC call next week.
  • Release 1 naming: Ray will send out a survey today so that people can vote up to 5 choices for the name. Vote will close on Monday (16th) next week.
  • Awards program for the technical community: Possible categories of awards were discussed such as documentation, integration, collaboration, testing in addition to code. A concrete proposal to the board is required for a budget approval, so Ray will send out a proposal to the mailing list.
  • Project plans & testing
    • BGS: The plan is not to have manual installation on the LF hardware. This should be deployed using the existing toolchain.Jira for BGS
    • Octopus: Working mode is now Jira-based and Octopus is now awaiting build scripts to be made available from other projects.
    • Functest: The team is working with Tempest and Rally against a manually installed BGS environment. Also working with tools and integrating them with CI.
    • Documentation: Documentation project posted. There was also a discussion on hiring a technical writer to bootstrap release documentations.
  • Creation review for the Resource Scheduler project: Zhiqi Wang (Huawei) presented the project proposal. Recommendation for the project team to work in close collaboration with other OPNFV projects like Promise and Copper. Project creation was approved via the IRC vote.
  • OpenStack community update: Dave Neary outlined the blueprint process for OpenStack, including the level of detail required including implementation details and high level use cases associated with the feature. The target is to be ready by May with OPNFV blueprints with the right level of detail and structure. See the OPNFV OpenStack community page.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-10-14.02.html

TSC meeting March 3 , 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Review of NFV#9 meeting
  • OPNFV Release 1 Naming
  • opnfv-tech-discuss topic filters
  • Maintaining project leader, committer & contributor list
  • Development tool training, Jira, Gerrit, Git, Jenkins
  • OPNFV Release 1 discussion
    • Project plans & tracking
      • bootstrap
      • octopus
      • function test
    • Documentation
  • OpenStack blueprint handling
  • Project Approvals
  • AOB

Minutes

  • Previous minutes approved
  • Review of ETSI NFV#9 meeting in Prague: Chris Price gave an update from the TST meeting. He suggested ETSI to propose a LOI to OPNFV. Parviz also shared that TMF, ETSI NFV, 3GPP SA5 will work closely together. Immediate impact to OPNFV will be minimal. In general, ETSI was happy to see participation from OPNFV.
  • Release 1 naming: There was a good discussion on if the voting should to open to everyone (i.e. not just the TSC members), and the consensus was that it should be open to everyone on the tech-discuss mailing list. Ray will simplify the list, get legal feedback, and send a survey out for vote. In the survey, voters will be asked to write in their names.
  • Topic filters: TSC agreed to enable topic filters on tech-discuss mailing list. Ray will also send instructions/documentations plus post on the wiki.
  • Maintaining project leader, committer & contributor list: Aric wants to have a more reliable source than the wiki and suggested that when a project is created a file is created in the repository that describes the current list of committers & project lead. Aric will also investigate if we can auto-generate key project facts onto the project wiki page.
  • Development tool training, Jira, Gerrit, Git, Jenkins: Chris proposed doing training sessions that is also recorded. This can be used as an on-boarding tool.
  • Release 1 update: There was an agreement to begin describing Release 1 on the OPNFV wiki page, capturing the intended activities and objectives. Uli will begin to put this on the wiki.
  • Project plans & testing: Frank shared that the team is starting to put the material into Jira for more public visibility. There are also separate pages for different deployment tools showing current activities. Invitation to the technical community to visit status pages and find areas where they can help. Uli shared that the Octopus team is currently focused on integrating with other projects for automated test. Jira also setup for functest, and Palani is looking for help on creating user stories.
  • Documentation: Seeking volunteers. Documentation wiki page already started.
  • OpenStack blueprint (BP)
    • There was a discussion that proposed BPs should be as visible and aligned among multiple projects. Chris Price proposed having a 30 minute meeting prior to the next TSC call.
    • Final call for BPs for L-release will be Vancouver meeting in May. Reviewer resource is the bottleneck for OpenStack.
    • There was also a suggestion to have release information for other upstream projects such OpenDaylight, Open vSwitch, DPDK, etc.
  • Project Approvals
    • Data Collection for failure prediction - OPNFV failure prediction:: Linghui Zeng (Huawei) presented the project proposal. The initial goal of the project will be on the data collector (e.g. what data should be collected but is not yet available). Project creation was approved via the IRC vote.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-03-15.01.html

TSC meeting February 24 , 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Meet-up/Hackfest Summary
  • OPNFV Release 1 discussion
    • Project plans & tracking
      • bootstrap
      • octopus
      • function test
    • Documentation
    • Release 1 target date
    • Release 1 naming
  • ETSI-OPNFV Collaboration
  • Project Approvals
  • AOB

Minutes

  • Previous minutes approved
  • Will hold the TSC meeting next week with whoever can attend
  • Meet-up/Hackfest summary: Heather mentioned that there were good attendance both in Santa Rosa & Prague. Good discussions on working with upstream communities, Release 1 projects, and requirements projects. Meeting materials posted at Santa Rosa MeetUp & Prague Hackfest
  • OPNFV Release 1 discussion:
    • Octopus: Uli outlined CI activities including the Jenkins environment and jobs structure.
    • BGS: Frank described two projects using Foreman vs. Fuel deployment tools. There was a good discussion on the possibility of picking one installer and focusing our resource on one project. However, people working with one installer will not be able to transition over to the other project to provide additional bandwidth. Thus we would not necessarily gain anything by focusing only on one particular installer
    • Another critical element for Release 1 is the OPNFV hardware @LF data center. The target date for the hardware availability is March 15th.
    • Chris Price proposed 6 weeks after the hardware availability to pull the first release together (April, 23, 2015). There was a good discussion on the desire from projects teams for more time, but there were also comments from the community that having an early release maybe preferred even if it's not feature-rich (e.g. missing HA). This gives people an opportunity to experiment & participate. There was also consensus that setting the release date to coincide with the OpenStack Kilo release or the NFV World Congress will not be ideal.
    • The TSC voted via IRC to approve the proposed release date of April 23, 2015
  • OPNFV Release 1 Name
    • Ray has the action item to send email to mailing lists for the naming of OPNFV Release 1 (theme is Rivers)

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-02-24-15.01.html

TSC meeting February 17 , 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Formation of a security group
  • OPNFV Release 1 discussion
    • Project plans & tracking
      • bootstrap
      • octopus
      • function test
    • Community engagement
    • Projecting the release one target date
  • WiKi structure and content - Chris
    • Project
    • Meeting
    • Developer
    • Security
    • More/Less???
  • Project Approvals
  • AOB

Minutes

  • Previous minutes approved
  • Formation of a security group: Luke led the discussion on the security group in OPNFV. There was a discussion on the need to work towards actionable items for development that lead to security improvements in OPNFV. The TSC agreed to the formation of a security group.
  • There was a discussion on potential licensing issues when OPNFV works with upstream communities that are using GPL licenses. Ray has the action item to get clarity on licensing and how code scanning is going to be implemented in OPNFV.
  • Release 1 update
    • Frank provided an update on BGS. By the end of February, base installer will be completed. Targeting installation on OPNFV hardware & CI integration by mid-March. Then Tempest / Robot scenario tests available by the end of March. The team will likely need additional 2-4 weeks to deliver Release 1.
    • Uli provided the CI update and notes that Jenkins is setup
    • Trevor outlined the function test requirements. The expectation is that the CI first deploys and testing will be invoked from the staging server and Jenkins will determine success/failure
    • Chris noted that we will also need BGS documentation for Release 1.
    • The TSC agrees to target the first release for April and will continue to define the exact target date during the next TSC meeting (Feb. 24th)
  • Chris provided an update from the February Board meeting.
  • Re-visit OpenStack Based VNF Forwarding Graph Forwarding Graph: Cathy discussed updates to the diagram and the project proposal wiki page. There was good discussion on how the project fits within the scope of OPNFV. The project creation was approved via the IRC vote.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-02-17-14.59.html

TSC meeting February 10 , 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Committer promotions:
    • Process overview
    • Ulrich Klebier - Octopus project
  • OPNFV Release 1 discussion
    • BGS update - Frank
    • CI update - Uli
    • Release intent discussion - Chris/Heather
    • Setting our release date - Chris
  • Quick update on Meet-up (Santa Rosa) & Hackfest (Prague) - Ray
  • Project proposal process - Chris
    • Best use of the review period and the technical review forum
  • Project Approvals
  • AOB

Minutes

  • Previous minutes approved
  • Committer promotions: There was a discussion on whether the TSC should approve new committers, and the consensus is that committer promotions should be handled by the project committers, the TSC should only be involved when there are highlighted issues to be addressed in the promotion. Dave Lenrow has the action item to update the wiki (https://wiki.opnfv.org/developer/committer_promotion) to reflect this consensus.
  • OPNFV Release 1 discussion
    • BGS: The focus is to get the OpenStack OpenDaylight integration done and the team is working to create a draft schedule for release 1.
    • CI: Team is looking at the infrastructure and working with the Linux Foundation team on the tools
    • Release intent discussion: There was a good discussion on the "Release 1 intent" that was sent to mailing lists and several suggestions were made to the text. Agreement to continue to work on the text via email and set the Release 1 target date at the next TSC call on February 17th.
  • Meet-up & Hackfest: A reminder that the latest working agenda are on etherpads (https://etherpad.opnfv.org/p/MeetUpFeb19 & https://etherpad.opnfv.org/p/HackfestFeb23) and that you can propose new agenda topics
  • Project proposal process: There was a discussion that Thursday's Weekly Technical Discussions meeting is a good forum to gather community feedback and identify cross project collaboration opportunities. Even if not all TSC members are present on the Thursday call, it is highly recommended that project teams present their proposals at the Technical Discussion meeting prior to TSC calls.
  • Project Approvals
    • Re-visit Data Plane Acceleration: Now there is an accommodation of both hardware and software acceleration and will leverage compatibility to existing API's. Also added OpenStack as a relevant upstream project. The project creation was conditionally approved via IRC vote pending clarification of the committers list.
    • OpenStack Based VNF Forwarding Graph: Cathy Zhang (Huawei) presented the project proposal. There was a lot of question/discussion on how the scope diagram in the project proposal maps to the OPNFV architectural diagram. Suggestion is to continue this discussion during Thursday's Technical Discussion meeting before coming back to the TSC next week.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-02-10-14.58.html

TSC meeting February 3, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Project Approvals
    • Data Plane Acceleration - dpacc
  • OPNFV Release 1 discussion
    • BGS update - Frank
    • CI update - Uli
    • Release intent discussion - Chris/Heather
  • Project leads assignment - Aric
  • OPNFV Security discussions - Luke/Tapio
  • Development process & description - Chris
  • Project Approvals
  • AOB

Minutes

  • Previous minutes approved
  • Data Plane Acceleration project review: Lingli Deng (China Mobile) presented the project proposal. There was a question/discussion if recently proposed changes have been reflected in the latest proposal. TSC recommended that the project team revise the wiki/project proposal and come back for a quick review next week.
  • Release 1 update: Frank provided the latest status on BGS and mentioned that the team is making progress on two efforts on the installer component. A demo of foundations are planned for next Monday's BGS call. Uli outlined the progress on CI and noted that interfaces/dependancies on other projects are being defined.
  • Project contacts: Aric requests that each project identify a point of contact for administrative/infrastructure questions (e.g. Jira). This is not necessarily a project lead, but the contact person whould be one of the committers. [Action Item: Ray/Aric to send email to mailing lists to remind projects to identify a point of contact and email Ray/Aric]
  • OPNFV security discussion: Luke Hinds summarized discussions on mailing list regarding a security community. There was a discussion that some functions of the security group could integrate themselves with OPNFV operational activities.
  • Development process: Chris gave an overview of latest wiki documentation and project page templates. There will be further discussion on mailing lists for defining methods for working with upstream communities (amongst requirements projects)
  • Parser project review: This is an integration & testing project to provide a template translation engine. There was a good discussion on the scope of this project, but the consensus was that there was a diverse group of people who are interested in the project. The project creation approved via the IRC vote.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-02-03-14.57.html

TSC meeting January 27, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Developing OPNFV tracks for upcoming events (NFV World Congress, Open Networking Summit, ODL Summit) - Brandon Wick
  • OPNFV Release 1 update - Frank / Uli / All
  • Confirming the OPNFV Release 1 date
  • Test project structure and relationships overview
  • Development process development and description
    • Release two planning discussion
  • Project Approvals
    • Quick update on Qtip proposal Qtip
  • Pending future reviews
  • AOB

Minutes

  • Previous minutes approved
  • Brandon Wick discussed developing OPNFV tracks for upcoming NFV World Congress & Open Networking Summit. Request for volunteers from the OPNFV technical community to help plan organize the OPNFV tracks.
  • Release 1 update: Uli provided an update on the Octopus project and walked through the diagram at https://wiki.opnfv.org/_media/octopus/octopus_diagram_v2.pdf to discuss input components and deployment tools. Palani provided an update on BGS and discussed that the focus will be on brining up the puppet framework on the current infrastructure.
  • OPNFV Release 1 date: BGS team is working towards a draft release on February 15th and a second release on the 28th. There is a need for a small group to meet to establish a timeline for the first release. Palani, Bin, and Frank agreed to spend time on this.
  • Test project structure: Trevor discussed that the Pharos project is defining the test bed and the latest descriptions/diagrams can be found here. Morgan added that Pharos is defining the test bed infrastructure that include access, governance, time scheduling, test deployment across environments.
  • Qtip project creation review: Wenjing clarified the scope & priority activities for Qtip. Also discussed use cases that were added to the project proposal page. The project creation was approved via IRC vote.
  • Development process development & description: Uli discussed OpenStack's release milestones and how OPNFV requirements projects need to be aligned to these milestones.
  • There was also a discussion on ETSI collaboration and the consensus was to continue this discussion at the Hackfest in Prague.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-01-27-14.59.html

TSC meeting January 20, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Introducing Heather Kirksey as Director for OPNFV
  • OPNFV Summit Program Committee
  • OPNFV Release 1 update - Frank & Uli
  • Project meetings and minutes - best practices
  • Simultaneous release and development process work
  • OPNFV infrastructure hardware requirements
  • Project Approvals (review until time runs out, limited to hopefully 20 minutes per proposal.)
    • OPNFV base system functionality testing project functionality testing
    • Qtip - Qualification, Tool Integration, Platform performance benchmarking Qtip
    • Parser - VNF descriptor parsing project Parser
    • OpenStack Based VNF Forwarding Graph Forwarding Graph
  • AoB

Minutes

  • Previous minutes approved
  • Heather Kirksey introduced herself as the Director for OPNFV @LF. She will be reaching out to TSC members soon.
  • OPNFV Summit Program Committee: Ray discussed the formation of a program committee for the upcoming summit and a request to have the technical community represented. Ray will send an email to the TSC mailing list soliciting volunteers.
  • Release 1 activity update
    • Boostrap/Get-started (BGS): Team is looking at installer options and reviewing a proposal from RedHat for using puppet modules to integrate OpenStack with ODL. Palani added that in the Intel lab, he demonstrated the installation of the platform using Fuel, however there were high availability issues.
    • Octopus: Team is focusing on the integration of the BGS activities into the octopus workflow for the CI pipeline.
  • Project meetings & minutes: There was a discussion on best practices for project meeting minutes and questions on effectively using the MeetBot. Chris has an action item to start a discussion on mailing lists around meeting minutes and using meetbot [Dave Neary wrote a quick tutorial on MeetBot that can be found at: Creating meeting minutes with MeetBot]
  • Simultaneous release & development work: Chris Price discussed the need to kick off the development process and simultaneous release process development. Uli added that the CI process will be heavily dependent on the development process. Chris took the action item to kick start this process on mailing lists.
  • OPNFV hardware infrastructure: Chris provided a quick update on the hardware infrastructure and added that leasing is not necessarily a cheaper options as we are looking at cutting-edge hardware. There was also a discussion on using the hardware to focus on CI & functional testing.
  • Project Approvals:
    • Functionality Testing: The focus is on testing the OPNFV platform. There were suggestions to clarify "life cycle management" in the proposal plus edit the repo name. The project creation was approved via IRC vote.
    • Qtip: Wenjing Chu (Dell) presented the Qtip project that will perform "bottom up" testing. There were questions on how this project relates to other projects such as Pharos & Functionality Testing. Wenjing will incorporate these feedback and present the updated proposal at the next TSC call.
    • Parser: Zhipeng Huang (Huawei) presented the project proposal. There was a feedback that clarity on the project scope is needed before the TSC can vote. Suggestion was made to also have a discussion on mailing lists prior to the TSC meeting.

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-01-20-14.57.html

TSC meeting January 13, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Q1 Release - hot topics
    • OPNFV interim hardware solutions
    • OPNFV hardware discussion and decision
    • Bootstrap update & discussion - 5 mins
    • CI update & discussion - 5 mins
    • Parser project aspects of interest to release 1 - 5 mins
  • WiKi page maintenance and procedures
  • Project Approvals (review until time runs out, limited to hopefully 20 minutes per proposal.)
    • OSCAR - continuous deployment project OSCAR
    • Pharos - Testbed Infrastructure project Pharos
    • OPNFV base system functionality testing project functionality testing
    • Qtip - Qualification, Tool Integration, Platform performance benchmarking Qtip
    • Parser - VNF descriptor parsing project Parser
    • OpenStack Based VNF Forwarding Graph Forwarding Graph
  • AoB

Minutes

  • Approve previous minutes: deferred until next week as the minutes for the January 8th meeting was not posted until late.
  • Q1 Release - hot topics
    • OPNFV interim hardware solutions: There was a discussion on hardware solutions available from Ericsson & Intel. Currently, here are some restrictions for accessing both (e.g. you need VPN for Ericsson and individual accounts need to be setup for Intel). Dell will also have an infrastructure that can be used. A suggestion was made to post updates or information on how to access these hardware on the wiki or mailing lists.
    • OPNFV hardware (Work environment for Bootstrap/Get-started): There was a good discussion on the BOM and a question was raised if the number of servers per PODs need to be corrected and Frank Brockners replied that it should be corrected to 6 per POD. Action Item: Frank & Chris Price to bring back a proposal to the TSC next week.
    • Bootstrap/Get-Started update: Team agree to a weekly conference call on Mondays at 8am PT. The recent focus has been the OPNFV hardware requirements.
    • Continuous integration: nothing to report
    • Parser project and relevance to the first release: Uli Kleber discussed that the Parser project may bring additional value to the 1st release as it is independent from projects and integration. However there is a concern that this may take resource away from the first release.
    • Wiki page maintenance: Chris Price has the action item to begin a Wiki maintenance and governance team on the OPNFV mailing lists.
  • Project Approvals
    • OSCAR:Parviz Yegani & Stuart Mackie (Juniper) presented the OSCAR project proposal. There was a question if Stack #2 is available to the community and Stuart replied that it is available on github & OpenContrail site. Suggestion was made to change the repo name to 'oscar'. The project creation was approved via IRC vote.
    • Pharaos: Wenjing Chu (Dell) presented the project proposal. So far sites in Asia, Europe, and the US have been identified. The project will not cover benchmarking, VNF deployment testing, carrier grade requirements. Wenjing also explained that the project does not dictate the definition of the test bed. Also, a work item exists to define access needs for labs wanting to participate. The project creation was approved via IRC vote.
  • February events update: Ray Paik provided a quick update on the Meet-up (Santa Rosa, CA) and Hackfest(Prague). Registration information are available on etherpad along with agenda in development.

MeetBot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-01-13-14.57.html

TSC meeting January 8, 2015

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Working with the OpenStack Community - Russell Bryant/Jay Pipes/Kyle Mestery
  • bootstrap update - Frank B
  • continuous integration update - Ulrich K
  • OPNFV HW infrastructure requirements

Minutes

  • Previous minutes approved
  • There was a discussion if 2 hours is still needed for the TSC meeting. Consensus was to keep it at 2 hours and the meeting can always end early if there are not enough topics.
  • Jay Pipes/Kyle Mestery/Russell Bryant/Thierry Carrez from OpenStack attended the call to discuss how to best work with the OpenStack Community. There is a weekly Telco working group meeting (https://wiki.openstack.org/wiki/Meetings) IRC channels also available at #openstack-[nova|neutron|dev]
  • Update on the Bootstrap project: Frank Brockners (Cisco) provided a quick project update. Hardware is a blocking issue and an installer needs to be selected. Also discussed moving the daily IRC session to 7:30am Pacific Time.
  • Update on the Continuous Integration project (Octopus): Uli Kleber (Huawei) provided a project update and mentioned that the team is working on a task list for the project. Also noted that Octopus planning needs to be done in anticipation of the baseline output from the Bootstrap project.
  • Hardware requirements for OPNFV: There was a good discussion on hardware requirements (Work environment for Bootstrap/Get-started). Please add your suggestions/inputs directly on the wiki page. Frank Brockners has an action item to present HW proposals at the next TSC meeting on January 13th.
  • Suggestion was made to add wiki update/maintenance as an agenda topic for the TSC call next week.

MeetBot Minutes

TSC meeting December 16, 2014

Agenda

Minutes

  • Previous minutes approved
  • OSCAR project to be further reviewed in the community prior to TSC review.
  • Project repo's
    • You can find repositories for approved projects at https://gerrit.opnfv.org/gerrit/#/admin/projects/
    • Need to have a Linux Foundation account in order to be added as a committer. (Please use the corporate email address for the Linux Foundation account)
    • For any technical issues, file a ticket by sending an email to opnfv-helpdesk@rt.linuxfoundation.org
  • Meet-up and HackFest
    • Frank Brockners setup etherpads for upcoming Meet-up & Hackfest in February. We will use these etherpads to list registration information and collaborate on goals, agenda, topics, etc.
    • For Prague Hacfest, no suitable venue is available within walking distance of the ETSI meeting. Best recommendation is to go with Prague Marriott Hotel which is 15 minutes away by Metro (no transfer required and the Metro stop is very close the Marriott). The TSC came to a consensus to move forward with securing the venue at the Prague Marriott for the Hackfest (February 23-24)
  • Development process discussion
    • There was an agreement that there is a need for a discussion design process for requirements projects. [Action item: Bryan Sullivan to kickoff/facilitate this discussion]
    • Good discussion on working with upstream projects and there were consensus on (1) identifying trial projects to provide guidance and (2) inviting members of OpenStack community to future OPNFV TSC calls.
  • Project reviews
    • Project name & committer check for the now Software Fastpath Service Quality Metrics project. Consensus that this is a Collaborative Development project and will be a good trial project to work through OPNFV' development process and working with the DPDK community. The project creation was approved via IRC vote.
    • vSwitch Performance project: There was a question on hardware requirements and the project team responded that this is documented on Test & Infrastructure subteam wiki page. The project creation was approved via IRC vote.

Meetbot Minutes

TSC meeting December 9, 2014

Agenda

Minutes

  • Previous minutes approved
  • Meeting sequences around the year end: No meetings on December 23 & 30. May decide to have an extra meeting on December 18th. Since January 6th is also a holiday in some regions, we will have the first TSC meeting of 2015 on January 8th (Thursday) before resuming the regular Tuesday TSC calls the following week.
  • Collaborative development projects: Two approaches were discussed. The first is project is a use case/feature and engages as needed upstream. The second is project is upstream liaison and maps to upstream. Since there was no clear consensus after a lengthy discussion, suggestion was made to move this discussion to the mailing list. There was also a suggestion to use the first collaborative development project could be used as a pilot.
  • Project proposals:
    • Committer check for Continuous Integration (Octopus): Confirmed the updated list of committers. The Octopus project was approved via voting on IRC.
    • Committer check for Virtual Infrastructure Policy project (Copper): Added more committers & contributors. The Copper project was approved via voting on IRC.
    • High Availability for OPNFV: Qiao Fu (China Mobile) presented the High Availability project proposal. Based on feedback, updates were made to the list of committers/contributors and also for the scope to specify "requirements for HA API". The Availability project was approved via voting on IRC.
    • Bootstrap/Get-Started: Frank Brockners (Cisco) presented the project proposal. Plan is to have something working for Release 1. Made update to the OS (Centos 7). Reminder that communication occurs daily on IRC and meeting information is on the wiki. The Bootstrap/Get-Started project was approved via voting on IRC.
    • Telco KPI Monitoring: Mike Lynch (Intel) presented the project proposal. General consensus that the project name suggests something broader and could be confusing. Project team to come back to the TSC with a new project/repo name.

Meetbot Minutes

Special TSC meeting December 4, 2014 @6-7am Pacific Time

This meeting is to review project proposals only. Please use the same GoToMeeting logistics below to participate in the call.

Agenda

Minutes

  • Project reviews
    • Resource Management (Promise): Ashiq Khan (DOCOMO) presented the proposal and described the current issue around resource reservation in OpenStack, that it is not possible to reserve resources for future assignment. There was a feedback to add use cases description in the deliverables and add email addresses of committers/contributors. The Promise project was approved by the TSC vote on IRC.
    • Virtualized Infrastructure Deployment Policies (Copper): Bryan Sullivan (AT&T) presented the proposal and explained that the goal to determine when a resource has been allocated/deallocated according to a decision. There was a feedback that the list of committers plus project output need to be finalized/clarified. Bryan to make these updates prior to the next TSC call for a final vote (no further discussion needed).

Meetbot Minutes

TSC meeting December 2, 2014

Agenda

  • Simultaneous Release
    • Simultaneous release process review and discussion
  • Follow-up on action items
    • Action Item: Tapio to create a proposal about how to use Git and Gerrit to review project proposals
    • Action Item: Dave Lenrow to propose initial release schedule on the WiKi
    • Action Item: Ray to investigate the vote functionality on IRC
    • Action Item: Chris Wright to begin discussion to review the project lifecycle
    • Action Item: LF will also setup registration for the Hackfest once logistics are finalized.
  • AoB

Minutes

  • Previous minutes approved
  • December board meeting overview: Chris Price reviewed discussions at the Board meeting. Chris communicated that there was a consensus from the Board to target March'15 release date with less functionality and get the process started.
  • Project proposal process update: Chris Wright explained that the project proposal template was updated to match the Project Lifecycle document and to clarify that a project proposal should be of only one type. There was a general consensus to reduce the process overhead and there will be further discussions to accomplish this. Also a reminder that there is a 2 week public review period for proposals and TSC members need to review & provide feedback before the formal TSC review sessions.
  • Upstream software strategy: There was a good discussion on which versions of upstream projects OPNFV should take. The group also discussed if there is a need for the Simultaneous Release (SR) for the first OPNFV release. There was a general consensus that the focus will be on the latest stable upstream release as a baseline for OPNFV and the SR can come after the first OPNFV release.
  • Release date & composition: Again, there was an agreement that the SR is not needed for the first OPNFV release in March. The TSC agrees that the focus of the first release will be on the integration of upstream components into a platform, the development of our continuous integration process, and test projects focused on proving platform and NFV related functionality.
  • Project proposal review
    • Doctor: Ashiq Khan presented the revised Doctor requirements project to define requirements to improve fault management in VNFI components and an OpenStack-based VIM component. The Doctor project was approved by the TSC vote on IRC.
    • Octopus/CI Project: Uli Kleber presented the latest Octopus proposal. One of the feedbacks was that the list of committers need to be finalized/updated. Uli will bring this proposal back to the next TSC meeting
  • A suggestion was made that additional meetings may be needed for project reviews as there is a large backlog. There was a consensus to have a one hour meeting on December 4th at 6-7am Pacific Time just to review project proposals (instead of the weekly technical discussions call).

Meetbot Minutes

TSC meeting November 25, 2014

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Proposed events for 2015
  • Board Alternate
  • Simultaneous Release
    • Simultaneous release process review and discussion
    • Simultaneous release deliverables discussion
    • Proposed dates for the simultaneous release
  • Project Approvals scheduled for November 25th
  • Follow-up on action items
    • Action Item: Tapio to create a proposal about how to use Git and Gerrit to review project proposals
    • Action Item: Ray to propose TSC call time options to the mailing list.
    • Action Item: Dave Lenrow to propose initial release schedule on the WiKi
    • Action Item: Aric will get together with Palani to make a proposal on getting a pool of development systems with needed resources
    • Action Item: Frank will send out an email to the community to see if there are objections to Ubuntu.
    • Action Item: Ray will send out a note to the mailing list to seek community feedback around opening the mailman archives.
    • Action Item: Ray to send email to the mailing lists outlining two hackfest options for Q1'2015
  • AoB

Minutes

  • Previous minutes approved
  • Ray presented the events proposals posted at https://wiki.opnfv.org/ under the "Community & Events" section
    • Good discussion on the Q1 Hackfest in Prague. Preference is Monday & Tuesday. LF team will work with ETSI to explore co-location opportunity. [Action Item: LF will also setup registration for the Hackfest once logistics are finalized.]
  • Board Meeting alternate: Chris proposed Frank Brockners as the TSC representative alternate when Chris can not attend board meetings. The TSC approved the proposal via a vote on IRC.
    • [Action Item: Ray to investigate the vote functionality on IRC]
  • Project Reviews
    • IPv6: Bin Hu (AT&T) presented the project proposal. There were good discussions on if the integration scripts will be upstreamed vs. residing in OPNFV, project duration, repository name, project outcome, etc. Bin made real-time updates on the wiki and the updated proposal was approved via a vote on IRC. Congratulations on being the first approved OPNFV project!
    • Doctor: Ashiq Khan (DOCOMO) presented the proposal. There was a question from Qiao Fu (China Mobile) if there's an overlap with the High Availability project, but there was a general consensus that the goal is not to eliminate possible duplication early in the life cycle. On the Doctor project, the general feedback from the TSC is that the scope maybe too board. Ashiq will edit the proposal to bring a Requirements Project for review at the future TSC meeting.
      • Based on discussions, there is probably a need to revise/clarify the OPNFV Project Lifecycle document. The process should not slow work/discussions with upstream projects. [Action Item: Chris Wright will will send an invitation to work on the Project Lifecycle]

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2014/opnfv-meeting.2014-11-25-14.59.html

TSC meeting November 18, 2014

Agenda

Minutes

  • Reminder on the antitrust compliance notice
  • Previous meeting minutes approved
  • Discussion on base distribution: Palani shared with the team that PackStack & CentOS looks like a good starting point. However, there were feedback that we may need more information filled out in https://wiki.opnfv.org/wiki/opnfv_distribution. There was a consensus to defer the base distribution decision.
  • "Get Started": This is to establish a 3-node baseline OPNFV deployment (2 control nodes and 1 computer note)
    • The 2 control nodes are intended for redundancy.
    • This could be part of the sandbox activity that the TSC already approved
      • Aric is the Linux Foundation contact for the sandbox
    • Suggestion to use a different name since "Get Started" sounds more like a documentation
  • Performance & Testing: Morgan provided an update for the sub-team. Project proposal will be submitted by next week
  • There was a good discussion on approval for project proposals
    • Clarity on project deliverables/outcomes would be helpful for project approval
    • For requirements & documentation projects, TSC will start reviewing projects next week
    • There's no deadline for submitting project proposals. Keep in mind that there's a 2-week review period before the TSC can approve them.
  • There has been some feedback that information is hard to find on the wiki. Ray will start a discussion on mailing lists to solicit ideas
  • There is a consensus to have a hackfest in Prague during ETSI NFV #9 meeting in February. Proposal to have Marie-Paule Odini (HP) talk to ETSI to explore co-locating.

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-meeting/2014/opnfv-meeting.2014-11-18-14.57.html

TSC meeting November 11, 2014

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • 2015 OPNFV events planning - Brandon Wick
    • Hackfest dates
    • OPNFV Summit
  • Project Status
    • Performance & Testing, status summary - testing team
    • CI, status update on discussion and manning - Uli
    • Technical discussion call update - Bin
  • Open Stack Summit Learning's
    • Summary and reflections - Dave Neary & Participants
    • 3rd Party CI for OpenStack - Chris & All
  • Follow-up on previous weeks' action items
    • Action Item: Aric will get together with Palani to make a proposal on getting a pool of development systems with needed resources
    • Action Item: Frank will send out an email to the community to see if there are objections to Ubuntu.
    • Action Item: Tapio to create a proposal about how to use Git and Gerrit to review project proposals
    • Action Item: Ray will send out a note to the mailing list to seek community feedback around opening the mailman archives.
    • Action Item: Ray to send email to the mailing lists outlining two hackfest options for Q1'2015
    • Action Item: Ray to propose TSC call time options to the mailing list.
    • Action Item: Dave Lenrow to propose initial release schedule on the WiKi
    • OPNFV release names
  • AoB

Minutes

  • Approval of previous minutes postponed. Ray to correct the action item for Tapio.
  • 2015 events plan by Brandon Wick (LF)
    • Brandon outlined event candidates for 2015. These are being discussed in bi-weekly marketing committee calls (Wednesdays at 7:30am PT).
    • OPNFV Summit targeted for Q3/Q4 next year.
    • Also looking at co-location opportunities for OPNFV hackfests. (Action Item: Ray to send out a poll for events that people are planning to attend in 2015)
  • Project Status
    • Test & Performance: Will propose infrastructure & platform characterization sub-projects. Trevor and team will come back with a more detailed presentation to the TSC next week.
    • CI: Uli is still waiting for resource commitments on the project proposal.
    • Requirements & Collaborative projects: Several projects are in public review window. Please familiarize yourself with these projects
    • Getting committers list is critical before the approval meeting.
    • Reminder on the process: Sending email to TSC mail list starts two week review window, after two weeks founders can request by email to TSC a creation review
  • OpenStack Summit update (Dave Neary)
    • Lots of NFV/sessions were well attended. See the Meetbot minutes below for links to sessions that were of particular interest.
    • OpenStack kilo M1 and M2 are critical dates for work proposed to support NFV
      • Ian Wells represented OPNFV at the OpenStack summit and agreed we would respect their dates
      • Need to have Ian on a call to determine if we need a separate project in OPNFV
  • Simultaneous Release: Dave Lenrow took an Action Item to schedule meeting this week to discuss SR strawman schedule and SR process proposals
  • Action items review
    • Linux distribution: Need a decision on this quickly. (Action Item: Palani to organize a meeting to get towards a decision)
    • Archives to TSC & Tech-Discuss mailing lists will now be open (i.e. you don't need to subscribe to the mailing lists)
    • New TSC meeting time: Ray to an Action Item to send out a poll on two proposed options.
    • Q1 Hackfests: Will have a hackfest at LF' Collaboration Summit since the space is free. For ETSI NFV#9 in Prague, Marie-Paule Odini drafted a liaison proposal and is on the agenda for the plenary meeting next week
      • Action Item: Ray to send another a poll to gauge community's interest in ETSI NFV#9 meeting.

Meetbot minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2014/opnfv-meeting.2014-11-11-15.01.html

TSC meeting November 4, 2014

Agenda

  • Approve previous minutes - Chris
  • Agenda Bashing - Chris
  • OPNFV developer tools/infrastructure - Aric
  • Project updates
  • Hackfest @LF Collaboration Summit (Feb 18-20, 2015) - Ray
  • Archives for the "tech-dicuss" mailing list - Ray
  • New meeting time for the TSC call
  • Board update

Minutes

  • Previous minutes approved
  • Aric gave an overview of developer tools/infrastructure available on opnfv. org (incl. Jenkins, Gerrit, Jira, etherpad, etc.)
    • Discussion on why login/password is required for etherpad. Aric to investigate options.
    • Action Item: Aric will get together with Palani to make a proposal on getting a pool of development systems with needed resources
    • Linux distro for the OPNFV stack: A suggestion was made for Ubuntu main trunk.
      • Action Item: Frank will send out an email to the community to see if there are objections to Ubuntu.
    • A wiki page for developer sandbox needs to be created. Palani will be the project lead. Interested contributors should contact Palani.
    • Action Item: Tapio to create a proposal about how to use Git and Gerrit to review project proposals
    • Action Item: Dave Lenrow to post draft Simultaneous release draft by 10/30 (Thursday)
  • A request to open the mailing list archives (without requiring subscription to the mailing list)
    • A general consensus is to open the archives. However, Ray will send out a note to the mailing list to seek community feedback (Action Item).
  • Q1'15 Hackfest options: One is at the LF Collaboration Summit in Sonoma. Another possibility is to co-locate with ETSI NFV#9 meeting in Prague.
    • At the LF Collaboration Summit, there's no cost for the room and is close to a lot of member companies in the Bay Area. Ray will go ahead and request a room.
    • For ETSI NFV meeting, Marie-Paule Odini @HP will contact Vanessa from LF' event team to explore options
    • Action Item: Ray to send email to the mailing lists outlining two hackfest options for Q1'2015
    • If anyone plans to blog from OpenStack Summit, please feel free to contact Prathima (pramesh@linuxfoundation.org) if you need any assistance.
  • Time for TSC call is not convenient for APAC with the end of day light savings time.
    • Action Item: Ray to propose options to the mailing list.
  • Project Status
    • CI: Need more feedback on the proposal. A meeting will be scheduled to discuss/review the proposal.
    • Two projects (IPv6 & Parser) are ready for the 2-week review period.
    • Bin Hu's Thursday meetings will be the venue to review project proposals.
    • Reminder on requirements for creating project. 1) email to TSC announcing project proposal and begin (minimum) two weeks public review 2) email to TSC asking to approve a project that has had at least two weeks public review
  • Chris provided an update from the November Board Meeting:
    • Chris informed the Board that:
      • We need more headcount assigned, more community engagement.
      • We need and are working on upstream project timing and implications for our relese

TSC meeting October 28, 2014

Agenda

  • Approve previous minutes - Chris
  • Agenda Bashing - Chris
  • OPNFV meetup in Paris - Chris
  • CI project update - Uli Kleiber
  • Test projects update - Trevor Cooper
  • Simultaneous Release update - Dave Lenrow
  • Release schedule, date and source project discussion - All
  • Upstream community projects discussion - All
  • Liaison with entities such as ETSI NFV SIG - All
  • OpenSource Vs Proprietary NVF testing - Palani / All
  • Release naming poll - Ray & Palani
  • New GoToMeeting account for project meetings - Ray
  • Any other business - All

Minutes

  • Previous minutes approved
  • OpenStack Summit in Paris
  • CI Update (Uli Kleber): Agreed to keep project proposal short and simple and focus on the problem statement. Push lots of detail to project work items later.
    • Action Item: Uli to submit an updated document by 10/30 (Thursday)
    • Discussion on creating a sandbox so people can start work before projects are approved.
      • Action Item: Ray to investigate with the LF infrastructure team
  • Test & Performance subteam update (Trevor Copper):
    • Weekly meetings on Thursdays as noted on the wiki.
    • Likely have separate projects for use cases and test infrastructure
  • Simultaneous release (Dave Lenrow)
    • Agreement to focus on the release process and delegate the peripheral problems to other projects and processes to solve.
    • Action Item: Dave to post draft Simultaneous release draft by 10/30 (Thursday)
  • Discussion on release schedule
    • Board is asking for a V1.0 release by March, 2015. Consensus is that we do not have enough information/progress to commit to this date.
  • Engagement with upstream communities: There was a discussion on formal liaison with upstream, but suggestion was made to bring OPNFV developers and requirements to upstream projects.
  • FOSS vs. private VNFs
    • Discussed that both FOSS & proprietary VNFs can be looked at. For proprietary VNFs, we need to consider issues around licensing, performance data, etc. If performance testing requires special integration to use vendor specific APIs, vendor can do that work
    • Action item: Test & Perf sub-team to make recommendations on VNFs
  • Suggestion was made to use "[Action Required]" in email subject line when sending e-mail to the lists requiring action from list members. Please use this sparingly.
  • New GoToMeeting account created for project meetings. Contact Ray at LF if you need to organize a meeting.

TSC meeting October 21st, 2014

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Discuss project proposals on the wiki (everyone who submitted proposals)
  • CI & Test infrastructure (Uli Kleber)
  • Simultaneous Release (Dave Lenrow)
  • Release naming poll (Palani/Ray)
  • Any other business

Minutes

  • Discussion on project proposals
    • Uli Kleber reviewed the CI proposal
      • Lots of details here including infrastructure that will be provided by LF (e.g. Gerrit, Jira, Jenkins, etc.)
      • Action Item: Need to draft a development process. Frank, Palani, Chris Price, and Tapio volunteered to start this. Palani will setup a call.
      • Action Item: Uli will setup a call to discuss the development process and co-existence with upstream projects. Will also discuss packaging tools during the meeting.
    • Testing Projects: Trevor Cooper from Intel setup a meeting on Thursday mornings at 7am Pacific Time
    • Ashiq Khan presented project proposals for resource management and fault management & maintenance
      • There was a discussion on contributors and committers. Consensus is that list of contributors & committers will remain open until the project approval vote by TSC.
    • Bryan Sullivan presented the proposal for virtual infrastructure deployment policies.
      • Seeking committers & contributors
      • A reminder that a project scope should be much bigger than a single release
    • Bin Hu reminded everyone that IPv6-enabled Vanilla OPNFV project proposal is also posted on the wiki
    • Action Item: Dave Lenrow to schedule a meeting to discuss simultaneous release planning.
  • Open Topics
    • There was a consensus to send out a poll to decide on release names (cities, gemstones, mountain, nobel prize winners, and rivers). Poll will be open until October 31.
    • Consensus to add liaison with external entities (e.g. ETSI NFV SIG) as an agenda topic next week
    • Reminder that the Daylight Savings time ends in Europe next week (a week before the US).

TSC meeting October 14th, 2014

Agenda

Minutes

  • Chris Price reminded attendees of the Antitrust Policy Notice posted on opnfv.org
  • Previous meeting minutes (from October 1st & October 7th) approved
  • Release Naming: Palani will work with Ray to get a poll out for voting on release name themes
  • Palani is proposing we get volunteers to build a prototype based on simply taking the upstream parts and building a test platform (e.g. OpenStack, ODL, etc) and establish baseline of upstream components. Palani will send an email to the list to solicit volunteers
  • Brandon/Prathima/Vanessa (LF) discussed the OPNFV marketing committee and event planning for 2015. For 2014, there will be a meet-up at the OpenStack Summit in Paris and there was a consensus to use create stickers (with OPNFV logo & URL) vs. ordering hoodies.
  • Aric/Clint (LF) will be setting up CI infrastructure (plan is to use the Google Compute Engine)
    • Aric/Clint can reach out to Uli/Palani/Ian who started thinking about CI & test infrastructure
    • Uli will post his document on CI & test infrastructure on the wiki by the end of this week
  • A suggestion was made to create a living document to capture components of interest that don't get included in a OPNFV release
    • Project proposal is not the same as project applying to join a simultaneous release (SR). We need to have a separate discussion on requirements to join a simultaneous release.

TSC meeting October 7th, 2014

Agenda

  • Approve previous minutes
  • Agenda Bashing
  • Project proposals and reviews
    • Establishing baseline project proposals
    • Project review process updates (4 week review phase)
  • Upstream community engagement and discussion
  • Simultaneous release project establishment
  • TSC call logistics for October 14th
  • Any other business

Minutes

  • Chris Price reminded attendees of the Antitrust Policy Notice posted on opnfv.org
  • Decided to defer approving previous meeting minutes until next week.
  • No new agenda topics proposed
  • Next week's TSC meeting will be shortened to an hour (8-9am Pacific Time) to accommodate the Board meeting in Düsseldorf.
  • Reminder to TSC members to send the delegate contact information to the TSC mailing list in case you are not able to attend. Proxy voting can be cast by the delegate or emailed to Ray Paik at the Linux Foundation (LF).
  • Project proposals and reviews
    • Project proposals should be posted at https://wiki.opnfv.org/project_proposals
      • Use the template on the wiki and send an email to opnfv-tech-discuss
    • A question was raised on when project proposals can be made. There was a general consensus that proposals can be made anytime. However, there would be a cutoff date for when a project will be included in a simultaneous release.
    • There was a proposal & discussion on reducing the review period for project proposals from 4 weeks to 2 weeks. TSC members voted on this proposal and there were no objections. LF will update the Project Lifecycle document on opnfv.org.
    • Upstream community
      • Based on discussions at the face-to-face last week, the proposal is to target stable releases of upstream projects (e.g. OpenStack Juno, ODL Helium, etc.)
      • Good discussion on effectively working with upstream projects: A liaison with upstream projects, have TSC oversight of people working upstream projects, etc. There was a general consensus that we can have a point of contact within TSC for upstream projects.
      • Proposed action item for the TSC: Write down timeline for integrating with upstream projects identified to-date
        • A gap analysis against upstream roadmaps will also be helpful
    • Simultaneous release
      • There was a consensus on the need to firm up the simultaneous release process
        • Dave Lenrow will post a draft proposal on the wiki. Palani Chinnakannan also offered to help with this.
    • Continuous Integration (CI) project proposal needs to be posted ASAP. Ian Well/Uli Kleber/Chris Wright have the action item to start drafting this.
    • The integration/testing project group has started scheduling follow-up meetings
    • A reminder that a project proposal mostly captures scope. There is not need to document implementation plans in detail
      • Once projects are approved, we need to create a project page on wiki and not make changes to proposal pages
    • There was a question on how people can get visibility into projects. Once projects kickoff, each will have regular (e.g. weekly) calls with IRC and information will be posted on the wiki. Anyone can join meetings and access the wiki.
    • A question on what will be accomplished in the first release. Some of the ideas suggested were things like data plane acceleration or distribution installer. However, it is probably too early to define the first release yet.

TSC meeting October 1st, 2014

Agenda/Minutes

  • Antitrust compliance notice read
  • TSC Chair Election:
    • Voting was done via paper ballots plus e-mail votes from three TSC members who could not attend the meeting.
    • Christopher Price (Ericsson) was elected as the first TSC Chair for OPNFV
  • Future TSC meetings: There was a consensus to keep the TSC meetings open to everyone. (Anyone will be able to participate, but only TSC members can vote) Decision was made to schedule TSC meetings every Tuesday 7-9am Pacific Time. Meeting will be done via phone & IRC. Will also investigate switching to GoToMeeting.
    • Face-to-face meetings: Will target 4 face-to-face meetings/year and look for events/conferences where a lot of TSC members will be in one place. Decision on the next face-to-face meeting can be made based on projects or project proposals.
  • TSC Vice Chair discussion: There was a general consensus not to have a formal TSC Vice Chair position. If Chris Price is not able to chair/attend meetings, he will ask other TSC members to help.
  • Getting to the first release in 1H'2015
    • Discussion ensued on the first OPNFV release and there was a general consensus on the following items.
      • Importance of identifying & working with upstream communities
      • Development & release processes need to be defined and posted on the wiki
      • Communicating to the Board what can be delivered in 1H'2015 (based on project proposals)

  • No labels