12:59:09 #startmeeting Weekly TSC meeting 12:59:09 Meeting started Tue Aug 8 12:59:09 2017 UTC. The chair is tallgren. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:59:09 Useful Commands: #action #agreed #help #info #idea #link #topic. 12:59:09 The meeting name has been set to 'weekly_tsc_meeting' 12:59:17 #chair rpaik 12:59:17 Current chairs: rpaik tallgren 12:59:32 #info Tapio Tallgren 12:59:45 #info Uli 13:00:13 #info Frank Brockners 13:00:16 #info joehuang 13:00:40 #info hongbo 13:00:41 #info Rossella Sblendido 13:00:54 #info Carlos Goncalves (proxy for Xavier Costa) 13:00:57 #info Fatih Degirmenci 13:02:04 #info Bryan Sullivan 13:02:05 #info Morgan Richomme 13:03:54 #topic agenda bashing 13:04:11 #link https://wiki.opnfv.org/display/meetings/TSC#TSC-August8,2017 today's agenda 13:05:33 #info no other topics suggested 13:06:07 #topic approval of previous meeting minutes 13:06:20 #info dradez (proxy for dneary) 13:06:26 we now have a quorum 13:06:34 #info no feedback on previous minutes thus minutes are approved 13:06:52 #topic Multisite project termination review 13:07:35 #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-July/017258.html Joe's email 13:07:54 joe is here :) 13:07:55 joehuang can you provide additional updates (if any) on irc? 13:08:09 ok, no new update yet 13:08:36 #info multisite is an requirements project where development work was done in OpenStack 13:09:42 #info 13:09:51 #info fuqiao 13:10:23 #info joehuang has stepped down as PTL and no one else from the community has stepped forward to lead the project 13:11:27 #info morgan_orange notes that multisite is one of the key pain points for end-users 13:12:40 #info an option would be to put the project in "hibernation" and see if there are others interested in continuing the project 13:12:51 fine 13:12:58 #info jmorgan1 mentions that Multisite is an important project and has address a service provider painpoint 13:13:13 #undo 13:13:13 Removing item from minutes: 13:13:27 #info morgan_orange mentions that Multisite is an important project and has address a service provider painpoint 13:15:31 #info from the Pain Point list: Support multisite deployments ranging from simple site pairs, to massively distributed and hierarchical deployments. Key aspects include identity/auth federation, quota management, catalog distribution, global/local resource orchestration, ... 13:17:13 #info frankbrockners suggests that if there's no one willing to step in even in hibernation stage, it may make sense to move forward to terminate the project 13:17:19 @frankbrockners well said... 13:17:19 tallgren: Error: "frankbrockners" is not a valid command. 13:17:25 frankbrockners well said... 13:18:13 #info Trevor Cooper 13:18:47 #startvote does the TSC approve termination of the multisite project? (+1, 0, -1) 13:18:47 Begin voting on: does the TSC approve termination of the multisite project? Valid vote options are , +1, 0, -1, . 13:18:47 Vote using '#vote OPTION'. Only your last vote counts. 13:18:54 #vote +1 13:18:55 #info +1 13:18:58 #vote +1 13:18:59 #vote +1 13:19:00 #vote +1 13:19:00 #vote -1 13:19:00 #vote +1 13:19:02 #vote +1 13:19:02 #vote +1 13:19:04 #vote +1 13:19:05 #vote +1 13:19:41 #vote +1 13:19:46 #endvote 13:19:46 Voted on "does the TSC approve termination of the multisite project?" Results are 13:19:46 +1 (10): frankbrockners, hongbo789654236, cgoncalves, fdegir, radez, Julien-zte, trevor_intel_, bryan_att, uli-k, tallgren 13:19:46 -1 (1): morgan_orange 13:20:02 #info termination of multisite is approved 13:20:04 I voted +1 because it only makes sense to allow projects to terminate if there is no support; that has no bearing on this area's priority though - just realistic chances of progress at this time 13:20:25 thank you :) 13:20:26 #topic creation review for Auto 13:21:03 bye 13:21:16 thanks joehuang 13:21:31 #link https://wiki.opnfv.org/pages/viewpage.action?pageId=12387216 Auto project proposal 13:21:42 joehuang: I voted -1 because the project was great (demo in Beijing) and multisite corresponds to a pain point and a service provider main goal..so I think the project should exist anyway...but I understand bryan_att & TSC point .. 13:22:33 it means that we must clean functest...(remove multisite support) 13:23:53 #link https://lists.opnfv.org/pipermail/opnfv-tsc/2017-August/003676.html 13:26:01 #info bryan_att notes that there has been discussions with the Opera team on how quickly that project can get restarted and how the Auto team should work with the Opera team 13:29:04 #info please add Prasad Gorja of NXP as Auto commiter 13:31:40 #info tallgren asks about dependencies on installers, and bryan_att notes that is the focus of Opera 13:32:14 #info there are concerns about the list of committers (there's only one so far) 13:33:50 #info suggestion is to come back to the TSC for approval when there are details for additional committers and planned deliverables for F-release 13:36:28 #info suggestion that it'd be ideal for the deployment project in ONAP to become a "sister" project to Auto 13:39:06 #topic Euphrates update 13:39:28 #info the new MS5 (scenario integration + feature freeze) date is this Friday (Aug. 11th) 13:40:00 #info if anyone needs to file an exception request for MS5, please go to https://wiki.opnfv.org/display/SWREL/Milestone+Exception+Requests+for+Euphrates 13:40:20 #info new MS6 (test case implementation + preliminary documentation) is Aug. 25th 13:40:32 #info new target release date for Euphrates 1.0 is October 6th 13:41:54 #link https://wiki.opnfv.org/download/attachments/8689511/OPNFV%20Release%20%2522Euphrates%2522%20r9.pdf?version=1&modificationDate=1501705987000&api=v2 updated schedule 13:42:13 #topic LF IT/infra update 13:43:03 #info no scheduled maintenance/upgrades 13:43:57 #topic Multiple repo's/projects 13:44:17 #info rpaik had an action item to investigate if there's written rule somewhere in OPNFV on one repo/project 13:44:23 #info ericsson-build3,4 ran out of disk space yesterday. bramwelt will be looking into distributing resources better. 13:44:53 #info there doesn't seem to be a written rule, but this seems to be based on "convention" 13:45:38 May I catch the committer's name for Auto Project while I was presenting just now? 13:46:26 #info +1 for letting the PTLs do what they need 13:47:35 #info frankbrockners and fdegir adds that he thinks it's OK to give PTLs the freedom to make a decision on multiple repo's and notify the community when that is done 13:48:40 #info suggestion to make a note on the relationship with main/master "repo" in the INFO file 13:49:57 #info naming convention could be "project name-subrepo" 13:51:00 #agree that PTLs can create multiple repos for their projects, but should notify the community 13:52:08 #action aricg/bramwelt to add a comment on the naming convention in the INFO file 13:52:26 #topic TSC elections 13:53:10 #info tallgren notes that normally there will be an annual election in September (for committers-at-large, TSC Chair, Committer Board) 13:54:08 #info with project harmonization happening does it make sense to still hold the annual elections? 13:54:21 hi rpaid, as uli-k suggested that we'd better update the procedure of development to support the PTL to decide to use mulitple repos. 13:54:57 without kept in the wiki, new PTLs won't know these rules. 13:55:13 #info I don't think we should make any change at this time, continue the election process as normal for the current cycle. If/when surrounding conditions change, we can consider the most appropriate changes then. 13:55:33 #info one option would be to postpone the elections until after harmonization 13:55:38 #info I note that any discussion of how LF may structure projects is preliminary at this time. 13:56:57 #info bryan_att proposes having the elections as usual 13:57:11 agree with bryan_att 13:57:36 agreed 13:58:34 #info next OPNFV F release name may be discussed after PTO, maybe in Sep. 13:58:42 rpaik: +1 for F and E release name voting 13:58:56 I prefer F+G 13:59:01 #agree 13:59:01 oops :-) 13:59:10 * uli-k :) 13:59:15 #agree to continue the annual TSC elections 13:59:17 #agree 13:59:25 prefer 1 per time and we can discuss twice this time 13:59:36 #endmeeting