Anuket Project

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

Compare with Current View Page History

« Previous Version 504 Next »

Topics for OPNFV Board-TSC meeting on June 16th

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

June 27, 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

June 20, 2017 

Agenda

Minutes: 

  • Previous minutes approved
  • 2017 Summit recap: Brandon Wick noted that there were over 560 people at the Beijing Summit last week with several co-located events (e.g. ONAP, ODL, fd.io, etc.).  Summit recap page is at https://www.opnfv.org/opnfv-summit-2017-event-recap and all summit presentation videos should be available.
  • Danube/Euphrates update: Ray noted that Danube 3.0 is schedule for June 23rd and Euphrates MS 3.1 (basic health check) is due today.  On Danube 3.0 Morgan noted that there were not enough test results and the quality is worse than Danube 1.0.  Suggestion was made to move the discussion to the release call. 
  • Graduation review discussion: Tapio noted that the functest team came forward with the graduation review proposal and covers areas such as activities, contributors, accomplishments, etc. over past releases.  The proposal will also be reviewed on Thursday's Weekly Community call.  There was a question if other projects in the future need to follow Functest graduation review proposal as a template, and Jose replied that the Functest presentation should be viewed as an example.  Past discussions on the graduation review can be found at https://wiki.opnfv.org/display/PROJ/Graduation+review+discussions 
  • June Board meeting update: Tapio discussed that there were a lot of conversations around project harmonization in the Board meeting and potential impact on TSC composition.  Fatih/Frank also shared the proposal for Lab-as-a-Service (LaaS) that will require resources for HW equipment and support services.  Infra WG will send an invite out to the wider community before Infra WG addresses this topic in their next meeting.   
  • Euphrates MS3 exception review for Compass:  Chigang explained the need for milestone exception for the Compass team and noted that they are asking for delay in MS 3.0 & 3.1 but plan to get caught up my MS 3.2 (July 11th). Via IRC vote, the TSC approved MS3 exception for Compass.
  • TSC meeting time: Ray proposed moving the TSC call an hour earlier (6am Pacific Time) to better accommodate community members in Asia.  Ray will continue the discussion on the mailing list.  
  • Dovetail discussion: Tim Irnich noted that the Dovetail team is looking for actionable feedback from the TSC and there's a new email thread seeking feedback at https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-June/016631.html 

     

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-06-20-14.00.html 

June 13, 2017 (During Design Summit)

Agenda

Meeting Minutes: 

  • Previous minutes approved.
  • Danube 3.0 update: David McBride noted that the TSC approved the new Danube 3.0 release date of June 23 with micro-milestones as outlined in https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-June/016614.html
  • Euphrates Exception milestone reviews: Bob Monkman noted that Armband is reliant on Fuel installer that is going through major changes and a lot of manual work is involved for the new Fuel installer and the team is playing catch-up (have a target getting "caught-up" my MS5 on July 28th).  Armband is also working with the Apex team as another installer option (targeting trial deployment in the next few weeks).  Via IRC vote, the TSC approved the ArmBand Exception Review.  For the Compass team, suggestions were made to postpone the Exception Review as the project team was not available.  
  • TSC composition: Tapio notes that there were discussions on the TSC composition during the design summit yesterday.  One of the proposals was to limit the size of the TSC to 15 members and have 2 elections (i) for TSC members among Platinum members and (ii) among committers at large prior to transitioning to fully merit-based TSC.  Tapio added that that when OPNFV was formed TSC members were populated from Platinums for boot strapping, but there have been discussions of going to fully merit-based TSC.  There were discussions on how we’d know if the new TSC would be more effective and collecting issues with the current TSC composition.  
  • AoB: 
    • There was a suggestion to add graduation review discussion to next week’s TSC call. 
    • A wiki page for TSC’s feedback on Dovetail will be created after the Dovetail breakout session during the design summit.
    • Bryan announced that he created a new OPAP community wiki page (https://wiki.opnfv.org/display/COM/ONAP) and asked community members to contribute to the page.       

MeetBot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-06-12-23.59.html

June 6, 2017

Agenda

Minutes:

  • Previous minutes approved
  • Design Summit/Summit update: Brandon noted that there will be co-locates events for ONAP, OpenDaylight, fd.io, CNCF, Open-NFP during the Design Summit (Mon-Tue).  There is also a plan for community demo during the keynotes and Annual Awards.  Speakers are reminded to register soon and upload their presentations.  Local member companies are also encouraged to help promote the event in China.
  • Joint TSC-Board meeting: Tapio reviewed the meeting agenda as captured in the wiki page.
  • Renaming vina project: Koren noted that no code has been committed to the repo yet and would like to to change the name to Calipso as there was an internal conflict with the original name.  Via IRC vote, the TSC approved changing the project name to Calipso.
  • Danube/Euphrates planning and update: 
    • David McBride shared that Euphrates MS 3 was last week and have full compliance except from Compass/Armband.  Exception requests have been submitted by both projects and will be reviewed by the exception committee.  MS4 is this week for test framework readiness.
    • Danube 3.0 is this Friday and formal testing needs to be wrapped up today plus repo tagging should be done by EOD June 8th.  Mark Beierl added that Storperf will have challenges meeting the Danube 3.0 deadline.
  • Dovetail: Tapio/Wenjing noted that there has been a lot of discussion on mandatory/optional tests, test scope, etc.  There is also a plan to get EUAG feedback at the face-to-face meeting in Beijing next week.  There was a discussion on mandatory tests having the goal of broader scenario coverage.  In other words, CVP tests should be able to run on more than one scenario as described in the requirements document: "Tests must not require a specific NFVi platform composition or installation tool."  Frank also made a suggestion to have the scope document also reviewed by the TSC.  

 

MeetBot Minutes:

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

May 30, 2017

Agenda

Minutes:

  • Previous minutes approved
  • Annual awards vote reminder: Ray encouraged community members to vote on the annual awards before the poll closes tomorrow.
  • Danube/Euphrates planning and activities: 
    • David McBride noted that there was a full compliance on MS2 for Euphrates (after Escalator decided to drop out of the release).  MS3 (installer integration) is today and David will be following up with installer PTLs.  David also reviewed 3 sub-milestones (below) for MS3 and noted that there's no change to the overall release schedule.  There was also a discussion of having a similar milestone for Kubernetes although Functest+Kubernetes integration is still in progress.  
      • MS3.0: OpenStack integration + nosdn/no feature + Functest support for health check
      • MS3.1: installers passing health check
      • MS3.2: deploying integrated SDN scenario and passing health check
    • MS3 MS4 changes.pdf
    • Via IRC vote, the TSC approved the sub-milestones for MS3.  
    • Danube 3.0 is scheduled for June 8th and David will also start a daily stand-up meeting (IRC only)
  • Dovetail discussion: Wenjing reviewed the CVP process and files for test cases (e.g. for BGPVPN).  The plan at the Summit is to introduce the CVP (e.g. our intent), but not officially launch the program.  There was a good discussion on mandatory vs. optional tests as all mandatory tests in Dovetail at this point are a subset of OpenStack tests .  Individual project teams have been making decision on mandatory/optional tests, but Dave Neary added that the focus within the Dovetail team so far has been on documentation prior to test cases becoming mandatory.  There was a consensus that the Dovetail team is heading in the right direction, but also a discussion that it would be good to evaluate key features of OPNFV releases (e.g. as reflected in marketing messages).  There was also a comment from the Dovetail team that it'd be good to get input from the TSC on what additional tests would be valuable to be added to the test suite.  

MeetBot Minutes:

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

May 23, 2017

Agenda

Minutes: 

  • Previous minutes approved.
  • Termination review for Movie project: Uli shared that that project team (incl. the PTL) has been reassigned to other work and no other community volunteers stepped forward to carry on with the work.  Via IRC vote, the TSC approved termination of the Movie project.  
  • Fuel/MCP update: Greg noted that Fuel installer has switched technology to MCP as now the emphasis is more on operating clouds (vs. installation).  MCP 1.1 (schedule for Q2'17) will have experimental support for OpenStack Ocata.  Greg added that work is in progress to support dynamic POD descriptor file and plan is to convert every scenario (with the exception of ONOS) to MCP.  The Fuel team will have challenges meeting installer related milestones for Euphrates, but are doing their best and will let community know if there are schedule slips.  There was a suggestion to add MCP training session during the Design Summit in Beijing.  
  • June TSC-Board meeting: Tapio noted that there will be a joint Board-TSC meeting on Friday after the Summit in Beijing and shared proposed agenda topics on the wiki.   Frank made a suggestion that it maybe premature to cover release model and container/kubernetes topics.  A few other suggested topics were XCI update (if there's a Board request) plus Design Summit report out.  
  • Danube/Euphrates planning and activities: David McBride noted that Euphrates Milestone 2 (test case documentation) was yesterday, but only received report from ~40% of participating projects.  David also discussed breaking out MS 3 (installer integration).    MS 3.0 will include nosdn deploy + Functest support for health check, MS3.1 is installers passing health check, and MS 3.2 include deployment for SDN controller and passing health check.  David also suggested repurposing MS4 as "test framework ready."  

 

MeetBot Minutes: 

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

May 16, 2017

Agenda

Minutes: 

  • Previous minutes approved
  • Annual awards and Design Summit update: Ray reminded community members to add nominations for community awards at 2017 Annual Award Nominations (nomination closes on May 22nd).  Award winners will be announced at the Summit.  Speakers for selected Design Summit sessions will be notified shortly and the schedule will be posted at Beijing Design Summit Schedule (in addition to the Summit Schedule page).  Community members are also encouraged to add their breakout sessions on the wiki page.  
  • Danube/Euphrates planning and activities: David McBride encouraged PTLs to complete the scenario status page and gave a reminder that Milestone 2 for Euphrates (test plan ready) is coming next week.  On Milestone 3, David noted that an effort will be made to have better visibility as that was one of the challenges in Danube.  David will also come to the TSC with a proposal to break Milestone 3 into several steps.  Danube 3.0 is scheduled for June 8th and David will also propose micro-milestones for testing/documentation leading up to Danube 3.0.  
  • TSC composition: Tapio noted that he posted his initial presentation and summarized different options for TSC composition at TSC composition discussion.  Community members are encouraged to add comments/feedback on the page leading up to the TSC meeting in Beijing.  
  • Dovetail update: Wenjing noted that there's a documentation on test suite that will be ready by the end of the day and TSC members will have 2 weeks to review prior to a vote on May 30th.  Wenjing added that there maybe a few more revisions in the next few days.  There was a good discussion on approval criteria, and Trevor Copper made a comment that the TSC should be evaluating the completeness of the CVP test solution to establish a compliance program. The TSC needs to provide a judgment call on solution's launch readiness for commercial evaluations and application of the OPNFV brand.

MeetBot Minutes: 

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

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

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

  • No labels