13:01:06 #startmeeting Weekly TSC meeting 13:01:06 Meeting started Tue Jul 25 13:01:06 2017 UTC. The chair is tallgren. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:06 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:01:06 The meeting name has been set to 'weekly_tsc_meeting' 13:01:16 #rollcall 13:01:17 #chair rpaik 13:01:17 Current chairs: rpaik tallgren 13:01:24 #info Uli 13:01:28 #info hongbo 13:01:33 #info Frank Brockners 13:01:46 #info Bin Hu 13:02:02 #info Luke Hinds (proxy for Fatih) 13:02:18 #info Tim Irnich 13:02:34 #info Rossella Sblendido 13:02:50 #info Bryan Sullivan 13:02:54 #info Xavier Costa 13:02:54 we now have a quorum 13:03:31 #topic approval of previous meeting minutes 13:03:43 #info no feedback on minutes, thus previous minutes are approved 13:03:50 #topic agenda bashing 13:04:05 #link https://wiki.opnfv.org/display/meetings/TSC#TSC-July25,2017 today's agenda 13:04:28 #info Jose Lausuch (Morgan's proxy) 13:05:23 #info no other topics suggested 13:05:54 #topic Request for OPNFV infra resources for project Bamboo PNDA instance 13:06:44 #info donaldsh notes that the aim is to deploy an infrastructure for Bamboo PNDA analytics 13:07:31 #info fuqiao 13:07:51 #info correlation of data from tests is one of the value that the project is trying to provide 13:08:33 what link? 13:08:52 #link https://github.com/pndaproject/pnda-guide/blob/develop/provisioning/aws/PREPARE.md#required-resources pico requirements 13:09:31 #info VM deployment will work so BM is not needed 13:11:22 #info donaldh notes that the pico spec above is based on AWS 13:12:08 #info Julien 13:13:30 #info running on GCE is also an option 13:14:52 #info Is there a link to a clear description of what we will obtain for this expense, e.g. ala what you would have to get by your boss if you wanted to pay for this directly? 13:16:18 #info any request to the BOD needs to have such an explanation and all the TSC should agree that the cost serves a globally-useful goal for OPNFV, i.e. we will get ongoing value as an org (not just a single project) 13:16:31 #info rpaik notes that there's funding in TSC Initiatives bucket to try this out in GCE for a few quarters 13:18:20 https://github.com/pndaproject/pnda-guide/blob/develop/provisioning/aws/PREPARE.md#required-resources 13:18:42 The Pico instance requirements on this link ^^^ 13:21:06 #info donaldh notes that there community interest in deeper analysis of test results data 13:21:54 #info there can be a checkpoint in 5-6 months to ensure that there's value to OPNFV 13:24:51 #info I want the TSC to be diligent on understanding and reacting with consensus based upon that understanding. What are the goals of this data mining resource? It has t be more than just standing up another dashboard. There needs to be specific valuable things that we hope to learn from this. Otherwise in the interim it should be stood up on resources provided by the project team. 13:25:09 #action donaldh to describe value to be provided via email/wiki and work with aricg to get a GCE quote before a decision at the TSC next week 13:25:33 #into The TSC needs to set expectation that projects are self-funded wrt server resources if at all possible. 13:25:41 #topic Euphrates update 13:26:43 #info dmcbride notes that MS5 is due on July 28th where feature projects need to complete scenario integration/feature freeze 13:27:41 #info MS6 is due on Aug 11th where test cases/preliminary documentation is due 13:28:18 #info Stable branch freeze is open from August 11th to September 1st 13:28:38 #link https://wiki.opnfv.org/display/SWREL/Documentation+Compliance+for+Euphrates 13:29:32 #info there's also a new wiki form where exception requests can be submitted 13:29:55 #link https://wiki.opnfv.org/display/SWREL/Milestone+Exception+Requests+for+Euphrates 13:31:26 #info there's a one week grace period for an exception request, so for people who miss MS5. So exception request for MS5 needs to be in by August 4th 13:31:51 #topic LF IT/infra update 13:35:31 #info Upcoming Java service restarts to address recently announce vulerability. Tenativly scheduled for this Saturday the 29th. Should be less than 30 minutes of downtime. 13:35:34 #info basic is also looking into tech-discuss subscription to the status page and make sure it's still subscribed 13:36:06 #topic Testing working group proposal on test strategy evolution 13:37:26 #info gabriel_yuyang notes that there was a discussion in the Infra WG and a request for a POD for stress testing 13:38:14 #info gabriel_yuyang create a jira ticket in Infra WG 13:38:54 #info jose_lausuch notes that round-robin testing across all 5 installers maybe a challenge 13:39:02 #info If we could get 1 POD, then we could start discussion about installers that could be tested 13:39:57 #info new test cases will be implemented for Euphrates in addition some cases developed for Danube 13:40:27 #info is there a link to the scenarios that will be tested using OSA as the installer? We need to be sure this does more than validate what OpenStack as a project should itself be validating (resilience of that generic platform). 13:41:24 #info we need to focus on test cases that stress what is unique to OPFNV - e.g. integration of cloud and SDNCs, detailed networking features e.g. FD.io / DPDK, etc 13:42:05 #info gabriel_yuyang and jose_lausuch note that work can start once a pod can be secured 13:44:24 #info jose_lausuch notes that the team will start with simple scenario (e.g. nosdn-nofeature) and will build from there 13:47:05 #info bryan_att notes that he desires moving aggressively to do stress testing beyond OpenStack 13:48:06 From my experience, you will have a lot of problems from just testing OpenStack... 13:48:24 #info I think we need to set broader and higher goals in OPNFV, even to start. Just focusing on OpenStack does not add enough value for OPNFV IMO. OpenStack has *thousands* of devs and they can't do resiliency testing? 13:50:19 #info there's consensus that the ultimate goal is to stress test OPNFV components 13:50:41 #topic projects health review 13:50:57 #link https://wiki.opnfv.org/download/attachments/2926284/Q2%272017%20OPNFV%20Project%20Health%20Metrics%20v1.xlsx?version=1&modificationDate=1500935803574&api=v2 data for Q2'17 13:52:11 #info Re the last opic: In the first phase the issues in OpenStack that are investigated any deeper than a bug fix request should be those that are truly show-stoppers, i.e. blockers for more complex scenarios. Otherwise we risk getting distracted by issues that take focus off the real goal - resiliency of an integration scenario of components. 13:55:41 #info discussion on tracking upstream work 13:59:29 #action rpaik to follow-up with frank_brockners on tracking fd.io activities 14:02:49 #endmeeting