13:59:09 #startmeeting OPNFV TSC 13:59:09 Meeting started Tue Jun 30 13:59:09 2015 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:09 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:59:09 The meeting name has been set to 'opnfv_tsc' 13:59:16 #topic Roll Call 13:59:28 Please # in standng TSC members or delegates 13:59:38 #info Chris Price 13:59:45 #info narinder gupta 14:00:32 #info dlenrow 14:00:58 #info Frank Brockners 14:01:17 #info Carlos Goncalves 14:01:33 #info Ildiko Vancsa 14:01:35 #info Uli 14:01:36 #info Gerald Kunzmann 14:03:04 #info Tapio Tallgren 14:03:19 #info Bryan Sullivan 14:03:27 #topic Approval of previous minutes of meeting 14:03:28 #info Parvz Yegani 14:03:39 #agree previous minutes of meeting approved 14:03:58 #topic Agenda Bashing 14:04:01 #link https://wiki.opnfv.org/wiki/tsc TSC Agenda 14:04:01 #info Wenjing 14:07:17 #topic OPNFV lab utilization 14:07:30 #link http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2015-June/003396.html e-mail on the topic 14:07:47 #info Morgan Richomme 14:07:58 #info Brian Skerry (Intel) 14:16:47 * frankbrockners supports the proposal by ChrisPriceAB 14:21:55 #agree The TSC agrees to have the octopus and pharos teams reconfigure the LF lab to provide build infrastructure on one of the POD's 14:22:09 #action Pharos team to provide lab configuration accordingly 14:23:05 #action octopus team to enable CI pipeline to utilize one build POD and one deploy POD 14:23:24 #topic Arno Stable Release proposal 14:23:47 #link https://wiki.opnfv.org/releases/stablebranch link to proposed arno stable methodology 14:23:52 #chair rpaik 14:23:52 Current chairs: ChrisPriceAB rpaik 14:24:17 chair frankbrockners 14:25:32 #chair frankbrockners 14:25:32 Current chairs: ChrisPriceAB frankbrockners rpaik 14:25:59 #info ulik outlines the approach to working with the arno stable release branch 14:30:22 #info ChrisPriceAB ask if therre is a cadence for stable releases 14:31:46 #undo 14:31:46 Removing item from minutes: 14:32:01 #info ChrisPriceAB asks if there is a cadence for stable releases 14:35:21 #info frankbrockners asks how feedback should be provided (e.g. directly edit the wiki or send comments to Uli) 14:35:49 #info uli-k asks feedback to be sent to Uli and he will own the edits 14:35:51 #agree TSC agrees to use the documented stable release plan for the Arno stable branch. 14:36:05 #action ulik to migrate the WiKi to RST formal in the octopus repo 14:37:22 #topic Release 2 planning 14:41:49 #info Julien 14:45:15 I suggest that we informally can refer to Brahmaputra as "BP" for brevity... 14:47:02 bryan_att: it's also used for blueprint, maybe just simply 'B' 14:54:00 #info frankbrockners suggests adding further dependencies such as deployment tools in the upstream schedule slide 15:04:28 #info Debra adds that timeframe between milestones are not define yet 15:07:32 #info After milestones A/B are set, subsequent milestones could be defined 15:10:03 #info how does a release date get set without identifying content and resources? 15:11:32 #link https://wiki.opnfv.org/developers/project_proposal_creation_review_checklist Project Creation checklist 15:12:19 #info overall information on project proposals: https://wiki.opnfv.org/project_proposals 15:12:25 Do we have a concrete understanding of what it means to "participate in a release"? 15:12:33 #info Inclusion in B-release is open until Milestone C 15:13:19 And are there any implications on resources etc available to projects that are "not participating"? 15:21:29 #info bryan_att is referring to infrastructure resources in addition people 15:22:23 Participate in release means having OPNFV functional and test code that is part of the continuously integrated system that is built tested and released from LF/OPNFV for e.g. release B 15:23:02 Upstream code is not part of our release train, except as a dependency 15:25:49 Rpaik, yes I mean if a project is not intending to publish anything, rather continue requirements analysis at least until the final gate milestone (by which it will decide), are there any presumed limitations on resources (tools, infra, lab, LF support) in deference to projects which know *now* that they intend to "participate"? 15:25:58 rpaik: joining B ends at MS C was not explicit on Debra's slides... 15:26:50 #topic Agenda for the TSC & Board joint meeting on July 27th @CableLabs 15:26:57 #info can we agree to put specific language that new projects can't join after C? 15:27:08 dlenrow: not on slides, but Debra mentioned that during the presentation can ask her to add that detail 15:28:12 #topic OPNFV Kiosk @OpenDaylight Summit & OpenStack Tokyo 15:28:20 #undi 15:28:23 #udo 15:28:25 #undo 15:28:25 Removing item from minutes: 15:28:34 #info Agenda reviewed without comment 15:28:37 #topic OPNFV Kiosk @OpenDaylight Summit & OpenStack Tokyo 15:28:44 Once we approve release process, we can't change. it until next release. It's a contract w/ projects 15:29:47 #info Will have a Kiosk at OpenDaylight Summit. Need community volunteers to staff the Kiosk 15:30:14 * ChrisPriceAB volunteers to sit in a booth as long as there isn't a bucket of water under it. 15:30:21 ChrisPriceAB: Do we have target date for TSC to approve final release plan/process for B 15:30:48 dlenrow: not yet no, after a first round of PTL/Debra we will review a proposal on the TSC for implementation 15:31:11 two questions on OPNFV hackfest @ODL Summit: 1) any more concrete planning to meet with ETSI NFV (when to meet with them? are they already aware of it?)? 2) status of hackfest agenda? have demos part of morning sessions or within project sessions? 15:31:33 Gerald_K, yes discussions are ongoing, Thursday is a main day 15:33:57 #info For OpenStack Summit Tokyo, we have another opportunity for OPNFV Day 15:35:28 #1 for an OPNFV day 15:36:39 #info OPNFV Day maybe on Tuesday/Wednesday this time around 15:37:21 #topic Project creation review: kvm for nfv 15:37:37 #link https://wiki.opnfv.org/nfv_hypervisors-kvm project proposal 15:40:41 #info suggestion to select a single project category (e.g. Collaborative Development) 15:40:50 What about the licensing of KVM I.e. GPL-based, is that an issue for OPNFV contribution which is Apache 2.0 based? 15:41:18 #action jun to remove one categories from the proposal. 15:43:05 #info plan is to submit patches in upstream 15:43:15 #undo 15:43:15 Removing item from minutes: 15:43:24 : #info plan is to submit patches in upstream repo 15:43:49 #startvote TSC vote for the creation of the kvmfornfv project? (+1, 0, -1) 15:43:49 Begin voting on: TSC vote for the creation of the kvmfornfv project? Valid vote options are , +1, 0, -1, . 15:43:49 Vote using '#vote OPTION'. Only your last vote counts. 15:43:52 #vote +1 15:43:53 #vote +1 15:43:53 #vote +1 15:43:53 #vote +1 15:43:55 #vote +1 15:43:55 #vote +1 15:43:56 #vote +1 15:43:56 #vote +1 15:43:57 #vote +1 15:43:58 #vote +1 15:44:01 #vote +1 15:44:10 vote as proxy for Ashiq Khan 15:44:13 #vote +1 15:44:20 Congratulations KVM team 15:44:22 #endvote 15:44:22 Voted on "TSC vote for the creation of the kvmfornfv project?" Results are 15:44:22 +1 (12): AndreaP, frankbrockners, dlenrow, cgoncalves, skerry, tapio_, bryan_att, ChrisPriceAB, Gerald_K, uli-k, julien_ZTE, Wenjing 15:45:00 #vote +1 15:45:10 #topic action points 15:45:39 #info Requirements projects development process. 15:45:50 #info no progress this week. 15:45:53 sorry for casting my vote a bit late;) 15:46:13 #info ulik stated a lack of time for progress, ildikov volunteered to drive the topic forward. 15:46:57 #info no update from trevor as he is on vacation. 15:46:57 #topic AoB 15:47:15 #info no other business mentioned 15:47:32 #endmeeting