=============================== #opnfv-meeting: TSC weekly call =============================== Meeting started by uli-k at 12:59:03 UTC. The full logs are available at http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-07-18-12.59.log.html . Meeting summary --------------- * rollcall (uli-k, 12:59:41) * Luke Hinds (lhinds, 12:59:49) * hongbo (hongbo4536982147, 12:59:51) * Rossella Sblendido (rossella_s, 13:00:16) * Jose Lausuch (Morgan's proxy) (jose_lausuch, 13:00:28) * Yifei Xue (proxy for Justin) (yifei, 13:01:00) * LINK: https://wiki.opnfv.org/display/meetings/TSC#TSC-July18,2017 today's agenda (rpaik, 13:01:25) * fuqiao (fuqiao, 13:01:38) * Tim Irnich (timirnich, 13:02:05) * dneary (dneary, 13:02:47) * agenda bashing (rpaik, 13:04:03) * Trevor Cooper (trevor_intel, 13:04:05) * Security gate check/Anteater (rpaik, 13:04:15) * Security gate check/Anteater (uli-k, 13:04:22) * lhinds notes that anteater scans against patchsets and logs are done (e.g. flagging security issues) (rpaik, 13:06:07) * lhinds discussed setting up anteater as a chron job and notifying project team members (PTLs, committers, etc.) and asks how this could be done in a secure manner (rpaik, 13:07:52) * uli-k proposes that scanning could also be scheduled via Jenkins (rpaik, 13:09:17) * The reason to restrict scan results is to prevent security vulnerabilities from being made public (trevor_intel, 13:11:24) * uli-k also proposed to notify PTL and committers about findings (uli-k, 13:12:41) * still looking for the right location where to store these results, so only PTL and committers can access. (uli-k, 13:13:09) * ACTION: lhinds aricg- to provide the missing details for the proposal (uli-k, 13:14:09) * ACTION: lhinds/aricg to start a maling list conversation on where to store/communicate sensitive information from anteater (rpaik, 13:14:32) * multiple repo's for OPNFV projects (rpaik, 13:15:31) * LINK: https://gerrit.opnfv.org/gerrit/#/admin/projects/?filter=releng (jose_lausuch, 13:16:31) * trozet shares that for Apex they need to modify upstream code and additional repo's are used to fork upstream code to put NFV features (rpaik, 13:17:43) * https://wiki.opnfv.org/display/INF/Split+up+Releng+Repository (aricg-, 13:18:29) * Apex team had a separate Github repo for upstream work, but this was brought into OPNFV (rpaik, 13:18:36) * Bryan Sullivan (bryan_att, 13:19:41) * uli-k notes if a process is needed for projects having multiple repos, or simply allow projects to create multiple repo's (by default) (rpaik, 13:21:12) * bryan_att suggests not to restrict projects (uli-k, 13:21:26) * ACTION: rpaik to confirm if there's written "rule" somewhere for 1 repo/project (rpaik, 13:22:35) * there seems to be consensus to allow project teams to decide what is best for their project in terms of number of repo's (rpaik, 13:23:30) * ACTION: rpaik to follow-up with community members via mailing list (rpaik, 13:24:45) * in the absence of any specific bylaws constraint I suggest we just enable projects to notify (as a courtesy) the TSC that a new repo has been created, and if for some reason it seems that the freedom to do so is cuasing misbehavior, the TSC can step in later (bryan_att, 13:26:05) * 3rd party license codes have been put into a "3rd party" directory (rpaik, 13:26:23) * Request for OPNFV infra resources for project Bamboo PNDA instance (uli-k, 13:27:05) * Aric and Ray propose to do it via google cloud (uli-k, 13:27:57) * cost estimate would be 350$ (uli-k, 13:28:14) * aricg notes that additional GCE resources maybe needed but donaldh is looking into this (rpaik, 13:28:44) * that could be covered by TSC money (uli-k, 13:29:14) * we need to look at alternatives that are not GCE based (bryan_att, 13:29:26) * suggestion from trevor_intel and bryan_att is to also look at other alternatives and evaluate if resources are being used (after the decision is made) (rpaik, 13:30:06) * ACTION: rpaik to ping donaldh and ask him to return to the next TSC call (rpaik, 13:32:43) * Julien (Julien-zte, 13:32:47) * approval of previous meeting minutes (rpaik, 13:33:13) * no feedback/comments on previous minutes, thus minutes approved (rpaik, 13:33:24) * mchandras (hwoarang, 13:33:38) * Danube/Euphrates update (rpaik, 13:33:45) * Danube/Euphrates update (uli-k, 13:34:03) * dmcbride notes that Danube 3.0 is out (rpaik, 13:34:05) * LINK: https://www.opnfv.org/software/downloads SW downloads page (rpaik, 13:34:16) * mchandras (proxy for Fatih) (hwoarang, 13:34:24) * for Euphrates Milestone 5 is July 28th (scenario integration & feature freeze) (rpaik, 13:34:56) * MS6 (test case implementation) is August 11th (rpaik, 13:36:37) * Milestone 5 implies that we don't expect new scenarios created after that (uli-k, 13:38:31) * dmcbride notes that Fuel team has also documented their scenarios (rpaik, 13:39:08) * LF IT/infra update (rpaik, 13:40:40) * Rudy reports from the outage in Portland (uli-k, 13:41:25) * basic notes that there was a power outage in Portland data center last week (rpaik, 13:41:30) * this impacted many of our services in OPNFV (git/gerrit, wiki, etc) (rpaik, 13:42:13) * outage for git/gerritt and JIRA was about 30 minutes, but for wiki it was bout 3 hours (rpaik, 13:44:32) * root cause analysis is still on-going and there will be further communication to mailing lists (rpaik, 13:45:00) * opnfv-tech-discuss is now subscribed to status.opnfv.org page (rpaik, 13:46:30) * ACTION: basic to test the automatic posting on opnfv-tech-discuss (rpaik, 13:47:01) * Test WG proposal (rpaik, 13:47:42) * uli-k notes that there's a further action item for Test WG to work with Infra WG but this has not been done yet (rpaik, 13:48:34) * Gabriel requires for a pod for long term stress test from test WG (Julien-zte, 13:49:11) * LINK: https://global.gotomeeting.com/join/798898261 (GTM) (uli-k, 13:51:50) * LINK: https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-July/017025.html (rpaik, 13:51:55) * Is this about x-CI or stability testing? (bryan_att, 13:56:00) * we need further discussion on this. I don't understand why we are using a new installer for this rather than the existing installers. (bryan_att, 14:00:43) * we need to do stability testing on the existing OPNFV scenarios using existing OPNFV installers. (bryan_att, 14:01:36) * propose to postpone this discussion to next week (rpaik, 14:01:48) Meeting ended at 14:02:33 UTC. Action items, by person ----------------------- * lhinds * lhinds aricg- to provide the missing details for the proposal * lhinds/aricg to start a maling list conversation on where to store/communicate sensitive information from anteater * rpaik * rpaik to confirm if there's written "rule" somewhere for 1 repo/project * rpaik to follow-up with community members via mailing list * rpaik to ping donaldh and ask him to return to the next TSC call People present (lines said) --------------------------- * rpaik (41) * uli-k (23) * bryan_att (12) * jose_lausuch (6) * Julien-zte (5) * collabot (4) * dneary (3) * trevor_intel (2) * lhinds (2) * aricg- (2) * hongbo4536982147 (2) * hwoarang (2) * yifei (1) * timirnich (1) * fuqiao (1) * rossella_s (1) * trozet (1) Generated by `MeetBot`_ 0.1.4