Thursday September 26th, 2013; 10:00-12:00pm PDT Virtual Phone & WebEx. Abhishek Chauhan X Ed Warnicke X Ken Gray X Chris Wright X

Transcription

1 Meeting: Meeting Logistics: Date/Time: Location: OpenDaylight TSC Thursday September 26th, 2013; 10:00-12:00pm PDT Virtual Phone & WebEx TSC Members (X = In attendance): Abhishek Chauhan X Ed Warnicke X Ken Gray X Chris Wright X Luis Gomez for Chris Price X Vijoy Pandey X David Meyer Rajeev Nagar List: tsc@opendaylight.org TSC Wiki: Project Proposals Wiki: Agenda: Agenda Bashing/Administrivia (dmm) Acceptance of minutes Misc NfV liasion(s) Event Updates Hackfests vhackfest review Next phackfest (Ed) Other Events (Phil) Review: OpenDaylight Mini-Summit (CloudOpen North America) CloudOpen Europe OpenDaylight Summit Planning INTEROP NYC, ONUG Summit (dmm) Creation reviews VieUX Integration System Integration and Testing Update (Luis) Facilities (all) Release Vehicle Discussion (all) Base Edition Virtualization Edition SP Edition Other?

2 Election of new TSC members Proposal: I will send a note to the Board asking to postpone any action on this until after the first Simultaneous Release. TSC Charter: "The TSC members are the project leads from the Core projects. There is only one project lead per project." No projects in Core state Do we (the TSC) wish to forego elections of new TSC members on October 8th, 2013 and instead wait until such a time that one or more projects have reached the "Core" state? If no, then The Charter could be changed to include other states besides "Core" projects (such as Mature and possibly BootStrap)... or even Incubation depending on the intent of the TSC. This type of change would require both the TSC and Board approval, and/or Some of the projects currently in Bootstrap (and possibly Incubation) could apply for Mature (and possibly Core) status prior to the October 8th timeframe if they felt ready. Note: The lifecycle calls for a 2 week review period prior to each TSC review. This will affect the scheduling of the reviews and any resulting elections from project promotions to Core. Do we need a "Security Review" somewhere in the project lifecycle/release plan (dmm)? Held Over API Review Process (Chris Wright) "Commonalities" (Ken Gray) Architectural_Principles Page(s) in serious need of work See dmm (and others) comments on discuss Call for volunteers TSC Charter Deliverables Deliverable 1: Section 4 of TSC Charter "The active Committers will elect a number of TSC members; the exact number to be determined by the TSC after the organization is formed. In order to ensure a true community is in place prior to election, these TSC community seats will be elected six months after the organization forms. These elected community seats must be filled with individuals from separate, unaffiliated companies." How many active committers/project on the TSC? "The TSC will serve as ODP's liaisons with other consortiums and groups." Liaisons: IETF, ETSI, ONF, ITU- T, OIF, OpenStack, ONRC, and OMG Others? Deliverable 3: Section 6 of TSC Charter "The Development Process will include provision for a voting process to be implemented for decision making in accordance with the following guidelines:" See Section 6 of the TSC Charter To Be Done Items

3 Minutes: Topics Discussion/decisions/action items Agenda Bashing / Administrivia Approval of Minutes NFV Liaisons Event Updates Creation Reviews Dave Meyer called the meeting to order. Dave Meyer called for comments on the Minutes from the TSC meeting on 9/5/2013. No comments were made. A vote was then called to approve the minutes from the prior meeting. The Minutes were approved unanimously Dave Meyer introduced the topic and reminded the TSC that Ed Warnicke had been appointed as the Liaison from ODP to the ETSC NFV ISG. Dave Meyer had contacted Diego Lopez about Liaison efforts between the two groups. Diego Lopez is Assistant Technical Manager of ETSI s Network Functions Virtualization ISG and Head of Technology Exploration in the Global CTO Unit of Telefonica, Spain. Diego Lopez suggested that Mukhtiar Saikh of Brocade act as the Liaison from the ETSI NFV ISG. Dave Meyer volunteered to introduce Ed to Mukhtiar to begin the Liaison activities. Dave Meyer suggests that ODP only have liaisons where we need them. For example we do not need a liaison to ONF unless we have needs regarding the OpenFlow protocol. vhackfest Dave Meyer asked that Ed Warnicke to provide a recap. The event was relatively well attended and seemed to work well. Next physical HackFest. Ed introduced the topic of the possibility of another physical hackfest before the Hydrogen release The last physical hackfest went very well and as a result, a suggestion to revisit the decision for another physical hackfest prior to release. Vijoy Pandy expressed support for having another hackfest. Given a look at the schedule and timing, consensus was made that a physical hackfest is not possible between now and the Hydrogen release. VieUX Endre Karlson introduced the proposal. David Meyer asked how VieUX integrates with rest of ODP Answer- AngularJS is very modular. The current UI is not easily extended as the project evolves. VieUX provides for UI extensions for new functions. The current UI must be served as a webpage from the controller. vieux is only using NB APIs to the controller so is wholly separate. The question was asked will vieux change to just use REST calls to ODP? It was noted that the fundamental architecture of VieUX made good sense. The question arose, will we deprecate the inline UI code now present in the controller? Answer: The goal will be to deprecate the old UI and make it easy for users to add/customize the UI for their needs. Ken Gray is supportive of the prject, but requested to see a deprecation plan for existing UI as soon as possible. o Vote called to put vieux into Incubation state. The vote passed unanimously. Integration-Project: Luis Gomez introduced the project proposal to the TSC and provided an overview of the activity ongoing. David Meyer asked for TSC comment prior to a vote. Vijoy Pandey & Ed Warnicke expressed support and admiration for the work that Luis and team have produced in such a short period of time. o Vote called to put Integration project into incubation state. The vote passed unanimously.

4 System Integration Testing Release Vehicles Election of New TSC Members Dave Meyer asked that a report out from the Integration project be provided to the TSC on a weekly basis. Luis Gomez volunteered to provide such a report. Dave Meyer introduced the topic and asked Luis to provide a list of what is needed for testing. Luis identified the following: A few VMs for functional test for cloud type of environments. It should be automatic and all on VMs. o Andrew Grimberg the LF can provide VMs but Mininet does not work on Fedora or RedHat (what the Integration team is using). Chris Wright noted that RH has mininet working, but the patches aren t published. Chris Wright will work with Andrew and Luis to get mininet working in our environment. The questions was asked - How long will it take? Answer: The VMs can be up and running by the end of next week. Ed Warnicke noted that if Andrew works closely with Carol, the system may go up faster. Mininet is not supporting OF1.3. A comment was raised that the Pantheon team has a mininet version enhanced for OF1.3. Physical lab needs. Ericsson has committed lab space at their San Jose lab. Ericsson probably does not have all gear though (SB) needed for full System testing. Dave Meyer noted that we should coordinate across all testing participants to create a list of gear needed. Ed Warnicke suggested we create a federation of testing labs across the different participants. Logistically, it is easier this way then getting all the gear in one place. The comment was made that InCNTRE would/could be a good place. Dave Meyer noted that InCNTRE is good for OF testing, but not the other SB protocols. Luis Gomez needs names/contact for all members that would do federated work. (IBM, Cisco, Brocade, Juniper, etc) Dave introduced the topic are we converging on Base, Virtualization and Service Provider editions. It was noted that the categories seem right, but what goes into each is a more difficult question. Key Grey noted that whatever is in the base edition will create the perception that that version is the core ODP. For example ODP could be considered just an OpenFlow controller. Anees noted that there are some components that may not work together, for example VTN and OpenDOVE. The question was raised: Do we need a System Release Document process? Luis Gomez is expecting to have the data for the release documentation. Dave Meyer noted this the lack of this documentation may be an oversight in the Release Plan. Such documentation is important. Ed Warnicke noted that user annotatable documentation is helpful and this is what the project should strive for. Ed Warnicke volunteered to create build directories for these three Release Vehicles. Dave Meyer volunteered to drive documentation requirements. Dave Meyer introduced the topic. David Meyer proposed that the TSC send a note to the Board to postpone this activity until after the first simultaneous release. There are at-large TSC members that should be voted on at for Oct. 8 th. It was noted that the charter would need to be changed given that it specifies these elections are to be done at six months. It was also noted that elections could

5 Does ODP need a Security Review? distract the development community away from the first release. It was also noted that not doing the election will have the perception that the project is not community led. David Meyer volunteered to communicate this issue to the Board. Dave Meyer introduced the topic. Per project review, system wide review etc.. The comment was made that doing security reviews formally is difficult. Common Open Source Project practice has a Security Contact as a contact point for individuals to notify ODP when security issues are identified. It was noted that as the release gets close, such a contact is should be appointed. The TSC agreed by general consensus that this should be done. Any other No other topics were identified topics? Adjournment Dave Meyer adjourned the meeting