Anuket Project

  • Created by Unknown User (rpaik), last modified on Jun 26, 2017

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

Compare with Current View Page History

« Previous Version 4 Next »

December 20, 2016

Agenda

Minutes

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

 

MeetBot Minutes

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

December 13, 2016

Agenda

Minutes

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

 

MeetBot Minutes

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

December 6, 2016

Agenda

Minutes:

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

MeetBot Minutes:

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

November 29, 2016

Agenda

Minutes:

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

MeetBot Minutes:

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

November 22, 2016

Agenda

Minutes:

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

 

MeetBot Minutes: 

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

November 15, 2016

Agenda

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

Meeting Minutes

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

MeetBot Minutes

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

November 8, 2016

Agenda

Meeting Minutes

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

 

MeetBot Minutes

November 1, 2016

Agenda

Meeting Minutes:

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

 

MeetBot Minutes: 

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

 

October 25, 2016

Agenda

Minutes

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

MeetBot Minutes

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

October 18, 2016

Agenda

 

Minutes:

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

 

MeetBot Minutes: 

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

October 11, 2016

Agenda

Minutes

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

MeetBot Minutes

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

October 4, 2016

Agenda

Minutes

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

MeetBot Minutes

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

September 27, 2016

Agenda

Minutes

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

 

Meetbot Minutes

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

September 20, 2016

Agenda

Minutes

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

 

MeetBot Minutes

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

September 13, 2016

Agenda

Minutes

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

 

MeetBot Minutes 

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

September 6, 2016

Agenda

Minutes

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

MeetBot Minutes

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

August 30, 2016

Agenda

Minutes

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

MeetBot Minutes

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

August 23, 2016

Agenda

Minutes

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

MeetBot Minutes

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

August 16, 2016

Agenda

Minutes

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

MeetBot Minutes

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

August 9, 2016

Agenda

Minutes

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

 

MeetBot Minutes

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

August 2, 2016 

Agenda

Minutes

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

MeetBot Minutes

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

  • No labels