Page tree
Skip to end of metadata
Go to start of metadata

Welcome to the OPNFV release meeting page.

Logistics

  • Weekly on Tuesday, 7:00am - 8:00am Pacific Time (15:00 UTC Find your local time  when US in Standard Time /  14:00 UTC when US in Daylight Savings Time Find your local time ).  
  • Chaired by David McBride (Linux Foundation)
IRC:  
GTM:

Call logistics (GoToMeeting):Please join my meeting from your computer, tablet or smartphone.

https://www.gotomeeting.com/join/285662629

You can also dial in using your phone.Australia: +61 2 8355 1039
Australia (toll-free): 1 800 189 049
Canada: +1 (647) 497-9379
Canada (toll-free): 1 888 299 1889
China (toll-free): 4008 866143
France: +33 (0) 170 950 589
France (toll-free): 0 805 541 043
Germany: +49 (0) 692 5736 7301
Germany (toll-free): 0 800 723 5120
Hong Kong (toll-free): 30713171
India (toll-free): 000 800 852 1424
Ireland (toll-free): 1 800 946 534
Ireland: +353 (0) 15 360 757
Israel (toll-free): 1 809 452 627
Japan (toll-free): 0 120 352 900
Korea, Republic of (toll-free): 0806110880
Russian Federation (toll-free): 8 800 100 6217
Spain: +34 932 75 1230
Spain (toll-free): 800 900 578
Sweden: +46 (0) 852 500 516
Sweden (toll-free): 020 980 768
Taiwan (toll-free): 0 800 666 674
United Kingdom: +44 (0) 330 221 0099
United Kingdom (toll-free): 0 800 031 4726
United States: +1 (669) 224-3318
United States (toll-free): 1 866 899 4679

Access Code: 971-789-629

October 24, 2017

Agenda

  • Schedule Review
    • Euphrates wrap-up
      • Download page goes live TODAY!
    • Fraser
      • Nov 3 - MS1
        • Release plans
        • Intent-to-participate window closes
      • Nov 17 - MS2
        • test cases documented in test case database
  • Docker containers as a release vehicle
  • Logging
  • Tracking installer status after MS3
    • os.nosdn.nofeature.noha
    • os.<sdn>.nofeature.noha

Minutes

Actions

Meetbot Minutes

October 17, 2017

Agenda

  • Upcoming milestones
    • Euphrates
      • TODAY! - MS8 - Formal test execution completed
      • October 18 - MS9 - Documentation updated
      • October 19 - MS10 - JIRA cleanup
      • October 20 - MS11 - Tag repos / technical release of 5.0
    • Fraser
      • Nov 3 - MS1 - Release plans
  • Follow-up on testresults.opnfv.org
    • Landing page
    • Web page generation
  • Observations about testresults dashboard
  • Tracking status of os.nosdn.nofeature.noha after MS3
  • Proposal: Lock version of ODL after MS3

Minutes

  • Schedule review
    • Euphrates
      • Euphrates 5.0 approved for release on Friday, per the revised schedule
      • Today (Oct 17) is the completion of formal testing
      • Scenario owners should revise intent to release for scenarios that are failing deploy
      • Oct 18 (tomorrow) - final documentation
      • Oct 19 - JIRA cleanup
        • issues either closed or the "fix version" field updated to a future release
        • no issues should be assigned to 5.0.0 or older versions
        • David McBride to look into updating release status for current and past release versions in JIRA
      • Tag repos on Friday, Oct 20
      • Jose Lausuch to update script that's used for tagging containers to use revised naming convention
      • Gerald Kunzmann asks whether LF will tag repos
        • David McBride says that first preference is for PTLs to tag own repos, but then LF (Aric) will tag any that have not been tagged by Oct 20
    • Fraser 
      • David McBride says that Fraser release page is in place
      • MS1 is Nov 3
      • two events: 
        • intent to participate window closes
        • project release planning due
      • David McBride requests that PTLs add their release plans and scenarios using the links on the Fraser release page  
  • test results landing page (testresults.opnfv.org)
    • David McBride says that LF considers test results web server and pages a community application.  Therefore, the community needs to update it and maintain it.
  • Proposal to lock down ODL after MS3
    • No objections
    • Tim Rozet says that Apex usually settles on a version of ODL long before MS3
  • AoB
    • ODL
      • Tim Rozet says that floating IP issues are an ongoing problem, crossing multiple major releases
      • Do we need another meeting with ODL team?
    • Logging
      • need releng tool to extract logs for ODL, OVS, etc. (not a functest issue)
      • continue discussion in weekly technical call and/or infra call
      • David McBride to request agenda space for log discussion

Actions

  • David McBride Follow up with scenario owners whose scenarios are failing the deploy step
  • David McBride investigate setting old OPNFV versions as "released".
  • Jose Lausuch update script used to tag containers with revised release naming convention
  • David McBride request agenda space to discuss logging issue

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-release/2017/opnfv-release.2017-10-17-14.00.html

October 10, 2017

Agenda

  • Upcoming milestones
    • Euphrates
      • October 17 - MS8 - Formal test execution completed
      • October 18 - MS9 - Documentation updated
      • October 19 - MS10 - JIRA cleanup
      • October 20 - MS11 - Tag repos / technical release of 5.0
    • Fraser
      • Nov 3 - MS1 - Release plans
  • Huawei lab status
  • Branching improvement

Minutes

Actions

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-release/2017/opnfv-release.2017-10-10-14.03.html

October 3, 2017

Agenda

  • Upcoming milestones
    • Euphrates
      • October 17 - MS8 - Formal test execution completed
      • October 18 - MS9 - Documentation updated
      • October 19 - MS10 - JIRA cleanup
      • October 20 - MS11 - Tag repos / technical release of 5.0
    • "F" - release
  • CI/CD status post-branch
    • docker builds
    • update on Intel lab (Jack Morgan)
      • Installer POD allocation
    • test results dashboard update
  • ODL issues (Tim Rozet)
  • Documentation

Minutes

  • Review of Euphrates schedule
    • release delayed to Oct 20
    • will also likely eliminate the Nov 10 point release
      • TSC to vote Oct 10
    • download page will go live on Oct 24 (tentative)
  • Review of F-release schedule
  • CI/CD
    • Cristina Pauna says that ArmBand project continuing to work on YardStick integration with MCP
    • release engineering team has workaround to Intel lab firewall issue
    • Trevor Bramwell says that workaround is strictly temporary and will be removed once jmorgan1 request to corp IT has been resolved
  • Docker builds
    • Mark Beierl says that docker build performance has improved 
    • Morgan Richomme says that we need a more consistent approach to docker builds 
    • Alec Hothan agrees that we need an improved approach to container use within OPNFV 
    • should RELENG take responsibility for implementing a consistent docker build service for all projects? 
    • alec hothan says that we need tagging proposal for docker containers for Euphrates 
    • List of projects that create docker builds via releng: releng-anteater, bottlenecks, cperf, dovetail, functest, nfvbench, qtip, storperf, yardstick
    • Should be a topic for discussion at the plugfest

Actions

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-release/2017/opnfv-release.2017-10-03-13.59.html

September 26, 2017

Agenda

Minutes

Actions

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-release/2017/opnfv-release.2017-09-26-14.01.html

September 19, 2017

Agenda

  • Upcoming milestones
    • October 3 - MS8 - Formal test execution completed
    • October 4 - MS9 - Documentation updated
    • October 5 - MS10 - JIRA cleanup
    • October 6 - MS11 - Tag repos / technical release of 5.0
    • October 10 (tentative) - Download page goes live
  • CI/CD status post-branch
  • ODL issues

Minutes

  • Schedule review
    • Possible issue due to Chinese national holiday during first week of Oct.  David McBride to reach out to PTLs to gauge impact.
    • Issue in Intel lab may impact some projects (Intel Lab)
  • CI status
    • Jose Lausuch says that functest has been enabled on stable/euphrates
    • Fatih Degirmenci says jobs for stable branch have been created
    • Mark Beierl says that the stable jobs for docker is controlled by the releng/jjb/releng/opnfv-docker.yml file. Right now I have only done that for StorPerf. 
    • Mark Beierl says that each PTL needs to create a patch in releng for releng/jjb/releng/opnfv-docker.yml to update their Euphrates docker jobs
    • First projects that have Docker images must propose and have docker builds merged for Euphrates. Then the daily jobs can be created for Euphreates.
    • Mark Beierl says that pushing to Docker hub is giving "denied: requested access to the resource is denied" for at least my StorPerf jobs...
    • the full list of projects that need to update their docker jobs are: bottlenecks, functest, qtip, yardstick, releng-anteater, cperf, dovetail, nfvbench
  • ODL
    • Tim Rozet reports that ODL tests are now passing for "noha" scenarios
  • AoB

Actions

  • David McBride reach out to PTLs to determine which projects are affected by the Chinese holiday during the first week in October
  • Mark Beierl coordinate with PTLs to update docker yaml file

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-release/2017/opnfv-release.2017-09-19-13.54.html

September 12, 2017

Agenda

  • MS7 - Stable branch window closes.  All projects branched. Friday, Sept 15.
  • Upcoming
    • October 3 - MS8 - Formal test execution completed
    • October 4 - MS9 - Documentation updated
    • October 5 - MS10 - JIRA cleanup
    • October 6 - MS11 - Tag repos / technical release of 5.0
    • October 10 (tentative) - Download page goes live
  • "F" release schedule review
  • More on JIRA cleanup
    • Fix version field
    • Valid versions
      • 5.0.0
      • 5.1.0
      • 5.2.0
      • 6.0.0
      • Future Version

Minutes

  • MS7
    • scheduled for Friday, Sept 25
    • PTLs contact Aric when ready to branch
    • Jose Lausuch points out that releng should not be branched at this time
      • Agreement to not branch releng. However, should it be tagged?
    • Jack Morgan asks about the best way to contact Aric
    • Jose Lausuch requests that Functest be the last to branch to avoid breaking builds
  • Upcoming milestones
  • F-release schedule
    • TSC approved proposed schedule in today's meeting.
    • A link to the schedule is available in the agenda for the Sept 12 TSC meeting.
  • JIRA cleanup 
    • David McBrideasks teams to use "official" release names, e.g., 5.0.0, 5.1.0, 5.2.0, 6.0.0, 6.1.0, 6.2.0, or "Future Release" 
    • Filter 

Actions

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-release/2017/opnfv-release.2017-09-12-14.00.html

September 5, 2017

Agenda

  • Euphrates MS7 - Release Branch closes (Sept 15)
  • Installer status

Minutes

  • MS7 - stable branch window closes
    • scheduled for Sept 15
    • PTLs should contact Aric Gardner when they are ready to branch their project
  • Installer stability
    • Tim Rozet says that early bugs in Apex have been resolved
    • Still struggling with ODL issues that impact all installers.
    • Cristina Pauna says that ArmBand is making good progress.
  • AoB
    • David McBride reminds PTLs to update old JIRA issues, per the recent email.
    • julien zhang says that the access issue of securedlab is resolved, and now most of lab owners are submitting the PDFs.

Actions

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-release/2017/opnfv-release.2017-09-05-13.58.html

August 29, 2017

Agenda

  • Euphrates MS5 - follow-up on Milestone Exceptions
  • Euphrates MS6 - Test Case Implementation / Prelim Doc / Stable branch opens (Aug 25)
  • Euphrates MS7 - Release Branch closes (Sept 15)

Minutes

  • MS5 Exceptions
  • MS6 
    • David McBride says that reporting on MS6 is about 75% complete
    • Mark Beierl says that the StorPerf project is moving documentation currently in the wiki to the standard OPNFV documentation format (ReadTheDocs).
    • Frank Brockners says that the Bamboo project will likely not have any documentation for the Euphrates release.
  • MS7
    • David McBride reminds the team that project PTLs may branch their project any time between MS6 and MS7 (i.e., Aug 25 - Sept 15).
    • Frank Brockners requests that David McBride post instructions for branching.
  • AoB
    • Tim Rozet asks about when CI resources may be diverted from previous release.  Installer teams do this on an ad hoc basis, typically following the second SR.  However, there is no formal policy.  David McBride to make policy official.

Actions

  • David McBride post instructions for branching
  • David McBride define formal policy for moving CI resources from old release to current release.

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-release/2017/opnfv-release.2017-08-29-14.00.html

August 22, 2017

Agenda

  • Euphrates MS5 - follow-up on Milestone Exceptions
  • Euphrates MS6 - Test Case Implementation / Prelim Doc / Stable branch opens THIS WEEK (Aug 25)
  • Euphrates MS7 - Release Branch closes (Sept 15)

Minutes

  • MS5 - milestone exception status
    • Frank Brockners reports that the FDS project is on schedule to complete the milestone exception plan.
    • Frank Brockners reports that the Calipso project is working on a scenario to use as the base for a post-install deployment.
      • Frank also notes that the security issue identified by the anteater scan tool (Luke Hinds) is an artifact of the tool and not necessarily a true security issue.
  • MS6 - Aug 25
    • David McBride reminds team of requirements:
    • MS6 also opens the stable branch window
  • MS7 - Sept 15
    • Closes stable branch window.  All projects must be branched at this point.
  • AoB
    • Mark Beierl asks about integrating StorPerf with Installer
    • Tim Rozet suggests that this could be done with the Apex installer
    • Mark Beierl says that proposal is to add StorPerf similar to the ci/daily.sh from its git repo. This will create as many VMs as there are Ceph nodes detected, with a volume size of 1GB, fill them with random data, and then run 10 minutes of random read/write tests with block size of 16k and queue depth of 4. Should take less than 30 minutes total.

Actions

  1. Mark Beierl Tim Rozet to coordinate on integrating StorPerf with Apex operation.

Meetbot Minutes

http://meetbot.opnfv.org/meetings/opnfv-release/2017/opnfv-release.2017-08-22-14.02.html

August 15, 2017

Note:  David McBride is on vacation, so Ray Paik is hosting.

Agenda

  • Euphrates MS6 - Test Case Implementation / Prelim Doc / Stable branch opens (Aug 25)
  • Euphrates MS7 - Stable Branch closes (Sept 15)

Minutes:

  • On MS5, there was a good discussion on tracking compliance for scenarios vs. projects and how future exception requests should be handled with scenario owners/PTLs.  
  • If the assumption is that non-HA will work based on HA scenarios, these need to be stated explicitly.  Some projects are opting not to release/test non-HA scenarios.  
  • MS6 (test case implementation & preliminary documentation) is next Friday (August 25th).  Stable branch window will also open on August 25th.

Actions

  • Ray to follow-up with OVNO team on their MS5 status
  • Ray to work with David (when he returns) on milestone tracking of scenarios and follow-up on non-HA scenarios

 

Meetbot Minutes:

http://meetbot.opnfv.org/meetings/opnfv-release/2017/opnfv-release.2017-08-15-14.00.html

August 8, 2017

Note:  David McBride is on vacation, so Ray Paik is hosting.

Agenda

Minutes

  • Additional 2 weeks for MS5 is helping many projects with milestone compliance.  However, projects like FDS is still dealing with upstream ODL issues as the ODL community is dealing with Karaf migration.  
  • For MS6, Morgan noted that work needs to be done with test case integration for feature projects (in Functest). 
  • There was a discussion that it will be difficult to agree on "common" tests for ODL and it would be preferable to give scenario owners the choice on what needs to be tested. 

Actions: 

Meetbot Minutes: 

http://meetbot.opnfv.org/meetings/opnfv-release/2017/opnfv-release.2017-08-08-14.00.html 

August 1, 2017

Agenda

  • Euphrates MS5 - Scenario integration (July 28)
  • Euphrates MS6 - Aug 11
  • Vacation - Aug 7 - 18

Minutes

  • MS5
    • Rescheduled to Aug 11, due to revised schedule approved by TSC on Aug 1.
    • David McBride asks PTLs who filed milestone exception requests to add a comment to the request page, withdrawing the request.  This assumes that the revised schedule makes the exception request no longer necessary.
  • MS6
    • Rescheduled to Aug 25, due to revised schedule approved by TSC on Aug 1.
    • Trevor Cooper points out that a page titled "Euphrates Priorities", which is labeled "Draft," and is incomplete, could be potentially confusing to new users.  David McBride will follow up.
  • AoB
    • David McBride will be on vacation Aug 7 - 18.  Ray Paik will be hosting the release meeting on Aug 8 and Aug 15.

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-08-01-14.03.html

July 25, 2017

Agenda

  • Euphrates MS5 - Scenario integration (July 28)
  • Euphrates MS6 - Aug 11
  • Vacation - Aug 7 - 18

Minutes

  • MS5 
    • Ulrich Kleber asks when scenario status page should be frozen.  David McBride will come up with proposal.
    • Tim Rozet reports that the Apex team is having difficulty meeting MS5 due to the slip in Danube 3, which required ongoing work on Danube longer than expected.
    • David McBride reminds team about the new milestone exception request page.
      • Tapio Tallgren asks about how reviews will be conducted and asks whether we could use the wiki comment mechanism.
  • MS6 (Aug 11)
    • Requirements:
      • Test case implementation completed
      • Preliminary documentation 
    • Stable branch window opens (i.e. Aug 11 - Sept 1)
    • New wiki page for tracking details of documentation compliance
      • Includes sections for both MS6 (prelim) and MS10 (final)
      • PTLs complete the table row for their project, for the relevant milestone, then release manager updates MS compliance page
  • AoB
    • David McBride will be out on vacation from Aug 7 - 18
    • Ray Paik will be hosting the release meeting while David is out, on Aug 8 and Aug 15.

Actions

  • David McBride develop proposal for when to freeze the scenario status page
  • David McBride send email to review team explaining how reviews will be conducted in the wiki

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-07-25-14.04.html

July 18, 2017

Agenda

  • Danube 3 wrap-up
  • Euphrates MS5 - Scenario integration (July 28)
  • Euphrates MS6 - Aug 11
  • Naming scenarios that use ODL (i.e. odl_l2, odl_l3 ==> odl)
  • ODL Nitrogen (RC - Aug / release - Sept)
    • Karaf 4

Minutes

  • Danube 3 
    • release was completed July 14 and the download page went live on July 17.
  • MS5 - July 28
    • Requirements
      • Scenario integration
      • Feature freeze
    • Cristina Pauna says that Armband will successfully complete it's milestone exception recovery plan and rejoin the Euphrates release schedule as of MS5.
      • Note that Fuel/MCP is currently only supporting virtual deployments.
  • MS6 - Aug 11
  • ODL scenario naming
    • Some projects still naming ODL scenarios with "odl_l2" or "odl_l3" nomenclature.
      • Should these be replaced with simply "odl"
      • Cristina Pauna says that we should maintain distinction at least for Euphrates release.
      • Ulrich Kleber takes an action to work with Tim Irnich to produce a proposal
  • ODL Nitrogen
    • RC in August
    • Release in Sept
    • Primary change is integration of Karaf 4
    • After Nitrogen, ODL will switch to a 6-month cadence

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-07-18-14.02.html

July 11, 2017

Note new time, beginning this week, 6 a.m. Pacific!

Agenda

  • Danube 3 (Friday, July 14)
    • Weds, July 12 - complete testing
    • Thurs, July 13 - update documentation / JIRA cleanup
    • Fri, July 14 - tag repos
    • Download page will go live the following week
  • Euphrates MS3.2 - Installers able to deploy scenario with integrated SDN controller and pass health check (July 11 TODAY)
  • Euphrates MS5 - Scenario integration (July 28)

Minutes

  • Danube 3
    • Continued discussion from TSC meeting about whether we should release D3 this week, as planned, postpone it, or cancel it.
    • Due to the D3 release being delayed, some project teams may have already tagged their repos.  Advice from the release engineering team, in that case, is to tag as 3.1 instead of 3.0.
    • Release schedule for D3:
      • July 12 - complete testing
      • July 13 - complete documentation update and JIRA cleanup
      • July 14 - tag repos
      • Download page will go live July 17 or 18
  • MS3.2 
    • Jose Lausuch reports that health check is now fully supported in Euphrates
    • Tim Rozet reports that Apex is passing requirements for MS3.2
    • Justin chi reports that Compass team is on track with their MS exception recovery plan
    • David McBride asks Bob Monkman and Justin chi to be prepared to discuss their respective recovery plans at next weeks TSC cal
    • Discussion about blacklisting tests.  David McBride takes action to create process for managing blacklisting and ensuring transparency. 
  • MS5 - Scenario integration / feature freeze (July 28)
    • David McBride to follow up with feature projects to promote compliance.

Actions

  • Ray Paik Start vote on release of Danube 3 on July 14
  • David McBride contact feature projects to ensure awareness of and compliance with MS5

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-07-11-14.02.html

July 4, 2017 (CANCELLED)

June 27, 2017

Agenda

  • Danube 3.0 (TBD)
  • Euphrates MS3.1 (June 20 - installer nosdn/nofeature scenario passes health check)
  • Euphrates MS3.2 (July 11 - installer sdn scenario passes health check)
  • Euphrates MS5 (July 28 - scenario integration / feature freeze)
  • Reminder - Danube daily release meetings (next meeting Thurs, June 29)
  • Reminder - no meeting next week due to July 4 holiday in U.S.

Minutes

  • Danube 3
    • Mark Beierl believes that the problem with the Intel POD has been resolved.  Ross Brattain to follow up.
    • Justin chi reports that onos-sfc will soon be deploying with Compass on baremetal.
    • Jose Lausuchreports that recent patches on Apex are improving nosdn and odl/nofeature scenario performance on Functest.
  • MS3.1 compliance
    • Apex, Daisy, Fuel, Joid
    • Compass operating under milestone exemption
  • MS3.2 - July 11
  • MS5 - scenario integration
    • David McBride to follow up with new projects to ensure compliance
  • Documentation for Danube 3
    • David McBride to follow up with owners of new scenarios to ensure that they are prepared to deliver documentation
    • Justin chi reports that Compass team has a plan for documentation of onos-sfc scenario.  Justin to follow up with Sofia Wallin.

Actions

  • David McBride - follow up with new feature projects to ensure that they understand MS5
  • David McBride - follow up with owners of new scenarios for D3 to ensure that they are prepared to deliver scenario documentation

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-06-27-15.04.html

June 20, 2017

Agenda

  • Euphrates MS3.1 (June 20 - installer nosdn/nofeature scenario passes health check)
  • Danube 3.0 (June 23)

Minutes

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-06-20-15.02.html

June 13, 2017 

Note:  This will be a face-to-face meeting at the OPNFV Design Summit in Beijing.  The meeting will be held at 4 p.m. in the Pastel Room at the JW Marriott Beijing.  If you aren't available to attend F2F, the meeting will also be on IRC (opnfv-release).

Agenda

  • Euphrates MS3.1 (June 20 - installer nosdn/nofeature scenario passes health check)
  • Danube 3.0 (June 23)

Minutes

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-06-13-08.16.html

June 6, 2017

Agenda

  • Euphrates MS3 (May 30 - installer / OpenStack integration)
  • Euphrates MS4 (June 5 - test framework readiness)
  • Danube 3.0 (June 8)
  • Reminder about June 13 and June 20 meetings.

Minutes

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-06-06-15.03.html

May 30, 2017

Agenda

  • Euphrates MS2 (test case documentation)
  • Euphrates MS3 (May 30 - installer / OpenStack integration)
  • Danube 3.0 (June 8)
  • Danube Retrospective (continued)

Minutes

  • Milestone 2 (test case documentation ) 
  • MS3 - installer / openstack integration
    • MS3 now split into 3 sub-milestones: 3.0, 3.1, 3.2 
    • question: is virtual deployment sufficient for MS3.0? 
      • Tim Rozet says that baremetal deployment should be available on Apex this week 
      • Gregory Elkinbard believes that Fuel should be ready on virtual this week 
      • Maryam Tahhan would like to see support in both virtual and baremetal as soon as possible 
        • Maryam Tahhan says that there are subtle differences between the virtual and physical installs 
    • Frank Brockners points out that for MS3 and OS integration, virtual deployment should be sufficient 
  • Danube 3 - June 8
    • David McBride announces that the daily release meeting begins tomorrow (6:30 a.m Pacific -- IRC ONLY)
    • David McBride asks scenario owners to check the scenario status page and make sure that intent-to-release is accurate 
    • Jack Morgan points out that there may be some network interruption in HF2, due to some changes that Intel IT is making this week 
  • Danube retrospective
    • ARM architecture - Functest separating test results for ARM / non-ARM 
  • health check
    • Jose Lausuch says that there may be some problems with health check

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-05-30-15.01.html

May 23, 2017

Agenda

Note:  agenda was changed at the last minute due to a request from the TSC to continue the conversation about MS3 in the release meeting.

  • Changes to MS3 (Installer / OpenStack integration)
  • Danube Retrospective (continued)
  • Euphrates MS2 (test case documentation)
  • Euphrates MS3 (May 30 - installer / OpenStack integration)
  • Danube 3.0 (June 8)

Minutes

  • Changes to MS3 (Installer / OpenStack integration) 
    • Ulrich Kleber asks if the change will increase the total time of the release cycle
      • No - the changes to not add or remove time to complete the integration.  They simply add more granularity and transparency.
  • Test case documentation (MS2 - May 22)

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-05-23-15.05.html

May 16, 2017

Agenda

  • Danube Retrospective (continued)

Minutes

  • Documentation (MS10)
    • preliminary documentation requirement at MS6 was only partially successful 
    • Sofia Wallin says that we still need clarification around roles and requirements
    • Maryam Tahhan pointed out that it doesn't make sense to have JIRA ms before docs ms, since JIRA are often associated with JIRA
  • baremetal vs virtual deployment 
    • Frank Brockners says that we've had a requirement since Arno to deploy to baremetal. Bryan Sullivan agrees that baremetal should be the goal.
    • Gregory Elkinbard points out that there is a resource issue. Do we have sufficient resources to deploy to baremetal?
    • Tim Rozet agrees that there is a resource issue. Apex is adding an additional pod for Euphrates.
    • There is a consensus that HA scenarios must deploy to baremetal to qualify for release
  • release noha, based on successful release of ha? 
    • noha scenarios should be tested in virtual, as a minimum requirement 
    • Bryan Sullivan says that we should not set a requirement around the number of nodes required for baremetal deployment
  • minimum test requirements? 
    • Dave Neary says that we should continue to have a low bar for testing
    • Jose Lausuch would like to have some requirements but agrees with having scenario owners make the judgment about release
  • experimental scenarios 
    • Jose Lausuch says that we should support experimental scenarios, as long as they are documented as such in the release notes. Bryan Sullivan agrees that experimentation is important. 
    • What about entry criteria for experimental scenarios?
    • Should we limit experimental scenarios to 1 or 2 releases? i.e., cannot go on forever as experimental.
  • release/license scanning 
    • Luke Hinds says that this is informational only for Euphrates, but gating for 'F' release 
    • CI Gate Security project (Anteater)

Actions

  • Sofia Wallin add topics to docs meeting for doc requirements and release roles

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-05-16-15.00.html

May 9, 2017 (CANCELLED)

Agenda

  • Danube Retrospective (continued)

Minutes

Actions

Meetbot Minutes

May 2, 2017 (CANCELLED)

Agenda

  • Danube Retrospective (continued)

Minutes

Actions

Meetbot Minutes

April 25, 2017 (CANCELLED)

Agenda

  • Danube Retrospective (continued)

Minutes

Actions

Meetbot Minutes

April 18, 2017 

Agenda

  • Danube Retrospective (continued)

Minutes

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-04-18-15.00.html

April 11, 2017 

Agenda

  • Danube Retrospective

Minutes

  • Danube retrospective presentation
  • Milestone 1 - release planning
    • We currently do not use a template for release plans.  Do we need one?
    • Frank Brockners and others suggest that a release plan template might be useful for new projects.
    • Jack Morgan says that project teams should have JIRA tickets for each of their major goals for the release.
    • Bryan Sullivan cautions agains putting too much effort into a template.  There are higher priorities.
    • Euphrates includes a requirements for projects to document their CI resource needs
      • Fatih Degirmenci emphasizes the need to refresh this information throughout the release cycle
  • Milestone 2 - test requirement documentation
    • Compliance questions for Euphrates will be simplified
    • Bryan Sullivan says we should add or strengthen project plan checks in which the project clarifies how their scope is covered by feature tests (e.g. Tempest or other), and if that coverage is incomplete (we're not bored yet) they include plans to make progress toward better coverage in the release.
  • Milestone 3 - installer integration with OpenStack
    • Bryan Sullivan would like for the installer teams to ive a little more detail as to what the issue was with Danube/Newton late readiness, so we can know whether the issue is likely to continue and what if anything we can do to improve the situation and de-risk future readiness for feature project development/testing.
    • Dan Radez asks whether MS3/4 should be collapsed.
  • Milestone 4 - infrastructure ready
    • Two changes for Euphrates:
      • Test framework ready - test frameworks must be ready to support feature test case implementation (e.g. integration complete).
      • Installers passing "nosdn" scenario deployment and Functest testing
  • Milestone 5/6
    • Bryan Sullivan asks whether compliance checking could be automated
      • the verification that something is happening (e.g. feature project integration and successful test executions) is mine-able, so PTLs should not have to provide this information directly.
  • We ran out of time at slide 10, so we will continue the retrospective at next week's meeting.

Actions

  • David McBride to setup discussion with installer teams at plugfest

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-04-11-15.02.html

April 4, 2017 (CANCELLED)

Agenda

  • Danube 1.0 wrapup
  • Danube 2.0 (May 4)
  • Euphrates intent-to-participate (MS0)
  • Euphrates release planning (MS1 - April 24)
  • Danube retrospective - April 11

Minutes

  • Meeting cancelled due to low turnout during ONS.

Actions

Meetbot Minutes

March 28, 2017

Agenda

  • MS8 - test complete 
  • MS9 - JIRA update 
  • MS10 - documentation complete
  • MS11 - release Danube 1.0
  • Status of Yardstick
  • Euphrates intent-to-participate

Minutes

  • Revised schedule
    • New release date is March 31 (4 day slip)
    • MS8 - Test Complete - March 29
    • MS9 - JIRA update and MS10 - Documentation - March 30
  • Documentation
    • Sofia Wallin requests that project owners that are done with their documentation assign someone from the docs team in gerrit for review
    • Sofia Wallin recommends using cherry picks to stable as the point at which docs team reviewers should be added to gerrit
    • David McBride notes that KVMforNFV is missing documentation
    • Frank Brockners suggests that Sofia setup a wiki page that lists status of scenario and project documentation
    • Jack Morgan suggests documentation as a topic at the upcoming plugfest (process and responsibilities)
    • Jack Morgan asks who owns making sure documentation gets done: release manager? docs team? secenario owner? etc
    • Sofia Wallin asks Jack Morgan about status of Pharos spec.  Jack says that it is in process and will be completed by Thursday, march 30
  • Euphrates Intent to Release
    • Window is open from March 27 to April 24.
    • Process
  • Fuel status

Actions

  • David McBride to propose how and where JIRA issues for documentation will be created. Share with Sofia, then with Release meeting
  • Sofia Wallin will investigate status of KVMforNFV documentation and respond to email, topic same

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-03-28-15.03.html

March 21, 2017

Agenda

  • MS8 - test complete (March 20)
    • Functest status?
  • MS9 - JIRA update (March 22)
  • MS10 - documentation complete (March 24)
  • MS11 - release Danube 1.0 (March 27)

Minutes

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-03-21-15.03.html

March 14, 2017

Agenda

  • MS7 - stable branch (March 10)
  • MS8 - test complete (March 20)
  • MS9 - JIRA update (March 22)
  • MS10 - documentation complete (March 24)
  • MS11 - release Danube 1.0 (March 27)

Minutes

  • MS7 - stable branch
    • Fatih Degirmenci points out that CI is starting on the Danube branch this week, although the branch happened last week.
  • MS8 - test complete
    • Functest still must be enabled
    • Fatih Degirmenci will contact installer teams to enable triggers for Functest.
  • MS9 - JIRA update
    • David McBride to update JIRA projects with version strings for Euphrates.
  • MS10 - documentation
  • AoB
    • Bryan Sullivan asserts that since we are removing the release name from the version number, we need to adjust the documentation generation process so that the release name is visible on the document.

Actions

  • Fatih Degirmenci to contact installer teams to enable triggers for Functest
  • David McBride will update JIRA projects with version strings for Euphrates 
  • Sofia Wallin will update the "Testing Documentation" section in the documentation guide

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-03-14-15.00.html

March 7, 2017

Agenda

  • MS7 - stable branch (March 10)
  • Scenario status
  • Danube stability

Minutes

  • Discussion of Euphrates release schedule carried over from TSC meeting
    • Frank Brockners proposes enabling projects to release independently of the standard OPNFV 6-month cadence
    • Unclear how projects would get around limitations of installer integration and CI support.
    • Frank will propose a project, using FDS, to experiment with an alternate release strategy.
  • Documentation
    • Trevor Cooper is concerned about status of test documentation format. Test documentation organization is unclear.
    • The documentation guide will be updated, including recommendation on titles/naming 
    • Sofia Wallin will update the documentation guide, including recommendations on titles/naming
    • update will be based on email proposal from Morgan Richomme (response to action item from release meeting last week)
    • doc structure shared with test projects and agree during last test working group meeting

Actions

  • Frank Brockners to propose alternate release schedule for FDS, independent of standard OPNFV release
  • Sofia Wallin to update the documentation guide with test framework documentation information, based on recommendations from the test working group (see email from Morgan Richomme)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-03-07-16.04.html

February 28, 2017

Agenda

  • Danube schedule review
    • MS6 - Status
  • MS7 - stable branch (March 10)
  • OPNFV versioning

Minutes

  • MS6
    • Lengthy discussion about test framework documentation
    • Morgan Richomme took an action to create a proposal, based on the discussion, and send it to the Documentation Working Group (Sofia Wallin) for review.
  • MS7 - stable branch
  • Versioning
    • For E-release, David McBride recommends that we move to standard, three digit versioning (major.minor.patch) and drop the release name from the version.
      • For example, instead of danube.1.0, danube.2.0, and danube.3.0, we would have 4.1.0, 4.2.0, and 4.3.0.
    • David McBride will look at how our upstream components handle versioning.
  • Milestones for test frameworks
    • Note that this topic is also being discussed in the Test Working Group
    • Trevor Cooper emphasizes that test framework projects should follow the same milestones as feature projects as much as possible.
      • However, features have a dependency on test frameworks that requires that test frameworks be stable before features.
    • Jose Lausuch suggests a milestone called "framework ready" that would fall some time before MS6.
      • Should this be tied to MS4 in order to give feature projects sufficient time to implement test cases before MS6?

Actions

  • Morgan Richomme to create proposal for test framework documentation and send to Doc Working Group
  • David McBride to investigate versioning in upstream projects and report back

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-02-28-16.00.html

February 21, 2017

Agenda

  • Danube schedule review
    • MS6 - Status
      • Help with compliance verification
        • Test case implementation
        • Preliminary Doc Requirements (Sofia Wallin)
    • MS7 - Mar 10
    • "E" - release schedule
      • CI evolution schedule integration
      • 2.0 / 3.0

Minutes

  • How should we assess MS6 compliance for test case implementation?
    • Jose Lausuch suggests that commits would be a better guide than presence on the functest dashboard.
    • Commits for test case implementation are in two parts:
      • Commit to enable testing in functest repo
      • Commits that implement test cases in project repo
  • How should we assess MS6 compliance for preliminary documentation requirement?
  • Discussion about documentation
    • Trevor Cooper questions the term "Release Documentation"
      • How about "User Documentation"?
      • Sofia Wallin to follow up in the mailing lists.
  • MS7 - stable branch
    • Trevor Cooper asks for clarification about specific time for the stable branch deadline.  David McBride to follow up.
    • Stable branch opens as of MS6 (Feb 17) and closes at MS7 (March 10).
    • Bryan Sullivan says that projects may branch, even though they may not be part of the release.
    • The branching instructions have not been updated.  David McBride to follow up.

Actions

  • David McBride clarify timing of stable branch close (date and hour)
  • David McBride update branching instructions for the Danube release.
  • Sofia Wallin follow up on mailing list wrt documentation structure and naming (i.e. "release documentation" vs. "user documentation")

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-02-21-16.00.html

February 14, 2017 (abbreviated due to OSLS)

Agenda

  • Danube schedule review
    • MS5 
      • Final stats:  17 compliant / 8 non-compliant
    • MS6 - Feb 17
      • Test case implementation
      • Preliminary Doc Requirements (Sofia Wallin)

Minutes

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-02-14-16.05.html

February 7, 2017

Agenda

  • JIRA triage - meeting 3
  • Danube schedule review
    • MS5 - scenario integration - Jan 27
    • MS6 - test case implementation - Feb 17
  • Follow-up on MS3

Minutes

  • JIRA triage
  • Danube schedule
    • Project compliance is tracked on the Milestone Compliance page.
    • Note that not all milestones are applicable to all projects
    • Gerald Kunzmann suggests breaking up the table into separate tables, each with a common set of milestones
    • David McBride notes that the fact that the current set of milestones is not applicable to all projects is a problem that needs to be resolved in the release process (e.g test projects)
    • David takes an action to start an email thread with the test framework teams to determine appropriate milestones.
    • Milestone 6
    • Jose Lausuch and Bryan Sullivan express concern about CI stability.  Jose says that the current instability is similar in magnitude to Brahmaputra.
    • Can we better ensure CI stability through improvements to the release process?
      • Maryam Tahhan suggests an installer health check milestone between MS4 and 5.  Tim Rozet says that this is already done as part of OpenStack integration.

Actions

  • David McBride - provide link to JIRA triage slide deck shown in the meeting today
  • David McBride - start email thread to identify milestones for test projects

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-02-07-16.00.html


January 31, 2017

Agenda

Minutes

  • Danube schedule review
    • New compliance tracking page available.
    • Milestone 6 documentation requirements
      • Sofia Wallin walks the team through the documentation requirements for MS6
        • Each project should establish and commit directory structure, including placeholder documents, based on templates where available.
        • Documentation guide provides a description and examples
        • Sofia Wallin will fix a formatting problem in the documentation guide that displays the directory structure.  Some symbols or text are replaced by "???".
        • Sofia Wallin will complete a TBD in the guide related to test framework documentation.
        • Sofia Wallin hopes to have a new template for test framework documentation available in time for the next OPNFV release ("E").
        • Jack Morgan suggests sending an email to the team, reminding them about the documentation requirement for MS6, with a link to the doc guide.  David McBride will take that action.
    • Joid / Functest
      • Narinder Gupta is at ETSI plugfest, so is unavailable to discuss.  However, Jose Lausuch reports that he has seen functest running on Joid.
    • Daisy / Functest
      • Daisy team unrepresented today.  Jose Lausuch reports that he has not heard from the team lately.  May be due to New Year vacation  and celebrations.

Actions

  • Sofia Wallin to fix formatting problem on documentation guide page
  • Sofia Wallin to complete TBD related to test framework documentation in the documentation guide
  • David McBride to send email to the team reminding them of the documentation requirements for MS6, including a link to the documentation guide

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-01-31-16.01.html

January 24, 2017

Agenda

Minutes

  • Intel lab migration
    • Jack Morgan says that the migration has been completed and that all resources are back online.
  • Milestone 3
    • Joid / Functest 
      • Narinder Gupta says that he has been having problems with Functest.  He is in touch with Jose Lausuch to resolve.  Narinder requests additional resources in North America or Europe to help debug.
    • Daisy / Functest
  • Milestone 5
    • Just because a scenario is available as a Jenkins job does not necessarily mean that the feature that plans to use the scenario for deployment and testing is activated.  How to solve?
      • We could possibly use deploy settings files.  For example.
    • Bryan Sullivan points out that project owners do not have visibility into resources (i.e. compliance Q #2)
      • Agree to drop compliance Q #2
    • Prakash Ramchandran says that compliance questions 3 and 4 would be redundant if asked of all the project owners, since many projects share scenarios.  Better to ask the scenario owners those questions.
      • Agreed

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-01-24-15.59.html

January 17, 2017

Agenda

  • Follow up with Movie project
  • Follow-up on MS3
  • Danube schedule review
    • Updated schedule
    • MS5 - scenario integration - Jan 27
    • MS6 - test case implementation - Feb 17

Minutes

  • Movie project
    • Prakash Ramchandran reports that the Movie team is now able to add test cases to the test case database.
  • Daisy / Functest
    • Jose Lausuch continues to work with the Daisy team but progress is unclear.
  • Danube schedule
    • Jack Morgan is still working to bring resources in the Intel lab back online.  Expects to be finished by Weds, January 18.
    • Narinder Gupta, Trevor Cooper, and Bryan Sullivan report that their projects have been impacted by Intel lab unavailability.
    • Comment from Bryan Sullivan
      1. To clarify there are several underlying delay issues beyond the lab infra issues we experienced this time. I don't want to conflate these, but they are: (1) the timeline in which current upstream code is integrated in installers; (2) the complexity and resource requirements of OPNFV deploys
      2. As a result this year I am shifting toward more independence from OPNFV scenarios as a basis for test/dev, with functest integration at the right time (when installers are ready) and using OPNFV CI/CD infra for all that testing, rather than my dev lab resources
      3. This approach should enable more early/continual progress on current upstream release support and features - in essence this is like OPNFV on Devstack, and no/few tests will be OPNFV-specific (all will run on upstream dev environments
    • Trevor Cooper asks about preliminary documentation requirements.  Sofia Wallin responds that the Doc WG is continuing to develop the requirements and will be meeting again on Wednesday.
  • AoB
    • Jose Lausuch reports that he has seen no test activity from Joid scenarios.  Narinder Gupta reports that Joid has been impacted by the Intel lab migration.  
    • Jack Morgan says that Intel POD5 Node5 needs to be reset due to IMPI being stuck.  
    • Narinder Gupta will update the team on the status of Joid at the next release meeting.

Actions

  • Narinder Gupta update team on status of Joid following Intel lab migration activity

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-01-17-16.02.html

January 10, 2017

Agenda

Minutes

  • Movie
  • Followup on MS3
    • Discussion about whether we should standardize on a particular Keystone API
    • Ulrich Kleber believes that this is necessary in order to do scenario consolidation
    • Dave Neary expresses concern that standardizing on a particular API version could lead to using the oldest version available, contrary to OPNFV philosophy about preferring to work with leading edge upstream components.
    • Serg Melikyan says: "we never know which software people running on our openstack and which API this software requires, we should not only consider our project or official openstack projects" 
    • Frank Brockners says: "trying to harmonize all the components for a release does *not* make sense, because it would be a race to the lowest common denominator and hence stop progress."  Tapio Tallgren agrees with this statement.
    • Gregory Elkinbard says: ""API compatibility is a difficult topic. API differences between installers will limit the compatibility of applications running on top. Just like Java, write once, test and debug every where. But installers are simply packaging commercial efforts and delivering them to the community, it is not possible to deviate in a major way. So we will have to live with a degree of uncertainty"
  • Danube schedule
    • David McBride summarizes the changes approved by the TSC in the last hour.  MS5 moves to January 27.  MS6 moves to February 17.  Subsequent milestones, and the release date, remain unchanged.
    • Discussion about mitigating resource disruptions
      • Fatih Degirmenci suggests that we should map projects to resources so that it is easier to determine the scale of a disruption and which projects are affected.
      • Fatih Degirmenci and Ulrich Kleber say that we should allocate resources in a way that minimizes disruptions.  E.g. don't have all resources for a particular project in one pod or one lab.
      • Fatih DegirmenciUlrich Kleber, and Jack Morgan to propose a plan to improved resource resiliency.
    • Jack Morgan believes that all Intel lab resources will be back online by the end of the week.

Actions

  • Provide credentials to Prakash (Jose Lausuch)
  • Propose a plan to improve lab resource resiliency (Fatih Degirmenci with help from Uli and Jack)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-01-10-16.01.html

January 3, 2017

Agenda

  • Moon project status (Ruan HE)
  • Follow-up on Fuel / Colorado.
  • Shifting CI resources from Colorado to Danube
  • Follow-up on MS3
    • Functest integration with OpenStack Newton (Jose Lausuch)
    • Daisy on Functest dashboard
  • Danube schedule review
    • MS5 - scenario integration
    • MS6 - test case implementation

Minutes

  • Fuel / Colorado
    • Serg Melikyan reports that issue with Fuel / Colorado has been resolved upstream and that the workaround linked on the download page is no longer necessary.
  • Moon project status
    • Ruan HE suggests slipping MS5 by 1 - 2 months.  Release manager declines with agreement from Tapio Tallgren.
    • Ruan HE reports that Moon team plans to add support for additional installers in the 'E' release.
  • CI resource status
    • Gregory Elkinbard proposes maintaining a weekly build in order to support resolution of any critical issues identified before Danube is released.  Tim Rozet points out that any bugs found could be resolved using manual builds.  Morgan Richomme also suggested that the community lab could be used.
    • Discussion and then agreement to shift all CI resources to Danube now that the issue with Fuel on Colorado has been resolved.
  • Danube schedule
    • Discussion about requirements for MS5.  David McBride points out that Jenkins jobs need to be in place with assigned resources; however, they do not need to be bug free at this point.
    • MS5 - Jan 13
    • MS6 - Jan 26
  • AoB
    • The link for swagger seems to be broken.  Bryan Sullivan will investigate.

Actions

  1. Investigate broken link for swagger (Bryan Sullivan).

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-01-03-16.00.html

December 27, 2016 (CANCELLED)

December 20, 2016

Agenda

  • Follow-up on Fuel / Colorado.
  • Shifting CI resources from Colorado to Danube
  • Follow-up on MS3
    • Functest integration with OpenStack Newton (Jose Lausuch)
    • Installer support for OpenStack Newton / older
    • Daisy on Functest dashboard
  • Danube schedule review
    • MS5 - scenario integration
    • MS6 - test case implementation
  • Reminder - no release meeting on December 27
    • Release meeting resumes January 3

Minutes

  • Followup on Fuel / Colorado
    • Serg Melikyan has documented a workaround that has been linked from the download page for the Fuel ISO.
    • Sera Melikyan says that the workaround will not be necessary in 1 - 2 weeks when the issue is resolved upstream.
  • Shifting CI resources from Colorado to Danube
    • Once Fuel / Colorado issue is resolved, all CI resources can be shifted to Danube.
  • Followup on MS3 - OpenStack/Installer integration
    • Jose Lausuch reports that Functest team is continuing to work on integration with OpenStack Newton.
    • Tim Rozet reports that Apex is conducting daily runs using 'nosdn' and 'ODL' scenarios.
    • Question about which version of Keystone API (v2 or v3) is used by installers. David McBride to followup with installer teams.
    • Question: When will the Daisy installer be added to the Functest dashboard?  Jose Lausuch to followup.
    • Jose Lausuch comments that Daisy appears to be doing deployments but not running Functest.  David McBride to follow up with Daisy team.
  • MS5 / MS6
    • MS5 scheduled for Jan 13.
    • MS6 scheduled for Jan 26.
    • David McBride to follow up with project teams and remind them of milestone dates and requirements.
  • Holiday schedule
    • No release meeting on Dec 27.

Actions

  1. Determine which version of Keystone API is being used by each installer. (David McBride)
  2. Add Daisy to the Functest dashboard (Jose Lausuch)
  3. Start email thread with Daisy team to understand status of Functest integration (David McBride)
  4. Remind project team about schedule and requirements for MS5 and MS6 (David McBride)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-12-20-16.01.html

December 13, 2016

Agenda

  • Colorado 3.0 Wrap-up
  • Re-directing CI resources to Danube?
  • Danube schedule review
    • MS2 and MS3 compliance
    • MS5 - scenario integration
    • MS6 - test case implementation
  • Release meeting schedule through the winter holidays

Minutes

  • Colorado wrap-up
    • Tapio Tallgren notes that there is a bug with the Fuel installer
    • Gregory Elkinbard notes that the issue is unique to Ubuntu
    • Question:  re-release of document workaround?
      • Ulrich Kleber notes that another release would require approval by the TSC
    • Gregory Elkinbard will document the workaround and send to the community for review.
  • Shifting resources to Danube from Colorado
    • Gregory Elkinbard requests that we maintain some resources on Colorado for Fuel
    • Jack Morgan notes that the Intel lab will be shifting to Danube, which may affect some jobs.  Jack will send an email to the team with details.
  • Danube
    • David McBride reminds the team that MS5 (scenario integration) is January 13 and MS6 (test case implementation and preliminary documentation) is January 26.
    • Sofia Wallin is working on documentation requirements for MS6
    • Bryan Sullivan suggests making sure that the team understands what to do for preliminary documentation for MS6
  • MS2 and MS3 compliance
    • Bryan Sullivan working with Orchestra team via Models project to enable them to use Functest
    • David McBride notes that all installers have met MS3 except Daisy4NFV
  • Holiday meeting schedule
    • One release meeting will be cancelled:  December 27

Actions

  1. Provide documented workaround for Fuel issue on Colorado to the team (Gregory Elkinbard)
  2. Send email to team describing Intel lab shift to Danube and possible job interruptions (Jack Morgan)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-12-13-16.03.html

December 6, 2016

Note:  this week's meeting held F2F at the 4th quarter hackfest-plugfest at UNH IOL

Agenda

  • Colorado 3.0 
    • Release status
    • Download page goes live Dec 8 (Thursday)
    • Colorado retrospective - Nov 8, 2 - 4 pm / training room
  • Danube schedule review
    • Schedule review
    • MS4 - Infrastructure update 
    • MS5 - scenario integration
    • MS6 - test case implementation
  • Hackfest breakout sessions

Minutes

  • Colorado 3.0 release
    • Aric Gardner has identified some broken links in the documentation.  He is working with Sofia Wallin to resolve.
    • Download page still planned to go live on December 8
  • Danube
    • Functest not yet integrated with OpenStack Newton.  Prevents installers from enabling Functest.
      • Jose Launch expects to resolve this week
      • Functest integration with OpenStack should be a requirement of MS3 (Installer integration with OpenStack)
    • Need to reconsider timing of MS4 - Infra updates completed
      • Three components:
        • Project requirements
        • Capacity requirements
        • Infra WG updates and improvements (e.g. CI evolution)
      • Jack Morgan suggests a breakout session this week at hackfest to discuss further
    • MS6 - test case implementation and preliminary documentation
    • Now that Colorado is released, Fatih Degirmenci requests that we divert CI resources from Colorado to Danube
      • Team agrees to defer a decision to next week

Actions

  1. Complete integration of Functest with OpenStack Newton.  Ensure that installers can enable Functest. (Jose Launch)
  2. Develop requirements for preliminary documentation for MS6. (Sofia Wallin)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-12-06-16.02.html

November 29, 2016

Agenda

  • Colorado 3.0 
  • Orchestra discussion (Giuseppe Carella)
  • Danube schedule review
    • MS3 - OpenStack integration - Nov 30 (TOMORROW!)
    • OpenStack Newton as default on CI (Jack Morgan)
    • Installer reporting

Minutes

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-11-29-16.00.html

November 22, 2016

Agenda

  • Daisy CI integration status
  • Colorado 3.0 
    • Complete test and documentation - Nov 30
    • Technical release - Dec 5
  • Danube schedule review
    • MS2 - test requirements - TODAY!
    • MS3 - OpenStack integration - Nov 30
  • 2.0 and 3.0 process

Minutes

  • Daisy CI integration status
    • Zhijiang Hu reports problems with integration. 
    • Daisy has a need for OS installation, which is outside of the scope of CI, according to Fatih Degirmenci.  Installers must handle OS installation themselves.
    • David McBride will notify dependent projects of risk.
  • Colorado 3.0
    • David McBride reminds the team that test and documentation should be completed by Nov 30.  Release is on Dec 5.
    • David McBride asks scenario owners to update the "intent to release" column for Colorado 3.0
    • Sofia Wallin reminds the team to update documentation links even if the documentation is not changing.
  • Danube
    • MS2 - test requirements is today (Nov 22)
    • Discussion about MS2
      • David McBride points out that this MS lacks tangible ways to measure compliance
      • Bryan Sullivan says that documentation of test cases in the test case database should be sufficient
    • Installer status
      • David McBride reminds team that MS3 - installer integration with OpenStack Newton is Dec 5.
      • Apex - Tim Rozet reports success with basic deployments but still resolving bugs
      • Fuel - Fedor Zhadaev reports successful deployments for both bare metal and virtual
      • Compass - Justin chi reports problem with dependency on Functest for health check.  Jose Lausuch suggests disabling health check, temporarily.
      • Joid - Narinder Gupta says patch has been accepted. Issue with hardware when using OpenStack Newton by default. Jack Morgan is investigating.
      • Daisy - see notes above under "Daisy CI integration status"

Actions

  1. Notify projects dependent on Daisy installer of risk, due to ongoing CI integration problems. (David McBride)
  2. Continue investigating hardware issue described by Narinder Gupta. Update status at next week's release meeting (Jack Morgan)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-11-22-16.00.html

November 15, 2016

Agenda

  • Colorado 2.0 release wrap-up
  • Colorado 3.0 
    • Complete test and documentation - Nov 30
    • Technical release - Dec 5
  • OpenStack integration survey
  • Danube schedule review
    • MS2 - test requirements - Nov 22
    • MS3 - OpenStack integration - Nov 30
  • Escalator / Daisy4NFV update
  • 2.0 and 3.0 process

Minutes

  • Colorado 2.0
    • David McBride says that the Colorado 2.0 download page went live, yesterday (Nov 14).
  • Colorado 3.0
    • Question about which projects/scenarios will participate in Colorado 3.0
      • Participation of scenarios in each Colorado release are indicated in the right-hand columns of the scenario status page.
      • David McBride asks scenario owners to update their intent-to-participate entries for Col 3.0, if necessary.
  • OpenStack integration
    • David McBride has sent a survey to project leads, requesting their input on which version of OpenStack that OPNFV Danube should be based on and whether OpenStack Ocata should be skipped.
      • The survey will close on Monday, Nov 21, at 12 noon (PST)
    • Christopher Price and Bryan Sullivan object to the survey because a plan for Danube has already been approved by a vote of the TSC.
  • Danube
    • David McBride reminds the team that we have important milestones for Danube in the next two weeks:
      • MS2 (test requirements) - Nov 22
      • MS3 (openstack integration) - Nov 30
  • Escalator / Daisy 
      • Zhijiang Hu says that Daisy is having difficulties in understanding how to use Functest 
      •  Jose Lausuch to meet with huzhj to address questions about Functest
      • Zhijiang Hu reports progress integrating Daisy with CI and says that the lf-build1 has been solved.
      • Daisy artifact has been built and uploaded to the google storage successfully. Next step is that virtual deployment machine will be connected to OPNFV as new slave. 
      • For integrating Escalator, we are working on extending Daisy API to support Escalator requirement of getting VIM components' version. 
      • Zhijiang Hu to attend next Infra meeting to drive Daisy integration with CI 

Actions

  1. Work with Zhijiang Hu and Daisy team to understand and implement Functest testing. (Jose Lausuch)
  2. Attend the next Infra WG meeting to discuss CI integration (Zhijiang Hu)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-11-15-16.01.html

November 8, 2016

Agenda

  • Colorado 2.0 release status
    • JIRA fix version update NOW!
  • Danube schedule review
    • MS2
    • MS3
    • Scenario status page for Danube
  • Escalator / Daisy4NFV
  • OpenStack Newton vs. Ocata
  • 2.0 and 3.0 process

Minutes

  • Colorado 2.0
    • Fedor Zhadaev reported that Fuel is now stable
    • Frank Brockners notes that fdio scenarios are not yet ready to be release, so will not be part of Colorado 2.0.  
    • There are ongoing issues with SFC due to problems in OpenDaylight.
    • Fedor Zhadaev says that the problem with documentation in the archive not updating in response to committed changes has been resolved.  Thanks Aric Gardner
  • Danube
    • Discussion about combining scenarios to reduce scenario prolifieration
    • Suggestion to not release "core" scenarios (i.e. no-feature scenarios used simply for installer validation)
    • Jonas Bjurel suggests that one scenario owner should own all scenarios for a particular installer.
  • Escalator / Daisy
    • Is it a risk for Escalator to be dependent upon Daisy, since Daisy is still being integrated with CI?
    • Discussion about tasks that Daisy and Escalator must complete to be viable for the Danube release
    • Request for Daisy and Escalator PTLs to return to this meeting next week to update status.

Actions

  1. Update the release meeting on status of Daisy and Escalator (Jie HuZhijiang Hu)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-11-08-16.00.html

November 1, 2016

Agenda

  • Colorado 2.0 release status
    • JIRA fix version update NOW!
  • Danube schedule review
    • MS1 - Planning
    • Scenario status page for Danube
  • Refresher on JIRA triage #1
  • 2.0 and 3.0 process

Minutes

  • Colorado 2.0
    • Release was slipped to Nov 10.  Testing and documentation must be updated by Nov 7.
    • Please reassign to another release JIRA issues assigned to Colorado 2.0.
  • Danube
    • Most projects have completed release plans.  
    • Please add scenarios to the scenario status page
    • Reminder about MS2 and MS3 in November
    • Jack Morgan says that the Infra WG is developing a new naming scheme for scenarios and asks the team to review in gerrit and provide feedback.
  • Review of JIRA triage
  • Beginning of discussion about 2.0/3.0 release process
    • What does it mean to release a scenario?
      • Approved by scenario owner
      • Documented as supported in release notes
      • Updated documentation and test results

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-11-01-15.00.html

October 25, 2016 (CANCELLED)

Agenda

  • Colorado 2.0 release status
    • JIRA fix version update NOW!
  • Danube schedule review
    • MS1 - Planning
    • Scenario status page for Danube
  • Refresher on JIRA triage #1
  • Talk to me at OpenStack!

Minutes

Meeting canceled due to OpenStack Summit.

Actions

Meetbot Minutes

October 18, 2016

Agenda

  • Colorado 2.0 / 3.0 schedule review
    • Functest status
    • JIRA status
    • Documentation
  • Danube schedule review
    • Intent to participate
    • Project release planning
    • Scenario status page for Danube
  • AoB

Minutes

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-10-18-15.01.html

October 11, 2016

Agenda

  • Colorado 2.0 / 3.0 schedule review
    • Functest status
  • Danube schedule review
    • Intent to participate
    • Project release planning
    • Scenario status page for Danube
  • JIRA Triage
  • AoB

Minutes

JIRA triage.pdf

Actions

  1. Update intent-to-participate page for Danube so that  users may see the status of projects that participated in Colorado (David McBride)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-10-11-15.03.html

October 4, 2016

Agenda

  • Colorado 2.0 / 3.0 schedule review
    • Restarting Daily Release meeting Oct 10
    • Please update Colorado Scenario Status intent to release for 2.0/3.0
    • Review/discuss test results
  • Danube schedule review
    • MS0 - intent to release
    • Planning template
  • AoB

Minutes

  • Many having difficulty joining meeting due to last week's change in the GTM info.  Also, David McBride forgot to update the meetings page when the GTM was changed (sigh).
  • David McBride said that the release meeting will be split between discussion of Colorado 2.0 / 3.0 and Danube for the next two months.
  • David McBride reminded the team that the Colorado 2.0 daily (M, Th, F) will begin on October 10.
  • Colorado 2.0 / 3.0
    • Jonas Bjurel raised a concern about interference between Colorado 2.0 and the OpenStack Summit.
      • A similar concern was raised last week about Col 3.0 and Plugfest in December.  The consensus of the group on the call was that this should not be a major issue and the schedule does not need to be changed.
      • David McBride will follow up on action from last week to start an email thread on the subject
    • Morgan Richomme walked the team through improvements to the Functest dashboard, including graphs that show the scoring trend over time.
    • Review of current test results
      • Tim Rozet said that fd.io performance is misleading due to an issue in Functest.  Tim will file a ticket with Functest.
      • Tim Rozet said that L3 performance is likely due to ODL bug.  This will likely be resolved by using ODL Boron with new netvirt.
  • Danube

Actions

  1. File JIRA ticket with Functest project to correct problem causing problems for FDIO, among other scenarios (Tim Rozet)
    1. Notes from Tim:  dpdk based scenarios (fd.io, ovs-dpdk), need to use vhost user ports. This needs to be updated in functest to indicate to create instances with vhost user ports
  2. Update GTM info on meetings page and release meeting page (David McBride)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-10-04-15.01.html

September 27, 2016

Agenda

  • Colorado 2.0 / 3.0 schedule review
  • Danube schedule review
    • Intent to participate
    • Planning template
    • New planning documents!
      • Test plan
      • Infra/CI plan
    • Milestone tracking/compliance

Minutes

  • Colorado 2.0 / 3.0
    • Follow-up discussion from TSC call:  does Dec 5 release date for Col 2.0 collide with Plugfest/Hackfest scheduled for the same time period?
      • Consensus on the call was that this should not be a problem.  Activity for Col 2.0 is expected to be low enough that an event scheduled at the same time should not interfere.
      • David McBride took an action to start an email thread to solicit feedback from a larger audience.
    • David McBride requested that scenario owners review and update the Colorado Scenario Status page with intent-to-release for Colorado 2.0. 
    • Discussion about the risk of installer updates in Col 2.0 or 3.0 that break dependent projects that stop their development at Col 1.0.
      • Gregory Elkinbard acknowledged that there is a "small risk" of this happening and that it deserves more discussion.
      • Gregory Elkinbard said that, in general, there should be better coordination between installers and dependent projects.  Greg suggested a discussion at the upcoming plugfest/hackfest in NH.
      • David McBride took an action to propose this discussion as a breakout session at the hackfest in December.
    • David McBride requested that PTLs finish cleaning up the remaining unresolved JIRA issues assigned to Colorado 1.0.  These issues should either be closed or reassigned to future releases (i.e. by updating the "fix version" field for each issue).
      • Jack Morgan commented that some projects still have unresolved Brahmaputra issues.
      • David McBride to follow up with PTLs to cleanup the remaining unresolved issues.
  • Danube planning
    • Review of Danube schedule and Milestone Description
    • David McBride described a new project release plan template.  This will be discussed in more detail next week.
    • David McBride describes two new planning documents proposed for Danube:
      • Test Plan - feature projects will prepare a simple test plan that describes how projects intend to verify their feature.  This will be discussed in the Test Working Group.  Benefits:
        • Add visibility and transparency to test planning for all stakeholders.
        • Encourage feature project teams to think through testing and CI integration early in the release process.
        • Encourage feature project teams to collaborate with the Test Working Group and Infra Working Group early in the release process.
        • Identify and bring visibility to requirements for non-existing capabilities or infrastructure
      • Infra/CI plan - the Infra Working Group will prepare a plan documenting tasks that they plan to complete for the current release and a schedule for those tasks.  This will be discussed in the Infra Working Group.
      • Bryan Sullivan and Dan Lilliehorn raised concerns about the additional workload and advised that the new documents should be as lightweight as possible.
  • David McBride invited the team to stop by the OPNFV booth at the ODL summit this week to chat if they are available.

Actions

  1. Start email thread about possible collision between Colorado 3.0 release and the December plugfest (David McBride)
  2. Propose new topic for a breakout session at plugfest:  Coordination between installer projects and dependent projects (David McBride)
  3. Followup with PTLs about unresolved JIRA issues still assigned to Colorado 1.0 (David McBride)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-09-27-15.09.html

September 20, 2016

Agenda

Minutes

09162016_opnfv_jira.txt

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-09-20-15.04.html

September 13, 2016

Agenda

Minutes

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-09-13-14.59.html

September 6, 2016

Agenda

Minutes

  • Open DayLight
    • Boron release required for SFC
    • Scenarios not using ODL for HA in Colorado 1.0
    • ODL HA may be tested for Colorado 2.0
    • Christopher Price wants to make sure that SDN controller applications, with regard to HA, must be documented in release notes and scenario documentation
    • Daniel Smith raised the concern that "HA" scenario names are misleading if not all components are HA-enabled
    • Bryan Sullivan said that we shouldn't worry about the naming, we should just document exceptions.
  • Documentation
    • Sofia Wallin reports good progress on documentation
    • Frank Brockners asks about access to rendered documentation
    • Frank Brockners also wants to be able to setup his own local environment to render documentation
    • Also discussed results of last week's infra meeting, which determined that documentation CI is in place, but users need better access to output and to rendered documentation.
  • Colorado 2.0 / 3.0 Planning
    • David McBride reviewed the updated schedule.
    • Received request to remove JIRA milestone.
  • D-release Planning
    • David McBride reviewed the updated schedule.
    • Frank Brockners requested that the D-release have a window for stable branch, as was done for Colorado.
    • Frank Brockners also requested that the window should be closer to the release date.  General concurrence on the call.
    • Christopher Price requested that the revised schedule be made available ASAP to enable the team to review prior to the next meeting.

Actions

  1. Document user access to documentation rendered by CI (Sofia Wallin)
  2. Document setup of local environment for document rendering (Sofia Wallin)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-09-06-15.02.html

August 30, 2016

Agenda

Minutes

  • Documentation
    • Sofia Wallin reviewed the status of Colorado documentation
    • Sofia recently sent an email containing a list of projects that have not reported status: 
      • KVM for NFV
      • Parser
      • High Availability (HA)
      • SFC
      • Promise
      • Storperf
      • Bottlenecks
      • Prediction
    • Frank Brockners raised the issue that PTLs are unable to close documentation JIRA tickets.  
    • Sofia Wallin says that the current process is for PTLs to contact her when documentation JIRA tickets should be closed and she will close them.
    • Bryan Sullivan says that he is unable to get feedback on documentation build status when he makes changes to documentation.
    • Agreed that documentation CI should be discussed further in the Infra WG meeting.
    • Morgan Richomme suggests a cross-review of test project documentation.  He will raise the issue at the next Test WG meeting.
  • Morgan Richomme reviewed test status.  Cautiously optimistic.
  • D-release planning
    • David McBride reviewed the proposed D-release schedule
    • Frank Brockners and Prakash Ramchandran commented that the OpenStack integration milestone does not allow sufficient time.
    • Agreed that D-release planning should be discussed by the Infra WG to make sure that the release schedule and the CI-evolution schedule do not conflict.
    • Sofia Wallin suggests that Documentation milestone should be later than stable branch milestone.

Actions

  1. Discuss documentation CI at the Infra WG meeting (Jack Morgan)
  2. Update D-release schedule to allow for additional time for OpenStack integration and to complete Documentation (David McBride)
  3. Request that D-release planning be added to the Infra WG meeting agenda. (David McBride)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-08-30-15.01.html

August 23, 2016

Agenda

Minutes

  • Stable Branch
  • Documentation
    • Sofia provided some updates via email that were discussed:
      • Sofia: General update, we are moving forward, remind people to add at least one from the docs team as reviewer
      • Sofia: make sure that the feature project knows that there is a feature configuration template available in /git/opnfvdocs/docs/installationprocedure (I don’t think that to many knows, yet some project has already provided an configuration guide)
    • Agreed that documentation should not be released prior to associated code.  So, for example, if code will be released in Colorado 2.0, then the documentation should not be released before then.
  • Scenario status
    • David McBride notes that reporting on the Colorado Scenario Status page has improved.
    • David McBride notes that many scenarios are not yet running Yardstick testing
    • Question:  can virtual deployments be used to pass the deploy gate, vs. bare metal deployments, for "no-ha" scenarios.  This has a significant impact on resources.
  • Colorado 2.0 and 3.0
    • Need more detail for Colorado 2.0 and 3.0 than currently shown on main Colorado release schedule.
    • Include the following milestones:  documentation freeze, test complete, and JIRA cleanup
    • Christopher Price says that we also need to document expectations for Colorado 2.0 and 3.0

Actions

  1. Raise issue with infra and test WGs of using virtual deployment, instead of bare metal deployment, to satisfy deploy requirement for "no-ha" scenarios.  Get consensus. (David McBride)
  2. Create detailed schedule for Colorado 2.0 and 3.0 (David McBride)
  3. Create wiki page to document expectations for projects for Colorado 2.0 and 3.0 releases (David McBride)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-08-23-13.59.html

August 16, 2016

Agenda

  • Schedule review
  • Plans for August 23 release meeting (i.e. week of LinuxCon and OPNFV hackfest)
  • Stable branch milestone
  • Documentation milestone
  • Colorado Scenario Status

Minutes

  • Next release meeting (Aug 23) during the week of LinuxCon
    • Along with the TSC meeting, agreed to meet one hour earlier
    • For those attending the hackfest, we will be meeting on site.
  • Stable branch process
    • Considered two cases of projects deciding not to proceed with a release:  
      • Project that had not participated in a previous release
      • Project that did participate in a previous release
    • Agreed that if project had participated in a previous release AND their previously released code could pass deployment and daily tests then the project could participate in the current release.
  • Documentation
    • Sofia Wallin says that documentation is late.  Hoping to catch up next week.
    • Documentation working group is continuing to work on requirements for test projects.  For now, test projects will use the same documentation requirements as other projects.
  • Scenario Status 
    • There should be no constraint on which CI POD testing is conducted (e.g. should not be limited to LF CI POD)
    • Daniel Smith pointed out that we lack standardization across CI PODs.

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-08-16-15.00.html

August 9, 2016

Agenda

  • Schedule review
  • Stable branch milestone
  • Documentation milestone
  • Doctor project CI (julien zhang)

Minutes

  • Stable Branch
    • Frank Brockners and others expressed concern that using the OPNFV help-desk ticketing system lacks sufficient transparency and might not be a good choice for use in the stable branch process.
    • Daniel Smith suggested a Service Level Agreement (SLA) that would guarantee a turnaround time for help-desk requests.
    • Aric Gardner said that he would turnaround any help-desk requests for a stable branch within 24 hours.  Frank Brockners agreed that this would improve the odds for success of the proposed stable branch creation process.
    • David McBride agreed that cherry-picking would be from master to stable branch.
  • Documentation milestone
    • Sofia Wallin (Documentation WG chair) returns August 10.
    • Christopher Price said that documentation would probably be late.
    • David McBride suggested that future releases include intermediate milestones for draft documentation.
  • Doctor project CI

Actions

  1. Investigate improved transparency and/or SLA for (1) stable branch creation; and (2) help-desk, in general. (David McBride)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-08-09-15.01.html

August 2, 2016

Agenda

  • IPv6 Apex integration / test implementation status
  • Upcoming milestones:  Stable Branch (Aug 15) and Documentation (Aug 15)
  • Colorado Scenario Status
  • Stable branch process

Minutes

  • IPv6 Apex integration
    • Bin Hu reports that the new version of RabbitMQ resolves the bug that was previously blocking integration.
  • Colorado Scenario Status
    • Reviewed the Colorado Scenario Status page.
    • David McBride noted that the page has been substantially updated since last week.
    • Discussed the best way to link to the associated Jenkins job and results.  Agreed that a link to the Jenkins job should be placed in the comments column.  
      • See Tim Rozet entries for his scenarios for an example.
  • Stable Branch Milestone (Aug 15)
    • Frank Brockners asserted that project PTLs should be able to determine their own date for branching.
    • Tim Rozet pointed out that there is no point to branching if there is no point to branching if there is no difference with master.
    • Christopher Price reminded everyone that the TSC already agreed on the milestones and schedule, so any proposed changes should be considered for release D and not for Colorado.

Actions

  1. Provide direction to the team on the stable branch milestone. (David McBride)

Meetbot Minutes

Note:  I got engrossed in the conversation we were having and neglected to take IRC notes, so the following is very thin.  

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-08-02-15.03.html

July 26, 2016

Agenda

  • IPv6 Apex integration / test implementation status
  • Project milestone status
  • Scenario owner status reporting
  • Documentation milestone
  • Stable branch process

Minutes

  • IPv6 Apex integration
    • Patch that Bin Hu mentioned last week did not fix the bug as hoped
    • However, a new build of RabbitMQ appears to resolve the problem, but needs further verification
    • Tim Rozet suggested that the Apex team could verify the fix independently
  • Scenario status
    • Raghuveer Reddy asked whether scenarios that won't be implemented should be removed from the Colorado Scenario Status page.  David McBride said that they should be removed.  No disagreement noted.
    • Agreed that there should be a scenario status page for the D-release, so that scenarios removed from the Colorado release because they aren't ready, could be immediately added to the D-release.
    • Discussed request from Christopher Price to include links to Jenkins jobs or test results in the results columns of the Colorado Scenario Status
    • Fedor Zhadaev said that he would be taking over ownership of scenarios that Jonas Bjurel is currently assigned to.
    • Jack Morgan suggested that we should have a "how-to" wiki page for scenario owners.
  • Documentation
    • David McBride reminded the team that the documentation milestone is August 15.
    • Please contact Sofia Wallin to understand OPNFV documentation requirements
    • Christopher Price requested volunteers to help define the structure and content of scenario documentation

Actions

  1. update team on IPv6 integration (Bin Hu and Tim Rozet)
  2. Add scenario status page for D-Release (David McBride)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-07-26-15.00.html

July 19, 2016

Agenda

  • IPv6 Apex integration / test implementation status
  • Project milestone status
  • Scenario owner status reporting
  • JIRA triage discussion

Minutes

  • IPv6 Apex integration
    • Bin Hu provided summary of issue
      • Two issues:  integration and testing
      • Integration nearly complete, pending upstream bug-fix
      • Testing is larger issue
      • Testing includes both overlay and underlay.
      • A solution exists for overlay testing
      • Bin Hu proposed postponing underlay testing to future release
      • After discussion, release manager agreed to proposal
      • Tim Rozet noted that Apex provides some validation for the underlay
  • Scenario status
    • Kubi suggested that the scenario status page should have a column for reporting YardStick status
    • The team also agreed that we should have a column to indicate whether Jenkins job has been implemented.
    • Wei noted that Moon scenario isn't listed on scenario status page
  • ARM CI POD status
    • Alexandru Avadanii notes that original plan to setup new CI POD will not meet end-of-July deadline.
      • fall-back is to convert internal POD into CI POD
      • Jack Morgan agreed that this approach makes sense

Actions

  1. work with test team and IPv6 project to determine best approach to implement testing for underlay (Jose Lausuch)
  2. provide update on bug fix patch at next week's release meeting (Bin Hu)
  3. add Moon scenario to scenario inventory and scenario tracking pages (Wei)
  4. add column for reporting YardStick status to the scenario reporting page (David McBride)
  5. add colum for reportint Jenkins status to the scenario reporting page (David McBride)

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-07-19-14.58.html

July 12, 2016

Agenda

Minutes

  • SFQM
    • Billy was unavailable, so Maryam Tahhan provided a summary of the status of SFQM.
    • Work has been completed, but changes have not yet been accepted upstream
    • The team and the release manager (David McBride) agreed that this situation is not uncommon in OPNFV and that the changes should be pushed to Fuel.
  • Joid scenario
    • Wei Su provided a summary
    • Not really a "new" scenario
    • Requires changing a line in the installation script
    • Release manager (David McBride) agreed that the change should be made
  • Scenario status reporting

Actions

  1. Create new page for reporting scenario status based on a page that Tim Rozet created for Apex. Notify scenario owners when available. - David McBride

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-07-12-15.01.html

July 5, 2016

Agenda

Minutes

Actions

  1. Reorganize the Colorado release page - David McBride
  2. Add MS numbers to the Release Process pageDavid McBride

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-07-05-15.02.html

June 28, 2016

Agenda

Minutes

  • Discussed status of MS3 - Installer/OpenStack integration
    • Tim Rozet and Morgan Richomme described the resolution of recent problems with FuncTest smoke tests
    • Justin chi said that Compass integration is nearly complete; however, smoke tests are not yet running
    • The issue was raised that access is different for the deployments for each of the installers. David McBride asked if this was a requirement that could be documented and proposed by the Genesis project, then negotiated with the installer projects.  Frank Brockners took an action to file a JIRA ticket with Genesis.
    • Narinder Gupta said that JOID has completed integration and is successfully running with ODL, ONOS, and nosdn.  In addition, LXD is now enabled.
    • Gregory Elkinbard asked whether test project verification could be improved to reduce time lost due to a broken test framework.  Morgan Richomme agreed to take an action to improve verification of test projects.
  • Discussed status of MS4 - detailed test descriptions.
    • Morgan Richomme said that he believes that most projects have reported their requirements.
  • Discussed status of MS5 - infrastructure
    • David McBride requested that infra team review input to scenario inventory page.  Fatih Degirmenci took an action to do that at the next infra meeting.
  • David McBride reminded the PTLs that July 1 is the feature freeze milestone.

Actions

  1. File a JIRA ticket with Genesis to establish a requirement for uniform access to deployments, regardless of installer. - Frank Brockners
  2. Determine and implement improved verification of test frameworks. - Morgan Richomme
  3. Review infra requirements input on the scenario inventory wiki at the next infra working group meeting. Fatih Degirmenci

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-06-28-15.03.html

June 21, 2016

Cancelled due to OPNFV Summit in Berlin.

June 14, 2016

Agenda

Minutes

Actions

Meetbot Minutes

June 7, 2016

Agenda

Minutes

  • Discussed status of JIRA updates.
    • David McBride requested that PTLs complete Version updates this week.
  • There will be a JIRA breakout session at the OPNFV summit.  Specific topics TBD.
  • Installer / OpenStack integration:
    • Apex - identified and fixed upstream bugs
    • JOID - identified bug in ODL
  • Morgan Richomme requested that PTLs planning to use FuncTest should contact him to ensure support.

Actions

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-06-07-14.59.html

May 31, 2016

Agenda

Minutes

  • Result of branch date survey was August 15.
  • Frank Brockners requested that David McBride document the meaning of the new milestone
  • Discussed status of installer/OpenStack integration
    • Apex - FuncTest results improving
    • JOID - issues integrating ODL
    • JOID - issues integrating Ubuntu 16.04.
    • Fuel - successfully integrated no-SDN scenario, but not yet passing FuncTest

Actions

  1. Add "Stable Branch" milestone to the schedule - David McBride
  2. Document meaning of "Stable Branch" milestone - David McBride
  3. Update "Documentation" milestone to line up with "Stable" branch - David McBride

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-05-31-14.57.html

May 24, 2016

Agenda

  • Branch date survey
  • JIRA improvements:
    • Brahmaputra-labeled tickets
    • Use "version" field instead of label for assigning tickets to releases
  • Installer / OpenStack smoke testing status - Installer PTLs (Tim RozetNarinder GuptaWei Shao, Gregory Elkinbard)
  • Milestone status
    • MS4 - Detailed test case descriptions communicated to test project teams
    • MS5 - Test infrastructure updates completed
  • SFQM dependency issue (Maryam Tahhan)

Minutes

  • Discussed branch date survey.
    • A request was made to clarify the ranking (i.e. is 1 or 4 most preferred?)
  • Discussed some changes to how JIRA is used
    • All projects will begin using the "Fix Version" field and will stop using labels to indicate version.
      • The list of versions will be entered via the JIRA admin screen by the PTLs, based on a list documented by David McBride.
      • David McBride will provide instructions for setting up the list of versions.
      • Christopher Price requested that the list of versions be documented in a wiki.
      • Tim Rozet indicated that some projectds (e.g. Apex) are already using versions.
    • We will update all JIRA issues tied to Brahmaputra.  Going forward, we will strive to do one of the following for all issues related to a particular release, BEFORE the release date:
      • CLOSE the issue
      • Defer the issue to a future release by updating the "Fix Version" field
  • Reviewed the status of installer / OpenStack integration
    • During this discussion, the subject of OpenDayLight integration came up.  
      • There is some interest in attempting to integrate the "Boron" release which may be released in August.
      • Others insist that Boron is too risky and that OPNFV should use ODL "Beryllium".
  • Discussed a dependency issue that Maryam Tahhan raised in an email thread.
    • According to Maryam Tahhan:  "For SFQM, the plugins we are developing rely on DPDK 16.04. However out of the Box Fuel 9 doesn't support this version of DPDK. The OVS4NFV project is likely to land the right version of DPDK on the Platform as part of their Fuel plugin."
    • Gregory Elkinbard and Billy O'Mahony volunteered to follow up with Maryam to resolve the issue.

Actions

  1. Document instructions for adding versions to a JIRA project - David McBride
  2. Document the common set of strings that will be used for version names for all projects - David McBride
  3. Work with Maryam Tahhan to resolve dependency issue with SFQM - Billy O'MahonyGregory Elkinbard

Meetbot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-05-24-14.59.html

May 17, 2016

Agenda

  • Review schedule based on milestone discussion - David McBride
  • Discussion:  recommend to TSC that release dates shift to March / September - David McBride
  • JIRA improvements:
    • Brahmaputra-labeled tickets
    • Use "version" field instead of label for assigning tickets to releases
  • Installer / OpenStack smoke testing status - Installer PTLs (Tim RozetNarinder GuptaWei Shao, Gregory Elkinbard)

Minutes

  • Reviewed the proposed schedule (see first file below).
  • Bryan Sullivan requested that the dates for the milestones that have not yet been achieved be updated to make the schedule sync with the current state.
  • Bryan Sullivan expressed concern about the feature freeze date and indicated that his project would likely not freeze until mid-July.
  • Daniel Smith asked about the branch date, which is not explicitly documented on the schedule.
  • Christopher Price commented that the schedule should be proposed to the TSC, which would vote on the matter.  

File below shows status of schedule at the start of the release meeting.  Changes to the schedule, suggested in the meeting, will be posted as soon as they're available.

File below shows changes suggested during the release meeting.

Actions

  1. Update schedule per the comments in the meeting - David McBride
    1. Re-schedule unmet milestones
    2. Add two feature releases after the main release (i.e. Colorado 2.0, 3.0)
  2. Recommend the schedule to the TSC for consideration. - David McBride
    1. Note that this also includes a recommendation to shift the release cadence from Feb/Aug to Mar/Sept.

MeetBot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-05-17-15.00.html

May 10, 2016

Agenda

  • Continue release milestone presentation / discussion - David McBride
  • Report on status of Functest installer smoke tests - Jose Lausuch
  • Installer / OpenStack (Mitaka) integration & smoke testing status - Installer PTLs (Tim RozetNarinder GuptaWei Shao, Gregory Elkinbard)
  • Documentation - Sofia Wallin
  • Feature / Test project collaboration - Jose Launch
    • Test case descriptions
    • Test infrastructure status

Minutes

  • Note: meeting conducted during PlugFest, in a conference room at CableLabs in Colorado, with about 10 participants, in addition to participants that joined via GTM or phone.
  • Completed release milestone presentation.
  • Trevor CooperMorgan Richomme, and Mark Beierl indicated that we still do not have a firm definition of release criteria.  
    • David McBride took an action to coordinate with test teams and project teams to nail down criteria
    • We will use the Test meeting slot on Thursday to begin the discussion.
  • Frank Brockners said that tracking issues with upstream components is difficult with our existing JIRA implementation.  Possible solutions:
    • OPNFV could be part of a federated group of JIRA instances with upstream components that use JIRA.  This would allow for upstream JIRA tickets to be tracked in OPNFV JIRA filters and dashboards.
      • We would still have a problem, since some of the upstream components do not use JIRA (e.g. OpenStack)_.
    • Create tracking JIRA tickets that contain nothing but a pointer to an upstream issue.
  • Updated status of installer / Mitaka integration.
Installer TeamPresentMitaka IntegrationSmoke Test StatusNotes
ApexYYesPassingFinalizing Jenkins jobs. Should be completed by next week.
JOIDNNo --Expect to complete integration by next week.
FuelNNo --Expect to complete integration by mid-June. 
CompassNNo --Expect to complete integration by mid-May.
  • Jose Lausuch reported that FuncTest installer smoke tests have been repaired.

    • Action for installer PTLs to re-enable FuncTest installer smoke tests and report results.

Actions

  1. Coordinate with test and feature projects to nail down release criteria - David McBride
  2. Enable FuncTest installer smoke tests and report on results - Installer PTLs (Tim RozetWei ShaoNarinder GuptaGregory Elkinbard)

MeetBot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-05-10-14.50.txt

May 3, 2016

Agenda

  • Release milestone presentation / discussion - David McBride
  • Installer / OpenStack (Mitaka) integration & smoke testing status - Installer PTLs (Tim Rozet, Narinder GuptaWei Shao, Gregory Elkinbard)
  • Feature / Test project collaboration - Jose Launch
    • Test case descriptions
    • Test infrastructure status
  • Release meeting reporting - David McBride

Minutes

  • The release milestone presentation led into a discussion of a lack of consistency among CI pods.  
    • Morgan Richomme took an action to document the issue, in detail, and share with the team.  
    • This can be found in an email thread on opnfv-tech-discuss titled "Harmonization and CI use for Colorado".  
    • This issue is also being discussed in a weekly meeting by the newly formed Infra Working Group
  • Tim Rozet asked whether installer teams should be using internal smoke tests or the common Functest smoke tests. The common smoke tests have been disabled.
    • The team agreed that there is no problem using internal tests until the common tests are available.
    • Jose Lausuch agreed that this is an urgent issue and took an action to report on status at the next release meeting, as well as to inform the installer teams when the issue has been resolved.
  • The installer teams reported on the status of OpenStack Mitaka integration:
Installer TeamPresentMitaka IntegrationSmoke Test StatusNotes
ApexYYes (patch pending)PassingPatch should be completed by next week.
JOIDNUnknown gated by Ubuntu 16.04 integration
FuelNUnknown  
CompassNUnknown  
  • David McBride said that future Release meetings would be used more for PTL reporting rather than discussion.

Actions

  1. Report on status of common installer smoke tests (Functest) - Jose Lausuch

MeetBot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-05-03-15.01.txt

April 26, 2016

Agenda

  • Pharos spec modification
  • Coordination between feature projects and test projects
  • Documentation

Minutes

  • Per request from Trevor Cooper, we discussed the need to modify the Pharos specification to accommodate feature project requests.
    • Jack Morgan said that we are lacking a process for handling feature project requests.
    • It is unclear where engineering and hardware resources will come from to handle feature project requests.
    • Issue is being tracked as PHAROS-164 - Getting issue details... STATUS
  • Discussed coordination between test and feature projects.  
    • Feature projects must describe their test case needs early in the release process so that the test projects have sufficient time to implement the new requirements.
    • Jose Launch has set up a wiki page to capture this information.  Need PTLs to fill in the data.
  • Per request form Sofia Wallin, we discussed the Documentation release milestone.
    • Sofia is having a meeting on Thursday, April 28 and requests PTL input on documentation.
    • In addition, there is a regular weekly meeting, chaired by Sofia, to discuss documentation.  See the meetings page for details.

Actions

  1. Complete feature project test info. (feature project PTLs)
  2. Add weekly documentation meeting to the meetings page.  (Sofia Wallin)

MeetBot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-04-26-14.58.html

April 19, 2016

Agenda:

  1. Scenario planning
  2. Milestones for Colorado release

Notes:

  1. Bryan Sullivan reviewed the new scenario inventory page.
  2. Need PTLs to fill in scenario relationships in the lower table.
  3. Discussed scenario owner responsibilities.
    1. Coordinate integration and test of associated projects and features
  4. Discussed the need to document the process for requesting test resources.  
  5. Question:  how do we measure and manage test resource utilization so that we can enable all projects to complete testing for a release?  We need a test resource scheduling tool that allows us to project resource needs vs. capacity.
    1. Noted that not all OPNFV test resources are identical.  Therefore, some projects will need to be scheduled to use specific resources. 
  6. Discussed the possibility of changing the release cadence, as discussed at the recent board meeting.  Strong opinions for and against.  This discussion is ongoing in a mailing list thread.
  7. Reviewed an updated set of milestones.  A new milestone has been added to reinforce the need to provide test case descriptions, including clear pass/fail criteria, early in the process.
    1. Noted that the milestones require better definition.
    2. Need a template for documenting test cases.  Jose Lausuch said that this work is already underway. 

Actions:

  1. Fill in scenario inventory page with scenario associations for each project (PTLs)
  2. Document process for requesting test resources (Bryan Sullivan)
  3. Develop template for projects to document test cases (Jose Launch)
  4. Provide detailed descriptions of milestones (David McBride)

MeetBot Minutes

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2016/opnfv-release.2016-04-19-15.05.html

Artifacts


April 13, 2016

Notes:

  1. Discussed core scenarios vs. master scenarios.  Core scenarios verify a particular feature or component, while master scenarios enable system level, end-to-end test of realistic use cases.
  2. Discussed the difference between installer dependent scenarios and end-state dependent scenarios.  We agreed that the latter should be the goal; however, installer dependence is a necessary, interim step as OPNFV matures.
  3. Discussed the need for an inventory of scenarios, including owner, status, and dependencies.  Frank Brockners agreed that preparing this inventory would be compatible with the work of the Genesis project.  Bryan Sullivan offered to help, as well.
  4. In order to avoid a proliferation of meetings, further discussions about scenarios will be done during the weekly Colorado release meeting.

Actions:

  1. Finish proposing names as owners of current scenarios for review by the team. (David M)
  2. Provide Frank and Bryan with a location for the table of scenarios and dependencies. (David M)
  3. Create table of scenarios, including owner, status, and dependencies (Frank B / Bryan S)

April 12, 2016

Agenda

  • Colorado Milestone discussion
  • Status of Milestone 2

Artifacts

  • No labels

2 Comments

  1. About the time:  Wiki said 15:00-16:00 UTC . : But the Find your local time link directs to 14:00UTC ? 

  2. I have corrected this issue. (smile)