14:01:02 <bh526r> #startmeeting Weekly Technical Discussion
14:01:02 <collabot`> Meeting started Thu Feb  7 14:01:02 2019 UTC.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:02 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:01:02 <collabot`> The meeting name has been set to 'weekly_technical_discussion'
14:02:05 <CristinaPauna> #info Cristina Pauna
14:02:34 <mbeierl> #info Mark Beierl
14:02:40 <mbeierl> I need to leave in 30 minutes
14:02:59 <bh526r> #info Georg Kunz
14:03:03 <bramwelt> #info Trevor Bramwell
14:03:13 <bh526r> #info Pierre Lynch
14:03:24 <bh526r> #info Trevor Cooper
14:04:23 <ollivier> #info Cédric Ollivier
14:05:18 <bh526r> #topic Continue Discussion of Infrastructure Evolution
14:05:40 <acm> #info Al Morton (IRC only today)
14:05:42 <bh526r> #link https://wiki.opnfv.org/download/attachments/2925877/OPNFV%20Lab%20strategy%20discussion%20%2831Jan2019-v02%29.pptx?version=1&modificationDate=1548975828000&api=v2
14:08:09 <bh526r> #info Suggestion 1: Improve usage and visibility of Intel Lab, e.g. LaaS
14:09:37 <bh526r> #info and other community labs
14:18:43 <bh526r> #info Current LaaS in UNH is a model of how to book the lab resources through a GUI. The resources to be subscribed include both static resource and dynamic resource (e.g. VLAN tagging)
14:29:20 <bh526r> #info Intel is already working on replicating LaaS to Intel community lab
14:36:43 <bh526r> #info 2 steps approach:
14:37:23 <bh526r> #info 1st step: Trevor Cooper continues to drive Intel's effort on replicating LaaS to Intel community lab, which is happening now
14:38:13 <bh526r> #info Once this replication is successful, we can document the best practice of LaaS replication so that it can applied to other community labs
14:38:59 <bh526r> #info 2nd step: expand to other community lab. We can find the champion at that time. Trevor Bramwell should be able to find another champion
14:39:26 <bh526r> #info The expand usage of community lab is to become 3rd-party lab resources for compliance testing.
14:40:18 <bh526r> #info Governance doesn't prevent from charging a fee. But there is no precedent because there is really no 3rd-party lab yet
14:42:07 <bh526r> #topic Update of Compliance Program
14:42:33 <bh526r> #info CVC in LFN now focuses on VNF testing in ONAP
14:43:06 <bh526r> #info The effort was initiated from OPNFV, and now elevated to LFN about VNF testing
14:43:55 <bh526r> #info in ONAP
14:44:51 <bh526r> #info Dovetails resources are providing tooling for ONAP, such as portal and integration. We are really waiting for ONAP persons to finish their part. The targeted date is in April
14:45:56 <bh526r> #info Next release of OVP and Dovetail is in May, but not sure if it is achievable because we are helping ONAP now
14:46:53 <bh526r> #topic Update of Code and Release Quality Improvement
14:47:23 <bh526r> #info 1st proposal of removing inactive committers was agreed by TSC
14:48:09 <bh526r> #info 2nd proposal of enforcing disallowing self-merge needs more discussion
14:50:29 <bh526r> #info Cedric thinks that we should allow individual project to choose to participate in this enforcement
14:54:33 <bh526r> #info The proposal is that we let projects decide whether they want to enforce this rule in this project or not. Single active committer project is always excepted.
15:02:22 <bh526r> #info Georg suggests that we talk to each PTL and see if we really need it. For time being, we may be more pragmatic
15:03:36 <bh526r> #info Cristina will take the action to talk to each PTL and get a better overall picture.
15:05:21 <bh526r> #topic AOB
15:05:29 <bh526r> #info Meeting adjourned
15:05:33 <bh526r> #endmeeting