Minutes

Previous minutes approved

Project creation review for NetReady: Georg noted that the project name has been changed to Netready to better reflect the scope of the project. Also, there were no future discussions or inputs around the project scope. Via IRC vote, the TSC approved the project creation.

Hackfest update: Ray provided a quick recap from the Hackfest. Ray will also send out a follow-up note to gauge community's preference for hackfests in 2H'2016.

Board meeting update: There was a feedback from the board to investigate if more hardware is desired for testing/release activities and this conversation started during the Hackfest.

Wiki migration update: Migration to Confluence will commence on Friday (25th) morning Pacific Time and the wiki will be unavailable for a few hours.

Project creation review for Domino: Prakash presented the project proposal and noted that Domino is a label-based publication/subscription system. Interactions with other OPNFV project such as Models and Parsers were also presented in the project proposal page. Via IRC vote, the TSC approved the project creation.

Minutes

Previous minutes approved

Project creation review

OpenSAF - Jonas Arndt presented the history of the OpenSAF project. In response to question if OpenSAF addresses other markets besides telco/carriers, Jonas noted that there has been military applications, but the focus is on carrier networking. Jonas also added that the OpenSAF foundation will dissolve and the license will change to Apache-2 after the April release. There were questions on the license change–Jonas added that OpenSAF is the sole owner of the copyright–and Ray Paik took the action item to discuss the license issue with the legal team. There was also a discussion on hosting code development projects in OPNFV and Dave Neary will start this discussion on the mailing list.

NFV Ready Networking Services: Georg presented the project proposal and the goal of the project is to work with upstream communities to evaluate NFV use cases in the context of cloud networking. There was a good discussion if the work can be under existing projects and on the project scope. Suggestions were also made to change the project name. Georg took the action item to continue the discussion on the mailing list.

Marketing update: Brandon provided a quick marketing update including OPNFV's activities at ONS, CFP for OPNFV Summit that is open until the end of the month, Plugfest website/registration, and start of the OPNFV Meetup program.

Minutes

Previous minutes approved

TSC Meetings in Summer time transitions: With Daylight Savings/Summer times starting in the US, Europe, etc. there will be changes in meeting times for different timezones. TSC meetings will stay at 7-8am Pacific Time.

Brahmaputra 2.0 planning: Daily release meetings are continuing to be held at 6:30am Pacific Time, and Chris Price will send a reminder to the mailing list on the daily meetings.

Release C planning: Ash Young noted that having projects sign-up and begin recording our state for the C-release should be done quickly. Ash also added that project on-boarding is a key item and took the action item to send a mail to the mailing list to kick start the process. There was a consensus on starting the C-release work as soon as possible and having a one-month planning phase. Via IRC vote, the TSC approved establishing the C-release activity immediately with a release cadence of 6 months.

ONOSFW project remaining: Ash Young described that there is a confusion on the name ONOSFW and there is also a trademark issue. Ash also confirmed that this is a simple name change and there is no change in the project scope. Via IRC vote, TSC approved the project name change to NETWORKFW.

Minutes

Previous minutes approved

Brahmaputra release recap/update:

Debra outlines that the teams are focused on troubleshooting scenario's that were not in a completely "release ready" state for Brahmaputra. Also, some of the limitations may not be solved in the B release timeframe and may be documented limitations

Morgan notes the need to establish a methodology for handling C release activities in parallel with B-stable handling. The current assumption is that we will work only on Master and stable/Brahmaputra and tag the releases as they are ready on stable/Brahmaputra. Uli added that we are not doing stable releases, but only stabilizing scenarios. There was a discussion that there is a need to secure resources for stable handling of stable/Brahmaputra once the scenario's are in a stable state while other resources are assigned to the C-release. Octopus/Releng teams have the action item to work with the design teams to establish a resource plan for stable handling for Brahmaputra 2.0 plus document stable branch handling and labeling for stable/Brahmaputra on the release wiki page.

Brahmaputra marketing launch: Heather described various marketing assets that went live earlier in the morning such as the press release, blog post, software downloads page, Brahmaputra landing page, etc.

Release C planning

Chris Price discussed Immediate activities for release planning.. There were discussions on dates (e.g. a month later than the original target), inter-project dependencies, integration/testing, etc. Chris took the action item to start a discussion on the mailing list to iterate on the wiki page.

Release C naming: Ray still collecting nominations and the plan is to send out a poll on March 3rd. A question was raised on guideline for release names, and there was a discussion that there is no strong desire/reason to impose restrictions on release names.

February 23, 2016

Agenda

Minutes

Number of scenarios are ready for release (e.g. Apex/ODL-L2, Compass/ODL-L2, Compass/ONOS, Compass/NOSDN, Fuel/NOSDN, Fuel/ODL-L2, Fuel/ONOS, etc.) There are also projects that have not yet reached a stable scenario (e.g. NFVOVS, KVM4NFV, SFC, BGP-VPN, Doctor, etc.)

There was a good discussion on scenarios that are deploying successfully, but have known limitations. The TSC agreed that scenarios with known limitations can be release on Feb. 25th with limitations documented. (These scenarios need to be reproducible) The OPNFVDOCS team has the action item to work with the deploy and test teams to clarify and fully document the state of each scenario. Aric/Debra/Octopus team also took the action item to ensure that the release tagging process is well understood for the project leads. Tagging must be done by Wednesday for all projects.

Ray discussed updates on the software downloads page. The main download page will have links to deploy tools and users will be taken to a separate page that include software and documentation for each deploy tool. The main page will also have links to composite docs and a link to the release documentation page which will contain all project documentation.

Heather raised the question on the terminology for release iterations. Frank suggested "Release Additions", and there were no objections to the term.

Release C Planning:

Ray took an action item to start a mailing list conversation for the C-release naming

There was a good discussion on learnings from the Brahmaputra release such as resource issues on the back-end (e.g. for testing, CI, documentation, etc.), and with Pharos and install teams. There is also a need to identify early on how many projects will be involved and what impact they will have on integration, testing, and infrastructure. Shifting requirements late in the release cycle is also something that needs to be avoided. Another concern that was brought up was that the OPNFV community is not setup to provide adequate support across multiple versions of upstream projects.

Minutes

Previous minutes approved

Wiki update: Aric noted that once you login with LFID, people should be able to edit the wiki. If there are still issues, please let Aric know.

Committer removal for Releng: Fatih confirmed that there has been no objection from Releng committers to removing Victor Laza as a Releng committer. The TSC approved the committer removal via IRC vote.

Brahmaputra release update: Debra provided the latest on Brahmaputra. Number of scenarios are working (e.g. few Compass and Fuel scenarios are ready for release), but troubleshooting is on-going for issues such as ODL L-3. Debra will update the wiki with the latest status (incl. documentation of identified issues).

Plugfest/Dovetail update: Hongbo presented the latest on the May plugfest Logistics and the Dovetail project. Bryan Sullivan added that there's on-going discussion in ETSI regarding various certification programs and will provide suggestions/ideas to the Dovetail team.

Project creation review for Information Modeling: Bryan discussed the proposal and mentioned that the project is intended to collect information on data modeling, show best practices, and and then collect references to tools. Goal is to provide conduit to SDOs so they can interact with OPNFV through our tools. Suggestions were made to add new committers from HPE & Huawei as was discussed in email threads. The project creation was approved via IRC vote.

Project termination review for LSOAPI: Kevin discussed reasons for project termination listed on the project wiki page. Dave Neary asked if this is an area that needs to be worked on beyond the Brahmaputra release, and Kevin responded that the problem can now be worked on in ODL (e.g. for the Boron release). There was also a discussion that validation of the use case can be moved to other OPNFV projects such as SDNVPN. The TSC approved project termination via IRC vote.

Minutes

Previous minutes approved

Change Request for TSC approval of OpenDaylight Beryllium uplift: There was a discussion on taking OpenDaylight Beryllium due to blocking issues with Lithium. Tapio raised the question if there are any dependencies on dlux and none were noted. The TSC approved to support OpenDaylight Beryllium in Brahmaputra via IRC vote.

Brahmaputra release date and content: Chris discussed two scenarios outlined in https://etherpad.opnfv.org/p/steps_to_brahmaputra. For scenario 2, there was a discussion that some thought should be given to what can be included in Stable Releases. Comments were also made that the community may want to investigate creating a new lightweight release process for stable releases (post Brahmaputra). There was a consensus forming around scenario 2, and the TSC voted to set the Brahmaputra release date to February 25th with incremental stability releases.

TSC Policy document update: Brian Skerry presented the updates on the TSC Policy document following the removal of initial scope constraint on OPNFV. A block diagram from page 14 of https://www.etsi.org/deliver/etsi_gs/NFV/001_099/002/01.02.01_60/gs_NFV002v010201p.pdf will be added to the new TSC Policy page. Also, there was a consensus to remove "…, additional architectural functional blocks, …" above the block diagram. The TSC agreed to move forward with the proposed text and will approve it once we have received feedback from the Board. Ray has the action item to update the text on the wiki page.

OPNFV Hackfest update: Ray noted that the focus of the upcoming hackfest will be on project breakouts and plenary session will be limited to 3-4 hours on the first day Hackfest Etherpad. Will also have additional discussions during the Community Call on Thursday.

Update on Brahmaputra PlugFest planning and activities - Hongbo and team

AoB

Minutes

Previous meeting minutes approved

License scan update: Scott mentioned that another license scan will be done after the code freeze on Friday and individual project teams will be contacted if there questions/issues. Scott also added that if it is not possible to add license information in a file (e.g. for images, binaries, etc.), you can put a license file in a directory. For projects that require files with non-Apache v.2 license, a 3rd party OSS dependency questionnaire will be sent to be filled out by project teams. For documentation, Ray added that Creative Commons license should bs used as noted in the Documentation section of OPNFV Coding Guidelines. opnfvdocs team took an action item to work with the projects to ensure we have the right licensing in our documents. Finally, Scott added that if a file has an incorrect license it can be flagged as a bug, but one needs to be sure they have the rights to change the license of the file prior to making any corrections.

Brahmaputra status update: Debra noted that troubleshooting is on-going after code freeze. Some scenarios (e.g. Compass, JOID) have begun to stabilize, but for others more runs are needed to establish a stable trend. There was a good discussion on the latest proposal for a schedule captured on https://etherpad.opnfv.org/p/steps_to_brahmaputra. Morgan added that having all project teams use the same CI solution will make it easier to track & predict what is happening (e.g. on https://build.opnfv.org/ci/view/OPNFV%20Platform%20CI%20-%20Alternative%20View/). The consensus was that the community will likely have more confidence in setting the release date in about a week’s time. The TSC agreed to postpone setting the release date until next TSC meeting when more information will be available.

Agenda

Minutes

Previous minutes approved

Brahmaputra status update: Debra noted that currently there are 24 scenarios planned and 15 of them are installing successfully. Other scenarios have not been deployed and still working through known issues. On testing, both Functest & Yardstick are working through issues. Morgan also added that there are issues with vPing & vIMS. Currently, there is no scenario that is able to be run according to the release requirement of four successful runs (Compass is closest). Consensus that the community is about three weeks behind on meeting the Milestone E requirements (people are still working towards code freeze in many cases). The community also had to deal with the delay in CI lab resources as many were not available until early January.

Brahmaputra release date and content discussion: There was a good discussion on staying with the time-based approach for the release vs. moving to a more content-based approach (where a release date would be set based on achieving targets for scenarios). Community also learned in the past few weeks that testing required more time than originally anticipated. There was a consensus to create a new schedule with reasonable milestones in order to set a target release date. The TSC decided to postpone the target release date of Brahmaputra via IRC vote.

After the vote, there was a discussion on the definition of code freeze and Chris Price took the action item to start this discussion on the mailing list and vote on the code freeze date.

Minutes

Previous minutes approved

Brahmaputra update: Debra reported that code freeze for installers (e.g. Fuel, Compass4nfv) postponed for a few days due to hardware issues over the weekend. Major challenge now is to stabilize testing suites and test results for the scenarios. Some projects have decided to work in a post-install process to relieve the requirement to support a tested Brahmaputra scenario. Frank added that the TSC will need to determine next week how strict we are on maturity and conformance as we approach the final release date for scenarios that are struggling with stability.

Brahmaputra release marketing plan: Brandon Wick reported that the marketting team is preparing their content for going live on Thursday the 4th, pending a go/no-go decision by the TSC on February 2nd. A new Brahmaputra landing page will also be added to opnfv.org. Jill Lovato also discussed press release, blog post, and social media campaign. Jill also wants to include quotes from project leads in the Brahmaputra PR campaigns. Frank asked how much lead time the marketing team would need for release marketing, and Brandon noted that the 2 day buffer is there to allow for any fluctuation.

Q1'2016 Hackfest at ONS (March 14-15): Ray started a Hackfest planning etherpad and encourages everyone to add suggested topics on the etherpad.

Board meeting update: Chris went over the The January Board meeting summary that was sent out by Wenjing (Board Secretary). During the TSC update, Chris Price communicated to the board that the goal is to stay with the time-based release schedule for Brahmaputra.

TSC Policy document update: Brian Skerry provided an update on the TSC Policy document and suggested doing final edits over the mailing list before voting at the TSC meeting next week.

ETSI NFV Modeling Workshop summary: Bryan Sullivan provided an update from his participation at the workshop (http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2016-January/007651.html). Bryan also discussed his plan to incubate a project that evaluates interfaces from SDO's and how they are able to be applied to OPNFV (and our upstream communities) including evaluating any divergences.

AoB: Ray gave a reminder that an email has been sent to project leads if there were either missing or non-Apache v.2 license information in project repos. A request to address these issues as soon as possible.

Minutes

OPNFV Board update: The January OPNFV board meeting agenda was posted in Board agenda email, and Chris Price shared the TSC update slides that will be included in the board deck.

Q4'2015 Quarterly awards: Ray noted that it is time to start the quarterly awards process for Q4'2015. There was some concern that people that are new to the community may not be getting the recognition with the current process. Ray to start a discussion on the mailing list to collect community feedback.

Project life cycle update: Frank/Ildiko summarized the updates to the document and recent discussions in the community. There was a consensus that further iteration on the document will likely be necessary for latter stages like Integration. The TSC approved the latest project lifecycle document via IRC vote (with 13 votes in favor).

Brahmaputra update: Work is on-going to resolve Pharos issues in order to have a stable infrastructure. Testing is also constrained due to issues with deployment scenarios and this is being addressed. Scenario freeze date has been pushed out to January 15th to allow more features into Brahmaputra. Debra is also driving towards test tools, installers, and infrastructure projects freeze by January 19th. TSC should have the necessary information by the next TSC call (January 19th) to make an informed decision on the release.

C-release milestone discussion: There was a discussion on the need to clarify milestones for the C-release.

The following people volunteered to help Debra with this activity Uli, Fatih, Edgar, Ildiko, Trevor, Tim Irnich, and Frank Brockners.

January 5, 2016

Agenda

Release readiness team, to provide steering and the TSC with recommendations, with Ray and Debra

AoB

Minutes

Minutes for December 15, 2015 approved. Approval for the December 22nd minutes deferred to next week.

Confluence migration: Aric reported that the universal migration tool from Atlassian is no longer available and is looking for community help to structure the new wiki. Bryan Sullivan, Mark Beierl, and Chris Price volunteered to help with the work.

Alan Sardella also starts this week as a Technical Marketing Manager for OPNFV.

License scan for Brahmaputra: Scott Nicholas reported the outcome of the recent license scan and not all projects are following the best practice of including licensing information in files (and not just having a license file in each directory). Scott and Ray will be reaching out to project leads if there's missing license information or if there's a-non Apache 2 license. Scott also added that investigation on license for binary files is still on-going. Scott/Ray will also share the license scan data with files that are missing license or has non-Apache 2 license.

Brahmaputra update: Debra reminds everyone that the deadline for Milestone E (code freeze and establishing the stable branch) is today. Debra presented the idea of a "release group" that can evaluate release readiness. There was also a good discussion on Brahmaputra Scenarios. The preference is to ensure that key groups like functest, Pharos, yardstick, releng, installers, scenario leaders, etc. are represented in the "release group".

Release readiness team, to provide steering and the TSC with recommendations, with Ray and Debra

AoB

Minutes

Updates from the December board meeting: There are two new member to OPNFV. SUSE joined as Platinum and CENGN is the first Associate member. There was also a report out from the Strategic Planning Committee on MANO discussions. For future board meetings, agenda will be published and also a summary of the board meeting will be shared publicly.

Brahmaputra update: There are issues with a jump host at Intel labs, so not all PODS are available. There was also a discussion on the need to include development testing on Pharos infrastructure earlier in the release cycle.

AoB: Need to discuss the "release readiness team" during the next TSC call.

Minutes

Previous minutes approved

OPNFV internship program proposal: Ray presented the proposal for OPNFV internship. This is a year around program with options for either 3-month or 6-month project. The mentors will be responsible for posting the project proposal, selecting, and managing the intern. Thus the availability and dedication of mentors will be key to the success of the intern project. The community is asked to provide additional feedback via mailing list or wiki.

Review and comments on the API workshop material: Bryan Sullivan will be representing OPNFV at the API workshop, and the goal of his presentation is to communicate our desire to collaborate with SDO' performing interface modeling and specification. Bryan is soliciting feedback/input from the community especially on some technical areas.

Methods of publishing requirements work with our release: Uli noted "requirements" documents we release should receive a proper review. However, adding them to the documentation tree would not require a huge effort. There was also a discussion that requirements documents are living documents.

Project Creation Review

OVN for NFV project proposal: The goal of this project is to align on NFV requirements and contribute upstream to OVN. There was a question on what additional capabilities are provided by OVN, and Vikram noted that OVN provides an alternative method of implementing existing features and distributes network control elements. In response to questions regarding OVSNFV project, Vikram noted that objectives of OVN and OVSNFV projects are different, but the intention is to work with OVSNFV team. Via IRC vote, project creation was approved for ovn4nfv (+1: 8 votes, 0: 4 votes, -1: none as shown on IRC log)

Updates from the December board meeting: postponed to future meeting as time was running out

Minutes

Previous minutes approved

Action points

Plugfest working group e-mail: Chris Price sent an email to the mailing list seeking volunteers for the upcoming Plugfest.

Q1 Hackfest poll: The poll was close between Collab Summit (18):ONS (15). There was a good discussion on whether it makes sense to have two separate meetings or one meeting at one location. Via IRC vote, the TSC agreed to have the Q1 Hackfest co-located with ONS (week of March 14th, 2016).

Removal of OPNFV's initial scope constraints: Prodip Sen gave an update to the technical community on the board's decision to remove initial scope constraints. Prodip noted that most of the concerns were around the timing and not necessarily on removing the constraints. There was a feedback that the technical community would like more transparency and discussion around important topics like the scope. The community also discussed if the TSC Policy document needs to be updated with the removal of scope constraints, and there was a general consensus that an update is need. Dave Lenrow and Brian Skerry have the action item to start a workgroup and propose an amendment of the TSC policy for TSC review.

Brahmaputra milestone D report: Debra shared the Milestone D report plus projections for Milestone E. Some of the concerns approaching Milestone E are CI unknowns, installer interactions, resource issues, etc. Chris Price noted that one of the learnings from Brahmaputra is that there is a need for more detailed information on milestone criteria.

TSC meetings rest of the year: There will be TSC calls on December 22nd & January 5th. NO meeting on December 29th.

OPNFV input at Jan 13-14 ETSI NFV-ISG Inter-SDO Information Modeling Workshop: Bryan Sullivan sent out emails to mailing lists regarding the workshop and Bryan is looking for community to provide input from OPNFV as he is developing the presentation.

Artifact page updates, approval of budget: There was a discussion on revamping the current artifacts page and Fatih has an action item to start discussing the new artifacts page design on mailing lists. Via IRC vote, TSC approved the budget for the new artifacts page.

Minutes

Previous minutes approved

Milestone D update: Debra noted that milestone D reports are looking good, but projects are reporting issues as they work towards Milestone E. Debra will also reach out to project leads for 1-on-1 discussions.

Plugfest support: Certification & compliance committee wants to have plugfest events following each release. First one is targeted for March-June timeframe after the Brahmaputra release. Chris Price noted that a working group (for testing/integration) is needed to support plugfests. Chris Price/Wenjing will send a note to the mailing list to start the conversation on the Plugfest working group

Q1'2016 Hackfest LF Collab-Summit vs. ONS discussion: There was a good discussion on co-locating the Q1 hackfest at either the LF Collab Summit (Lake Tahoe) or ONS (Santa Clara). Ray Paik took the action item to send out a poll to gauge community preference.

OPNFV security initiative: Luke described LF's Core Infrastructure Initiative (CII) badge program and how many of the items in the program provides a recommended framework to help OPNFV focus on security as a community. There was a good discussion on impact of upstream components and how the program applies to an integration project like OPNFV. There was a consensus in the TSC for the OPNFV security group to pursue the CII badge program.

Pharos LF & Community lab use for Brahmaputra release processing: Fatih explained that there will be resource constraints for Brahmaputra testing if we constrain the release testing to be done only in the LF labs and would like to take advantage of capacity in community Pharos labs. There was a good discussion on which community labs can provide the capability and the need to re-purpose some of the developmental labs for release testing. Using community lab resources also gives the community to demonstrate portability of OPNFV. The TSC agreed to allow the use of Pharos community labs for release testing.

Confluence page is up for community review/feedback (both Dokuwiki & Confluence pages will be available during the review period): 2 weeks

Complete migration to Confluence and archive Dokuwiki pages (archived dokuwiki pages will be available for 6 months)

Finalize the review of the Board f2f and discussions - Chris

AoB

Minutes

Previous meeting minutes (from the past two meetings) approved

Milestone D update: Debra notes that she will prepare a list of questions for projects participating in Brahmaputra and will this will be listed on the wiki page.

Project lifecycle discussions: Ildiko provides updates on updates being made to project proposals wiki page and needs the project lifecycle page to be updated. Ray Paik responds that the update is in progress and should be updated soon. There was a discussion on the Word template of the project proposal and the consensus was to remove the Word template and continue using the Wiki template.

Project scope changes: There was a discussion on what needs to be done when project's scope changes post creation. The consensus was to have project teams notify the TSC of the scope change and the TSC reserves the right to discuss/review the scope change. There was also a suggestion that changes in the project should be well documented in the project wiki page.

Process for archiving projects: There was a discussion on how a project maybe archived when the project has no active members. Also, when dormant projects are listed on the wiki this may cause misconceptions on OPNFV's activities. So far, two dormant projects have been identified, and Ray Paik contacted the project teams regarding archiving those projects.

Finalize the review of the Board f2f and discussions: Uli raised the concern that a major changes in the technical aspect of the project as a result of board discussions should be discussed in the technical community. Chris Prise raised the point that board discussions are not public information so this is not always easy. Discussion ensued, and Uli made a request that in the future Chris Price ask for more time to the board in order to collect more input from the technical community.

Wiki migration plans: The community is generally in agreement with the proposed timeline, however, the request is made to start the migration process post December 1st (Brahmaputra milestone D).

Update on the Technical Community budget proposal: The OPNFV approved the technical community budget proposal on November 13th. Work can now start on new programs such as on-boarding and internship programs.

OPNFV Project Life Cycle changes and amendments to Bylaws & TSC Charter: The board approved amendments to bylaws and the TSC Charter with the streamlining of the project life cycle. Feedback from the board was that there is a proliferation of many projects and new projects may want to investigate joining existing projects. There was discussion on the need to re-visit metrics on how projects progress from incubation to mature and if changes are needed for project creation. Frank took the action item to begin working on establishing the metrics and evaluation criteria for project progression post Brahmaputra. Dave Neary and Ildiko will also work on clarifying expectations on project creation with the recent amendments

Four additional Cisco UCS servers at the LF Lab: New servers are now available in the LF lab and the infrastructure will now be reconfigured to provide 2 POD's for deployment and 2 stand alone servers for nested deployments as well as providing build machines for jobs. Trevor took the action item to update the Pharos page to reflect the changes in the LF lab.

Bryan noted the need for the install scripts to amend functionality to the common Genesis deployment. This creates and opportunity to invest in community crowd sourcing for developing and maintaining component integration scripts.

Agenda

Minutes

Previous minutes approved

Latest from the Design Summit & OPNFV Summit: Design Summit has been well attended with good energy. Some of the areas for improvement are room sizes, availability of whiteboards, video streaming, and confusion on room reservations (wiki/etherpad/whiteboards)

OPNFV Software License: Scott noted that the having the license information in a file (vs. a directory) is a good practice and should continue. There were questions on if the information on OPNFV Coding Guidelines is accurate and how to handle gif/jpeg/binary files. Ray has an action item to investigate these questions with Scott and report back to the technical community.

Brahmaputra artifact governance and expectations: Dave Neary noted that he wants Brahmaputra to be based on at a minimum patches that are accepted upstream. However, Frank mentioned that this may not always be possible due to the large cross project dependencies in OPNFV and adds that install teams are concerned about the amount of last minute work that might come up. PTL's have the action item to provide your requirements are into the genesis requirements by November 13th. Frank and Chris Price will also put a concrete proposal together on release contents

Design Summit & OPNFV Summit: Ray noted that there will be whiteboards at the design summit so that project teams can update their breakout sessions real time. Also the latest schedule can be found at http://events.linuxfoundation.org/events/opnfv-summit/program/schedule. Debra is also planning to have 1-on-1 sessions with PTLs. Ray will also schedule a meeting room (plus coffee/breakfast) for the TSC meeting at 7am on Tuesday (Nov. 10th).

Brahmaputra artifact governance and expectations: There was a good discussion on different approaches. There is a view that some level of stability needs to be provided by upstream communities. Another possibility is to introduce "experimental" features that are not published in upstream communities. There was also a desire to allow OPNFV community to push ahead and publish their work in OPNFV releases. The consensus was to have further discussions on this topic during the design summit and Chris Price has the action item to schedule this session.

Minutes

Previous minutes approved

TSC meeting times: Just a reminder that Daylight Savings Time ends in Europe next week and in N. America the following week. This will shift the TSC meeting times an hour later for many countries in Asia starting on November 3rd.

Committer removal:

There was a good discussion on how to deal with inactive committers and there was a consensus on the following text "An approval by the project's committers to remove the committer in question from the project, i.e. no objections." Via IRC vote, the TSC approved the committer removal process.

Committer removal requests for Octopus: The TSC agreed to removing Palani Chinnakannan from the committer list. Sudha Kumari is interested in continuing as Octopus as committer.

A reminder that Quarterly Awards nomination closes tomorrow and there'll be a separate nomination for the Annual Awards. For the annual awards, eligible voters will be limited to opnfv-tech-discuss subscribers with a Linux Foundation ID.

Pharos lab updates: Trevor discussed pre-requisites for using community labs for the purpose of parallelizing Brahmaputra release activities. All project leads have the action item to provide relevant information for the Brahmaputra release to the Pharos team. Relevant wiki pages are:

OpenSAF introduction and discussion: Jonas Arndt (HP) gave an overview of OpenSAF. Jonas noted that OpenSAF looked at use cases such as HA for NFVs and HA as a Service. There is also a plan to move from LGPL 2.1 to Apache 2.0 licensing. Companies currently involved in OpenSAF are HP, Ericsson, Oracle, etc. Jonas is proposing to bring OpenSAF under OPNFV (in addition to proposing projects with OPNFV). There was a consensus to continue the discussion on the mailing list and Chris Price took the action item to provide an update to the OPNFV Board (esp. on potential issues with scope, location of code, etc.)

Demo theater & design summit update: Community members are encouraged to sign up for project overview sessions at the demo theater etherpad page. Design Summit will have parallel tracks for tutorials and project breakouts, and you can add session proposals on the design summit etherpad. For both the demo theater & design summit, the deadline to sign up is October 23rd. Ray took an action item to send out a sample schedule for the design summit so people can gauge how many additional sessions can be accommodated.

Community election process: There was consensus on the overall process, and a good discussion on the publication of results. For the next few elections, there was a consensus to publish the results on opnfv-tech-discuss mailing list if all nominees agree. The TSC voted to approve the new community election process via IRC vote.

Minutes

Previous minutes approved

Strategic Planning Committee: Chris Donley discussed the need to address OPNFV end-users in Brahmaputra with a theme of "lab-ready". The mapping of identified capabilities vs. projects participating in Brahmaputra was also presented. Chris Donley also mentioned that the release cadence and iterative development was viewed as more important than feature completeness. The Strategic Planning Committee (SPC) will be happy to facilitate community support for resource shortages. SPC will also look into 2 release out moving forward and also try to return to the TSC with feedback earlier in the planning cycle (e.g. prior to Milestone C).

TSC update to the board: Chris summarized the TSC update to the board, which included community elections, project lifecycle updates, Brahmaputra milestone C, and Pharos update.

Community Lab readiness for Brahmaputra: There was a good discussion on the desire to have additional servers for the CI team in the LF lab and agreement to request additional funding to the board. There was also a discussion on the need to have more Pharos labs available to the community. The Pharos team have the action item to identify labs that intend to participate in Brahmaputra and be part of the CI pipeline.

OPNFV release artifacts: There was a voting on the preference for release artifacts, and the Genesis team will take the TSC members' preference into consideration. The "Install script per installer" received the most votes.

Release maintenance: There was also a vote on the preference for release maintenance, and "Latest and stable branch maintenance" received the most votes.

Wiki tool decision: Ray noted that the preference from the community was to migrate to Confluence. After a vote, the TSC agreed to migrate the wiki tool to Confluence.

OpenStack Tokyo: OPNFV' activities are listed at https://etherpad.opnfv.org/p/OpenStackTokyo and community members are encouraged to volunteer at the OPNFV booth. Ray will also follow-up with TSC members if re-scheduling the TSC call that week to Monday at 17:00 local time will work.

Minutes

Previous minutes approved

Release artifacts: Frank summarized options discussed to-date on what OPNFV releases. The concern is that the current approach requires a significant effort. Discussion ensued and Chris Price took an action item to start the email vote on the mailing list for the TSC members to state their preference.

Arno SR1 status: Frank noted that there are issues remaining with the CI pipeline, so SR1 will not be ready today. The TSC agreed to the delay of SR1 to enhance stability.

Brahmaputra milestone C: Debra reports that as of the TSC call, 38 projects have reported for Brahmaputra. No projects are reporting Red, while some projects have concerns around resourcing or dependencies (but are non-blocking). The TSC agreed to pass Milestone C for Brahmaputra.

Election processes and improvement opportunities: Dave Neary presented some of the feedback received after our previous round of community voting. Dave suggested "Active Technical Contributor" (vs. committer) for board representation and discussion ensued on the definition of Active Technical Contributor. Dave took and action item to lead a community discussion on what an Active Technical Contributor means and propose a concrete proposal for running future elections for the TSC to vote on next week.

Upcoming "meet-ups"

SDN/OpenFlow World Congress (Düsseldorf): Heather proposed a community dinner among mini-summit participants in lieu of a larger meet-up.

Wiki tool: Ray took an action item to request a vote on the TSC mailing list for the community's opinion on migrating to Confluence.

Minutes

Report on the OPNFV Board meeting: Chris gave a summary of the OPNFV Board meeting on September 14th including the report out from the Strategic Planning Committee

Bylaws amendment discussion: The proposal is to remove top-level projects and the nomination of a nominal number of community members to the TSC (vs. all top-level project leads). Via IRC vote, the TSC approved the changes and making the proposal to the board.

Election processes and improvement opportunities: Suggestions so far has been publicity of nomination statements, use of mailing lists, and publication of results. The discussion was postponed to next week.

Technical community budget overview: Ray made a proposal for the Year 2 budget (incl. "developer collaboration" for the technical community), and this still needs board approval. In addition to budget items we had in Year 1 (e.g. hackfests, awards, infrastructure maintenance, community analytics, etc.) newly proposed items are for ambassador/user group programs, training materials, internship program, etc. Training materials such as those on Jira that were recently developed and posted will be paid for from the proposed training budget. Ray took an action item to create a wiki page for the Developer Collaboration budget items.

Brahmaputra milestone C: Debra outlines that many projects are actively working with Jira, and work is on-going on solving tooling options. Debra will be opening IRC on Thursday to track project reporting on IRC for milestone C readiness and the IRC will remain open until Friday. The TSC will review milestone C and decide pass/no pass on milestone C during next week's TSC call

Minutes

Ray Paik suggests to have minutes posted by 17:00 Pacific Time on Thursdays to allow for feedback/questions. Ray also proposes that if there is no feedback by the next TSC call, the minutes can be considered accepted. The TSC agreed that this proposal to allow 5 days for review prior to the minutes being accepted automatically is acceptable.

Bylaw amendment review: Ildiko summarized the community member discussion on amendment to the Project Lifecycle and the Bylaw. Major changes include removal of the top level project, adjustment of the bylaws to remove TSC seat s for top level project leads. Frank Brockners proposed that adding a cap to the size of the TSC may be a good idea. Discussion ensued and consensus was that another call was needed for further discussions.

OPNFV release

Artifacts: Frank took an action item to provide a summary of our option for release artifacts in a wiki so that an informed decision can be made in a future TSC call.

Ray notes that three nominations have been received and nomination statements and links for the vote will be sent out to all committers on September 16th. Voting will close at noon Pacific Time on September 23rd.

Project creation review (tentative)

Project: StorPerf - Storage Performance Benchmarking for NFVI: Edgar described that the project plans to create a stand alone performance testing solution for storage. Following the first phase the plan is to integrate the tool with qtip and yardstick projects. "storperf" name will also be used for Jira and Git. Project creation was approve via IRC vote.

OPNFV wiki tool: Ray summarized the results from the poll for wiki tool preferences. Confluence received the most votes (10), but there was a concern that the number of people voting was low (23) considering the size of the community. There was a consensus to get additional data on the number of active wiki contributors and conduct another poll on the wiki tool.

Minutes

TSC Chair: Received two nominations and voting will start on September 8th and will close at Noon Pacific Time on September 15th.

Committer Board: Propose postponing the election process by a week so that PTL can make updates to the committers lists.

Managing the communities proliferation of project meetings: Dave Neary/Tom Nadeau notes that real time meetings are not a productive method to apply in open source projects and would like to see more discussions take place asynchronously. Discussion ensued on universal access to IRC, desire for real-time meetings for early stage projects, need to encourage PTLs to have IRC-based meetings, etc.

Community lab Pharos integration and CI processes report/discussion: Uli notes that activity is ongoing around the use of Pharos labs for octopus, but there's a need for community lab representatives in Pharos meetings. Trevor also added that he would like to see more direction around pharos planning and lab federation. Uli requests all TSC members who have labs involved in Pharos should ensure the labs are represented in Pharos meetings.

OPNFV Support review and next steps: Chris Price noted that most requests/questions on opnfv-users mailing lists have been answered by 2 people within a day. However, there is a concern that this is probably not scalable.

Project creation review:

ARM Band: Bob notes that the goal of ARMBand is to integrate and support the use of ARM in the Brahmaputra release. The project has identified a number of OPNFV project they will need to work with including CI & deploy projects, integration of ARM-based labs into Pharos, etc. The project creation was approved via IRC vote.

Pinpoint: Adi explains that the project will focus on fault correlation on the OPNFV platform. There is also an invitation for community members to join the project. The project creation was approved via IRC vote.

Minutes

Upcoming OPNFV elections: First election is for the TSC chair that is open to TSC members. Second is the Committer Board elections that is open to all committers in OPNFV. Nominations open for both elections starting today. Chris Price took the action item to add the topic of Committer Board elections to Thursday's Tech Discuss call.

OPNFV Design Summit: OPNFV Summit planning is done and speakers have been notified. Some talks were moved to the Design Summit which is in early stages now. See Design Summit Etherpad. OpenDataPlane & OpenDaylight will also co-locate their hackfests during the OPNFV Design Summit.

Linux Foundation Data Center: Another router is needed (~$US 1,500) so additional vlans can be added without downtime. The TSC approved the purchase via IRC vote.

Weekly Brahmaputra release project meeting: Debra will run a weekly meeting following the TSC call on Tuesdays.

Project creation review:

SDN distributed routing and VPN: The project intends to address extending VPN's in the datacenter. The project will be done in collaboration with the related bgpvpn project in OpenStack and supported implementations in SDN controllers to make sure that the functionality can be integrated on the OPNFV reference platform for the Brahmaputra release and onwards. The committer list needs to be updated for the project. The project creation was approved via IRC vote.

Controller Performance Testing: There is a need to establish a project that performs performance testing of controllers in real hardware deployments for SDN controllers. There will be participation from the upstream ODL performance testing project, and hopes to work with other SDN controller teams. The project creation was approved via IRC vote.

dovetail Project: The project will work under the guidance of the OPNFV C&C Committee. The project creation was approved via IRC vote.

Minutes

SDN OpenFlow World Congress: CFP running for the mini-Summit. Also exploring technical community meeting in Düsseldorf and will need local people's help with this.

OpenStack Tokyo: No OPNFV Day due to space constraints. Exploring a community dinner plus ~1/2 day meeting. Heather will create an Etherpad page to coordinate the "meet-up"

There is also an IETF hackfest on the weekend after the OpenStack Summit

OPNFV Summit

Currently reviewing CFP submissions: There were 131 submissions and expect ~25% acceptance rate. There may be some combining of topics and also planning on a "demo theatre" area for project-focused sessions

Weekly Brahmaputra release project meeting: Frank presented the idea to use the 1 hour after the TSC call for Brahmaputra release planning. This means that the Technical Community call will remain on Thursdays.

Minutes

OPNFV Arno SR1 date setting: Frank presented the Arno SR1 planning information captured in the OPNFV Arno SR1 page. The target release date will be September 29th with code freeze on the 15th. There was a discussion that the list of bugs will captured in release documentation (plus there is also a Jira list). The SR1 plan was approved by the TSC via IRC vote.

Brahmaputra release: There was a good discussion on two release date options of Nov’15 or Feb’16. The Feb’16 release will likely include ODL-Li and OpenStack-Liberty. Plus with a 5-month offset with OpenStack, will likely be working with a more stable version of OpenStack. Frank points out that a November release would be OpenStack-Kilo & ODL-Li. Chris Price also added that even with the Feb'16 release, year-end holidays mean 4 effective months from the Liberty release to Feb'16. The TSC voted for the Feb'16 release of Brahmaputra via IRC.

OPNFV release, stable support discussion & decision: Inconclusive discussion ensued on the topic, outlining the challenges of maintaining a release as compared to supporting consumers of OPNFV. Chris will raise the topic on the mailing list.

OPNFV release, artifact discussion & decision: Dave Neary noted that producing a release ISO was difficult in Arno and will be further complicated in Brahmaputra with multiple installers and component choices. Dave Neary will raise the topic on the mailing lists.

Project creation review:

Edge NFV: James outlines that the project intends to enable the utilization of edge compute capability in the OPNFV infrastructure, and the focus of EdgeNFV project is on the compute node. James has also been in communications with the LSO team and does not foresee conflicts between EdgeNFV & LSO projects. The project creation was approved via the IRC vote.

Minutes

Previous minutes approved

OPNFV Project classification discussion: Ildiko led a discussion on a proposal to combine the project types in the OPNFV project lifecycle document into a single project type. Projects would include needed combination of documentation, development, needed integration and testing and is reflective of the way the projects are working in OPNFV today. Ildiko also proposes re-classification of project types to; Continuous Build and Integration, Continuous Deployment and Testing & New Requirements and Features. There is also no need for a "top-level" project. TSC agrees to continue development of these proposals and there will be a community activity to revise documents such as Project Lifecycle, TSC Policy, Bylaws, etc. and bring to the TSC for review at a later date.

OPNFV Brahmaputra Release discussion: Debra mentions that based on feedback received so far, there is limited dependency on OpenStack Liberty which makes a December release a viable (with OpenStack Kilo). Discussion ensued if the community is comfortable with being “behind” on OpenStack release if we stay with June/December cadence (installer support & testing will likely require ~2 months post OpenStack release). Debra also shared the Brahmaputra release page (release_plan) with the definition of the release theme "Lab Readiness". A suggestion was made to agree on dates for Milestones A/B/C next week.

Project creation review:

Project Name: Genesis: Frank noted that the genesis project intends to work across the installer projects to create a common set of requirements for the installers to comply to during the release. The project will also work with component teams to facilitate the integration of new components into the installers. Frank also added that governance details are still in draft and will evolve. The project creation was approved via IRC vote.

Open Daylight Summit & OPNFV Hackfest report out: The hackfest included an awards, a panel with key OpenDaylight developers, and a session with ETSI NFV ISG Thursday morning. The rest of the hackfest was dedicated to tracks with good break-out sessions on Thursday afternoon and Friday.

Brahmaputra planning read-out: Debra will set up 2 weekly calls (EMEA & APAC timezones friendly) with project leaders to work through Brahmaputra planning and activity. Debra will also post the Brahmaputra planning presentation on the wiki

TSC meeting length: Based on votes from TSC members, the consensus is to reduce the TSC meeting length to 1 hour. The TSC agreed to reduce the meeting length to an hour starting in 2 weeks.

Project creation reviews:

OpenContrail Virtual Networking for OPNFV: Stuart Mackie (Juniper) described the use of the OpenContrail controller and OVR to provide the networking component of the OPNFV platform. A suggestion was made to remove the versions from the upstream releases in the proposal. Project creation was approved via IRC vote.

OpenSteak Installer: Arnaud Morin (Orange) outlined the strategy for the installer is to keep it very simple and streamlined. The installer is based on ubuntu, relying only on upstream puppet modules and foreman. Project creation was approved via IRC vote.

AOB: A question was raised if there is a need to validate all deployments on the LF infrastructure for Brahmaputra. Chris Price took the action item to clarify the relation between the Brahmaputra release process and various labs.

July 28, 2015

Agenda

Minutes

Meeting is shortened to 1 hour and will focus on project reviews.

Project creation review:

Bottlenecks: The project provides a framework for identifying coarse and fine-grained OPNFV system level performance including identification of performance bottlenecks. The project will work with Qtip and other performance-related OPNFV projects. The project creation was approved via IRC vote.

Minutes

No objections raised on the minutes of the previous meeting, however no quorum for approval

Evolving project categories: Ildiko started discussion on the mailing list and discussion on requirements & development projects is planned during the hackfest.

Release planning: Debra discussed projects for Brahmaputra that we will not release without/working plan/at risk/outside of plan. Debra will post an editable document on the wiki for feedback.

Joint Board-TSC meeting agenda: Ray presented the agenda for the meeting on the 27th and they are C&C committee report out, strategic goals for OPNFV, Brahmaputra planning, resource needs/gaps. The meeting is only for board & TSC members (or named alternates)

Compass Based OPNFV Installer Project Proposal: Weidong (Huawei) presented the proposal. A suggestion was made to update the list of committers. Also, when asked if there's a dependency on the new Genesis project, Weidong responded that their intention is to be part of Genesis and will reflect that on the wiki. The project creation was approved via IRC vote.

Open vSwitch for NFV: Mark (Intel) presented the proposal and noted that there's no intention to fork OVS. It is an upstream OVS project initially focused on enabling kernel and user space OVS deployments in the OPNFV platform. The project creation was approved via IRC vote.

New structure for TSC calls: Currently the TSC meeting is 2 hours long with a mixture of informational discussions and decision making. Proposal was to shorten to 1hr and focus on decision making. Ray will send out a SurveyMonkey poll to gauge TSC members' preference.

Minutes

Previous minutes approved

Requirements project development process: Ildiko noted that requirements projects should have end-to-end coverage from use cases to implementation. There will be a breakout session at the upcoming Hackfest and Ildiko will look for new requirements projects to test out the new approach being discussed. The current proposal includes (1) Evolution of the current project categories (2) Process for requirements projects, but further discussions should focus on (2). Ray Nugent & Ildiko took the action item to start a separate discussion on evolving project categories.

Request for a formal approval to allow CI/CD Pipeline to support script and ISO deploy methods: This was what was done for Arno, but it is too early to decide what the packaging options would be for Brahmaputra.

Support for OPNFV hardware @LF data center: LF support is limited to bare metal hardware support (cabling, power, network connectivity, etc.) and theres a need for additional infrastructure support from the community. More information available at Linux Foundation Infrastructure Support Process

Quarterly awards: Send your nominations to Ray Paik by Noon Pacific Time on July 15th. Ray will send email to TSC members for voting.

Proposals to split the current TSC calls to 1 hour of TSC (for decision making) plus 1 hour of technical discussions. Dave Lenrow took the action item to bring this discussion to the mailing list.

Project creation review:

Apex: This is a continuation of the Foreman work that was done as part of BGS and will include fixes for Foreman for Arno SR1 and a new installer (RDO manager) for Brahmaputra. Contact Tim Rozet if you're interested in being committer/contributor to the project. The project creation was approved via IRC vote.

Release Engineering: This is to formalize the already ongoing work for "OPNFV infrastructure" across various projects. releng repo exists already and was instrumental for Arno. The project creation was approved via IRC vote.

Connectivity Services LSO: This is requirements project for API on OpenDaylight controller to drive MetroEthernet Services. ODL is just the initial focus of the effort and API could also apply to other controllers. There was a discussion that this may be a good project to test the new approach for requirements projects and Ildiko will contact Kevin @CableLabs. The project creation was approved via IRC vote.

Minutes

Action Item follow-up

Requirements projects development process: Vacation period is making it difficult to gather inputs. There is a session planned at the upcoming hackfest

Test strategy overview: Trevor discussed the current set of testing and related projects that can be found at Testing page. The page includes information related to coverage of component testing, platform functional testing, and performance testing, etc. Tables listed under “Test Category” show areas where test coverage is lacking. Test & Releases” table shows plans for the Brahmaputra release. Morgan added that description of tools for testing will be developed (esp. for new projects). Also, Functest demo has been recorded and and will be posted on the OPNFV channel by Brandon.

OPNFV Kiosk at the OpenDaylight Summit: We want to have the booth staffed by community members. Ray will setup an Etherpad page for people to sign-up for 2 hour shifts. [Etherpad is now available at https://etherpad.opnfv.org/p/OPNFV_Kiosk_at_ODL_Summit] If we can not put together a demo in time for the ODL Summit, this will be an informational booth with collaterals.

Fuel based OPNFV installer project proposal: Jonas describes that the project will be a continuation of the fuel deployer activity from Arno into the Brahmapurta and beyond. The project will also collaborate with the new Genesis project and continue to work with the CI project to provide an option for deploy capability for OPNFV. Jonas also explained that you need to provide a Fuel plug-in if you want to incorporate a new upstream component and there is a demo available on how to write plug-in's for Fuel in OPNFV (https://mirantis.webex.com/mirantis/ldr.php?RCID=91679dc40d1c1d0360dc4a9602058aca). The Fuel project will have its own repository and Jonas will clarify the repo name on the wiki. The TSC approved the project creation via IRC vote.

Minutes

Previous minutes approved

OPNFV Lab utilizations: Chris discussed a proposal to configure one of the PODs to provide an infrastructure for continuous bare-metal deploy and test with the 2nd POD providing infrastructure for various jobs including build, test & virtual deploys when we work with pushing patches and merges. The TSC agreed to have the octopus and pharos teams reconfigure the LF lab to provide build infrastructure on one of the POD's The Pharos team has the action item to provide lab configuration accordingly. The Octopus team has the action item to enable CI pipeline to utilize one build POD and one deploy POD.

Arno stable release proposal: Uli described the approach for working with the Arno stable release branch and asked for feedback to be provided directly to Uli so that he can incorporate them on Stable release wiki page. TSC agreed to use the documented stable release plan for the Arno stable branch. Uli will also migrate the wiki page to RST format in the Octopus repo.

Release 2 planning: Debra discussed Brahmaputra planning activities. For milestones & timelines, Debra explained that once milestones A & B are set, subsequent milestones can be defined. Also, inclusion in the Brahmaputra release is open to any projects until Milestone C. The was also a suggestion that further dependencies such as deployment tools should be included in the upstream schedule slide.

Agenda for the joint board & TSC meeting on July 27th: Proposed agenda was reviewed without comment

OPNFV kiosk @OpenDaylight Summit: OPNFV will have a kiosk at the ODL summit and need community volunteers to help staff the kiosk.

OpenStack Summit Tokyo: Heather discussed that we have another opportunity for an OPNFV Day at the upcoming OpenStack Summit. The OPNFV Day maybe on Tuesday or Wednesday this time.

Project creation review for kvm for nfv: Jun Nakajima presented the project proposal. There was a suggestion to select a single project category. When asked about licensing of KVM vs. OPNFV, Jun responded that the goal is to submit patches in the KVM repo. The project creation was approved via IRC vote.

Minutes

Previous minutes approved

Release 2 Naming: The winner is Brahmaputra. Other contenders were Bourne, Bode, Beam, and Beppu.

Hackfest: Planning started with discussion among planning volunteers. Suggestion was made to involve Phil Robb & Colin Dixon from ODL to coordinate topics. Also Thinh Nguyenphu (ETSI NFV EVE WG chair) made a suggestion to reach out to the TST to explore collaboration opportunities as ETSI also has a meeting during the same week in San Jose.

Bitergia tool: Ray discussed that Bitergia came highly recommended from OpenStack & CloudFoundry and can track developer contributions in code, reviews, wiki, etc. There was a discussion on privacy concerns that LF team can investigate.

Committer roles and forge author identity: The purpose of allowing forge is to help project teams be more agile (e.g. when author is away, for very simple fixes, etc.). The TSC agrees to allow forge author identities on respositories for 3 months and then re-evaluate.Aric has the action item to enable this in repo's

Action item follow-up:

Requirements project development process: Uli reports that the work is ongoing, but nothing new to report yet

Pharos plans: Trevor reports that meetings for LF infrastructure support & testing strategy are being scheduled

Security group report: Luke discussed the idea of the idea of performing a security audit of a deployed Arno platform. The activity will help identify any issues and establish some best practices for OPNFV. In addition, this will allow the team to do a dry run of the vulnerability management process being defined by the security group. Will need a lab and some volunteers for the audit. Luke has the action item to create a proposal for the audit activity as a project.

Project creation review for OpenContrail Quickstart: Stuart Mackie presented the proposal and noted that this is a start-up project to help get hands-on experience and create visibility. There was a good discussion on why a project is needed for this effort vs. creating a wiki page. Stuart agreed that he will create a wiki page for the work and make it available as a developer resource (vs. creating a project).

OPNFV @ONS: Heather discussed the tutorial and dev track on Monday. Two panels are also planned for Thursday.

OPNFV hackfesk @OpenDaylight Dev Forum: Our hackfest will be a track at the OpenDaylight Dev Forum on July 30-13 in Santa Clara. Registration details can be found at Hackfest Etherpad. Ray will also send an email to the lists to start a planning committee.

Joint Board/TSC face-to-face meeting: Session planned in the afternoon of July 27th (Monday) at CableLabs in Sunnyvale, CA. Chris has the action item to send an email to the TSC mailing list to start discussing potential topics for the joint board/TSC meeting.

Action item follow-up

Requirements projects development process: Uli scheduled a meeting on June 17th on this topic

Pharos plans: Trevor discussed that the team is in the process of formulating a vision for Pharos for release 2 and beyond. Infrastructure management and tooling for managing the deploy environment are areas that need further development. Trevor will schedule a separate Pharos meeting for this topic.

Stable release: There was a good discussion on if there is a need & resource available to do a stable release. Consensus among the TSC is that a stable release should not include stepping a release version of our component pieces (e.g. stable release should not update OpenStack from Juno to Kilo)

Progression of BGS/Genesis: Frank followed-up on his email (http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2015-June/003094.html) that outlined potential evolution of BGS. Frank mentioned that continuous integration and common user experience are some of the key goals. When discussing project structure, Frank added that the contribution will be open to anyone but he was trying to have a limited number of committers.

Minutes

opnfv-users mailing list will be populated with everyone on the TSC mailing list

Uli will organize the meeting to discuss the requirements project development process.

Trevor will present the Pharos plans to the TSC

Project activities

Refreshing committer/contributor lists: Aric mentioned that he has the list of all contributors and will notify the project leads on who have been granted access.

Toolchain/workflow

Chris made a request for the community to help improve the documentation process in DOCS-33. Also a reminder that anyone can comment on Jenkins tickets.

Branching and patching arno/stable OCTO-xx: There was a good discussion on where bugs should be solved for arno/stable (in main or in the maintenance branch) and if any features should be added to arno/stable. Uli & the Octopus team has the action item to define the intention for our maintenance branch arno/stable and our methods for working with it

Debra shared her learnings/observations so far and mentioned that she heard a lot of feedback around scope creep, roles & responsibilities, communication, and dependencies. This creates a need for detailed scheduling (incl. project dependencies) and a change management process. Debra also added that project plans should provide a method for prioritization of the features and activities in order to schedule our activities.

Debra is also looking for a plan for project guidance in Release 2 planning and will be reaching out to project leads for help.

Want to go through steps outlined in the wiki page above on Wednesday (June 3rd) in preparation for the release on Thursday. (Release PR is planned for 8am Eastern Time on June 4th)

TSC agrees to use arno.2015.1.0 as our release tag

TSC also agrees to use stable/arno as our stable branch

Arno support: Consensus that support offered for OPNFV is community-based support, with no sla's associated.

Ray also has the action item to create a "opnfv-users"mailing list for the community-based support.

Frank also noted that bugs are to be reported on Jira.

There was a good discussion on the need for a community manager to help with user support activities and wiki content management.

Development process/project categories: There was a good discussion on the need to review both development process & project categories. The consensus was to postpone this discussion after the Arno release.

Release 2 "marquee" features: Good discussion on theme/marquee features for release 2 and three suggestions were Policy, Service Function Chaining, and High Availability + Fault Management.

Minutes

OpenStack Summit update: OPNFV Day & reception were both well attended on Day 1. Heather Kirksey/Chris Price/Jim Zemlin also led the OPNFV discussion at the OpenStack board meeting on May 17th.

OPNFV board meeting: Chris presented discussed some of the Arno learnings with the board but also mentioned that the technical community will have to do a formal post-mortem. The board will be having a discussion on major themes/features for Release 2 and will follow-up with an interactive discussion with the TSC on the topic.

Requirements projects: Uli reports that requirements projects cannot be seen to be finished until the requirements are implemented, but this is not reflected in the Project Lifecycle document. Uli has the action item to recruit a team from the requirements project community to further develop/update the requirement projects development process. (Ildiko Vancsa, Bryan Sullivan, and Gerald Kunzmann volunteered to be on the team)

Arno project plans & tracking:

Release tagging & maintenance: There was a good discussion on if there's a need for a maintenance branch or if we want to do stable releases at all. Providing some stability to our consumers and standing behind our release is important for our credibility. There was an agreement on the need to support and potentially provide stable releases on the Arno release with a minimum maintenance effort. Chris Price took the action item to start the discussion on the support structure on mailing lists.

Flag raising: Morgan reported that the full testing sequence will likely contain some errors at Arno release however will be able to explain them.

Release 2/B-release planning: There was a discussion if OPNFV Release 2 can support OpenStack Liberty, and there was an agreement that TSC would like to accommodate OpenStack liberty in our B-release planning. In addition to OpenStack, ONOS, OpenContrail, ODL, Open vSwitch, and DPDK are other upstream communities we need to factor in for the next release. Dave Neary has the action item to provide a release map for upstream communities as input in to the B-Release planning. The community will review project release map of upstream communities prior to setting the date for the B-release.

opnfvdocs: Chris updates that a lot of people are still heads down on Arno work and need to find time to edit documentation. Chris again asks for community to help with reviewing documents (Arno Release Documentation)

Octopus: Nothing new to report. In a ready state.

Pharos: In a ready state apart from needing to complete the documentation.

The TSC has agreed (via IRC vote) to set a target release date of June 4th for the Arno release, the Arno team has approximately 2 weeks to complete release activity.

Release 2 preparation & planning: There was a discussion on having a post-mortem session after the Arno release. Chris also noted that simultaneous release process needs to be defined and will be a learning process for the community. Dave Neary made a suggestion of identifying a marquee features for release 2 would be helpful (e.g. service function chaining, performance/functional testing, carrier-grade, etc.).

TSC update to the Board: Chris discussed that a couple of topics that will be raised to the board include

Need for updates development process

Project definitions and classification

Project Approvals

Inspector: There was a discussion that the list of committers/contributors need to be updated/completed before TSC votes on project approval. Juan has the action item update the committer and contributor list and the project proposal will come back for vote only next week.

Juju OPNFV Infrastructure Deployer: Similar to the Inspector project, Artur has the action item to update the committer/contributor list and JOID will come back next week for a vote only. There was also a good discussion on how BGS will evolve post-Arno.

Octopus: Automatic deployment continuing on POD2, but not yet integrated on POD1. Tests can be triggered automatically, but not completely ready.

Functest: Errors being worked through and the number of failed tests are going down on a daily basis.

Pharos: Pharos spec is being defined in the release documentation and working to make these documentations accurate and to improve the quality of the documentation.

Documentation: Release docs are being captured at Arno Release Documentation. Request to the community to review and provide feedback on documentation.

Requirements project document approvals and next steps: Uli presented the OPNFV project lifecycle and led the discussion on the process for requirements project documents. There was a consensus that a simultaneous release process needs to be established. Chris Price made a suggestion for requirements projects owners to review the current process and bring proposals to the TSC.

Moon OPNFV Security Management System: Ruan He presented the proposal for Moon that use a realtime mechanism to mitigate the security risk with having a one hour trust window for a provided security token. The project creation was approved via the IRC vote.

Minutes

Arno Project plans & tracking:

Documentation making good progress. There was a consensus not to timestamp documentation as documentation would then be tied to a specific release. Octopus team also have the action item to add a lab integration documentation in the Arno release.

BGS: Work still in progress to move Fuel work from Ericsson lab to the LF lab. There was a discussion that in the LF Lab, we need auto-deploy to work, hooked up to Jenkins, and required Functest tests are passing. There are still uncertainties to make a decision on the Arno release date. Ray to setup another Release Readiness meeting on Thursday (May 7th).

WiKi content management: There was a discussion on the importance of maintaining wiki content for accuracy. Pharos team to present lab definitions and tracking in a future TSC meeting.

Update on OPNFV Day at the OpenStack Summit: All breakout sessions in the afternoon has been identified and the latest is available at https://etherpad.opnfv.org/p/Vancouver_OpenStack. This will also be posted on the OpenStack Summit webpage.

Project proposal & creation review checklist: Chris Price's reminder that the TSC voted against requiring proposal review in the Technical Community calls but encouraged people to take advantage of input at the Technical Community meeting. Chris/Bin/Ray has the action item to return to the TSC meeting with an updated proposal.

Requirements project document approvals and next steps: postponed to next week.

Project creation review:

Re-visit ONOS Framework (ONOSFW): Mike Young continued his presentation from last week. There was a suggestion for additional committers from other companies, and Daniel Smith (Ericsson) volunteered. The project creation was approved via the IRC vote.

OPNFV Service Function Chaining: Brady Johnson presented the proposal. This project will create a link between OpenDaylight and OPNFV, and one of the goals is to allow OpenDaylight to create Service Function Chains across OPNFV Network Functions. The project creation was approved via the IRC vote.

Functest: Manual installs of tools (Rally, Robot) available. Documentation in progress. Rough estimate is a "couple of days" to have smoke tests available. vIMS still pending and not sure how much time is required to be completed.

Documentation: Lot of progress and team can help with converting proprietary file formats (e.g. MS Word). Suggestion was made to create an dashboard of what is required for the documentation project and Iben took the action item to create one on the wiki. Iben also took an action item to schedule a documentation happy hour" where people (esp. project leads) can meet on IRC and get their docs questions answered.

There was a consensus was that the community is still not able to define a more precise target release date for Arno.

Updating Section 7 of the TSC Charter: A consensus was reached on the following text. "For internal project decisions where no consensus can be reached, a majority vote among all Committers of the project via +1 voting should be used. A simple majority voting should be used for decisions within the TSC at which a quorum is present, unless otherwise required."

OPNFV Day @OpenStack Summit: There was a discussion on breakout sessions in the afternoon and a suggestion was made to limit to 2 parallel breakout sessions. Possible topics are IPv6, multisite, Doctor, SFC, VNFFG, etc. Dave Neary/Heather/Ray to schedule an IRC session to continue working on the agenda for OPNFV Day.

Project Approvals:

Project Proposal & Creation Review Checklist: Bin made a suggestion that the order of project review should be based on the "maturity" of proposals vs. when they were first submitted. This will be brought back to the TSC meeting next week after further discussions/feedback on the mailing list.

Yardstick: This project proposes a test framework, including test cases and test stimuli, to verify the infrastructure compliance when running VNF applications. The project creation was approved via IRC vote.

ONOS Framework (ONOSFW): The project addresses integrating an SDN controller of choice based on a target applications or use cases within the OPNFV defined NFVI and VIM framework. There was a good discussion on installers, build, etc. As time was running out, consensus was to continue the creation review discussion next week.

Minutes

Project leads need to evaluate the impact of the OpenStack Summit on resource availability leading up to Arno release. There was also consensus that release should not be scheduled during the week of the OpenStack Summit. There was a discussion of going with OpenStack Kilo for Arno, but the consensus was this will significantly change the scope of Arno.

Will not set a new release date today, but the TSC will review a new release date on a weekly basis

Contact Heather if you need help with messaging at the NFV World Congress.

Minutes

BGS: ISO images are ready, not deployed in an automated way, hardware configuration not yet complete. BGS team meeting daily for status updates.

Octopus: Octopus readiness pending configuration of hardware in the LF lab, but documentation is ready and scraped to the wiki. CI scripting for testing not confirmed yet.

Updates from Functest still pending

Documentation: Final release structure to be completed. Documentation team has the action item to to construct a consolidated presentation of release documentation.

Release readiness:

LF Hardware configuration is still on-going. There was a discussion that a reasonable approach may be to set a release date of one week after we have successful manual deployments

Consensus that we will not be able to release Arno on April 23rd. Project leads to craft a concise plan of action for Arno and will have another TSC meeting on April 23rd to discuss the new release date.

Arno marketing/messaging update: Heather indicates the marketing team will now have some work to do now that the release date has slipped pending a TSC decision.

OpenStack discussion: Heather asks for feedback on the room set-up during the OPNFV Day at the OpenStack Summit. The current proposal is to use a fishbowl style set-up in the morning. In the afternoon, use a smaller breakout style set-up to focus on specific topics.

Open Access update: Aric provided an update that Jira is now also open to the public. Will open Gerrit after Arno is released to save any collateral interruptions

Updating Section 7 of TSC Charter: There was a discussion on updating two sentences in Section 7 of the charter. Will continue the discussion over the mailing list and ratify during next week's meeting.

Project creation review:

Multisite Virtualized Infrastructure: Howard Huang (Huawei) presented the proposal, which is based on the ETSI NFV phase 1 work. There is a need in upstream communities to enable this functionality which are intended to be addressed in the requirements project. The project creation was approved via the IRC vote.

Escalator: Jie Hu (ZTE) presented the proposal, which intends to address the needs of operators for system upgrade. The project creation was approved via the IRC vote.

Minutes

Previous minutes approved

Committer update process: There was a discussion that votes on committer updates need to be captured in minutes/email. Frank asks what is meant by "a majority vote". For example, is it majority among all committers or majority of those who actually voted? The consensus was majority of all committers and Ray has the action item to propose a new language for Section 7 of the TSC Charter.

OPNFV Compliance & Certification (C&C) Committee: Heather discussed the board approval of forming a C&C Committee. There will be representatives from board, TSC, and marketing committee. For TSC members interested in volunteering, please email Heather.

Arno marketing update: There was a good discussion on the release diagram. Heather mentioned that all feedback for OPNFV & Arno overview slides (i.e. slides 1 & 2) have been incorporated and the updated version will be posted on the wiki. Please send feedback if there are any technical inaccuracies.

Hoodies: Ray discussed ordering new hoodies for upcoming technical gathering at the OpenStack Summit. Since we're ordering a larger quantity and higher quality hoodies, this will require ~20% of the remaining TSC initiatives budget. There was a consensus among TSC members that this is a worthwhile investment to raise awareness among developers and agreed to move forward with the purchase.

Open access to OPNFV tools: Iben outlines that the ability of external parties to review our patches and contributions is inhibited since you can not access OPNFV repo's without an LF account. Aric will investigate and report back to the TSC with options for enabling open read-only access to Gerrit.

Arno project plan & tracking: Due to delays in LF hardware availability, RC1 was not fully passed. Deploy scripts and auto testing scripts are available in repositories now, documentation templates are now available. For LF hardware, still waiting on an adaptor that is due to arrive this morning Pacific Time. Fatih reports that once the LF hardware is available, there will be a 1-day lead time required to have the jobs set up and connected. For Functest, scripts and structures are in place in the repo. Intel lab access for Jenkins has been resolved.

Project approvals: Chris reminds the community that request for creation review must happen via an email to the TSC. Also when your projects are approved, please list them on the main wiki page under approved projects.

Minutes

Previous minutes approved

OPNFV Hardware update at the LF Data Center: There have been some delays as purchasing of additional network & power connectors was necessary. Konstantin expects the hardware to be available for a dry-run by the end of this week (and ready for Jenkins setup early next week). Konstantin asks that if you need access to the OPNFV hardware, send your request to Chris Price, Trevor Cooper, or Frank Brockners. Since we will not be able to run RC1 activity on LF hardware, Frank will work with the Ericsson team to try to run RC1 activities in the Ericsson lab

Release diagram: Heather reviewed the draft release diagrams. There was a lot of discussion on "roadmap" slides. First, there was a consensus to drop the word "roadmap" and a preference to only include open source projects that are in the project pipeline. Will continue the discussion to the mailing list and will have the latest draft posted on the wiki. Please send any feedback/comment on release diagrams by Friday this week (April 10th).

OPNFV meeting tools and logistics: Frank reported that OPNFV have too many meetings that require audio and suggests some of the projects move to IRC-only meetings to see if this can become a default option for OPNFV meetings.

Award program: Ray discussed the proposal that was previously sent to the mailing list. For quarterly & "MVP" awards, the consensus is open nominations & voting. There can be a nomination/awards committee to help review & short-list nominees. Ray to write-up a final proposal for TSC approval.

Arno project plans & tracking:

Documentation: Toolchain in place, connecting it to Jenkins and getting templates in place

BGS: Teams are working on deployment scripts for Arno

Octopus:Automatic builds are ready, dependent on hardware at the LF datacenter.

Functest: The functest suites can be run manually in the intel labs. The vPing test cases are working but some issues in the pods. Morgan will reach out to the Ericsson lab with tools needed for tests on Thursday.

Project Approvals

Vote on VIM Northbound Model and Interface - vimnbi: The project has been renamed to Model Oriented Virtualization Interface and other questions were answered/clarified offline. The project creation was approved via the IRC vote.

Minutes

Previous minutes approved

Video & recordings: OPNFV YouTube channel to be used for posting training/tutorial contents and will look for ways to organize marketing vs. technical contents. There's issue accessing YouTube in China so alternatives will need to be investigated by the LF team.

OPNFV communication tools & meeting methods: Frank Brockners mentions that there are issues with using GoToMeeting due to increase in the number of meetings and audio quality. Consensus to form a separate team to investigate options (incl. doing more meetings via IRC). Frank, Ray Nugent, Bryan Sullivan, Iben, and Dave Lenrow will meet and report back to the community.

OpenStack summit update: Find the latest on the Summit at OpenStack Summit Etherpad. Heather also encourage everyone to contribute ideas to the Etherpad page. In general, event information (incl. registration, post meeting notes, etc.) will be available on the events Etherpad page at https://wiki.opnfv.org/#community_events as it was done for our two events in February.

Functest: There is an urgent need to add 6 new committers to the project. Trevor has the action item to get current committers to approve adding the new committers. As a rule, project leads need to communicate committer changes (showing votes in IRC, email, etc.)

OPNFV & Arno release graphic: Heather, Ray, and Brandon will meet with Craig (from LF' Creative Service team) will meet later in the day to discuss the release graphics. There was a meeting on Friday (March 27th) to explore several different options and proposed diagrams from Frank does a good job of capturing the OPNFV overview and Arno.

Arno release candidate (RC) planning: There was an agreement to run the RC meeting via IRC on the Thursday at 07:00 AM Pacific time

Arno Project plans & tracking

BGS team to reach consensus prior to Thursday for RC0 reporting

Octopus team expect to be ready for RC0

Functest: currently running on Jenkins in different labs

Documentation: Expect ~100 person hours of work

Project Approvals

OPNFV Documentation project - opnfvdocs describes all the required elements for a release. The project creation was approved via the IRC vote.

Re-visit VIM Northbound Model and Interface - Chris Price asks if renaming the project to "Service Oriented VIM Northbound Model and Interface" makes sense. There were also other questions on scope and implementation. As we were running out of time, the consensus was to post questions on the mailing list and the TSC meeting will be used for voting only (i.e. no further discussions) next week.

Minutes

Previous minutes approved

OpenStack community status: Dave Neary updates the community that blueprint reviews have been occurring on Thursday's Technical Community calls. Goal is to develop the blueprints to a point where we are ready to add them to the upstream gerrit for further discussion and review. Blueprints to be reviewed by the community should be handled through https://wiki.opnfv.org/community/openstack. We're targeting Liberty which will be released in October of 2015. Dave Neary is the main contact person for the OpenStack activity and will update the wiki page accordingly.

Arno release activities: Chris Price proposes weekly release candidate (RC) activities leading up to April 23rd. RC scope needs to be agreed up on during the next TSC meeting (March 31st).

Arno release diagram: Chris presented his proposal for the release diagram. There was a good discussion on the target audience, if we also need to address future plans/vision, etc. Ray took the action item to schedule a separate call to discuss the release diagram later in the week.

Minutes

Previous minutes approved

OPNFV Ambassadors program: Prathima introduced the Ambassadors program for technical speaking opportunities. More program details will be posted on the wiki. In the mean time, please email Ray or Prathima (pramesh@linuxfoundation.org) if you are interested in volunteering

Marketing committee update: Brandon provided update from MWC and plans for upcoming events such as NFV World Congress, Open Networking Summit, and OpenDaylight Summit. A suggestion was made to post event recaps on the wiki (similar to February Meetup & Hackfests).

OPNFV Hardware: Konstantin reported that all servers have been racked, but have a list of questions for the community. Suggestion was made to send the list of questions to mailing lists and setup a follow-up call later this week.

OpenStack Summit (Vancouver): Heather provided the latest on OpenStack Summit. The current plan is to have an OPNFV Day on Monday with a reception in the evening (post booth crawl). On Wednesday/Thursday, will participate in Telco WG Design Summit where blueprints will be discussed. OpenStack Summit Etherpad

Release 1 naming: Ray reported that the winner is Arno. Also a reminder not to include release names in the codebase in case if we have any issues in the future (using them in the filename is OK).

Developer tools training: Fatih has training material in place and the session will be ~2 hours long and will cover OPNFV Developer Tool Info, OPNFV Developer Workflow, and live Hands-on session.

Project plans & tracking:

BGS: BGS project is working on defining the commonalities across the final system states after the multiple installers

Octopus: Reviewed scripts from the Fuel team yesterday. Looking forward to running in Jenkins after issues are worked out.

Functest: Trevor communicating with Palani if he’s still interested in being a project lead. Also mentioned that a better coordination with Ci & BGS teams are needed. Uli suggested having a rep from Octopus join the Testing team meeting on Thursday.

Documentation update: Iben proposes using git for documentation. There are 2 areas to work on. One to write the documentation for Arno and another to establish a documentation process. Iben will schedule a meeting to discuss a potential process for documentation.

Project proposal review for VIM Northbound Model and Interface: Tianran Zhou (Huawei) presenting the proposal. The goal is to provide consistent/intuitive northbound interfaces for VIM. There were a lot of questions on scope, collaboration with ETSI, etc. and as time was running out consensus was to re-visit this proposal at the next TSC call (after possibly having another review on Thursday's Technical Discussions call).

Minutes

Previous minutes approved

Update from the face-to-face board meeting: Chris provided an update form the board meeting. One of the topics that the TSC will have to discuss in the near future is the topic of certification or compliance testing

Hackfest planning: Discussion on-going with the OpenStack community (esp. the Telco working group) on options for collaboration in Vancouver. There was also a discussion on if there is a need for a "standalone" OPNFV Hackfest as the next two planned hackfests are co-located with upstream projects (e.g. OpensStack & ODL). The consensus was to stay with the current plan and re-evaluate later in the year if necessary.

Development tools training: Aric has posted content on the wiki https://wiki.opnfv.org/developer, but some recorded sessions would be helpful. Ray has the action item to see if there are existing training materials @LF. Fatih/Iben/Aric will also build recorded training materials.

OPNFV Hardware: Ray provided a quick update on OPNFV hardware @LF data center. Delivery has been made to the data center and the team in currently doing inventory of items. Will invite Konstantin to the TSC call next week.

Release 1 naming: Ray will send out a survey today so that people can vote up to 5 choices for the name. Vote will close on Monday (16th) next week.

Awards program for the technical community: Possible categories of awards were discussed such as documentation, integration, collaboration, testing in addition to code. A concrete proposal to the board is required for a budget approval, so Ray will send out a proposal to the mailing list.

Project plans & testing

BGS: The plan is not to have manual installation on the LF hardware. This should be deployed using the existing toolchain.Jira for BGS

Octopus: Working mode is now Jira-based and Octopus is now awaiting build scripts to be made available from other projects.

Functest: The team is working with Tempest and Rally against a manually installed BGS environment. Also working with tools and integrating them with CI.

Creation review for the Resource Scheduler project: Zhiqi Wang (Huawei) presented the project proposal. Recommendation for the project team to work in close collaboration with other OPNFV projects like Promise and Copper. Project creation was approved via the IRC vote.

OpenStack community update: Dave Neary outlined the blueprint process for OpenStack, including the level of detail required including implementation details and high level use cases associated with the feature. The target is to be ready by May with OPNFV blueprints with the right level of detail and structure. See the OPNFV OpenStack community page.

Minutes

Previous minutes approved

Review of ETSI NFV#9 meeting in Prague: Chris Price gave an update from the TST meeting. He suggested ETSI to propose a LOI to OPNFV. Parviz also shared that TMF, ETSI NFV, 3GPP SA5 will work closely together. Immediate impact to OPNFV will be minimal. In general, ETSI was happy to see participation from OPNFV.

Release 1 naming: There was a good discussion on if the voting should to open to everyone (i.e. not just the TSC members), and the consensus was that it should be open to everyone on the tech-discuss mailing list. Ray will simplify the list, get legal feedback, and send a survey out for vote. In the survey, voters will be asked to write in their names.

Maintaining project leader, committer & contributor list: Aric wants to have a more reliable source than the wiki and suggested that when a project is created a file is created in the repository that describes the current list of committers & project lead. Aric will also investigate if we can auto-generate key project facts onto the project wiki page.

Development tool training, Jira, Gerrit, Git, Jenkins: Chris proposed doing training sessions that is also recorded. This can be used as an on-boarding tool.

Release 1 update: There was an agreement to begin describing Release 1 on the OPNFV wiki page, capturing the intended activities and objectives. Uli will begin to put this on the wiki.

Project plans & testing: Frank shared that the team is starting to put the material into Jira for more public visibility. There are also separate pages for different deployment tools showing current activities. Invitation to the technical community to visit status pages and find areas where they can help. Uli shared that the Octopus team is currently focused on integrating with other projects for automated test. Jira also setup for functest, and Palani is looking for help on creating user stories.

There was a discussion that proposed BPs should be as visible and aligned among multiple projects. Chris Price proposed having a 30 minute meeting prior to the next TSC call.

Final call for BPs for L-release will be Vancouver meeting in May. Reviewer resource is the bottleneck for OpenStack.

There was also a suggestion to have release information for other upstream projects such OpenDaylight, Open vSwitch, DPDK, etc.

Project Approvals

Data Collection for failure prediction - OPNFV failure prediction:: Linghui Zeng (Huawei) presented the project proposal. The initial goal of the project will be on the data collector (e.g. what data should be collected but is not yet available). Project creation was approved via the IRC vote.

BGS: Frank described two projects using Foreman vs. Fuel deployment tools. There was a good discussion on the possibility of picking one installer and focusing our resource on one project. However, people working with one installer will not be able to transition over to the other project to provide additional bandwidth. Thus we would not necessarily gain anything by focusing only on one particular installer

Another critical element for Release 1 is the OPNFV hardware @LF data center. The target date for the hardware availability is March 15th.

Chris Price proposed 6 weeks after the hardware availability to pull the first release together (April, 23, 2015). There was a good discussion on the desire from projects teams for more time, but there were also comments from the community that having an early release maybe preferred even if it's not feature-rich (e.g. missing HA). This gives people an opportunity to experiment & participate. There was also consensus that setting the release date to coincide with the OpenStack Kilo release or the NFV World Congress will not be ideal.

The TSC voted via IRC to approve the proposed release date of April 23, 2015

OPNFV Release 1 Name

Ray has the action item to send email to mailing lists for the naming of OPNFV Release 1 (theme is Rivers)

Minutes

Previous minutes approved

Formation of a security group: Luke led the discussion on the security group in OPNFV. There was a discussion on the need to work towards actionable items for development that lead to security improvements in OPNFV. The TSC agreed to the formation of a security group.

There was a discussion on potential licensing issues when OPNFV works with upstream communities that are using GPL licenses. Ray has the action item to get clarity on licensing and how code scanning is going to be implemented in OPNFV.

Release 1 update

Frank provided an update on BGS. By the end of February, base installer will be completed. Targeting installation on OPNFV hardware & CI integration by mid-March. Then Tempest / Robot scenario tests available by the end of March. The team will likely need additional 2-4 weeks to deliver Release 1.

Uli provided the CI update and notes that Jenkins is setup

Trevor outlined the function test requirements. The expectation is that the CI first deploys and testing will be invoked from the staging server and Jenkins will determine success/failure

Chris noted that we will also need BGS documentation for Release 1.

The TSC agrees to target the first release for April and will continue to define the exact target date during the next TSC meeting (Feb. 24th)

Chris provided an update from the February Board meeting.

Re-visit OpenStack Based VNF Forwarding Graph Forwarding Graph: Cathy discussed updates to the diagram and the project proposal wiki page. There was good discussion on how the project fits within the scope of OPNFV. The project creation was approved via the IRC vote.

Minutes

Previous minutes approved

Committer promotions: There was a discussion on whether the TSC should approve new committers, and the consensus is that committer promotions should be handled by the project committers, the TSC should only be involved when there are highlighted issues to be addressed in the promotion. Dave Lenrow has the action item to update the wiki (https://wiki.opnfv.org/developer/committer_promotion) to reflect this consensus.

OPNFV Release 1 discussion

BGS: The focus is to get the OpenStack OpenDaylight integration done and the team is working to create a draft schedule for release 1.

CI: Team is looking at the infrastructure and working with the Linux Foundation team on the tools

Release intent discussion: There was a good discussion on the "Release 1 intent" that was sent to mailing lists and several suggestions were made to the text. Agreement to continue to work on the text via email and set the Release 1 target date at the next TSC call on February 17th.

Project proposal process: There was a discussion that Thursday's Weekly Technical Discussions meeting is a good forum to gather community feedback and identify cross project collaboration opportunities. Even if not all TSC members are present on the Thursday call, it is highly recommended that project teams present their proposals at the Technical Discussion meeting prior to TSC calls.

Project Approvals

Re-visit Data Plane Acceleration: Now there is an accommodation of both hardware and software acceleration and will leverage compatibility to existing API's. Also added OpenStack as a relevant upstream project. The project creation was conditionally approved via IRC vote pending clarification of the committers list.

OpenStack Based VNF Forwarding Graph: Cathy Zhang (Huawei) presented the project proposal. There was a lot of question/discussion on how the scope diagram in the project proposal maps to the OPNFV architectural diagram. Suggestion is to continue this discussion during Thursday's Technical Discussion meeting before coming back to the TSC next week.

Minutes

Previous minutes approved

Data Plane Acceleration project review: Lingli Deng (China Mobile) presented the project proposal. There was a question/discussion if recently proposed changes have been reflected in the latest proposal. TSC recommended that the project team revise the wiki/project proposal and come back for a quick review next week.

Release 1 update: Frank provided the latest status on BGS and mentioned that the team is making progress on two efforts on the installer component. A demo of foundations are planned for next Monday's BGS call. Uli outlined the progress on CI and noted that interfaces/dependancies on other projects are being defined.

Project contacts: Aric requests that each project identify a point of contact for administrative/infrastructure questions (e.g. Jira). This is not necessarily a project lead, but the contact person whould be one of the committers. [Action Item: Ray/Aric to send email to mailing lists to remind projects to identify a point of contact and email Ray/Aric]

OPNFV security discussion: Luke Hinds summarized discussions on mailing list regarding a security community. There was a discussion that some functions of the security group could integrate themselves with OPNFV operational activities.

Development process: Chris gave an overview of latest wiki documentation and project page templates. There will be further discussion on mailing lists for defining methods for working with upstream communities (amongst requirements projects)

Parser project review: This is an integration & testing project to provide a template translation engine. There was a good discussion on the scope of this project, but the consensus was that there was a diverse group of people who are interested in the project. The project creation approved via the IRC vote.

Minutes

Previous minutes approved

Brandon Wick discussed developing OPNFV tracks for upcoming NFV World Congress & Open Networking Summit. Request for volunteers from the OPNFV technical community to help plan organize the OPNFV tracks.

Release 1 update: Uli provided an update on the Octopus project and walked through the diagram at https://wiki.opnfv.org/_media/octopus/octopus_diagram_v2.pdf to discuss input components and deployment tools. Palani provided an update on BGS and discussed that the focus will be on brining up the puppet framework on the current infrastructure.

OPNFV Release 1 date: BGS team is working towards a draft release on February 15th and a second release on the 28th. There is a need for a small group to meet to establish a timeline for the first release. Palani, Bin, and Frank agreed to spend time on this.

Test project structure: Trevor discussed that the Pharos project is defining the test bed and the latest descriptions/diagrams can be found here. Morgan added that Pharos is defining the test bed infrastructure that include access, governance, time scheduling, test deployment across environments.

Qtip project creation review: Wenjing clarified the scope & priority activities for Qtip. Also discussed use cases that were added to the project proposal page. The project creation was approved via IRC vote.

Development process development & description: Uli discussed OpenStack's release milestones and how OPNFV requirements projects need to be aligned to these milestones.

There was also a discussion on ETSI collaboration and the consensus was to continue this discussion at the Hackfest in Prague.

Minutes

Previous minutes approved

Heather Kirksey introduced herself as the Director for OPNFV @LF. She will be reaching out to TSC members soon.

OPNFV Summit Program Committee: Ray discussed the formation of a program committee for the upcoming summit and a request to have the technical community represented. Ray will send an email to the TSC mailing list soliciting volunteers.

Release 1 activity update

Boostrap/Get-started (BGS): Team is looking at installer options and reviewing a proposal from RedHat for using puppet modules to integrate OpenStack with ODL. Palani added that in the Intel lab, he demonstrated the installation of the platform using Fuel, however there were high availability issues.

Octopus: Team is focusing on the integration of the BGS activities into the octopus workflow for the CI pipeline.

Project meetings & minutes: There was a discussion on best practices for project meeting minutes and questions on effectively using the MeetBot. Chris has an action item to start a discussion on mailing lists around meeting minutes and using meetbot [Dave Neary wrote a quick tutorial on MeetBot that can be found at: Creating meeting minutes with MeetBot]

Simultaneous release & development work: Chris Price discussed the need to kick off the development process and simultaneous release process development. Uli added that the CI process will be heavily dependent on the development process. Chris took the action item to kick start this process on mailing lists.

OPNFV hardware infrastructure: Chris provided a quick update on the hardware infrastructure and added that leasing is not necessarily a cheaper options as we are looking at cutting-edge hardware. There was also a discussion on using the hardware to focus on CI & functional testing.

Project Approvals:

Functionality Testing: The focus is on testing the OPNFV platform. There were suggestions to clarify "life cycle management" in the proposal plus edit the repo name. The project creation was approved via IRC vote.

Qtip: Wenjing Chu (Dell) presented the Qtip project that will perform "bottom up" testing. There were questions on how this project relates to other projects such as Pharos & Functionality Testing. Wenjing will incorporate these feedback and present the updated proposal at the next TSC call.

Parser: Zhipeng Huang (Huawei) presented the project proposal. There was a feedback that clarity on the project scope is needed before the TSC can vote. Suggestion was made to also have a discussion on mailing lists prior to the TSC meeting.

Minutes

Approve previous minutes: deferred until next week as the minutes for the January 8th meeting was not posted until late.

Q1 Release - hot topics

OPNFV interim hardware solutions: There was a discussion on hardware solutions available from Ericsson & Intel. Currently, here are some restrictions for accessing both (e.g. you need VPN for Ericsson and individual accounts need to be setup for Intel). Dell will also have an infrastructure that can be used. A suggestion was made to post updates or information on how to access these hardware on the wiki or mailing lists.

OPNFV hardware (Work environment for Bootstrap/Get-started): There was a good discussion on the BOM and a question was raised if the number of servers per PODs need to be corrected and Frank Brockners replied that it should be corrected to 6 per POD. Action Item: Frank & Chris Price to bring back a proposal to the TSC next week.

Bootstrap/Get-Started update: Team agree to a weekly conference call on Mondays at 8am PT. The recent focus has been the OPNFV hardware requirements.

Continuous integration: nothing to report

Parser project and relevance to the first release: Uli Kleber discussed that the Parser project may bring additional value to the 1st release as it is independent from projects and integration. However there is a concern that this may take resource away from the first release.

Wiki page maintenance: Chris Price has the action item to begin a Wiki maintenance and governance team on the OPNFV mailing lists.

Project Approvals

OSCAR:Parviz Yegani & Stuart Mackie (Juniper) presented the OSCAR project proposal. There was a question if Stack #2 is available to the community and Stuart replied that it is available on github & OpenContrail site. Suggestion was made to change the repo name to 'oscar'. The project creation was approved via IRC vote.

Pharaos: Wenjing Chu (Dell) presented the project proposal. So far sites in Asia, Europe, and the US have been identified. The project will not cover benchmarking, VNF deployment testing, carrier grade requirements. Wenjing also explained that the project does not dictate the definition of the test bed. Also, a work item exists to define access needs for labs wanting to participate. The project creation was approved via IRC vote.

February events update: Ray Paik provided a quick update on the Meet-up (Santa Rosa, CA) and Hackfest(Prague). Registration information are available on etherpad along with agenda in development.

Update on the Bootstrap project: Frank Brockners (Cisco) provided a quick project update. Hardware is a blocking issue and an installer needs to be selected. Also discussed moving the daily IRC session to 7:30am Pacific Time.

Update on the Continuous Integration project (Octopus): Uli Kleber (Huawei) provided a project update and mentioned that the team is working on a task list for the project. Also noted that Octopus planning needs to be done in anticipation of the baseline output from the Bootstrap project.

Hardware requirements for OPNFV: There was a good discussion on hardware requirements (Work environment for Bootstrap/Get-started). Please add your suggestions/inputs directly on the wiki page. Frank Brockners has an action item to present HW proposals at the next TSC meeting on January 13th.

Suggestion was made to add wiki update/maintenance as an agenda topic for the TSC call next week.

Need to have a Linux Foundation account in order to be added as a committer. (Please use the corporate email address for the Linux Foundation account)

For any technical issues, file a ticket by sending an email to opnfv-helpdesk@rt.linuxfoundation.org

Meet-up and HackFest

Frank Brockners setup etherpads for upcoming Meet-up & Hackfest in February. We will use these etherpads to list registration information and collaborate on goals, agenda, topics, etc.

For Prague Hacfest, no suitable venue is available within walking distance of the ETSI meeting. Best recommendation is to go with Prague Marriott Hotel which is 15 minutes away by Metro (no transfer required and the Metro stop is very close the Marriott). The TSC came to a consensus to move forward with securing the venue at the Prague Marriott for the Hackfest (February 23-24)

Development process discussion

There was an agreement that there is a need for a discussion design process for requirements projects. [Action item: Bryan Sullivan to kickoff/facilitate this discussion]

Good discussion on working with upstream projects and there were consensus on (1) identifying trial projects to provide guidance and (2) inviting members of OpenStack community to future OPNFV TSC calls.

Project reviews

Project name & committer check for the now Software Fastpath Service Quality Metrics project. Consensus that this is a Collaborative Development project and will be a good trial project to work through OPNFV' development process and working with the DPDK community. The project creation was approved via IRC vote.

vSwitch Performance project: There was a question on hardware requirements and the project team responded that this is documented on Test & Infrastructure subteam wiki page. The project creation was approved via IRC vote.

Action Item: LF will also setup registration for the Hackfest once logistics are finalized.

AoB

Minutes

Previous minutes approved

Meeting sequences around the year end: No meetings on December 23 & 30. May decide to have an extra meeting on December 18th. Since January 6th is also a holiday in some regions, we will have the first TSC meeting of 2015 on January 8th (Thursday) before resuming the regular Tuesday TSC calls the following week.

Collaborative development projects: Two approaches were discussed. The first is project is a use case/feature and engages as needed upstream. The second is project is upstream liaison and maps to upstream. Since there was no clear consensus after a lengthy discussion, suggestion was made to move this discussion to the mailing list. There was also a suggestion to use the first collaborative development project could be used as a pilot.

High Availability for OPNFV: Qiao Fu (China Mobile) presented the High Availability project proposal. Based on feedback, updates were made to the list of committers/contributors and also for the scope to specify "requirements for HA API". The Availability project was approved via voting on IRC.

Bootstrap/Get-Started: Frank Brockners (Cisco) presented the project proposal. Plan is to have something working for Release 1. Made update to the OS (Centos 7). Reminder that communication occurs daily on IRC and meeting information is on the wiki. The Bootstrap/Get-Started project was approved via voting on IRC.

Telco KPI Monitoring: Mike Lynch (Intel) presented the project proposal. General consensus that the project name suggests something broader and could be confusing. Project team to come back to the TSC with a new project/repo name.

Minutes

Project reviews

Resource Management (Promise): Ashiq Khan (DOCOMO) presented the proposal and described the current issue around resource reservation in OpenStack, that it is not possible to reserve resources for future assignment. There was a feedback to add use cases description in the deliverables and add email addresses of committers/contributors. The Promise project was approved by the TSC vote on IRC.

Virtualized Infrastructure Deployment Policies (Copper): Bryan Sullivan (AT&T) presented the proposal and explained that the goal to determine when a resource has been allocated/deallocated according to a decision. There was a feedback that the list of committers plus project output need to be finalized/clarified. Bryan to make these updates prior to the next TSC call for a final vote (no further discussion needed).

Action Item: LF will also setup registration for the Hackfest once logistics are finalized.

AoB

Minutes

Previous minutes approved

December board meeting overview: Chris Price reviewed discussions at the Board meeting. Chris communicated that there was a consensus from the Board to target March'15 release date with less functionality and get the process started.

Project proposal process update: Chris Wright explained that the project proposal template was updated to match the Project Lifecycle document and to clarify that a project proposal should be of only one type. There was a general consensus to reduce the process overhead and there will be further discussions to accomplish this. Also a reminder that there is a 2 week public review period for proposals and TSC members need to review & provide feedback before the formal TSC review sessions.

Upstream software strategy: There was a good discussion on which versions of upstream projects OPNFV should take. The group also discussed if there is a need for the Simultaneous Release (SR) for the first OPNFV release. There was a general consensus that the focus will be on the latest stable upstream release as a baseline for OPNFV and the SR can come after the first OPNFV release.

Release date & composition: Again, there was an agreement that the SR is not needed for the first OPNFV release in March. The TSC agrees that the focus of the first release will be on the integration of upstream components into a platform, the development of our continuous integration process, and test projects focused on proving platform and NFV related functionality.

Project proposal review

Doctor: Ashiq Khan presented the revised Doctor requirements project to define requirements to improve fault management in VNFI components and an OpenStack-based VIM component. The Doctor project was approved by the TSC vote on IRC.

Octopus/CI Project: Uli Kleber presented the latest Octopus proposal. One of the feedbacks was that the list of committers need to be finalized/updated. Uli will bring this proposal back to the next TSC meeting

A suggestion was made that additional meetings may be needed for project reviews as there is a large backlog. There was a consensus to have a one hour meeting on December 4th at 6-7am Pacific Time just to review project proposals (instead of the weekly technical discussions call).

Minutes

Good discussion on the Q1 Hackfest in Prague. Preference is Monday & Tuesday. LF team will work with ETSI to explore co-location opportunity. [Action Item: LF will also setup registration for the Hackfest once logistics are finalized.]

Board Meeting alternate: Chris proposed Frank Brockners as the TSC representative alternate when Chris can not attend board meetings. The TSC approved the proposal via a vote on IRC.

[Action Item: Ray to investigate the vote functionality on IRC]

Project Reviews

IPv6: Bin Hu (AT&T) presented the project proposal. There were good discussions on if the integration scripts will be upstreamed vs. residing in OPNFV, project duration, repository name, project outcome, etc. Bin made real-time updates on the wiki and the updated proposal was approved via a vote on IRC. Congratulations on being the first approved OPNFV project!

Doctor: Ashiq Khan (DOCOMO) presented the proposal. There was a question from Qiao Fu (China Mobile) if there's an overlap with the High Availability project, but there was a general consensus that the goal is not to eliminate possible duplication early in the life cycle. On the Doctor project, the general feedback from the TSC is that the scope maybe too board. Ashiq will edit the proposal to bring a Requirements Project for review at the future TSC meeting.

Based on discussions, there is probably a need to revise/clarify the OPNFV Project Lifecycle document. The process should not slow work/discussions with upstream projects. [Action Item: Chris Wright will will send an invitation to work on the Project Lifecycle]

Minutes

Reminder on the antitrust compliance notice

Previous meeting minutes approved

Discussion on base distribution: Palani shared with the team that PackStack & CentOS looks like a good starting point. However, there were feedback that we may need more information filled out in https://wiki.opnfv.org/wiki/opnfv_distribution. There was a consensus to defer the base distribution decision.

"Get Started": This is to establish a 3-node baseline OPNFV deployment (2 control nodes and 1 computer note)

The 2 control nodes are intended for redundancy.

This could be part of the sandbox activity that the TSC already approved

Aric is the Linux Foundation contact for the sandbox

Suggestion to use a different name since "Get Started" sounds more like a documentation

Performance & Testing: Morgan provided an update for the sub-team. Project proposal will be submitted by next week

There was a good discussion on approval for project proposals

Clarity on project deliverables/outcomes would be helpful for project approval

Linux distribution: Need a decision on this quickly. (Action Item: Palani to organize a meeting to get towards a decision)

Archives to TSC & Tech-Discuss mailing lists will now be open (i.e. you don't need to subscribe to the mailing lists)

New TSC meeting time: Ray to an Action Item to send out a poll on two proposed options.

Q1 Hackfests: Will have a hackfest at LF' Collaboration Summit since the space is free. For ETSI NFV#9 in Prague, Marie-Paule Odini drafted a liaison proposal and is on the agenda for the plenary meeting next week

Action Item: Ray to send another a poll to gauge community's interest in ETSI NFV#9 meeting.

Action Item: Ray to send email to the mailing lists outlining two hackfest options for Q1'2015

If anyone plans to blog from OpenStack Summit, please feel free to contact Prathima (pramesh@linuxfoundation.org) if you need any assistance.

Time for TSC call is not convenient for APAC with the end of day light savings time.

Action Item: Ray to propose options to the mailing list.

Project Status

CI: Need more feedback on the proposal. A meeting will be scheduled to discuss/review the proposal.

Two projects (IPv6 & Parser) are ready for the 2-week review period.

Bin Hu's Thursday meetings will be the venue to review project proposals.

Reminder on requirements for creating project. 1) email to TSC announcing project proposal and begin (minimum) two weeks public review 2) email to TSC asking to approve a project that has had at least two weeks public review

Chris provided an update from the November Board Meeting:

Chris informed the Board that:

We need more headcount assigned, more community engagement.

We need and are working on upstream project timing and implications for our relese

Board is asking for a V1.0 release by March, 2015. Consensus is that we do not have enough information/progress to commit to this date.

Engagement with upstream communities: There was a discussion on formal liaison with upstream, but suggestion was made to bring OPNFV developers and requirements to upstream projects.

FOSS vs. private VNFs

Discussed that both FOSS & proprietary VNFs can be looked at. For proprietary VNFs, we need to consider issues around licensing, performance data, etc. If performance testing requires special integration to use vendor specific APIs, vendor can do that work

Action item: Test & Perf sub-team to make recommendations on VNFs

Suggestion was made to use "[Action Required]" in email subject line when sending e-mail to the lists requiring action from list members. Please use this sparingly.

New GoToMeeting account created for project meetings. Contact Ray at LF if you need to organize a meeting.

TSC meeting October 21st, 2014

Agenda

Approve previous minutes

Agenda Bashing

Discuss project proposals on the wiki (everyone who submitted proposals)

CI & Test infrastructure (Uli Kleber)

Simultaneous Release (Dave Lenrow)

Release naming poll (Palani/Ray)

Any other business

Minutes

Discussion on project proposals

Uli Kleber reviewed the CI proposal

Lots of details here including infrastructure that will be provided by LF (e.g. Gerrit, Jira, Jenkins, etc.)

Action Item: Need to draft a development process. Frank, Palani, Chris Price, and Tapio volunteered to start this. Palani will setup a call.

Action Item: Uli will setup a call to discuss the development process and co-existence with upstream projects. Will also discuss packaging tools during the meeting.

Testing Projects: Trevor Cooper from Intel setup a meeting on Thursday mornings at 7am Pacific Time

Minutes

Release Naming: Palani will work with Ray to get a poll out for voting on release name themes

Palani is proposing we get volunteers to build a prototype based on simply taking the upstream parts and building a test platform (e.g. OpenStack, ODL, etc) and establish baseline of upstream components. Palani will send an email to the list to solicit volunteers

Brandon/Prathima/Vanessa (LF) discussed the OPNFV marketing committee and event planning for 2015. For 2014, there will be a meet-up at the OpenStack Summit in Paris and there was a consensus to use create stickers (with OPNFV logo & URL) vs. ordering hoodies.

Minutes

Next week's TSC meeting will be shortened to an hour (8-9am Pacific Time) to accommodate the Board meeting in Düsseldorf.

Reminder to TSC members to send the delegate contact information to the TSC mailing list in case you are not able to attend. Proxy voting can be cast by the delegate or emailed to Ray Paik at the Linux Foundation (LF).

A question was raised on when project proposals can be made. There was a general consensus that proposals can be made anytime. However, there would be a cutoff date for when a project will be included in a simultaneous release.

There was a proposal & discussion on reducing the review period for project proposals from 4 weeks to 2 weeks. TSC members voted on this proposal and there were no objections. LF will update the Project Lifecycle document on opnfv.org.

Upstream community

Based on discussions at the face-to-face last week, the proposal is to target stable releases of upstream projects (e.g. OpenStack Juno, ODL Helium, etc.)

Good discussion on effectively working with upstream projects: A liaison with upstream projects, have TSC oversight of people working upstream projects, etc. There was a general consensus that we can have a point of contact within TSC for upstream projects.

Proposed action item for the TSC: Write down timeline for integrating with upstream projects identified to-date

A gap analysis against upstream roadmaps will also be helpful

Simultaneous release

There was a consensus on the need to firm up the simultaneous release process

Dave Lenrow will post a draft proposal on the wiki. Palani Chinnakannan also offered to help with this.

The integration/testing project group has started scheduling follow-up meetings

A reminder that a project proposal mostly captures scope. There is not need to document implementation plans in detail

Once projects are approved, we need to create a project page on wiki and not make changes to proposal pages

There was a question on how people can get visibility into projects. Once projects kickoff, each will have regular (e.g. weekly) calls with IRC and information will be posted on the wiki. Anyone can join meetings and access the wiki.

A question on what will be accomplished in the first release. Some of the ideas suggested were things like data plane acceleration or distribution installer. However, it is probably too early to define the first release yet.

TSC meeting October 1st, 2014

Agenda/Minutes

Antitrust compliance notice read

TSC Chair Election:

Voting was done via paper ballots plus e-mail votes from three TSC members who could not attend the meeting.

Christopher Price (Ericsson) was elected as the first TSC Chair for OPNFV

Future TSC meetings: There was a consensus to keep the TSC meetings open to everyone. (Anyone will be able to participate, but only TSC members can vote) Decision was made to schedule TSC meetings every Tuesday 7-9am Pacific Time. Meeting will be done via phone & IRC. Will also investigate switching to GoToMeeting.

Face-to-face meetings: Will target 4 face-to-face meetings/year and look for events/conferences where a lot of TSC members will be in one place. Decision on the next face-to-face meeting can be made based on projects or project proposals.

TSC Vice Chair discussion: There was a general consensus not to have a formal TSC Vice Chair position. If Chris Price is not able to chair/attend meetings, he will ask other TSC members to help.

Getting to the first release in 1H'2015

Discussion ensued on the first OPNFV release and there was a general consensus on the following items.

Importance of identifying & working with upstream communities

Development & release processes need to be defined and posted on the wiki

Communicating to the Board what can be delivered in 1H'2015 (based on project proposals)