14:59:31 #startmeeting OPNFV TSC 14:59:31 Meeting started Tue Dec 8 14:59:31 2015 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:59:31 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:59:31 The meeting name has been set to 'opnfv_tsc' 14:59:37 #topic Roll Caall 14:59:47 #info Chris Price 14:59:48 #info Frank Brockners 15:00:05 #info Gerald Kunzmann 15:00:10 #info DENG Hui 15:00:16 #info Uli Kleber 15:00:28 #info Bryan Sullivan 15:00:42 #info Jie Hu (ZTE) 15:00:59 #info Dirk Kutscher 15:01:01 #info Tapio Tallgren 15:01:24 #topic Approval of previous minutes of meeting 15:01:24 now have quorum 15:01:32 #link https://wiki.opnfv.org/wiki/tsc#december_1_2015 previous meeting agenda and minutes 15:01:36 #info Edgar StPierre 15:02:16 #info previous minutes approved 15:02:25 #topic Agenda Bashing 15:02:40 #link https://wiki.opnfv.org/wiki/tsc#december_8_2015 current agenda 15:03:21 #info Vikram Dham 15:04:01 #info Chris Wright 15:04:14 #topic action points 15:04:34 slugfest! 15:04:35 *) 15:05:18 #info the action on chrispriceab to send a call to arms for the plugfest was fulfilled this morning. Not enough time to report on the outcome. 15:05:48 #info the action on the poll for the Q1 plugfest is complete. We have 18 votes for Tahoe and 15 votes for ONS. 15:06:18 #info rpaik proposes we do a one day meeting at the ONS focused on development. And a one day "planning event" and board colabrotaion at Tahoe. 15:06:27 #info Brian Skerry 15:06:41 splitting the meeting into two doesn't make sense. it should be one meeting in one place 15:06:49 #info Morgan Richomme (IRC only) 15:06:53 agree to Bryan 15:07:19 #info dlenrow 15:10:49 #info the collab summit creates issues with the IETF running the following week. 15:11:25 I don't want to disagree, for asian people, it will be easy for travel from asian to american then ietf meeting 15:11:25 #startvote Shall the TSC relocate the Q1 hackfest to the ONS in Santa Clara? (+1, 0, -1) 15:11:25 Begin voting on: Shall the TSC relocate the Q1 hackfest to the ONS in Santa Clara? Valid vote options are , +1, 0, -1, . 15:11:25 Vote using '#vote OPTION'. Only your last vote counts. 15:11:42 #vote +1 15:11:43 #vote +1 15:11:44 #vote +1 15:11:45 #vote +1 15:11:45 #vote #1 15:11:45 bjskerry: #1 is not a valid option. Valid options are , +1, 0, -1, . 15:11:47 #vote +1 15:11:50 #vote +1 15:11:53 #vote +1 15:11:55 #vote +1 15:11:56 #vote +1 (for Parviz) 15:11:56 StuartMackie: +1 (for Parviz) is not a valid option. Valid options are , +1, 0, -1, . 15:11:58 #vote +1 15:12:04 #vote 0 15:12:04 #vote +1 15:12:04 #vote +1 15:12:14 #endvote 15:12:14 Voted on "Shall the TSC relocate the Q1 hackfest to the ONS in Santa Clara?" Results are 15:12:14 0 (1): TapioT_ 15:12:14 +1 (11): frankbrockners, dku, dlenrow, bryan_att, hujie, ChrisPriceAB, cdub, StuartMackie, uli-k, bjskerry, edgarstp 15:12:15 #vote +1 (for Julien) 15:12:28 #agree the TSC votes to move the Q1 hackfest to the ONS. 15:13:07 #info ONS starts on March 15th (Tues) 15:13:24 #info proposal is for the hackfest to start on the 14th (Mon) 15:13:34 #topic Removal of OPNFV's initial scope constraints 15:13:53 #info trevor_intel 15:15:02 rpaik: according to the event page it's 14th-17th (http://opennetsummit.org/) 15:15:32 ildikov: let me double check with the events team 15:15:38 the scope clarification essentially removes the 1st release constraint, that we are already in the process of removing through various projects in the B release, and will surely be expanding for the C release 15:15:58 rpaik: ok, tnx 15:16:40 #link https://www.opnfv.org/developers/technical-project-governance/tsc-policy 15:17:11 #info question to TSC on whether the TSC policy should be updated as a result of the Board decision? 15:17:21 #info Prodip notes that concerns expressed were mostly around timing (not necessarily on removing scope constraints) 15:17:53 as I noted earlier the TSC should expect specific project proposals related to VNFM and NFVO functionality, since there is substantial momentum toward implementing those functions in OpenStack, and we can't hold back that tide - we simply need to start by integrating those functions into the C release 15:22:54 #info many TSC members would like to see more transparency from Board 15:22:57 +1 for more open/transparent interaction between the TSC and Board 15:23:19 +1 15:24:44 +1 to moving on to the next topic! 15:26:04 # info the board should show leadership in transparency in all OPNFV communication 15:27:25 #info Gerald comments that the NO votes had been more than "timing" 15:28:21 RayNugent_: I agree with your sentiment, but much of BOD is not public and directors will all quit if meetings are open. We're talking about possibly having a public subset of BOD meeting that would be reported, but much is private, NDA, financial, personal and can't be discussed in public 15:28:25 can a link to the board minutes be posted? 15:29:53 #link https://www.opnfv.org/developers/technical-project-governance/tsc-policy TSC Policy 15:30:49 #info The scope of projects chosen by the TSC will focus on the following NFV architecture functional blocks, reference points and tools or infrastructure to support the scope. Additional details about these architecture functional blocks and reference points can be found in the ETSI NFV E2E Architectural Framework [1]: 15:30:55 #info Chris mentions that the TSC policy only gives a "focus" but does not put a constraint, so he believes there is no need to update the policy 15:31:47 #info Functional Blocks: Virtualised Infrastructure Manager (VIM), Network Functions Virtualisation Infrastructure (NFVI) 15:32:12 #info Reference Points: Or-Vi: The reference point in between the Orchestrator and the VIM, Nf-Vi: The reference point in between the VIM and the NFVI, ... 15:32:14 #info Policy doc should make clear that our scope includes MANO, etc. Needs update 15:32:28 #info Openstack seems to manage just fine with open board meetings 15:33:08 FSVO just fine 15:33:56 #info frankbrockners asks if tsc policy needs to be re-wrote by board and ratified by tsc, or other way around? 15:33:57 perhaps someone can take an action to propose changes, but I don't think we need to belabor this point here, it will just result in rabbit-holing on the words in the policy 15:34:17 TSC should be allowed to edit the policy doc 15:34:29 we did that on purpose during formation, as Ray just said 15:34:35 #info rpaik notes that tsc policy doc is fully w/in TSC puview 15:34:42 #info Gerald comments that as long as TSC is clear about the intention and will e.g. not object projects approval due to this, there is no strong need to update the TSC policy document 15:34:49 we have more pressing things to consider on the TSC call - this scope shift will occur on its own, regardless of whether we edit the TSC policy or not 15:34:53 #info I would be happy to take a cut at updating that document for next weeks TSC 15:35:31 GeraldK: +1 15:36:23 #info Gerald comments that in case we are going to change the policy document, we should ensure we keep the reference to ETSI NFV and ensure we are working along the building blocks and reference points defined there 15:37:07 pls include me to the discussion 15:37:09 #action dlenrow and bjskerry to establish a working group and propose an amendment of the TSC policy for TSC review. 15:37:25 #topic Brahmaputra milestone D report 15:38:19 #info debra outlines the Milestone D report 15:38:44 #info 32 project reported - green API and features frozen - at milestone D 15:38:56 #info 3 projects have not reported for Milestone D 15:39:08 #info out of 39 projects; 4 are "red" (no report received for 3) 15:39:26 thanks geraldk 15:39:35 #chair geraldk 15:39:35 Current chairs: ChrisPriceAB geraldk 15:39:39 #chair rpaik 15:39:39 Current chairs: ChrisPriceAB geraldk rpaik 15:40:25 #info project reporting have shared concerns and unknown items when approaching milestone E 15:41:00 #info Milestone E: 18 green, 4 red, 13 yellow, 4 orange 15:41:13 #info 18 projects report green for projected milestone E while others share concerns achieving code freeze in time due to CI unknowns, resource challenges and installer interation. 15:41:15 creative color mapping...green is blue, orange is green... ;) 15:41:27 * ChrisPriceAB is happy to be color blind. :D 15:41:47 * frankbrockners thinks its training for the color blind 15:42:09 #info debra will be following up on open issues in the next Brahmaputra planning meeting. She wants to run to completion on many issues on todays meeting. 15:48:35 #info ChrisPriceAB adds that in the future more information on milestone criteria maybe helpful 15:49:40 #info dneary asks if there is a set of must-have projects 15:50:55 #info debrascott notes that projects in Arno (e.g. Functest, installer, docs, etc.) are good examples, but that also can be re-visited 15:51:25 #topic TSC meetings rest of the year 15:52:08 skip it; holidays 15:52:14 no one is around 15:52:27 likely won't get quorum for any voting 15:52:30 yes, skip it 15:52:39 You probably won't reach quorum on either date 15:53:01 many companies are shut the week of the 25th. might want to check. 15:53:12 brcd is shut down that week, for example 15:53:18 #info 5th Jan is important as this is milestone E 15:53:22 #info there will not be a TSC on the 29th 15:53:36 #info a TSC call will be held on the 22nd, regardless of quorum 15:54:01 #topic OPNFV input at Jan 13-14 ETSI NFV-ISG Inter-SDO Information Modeling Workshop 15:54:42 #info bryan_att has sent e-mails to the list about an upcoming workshop. Bryan will be bringing a deck from OPNFV and is looking for community support on providing input from OPNFV. 15:55:02 #link http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2015-December/006807.html link to the email 15:55:07 There is an ETSI telecon on 12/17 to set the agenda for this meeting 15:55:22 #topic Artifact page updates, approval of budget 15:55:30 unanimous...unified... 15:58:30 #vote TSC to approve the budget allocation to improve the artifacts page for Brahmaputra? (+1, 0, -1) 15:58:38 #startvote TSC to approve the budget allocation to improve the artifacts page for Brahmaputra? (+1, 0, -1) 15:58:38 Begin voting on: TSC to approve the budget allocation to improve the artifacts page for Brahmaputra? Valid vote options are , +1, 0, -1, . 15:58:38 Vote using '#vote OPTION'. Only your last vote counts. 15:58:43 #vote +1 15:58:43 #vote +1 15:58:44 #vote +1 15:58:45 #vote +1 15:58:46 #vote +1 15:58:46 #vote +1 15:58:48 #vote +1 15:58:48 #vote +1 15:58:57 #vote +1 15:59:08 #vote 0 15:59:17 #endvote 15:59:17 Voted on "TSC to approve the budget allocation to improve the artifacts page for Brahmaputra?" Results are 15:59:17 0 (1): uli-k 15:59:17 +1 (9): frankbrockners, dku, dlenrow, bryan_att, ChrisPriceAB, StuartMackie, bjskerry, edgarstp, Wenjing 15:59:18 #vote +1 15:59:19 #vote +1 15:59:23 #action fdegir to send an email to mailing lists to get feedback on the design of the new artifacts page 15:59:48 #vote +1 16:00:21 #action fdegir to start a community thread on updates to the artifacts page. 16:00:26 #vote +1 16:01:23 #info the vote results were 13 +1 votes to update the artifact page, and one abstention. 16:01:29 #endmeeting