13:59:13 #startmeeting OPNFV TSC meeting 13:59:13 Meeting started Tue Jun 14 13:59:13 2016 UTC. The chair is frankbrockners. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:13 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:59:13 The meeting name has been set to 'opnfv_tsc_meeting' 13:59:22 #topic roll call 13:59:23 #info Bryan Sullivan 13:59:35 #chair rpaik 13:59:35 Current chairs: frankbrockners rpaik 14:00:33 #info Dave Neary 14:00:45 #info Stuart Mackie 14:00:58 #link agenda for today: https://wiki.opnfv.org/display/meetings/TSC#TSC-June14,2016 14:01:03 #info Ildiko Vancsa (stand in for Chris Price) 14:01:17 #info Jonas Arndt 14:01:31 #info Uli Kleber 14:02:04 frankbrockners, /me raises hand 14:02:08 #info Edgar StPierre 14:02:18 #chair dneary 14:02:18 Current chairs: dneary frankbrockners rpaik 14:02:27 we now have a quorum 14:02:59 #info Tapio Tallgren 14:04:00 #info Brian Skerry 14:04:01 #info Gerald Kunzmann 14:04:04 #chair bjskerry 14:04:04 Current chairs: bjskerry dneary frankbrockners rpaik 14:04:04 #info agenda approved 14:04:17 #topic approval of minutes from last meeting 14:04:19 #info Julien 14:04:36 #info no comments/feedback on previous miniutes 14:04:38 #info minutes approved 14:04:46 frankbrockners, Did the MANO project ask the TSC for consideration officially? That was unclear to me during the tech review call 14:04:51 #topic Next week's TSC meeting 14:05:23 #info Dirk Kutscher 14:05:28 dneary - I don't have the lasted on the MANO WG - let's wait for Chris 14:05:35 frankbrockners, OK 14:05:52 #topic TSC meeting next week in Berlin 14:05:57 #undo 14:05:57 Removing item from minutes: 14:06:02 Sorry 14:06:15 #info TSC meeting next week will be at 8-9am CET in Potsdam III during the design summit 14:06:27 #info next week's TSC meeting will be at 8am local time in Berlin, since most of the TSC members will be in person in Berlin. 14:06:36 #info room Postdam III 14:06:46 rpaik, The meeting is in Potsdam? 14:07:03 dneary - room Postdam in the Interconti 14:07:15 #info Meeting will be Tuesday morning in Berlin (Potsdam room in the Intercontinental Hotel) 14:07:28 #topic Joint Board-TSC meeting in Berlin - Updates 14:07:43 What time does that meeting end? 14:07:44 #info the room is Potsdam III @Intercontinetal Hotel and on Tuesday 8-9am CET (21st) 14:07:51 #undo 14:07:51 Removing item from minutes: 14:07:57 rpaik, Got it already 14:08:03 rpaik, Topic changed 14:08:13 thanks dneary:-) 14:08:49 #info topics include release planning, Bitergia roadmap, SPC-TSC interlock... 14:08:56 (did I miss topics?) 14:09:08 #info Trevor Cooper 14:09:32 #action Chris Price to send an email on TSC governance 14:09:40 #info the TSC can join the meeting at 10am CET on the 24th (Friday) 14:09:44 frankbrockners, Did I miss any TSC-Board topics? 14:10:01 #topic Design Summit update 14:10:06 why Board is interested in INFRA WG? 14:10:15 Julien-z_, capex 14:10:15 #link https://wiki.opnfv.org/display/meetings/TSC latest design summit schedule 14:10:27 #undo 14:10:27 Removing item from minutes: 14:10:30 thanks dneary 14:10:33 #info rprakash 14:10:39 #link https://wiki.opnfv.org/display/EVNT/Berlin+Design+Summit+Planning design summit schedule 14:12:11 rpaik, I think if multiple meetings are going on at the same time it will be noisy 14:12:17 #info in case you desire another (not yet scheduled) breakout - there is still room for it 14:12:30 #info schedule your breakouts in rooms Bellevue and Tegel 14:14:15 will the project track sessions on the schedule be updated with descriptions (there used to be descriptions on the wiki)? 14:14:25 https://www.eventscribe.com/2016/OPNFV/aaSearchByTrack.asp?h=Browse%20by%20Track&BCFO=P 14:14:34 #info soccer fans will find screens througout the venue 14:14:46 #topic Colorado planning and activities - David 14:15:01 The other David... 14:16:52 mbeierl: most of the project theater sessions (even on the wiki) didn’t have descriptions…. 14:17:05 rpaik: schade... 14:17:08 ok, thanks 14:17:20 I know… 14:17:52 #info David describes the triage process for JIRA issues 14:18:45 aka JIRA scrub 14:19:35 #info there is a plan for a breakout session during the design summit with dmcbride and mberierl 14:19:46 #info - possible proposal is to define the general process and delegate that to the PTLs to run with their own teams, and then report up at that level as needed 14:21:17 #link https://wiki.opnfv.org/display/SWREL/Colorado?preview=/2926065/6823197/colorado%20r7.pdf latest release schedule 14:21:50 https://wiki.opnfv.org/display/SWREL/Colorado+scenario+inventory+and+dependencies 14:22:28 #link https://wiki.opnfv.org/display/SWREL/Colorado+scenario+inventory+and+dependencies scenario invenroty & dependencies page 14:22:53 #info asking PTLs to fill in the information in the above page 14:25:27 #link https://wiki.opnfv.org/display/SWREL/Colorado Colorado page 14:25:54 #info there is a release schedule plus milestone descriptions on the Colorado page 14:28:02 #info fbrockners adds that there will be no separate feature freeze dates for 2.0 and 3.0 releases 14:30:22 #info dmcbride notes that documentation completion is to be aligned with the stable branch creation 14:31:16 #info frockners makes a suggestion to add a note that test results will not be part of the documentation completion in mid-August 14:31:28 specifically, https://wiki.opnfv.org/display/SWREL/Colorado?preview=/2926065/6823197/colorado%20r7.pdf ? 14:32:13 #startvote Do you approve the OPNFV Colorado schedule (https://wiki.opnfv.org/download/attachments/2926065/colorado%20r7.pdf?version=1&modificationDate=1465325418000&api=v2)? (+1,0,-1) 14:32:13 Begin voting on: Do you approve the OPNFV Colorado schedule (https://wiki.opnfv.org/download/attachments/2926065/colorado%20r7.pdf?version=1&modificationDate=1465325418000&api=v2)? Valid vote options are , +1, 0, -1, . 14:32:13 Vote using '#vote OPTION'. Only your last vote counts. 14:32:25 #vote +1 14:32:26 #vote +1 14:32:26 #vote +1 14:32:27 #vote +1 14:32:29 #vote +1 14:32:30 #info +1 14:32:32 #vote +1 14:32:32 #vote +1 14:32:35 #vote +1 14:32:37 #vote +1 14:32:39 #vote +1 14:32:50 #vote +1 14:32:59 #endvote 14:32:59 Voted on "Do you approve the OPNFV Colorado schedule (https://wiki.opnfv.org/download/attachments/2926065/colorado%20r7.pdf?version=1&modificationDate=1465325418000&api=v2)?" Results are 14:32:59 +1 (11): frankbrockners, dku, dneary, GeraldK, bryan_att, ttallgren, StuartMackie, Julien-z_, ildikov, bjskerry, ulik 14:34:36 #topic Project creation review - Daisy4NFV 14:34:49 dmcbride, How confident are you in the upcoming deadlines (this week re installer integration with OpenStack, feature freeze by 7/1)? 14:36:43 dneary: somewhat confident for Apex, JOID, and Fuel, but unclear for Compass 14:37:13 dmcbride, Thanks 14:39:19 #info Zhijiang discussed key highlights of Daisy4NFV such as multicacst, automatic deployment, containerized OpenStack services, configration template, etc. 14:41:42 #link http://lists.opnfv.org/pipermail/opnfv-tsc/2016-June/002708.html follow-up discussion after the last TSC meeting 14:42:53 just sent our comments - see http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2016-June/011060.html 14:43:00 #info Zhijiang says that one concern expressed is that a new installer will add new scenarios, and add strain to CI and testing teams. He sees this as a flaw in the scenario process which we should address. There is also a plan to add a new CI pod for testing 14:45:22 and the installers should essentially be running in different labs 14:45:36 to really make sure the portability 14:45:42 at least in my opinion 14:45:42 #info there is also discussion in the Infra WG on supporting additional installers 14:47:03 concern is the need for 2 dedicated POD for CI per installer + scalling with new scenario model 14:52:02 #info jmorgn1, ZTE has one CI POD working already and the other two are in the progress of applying for new CI slaves 14:53:04 well, the thing is not about adding pods 14:53:17 it is about keeping things operational 14:53:28 #info question on how we ensure we don't impact other projects resources? 14:53:40 the broader value of this proposal is expanding infra deployment approaches; that should not be "kicked down the road" just because our existing installer projects/infra are not efficient enough. we have to get more efficient, but also not inhibit valuable ideas from being brought as projects. 14:53:42 #info ttalgren asks to move Suvendu Mitra to contributor in the project proposal 14:53:45 #info how do we test the scaling aspects? 14:54:29 tbh, we already are burning out the same people even though we haven't reached the release phase 14:54:46 and wishful thinking helps up to certain point 14:55:59 in essence, if 60-80% of our POD bandwidth is consumed by keeping the existing installer engines running, that is an opportunity to do things better. But it should not be a rationale for deferring projects focusing on important new technology. 14:57:17 #info discussion on the need to investigate resource issues on scale testing and requirements for OPNFV test project teams 14:57:21 what I say is not about this project but in general 14:57:30 we are supporting more than installer projects 14:57:43 some put less demands and some more 14:58:18 but again, the no of contributors is the bottleneck 14:58:34 anywa, I have no objections 14:58:37 just concerns 14:59:05 I agree that all of use need to bring more resources to the table 14:59:47 this will go into infra project onboarding proposal page - human resource needs 15:00:23 #startvote Do you approve the creation of the Daisy4nfv project? (+1, 0, -1) 15:00:23 Begin voting on: Do you approve the creation of the Daisy4nfv project? Valid vote options are , +1, 0, -1, . 15:00:23 Vote using '#vote OPTION'. Only your last vote counts. 15:00:26 fdegir: The second zte pod shares a jumpserver with the first pod. not sure how well that will work. 15:00:33 #vote 0 15:00:37 #vote +1 15:00:37 #vote 0 15:00:37 #vote -1 15:00:39 I think the proposal needs more work 15:00:40 #vote 0 15:00:42 #vote 0 15:00:43 #vote +1 15:00:45 #vote 0 15:00:46 then that's not a phaors pod? 15:00:52 #vote 0 15:00:56 I think same as dneary 15:01:02 #vote 0 15:01:05 #StuartMackie #vote 0 15:01:08 #vote +1 15:01:17 #vote -1 15:01:17 aricg: not a pharos pod? 15:01:22 fgedir, Pharos-SH, not the same places 15:01:27 #info proxy for tnadeau 15:01:29 StuartMackie, Without your name 15:01:30 I mean, technically, no that is not how we do things. 15:01:36 I have added into the list 15:01:49 well it might cause conflicts for non-jenkins stuff 15:01:52 test projects maybe 15:02:00 #endvote 15:02:00 Voted on "Do you approve the creation of the Daisy4nfv project?" Results are 15:02:00 0 (7): dneary, dku, ildikov, GeraldK, ttallgren, frankbrockners, bjskerry 15:02:00 +1 (3): bryan_att, Julien-z_, edgarstp 15:02:00 -1 (2): rpaik, ulik 15:02:04 we can't do that 15:02:18 yes, depending on how much stuff is running on the jump host. I would be at least complicated to stop if from conflicting. 15:02:56 #info daisy4nfv has been approved 15:03:17 I wonder if the "vote 0"s understood that 15:03:28 #endmeeting