15:00:17 #startmeeting Infra WG Weekly Meeting 15:00:17 Meeting started Wed Sep 7 15:00:17 2016 UTC. The chair is fdegir. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:17 The meeting name has been set to 'infra_wg_weekly_meeting' 15:00:31 #topic Roll Call 15:00:46 #info Ray Paik 15:00:51 #info Lincoln Lavoie 15:00:59 #info Jack Morgan (Pharos) 15:01:05 We can hear you 15:01:09 #info Yujun Zhang 15:01:19 #topic Agenda 15:01:27 #link https://wiki.opnfv.org/display/INF/Infra+Working+Group#InfraWorkingGroup-Agenda 15:01:58 #topic Adding Huawei POD2 to CI PODs 15:03:13 #info How can a resource can be declared as CI Resource 15:03:15 #link https://wiki.opnfv.org/display/INF/Continuous+Integration#ContinuousIntegration-HardwareResources 15:05:10 i'm suggest sticking to plan (2 weeks to monitor) 15:08:59 #info Intel POD8 is not connected to Jenkins at the moment 15:09:45 #info Julien 15:09:54 #info Because of this, Compass requests addition of Huawei POD2 as CI POD 15:10:15 #action aricg and May-meimei to fix Intel POD8 Jenkins connection 15:10:54 #info Infra WG will monitor Huawei POD2 for 2 weeks and then take action 15:11:19 May-meimei: Sending connection string via pm 15:11:23 #topic Upcoming migration of Ericsson lab 15:11:40 #link http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2016-September/012466.html 15:12:36 #action fdegir and Daniel Smith to follow this up 15:13:32 #info The biggest impact will be on Fuel 15:13:57 #info The builds might be impacted as well 15:14:30 Doctor + Fuel + KVM not work for now 15:14:44 for a week in our pods 15:15:45 #chair jmorgan1 15:15:45 Current chairs: fdegir jmorgan1 15:16:21 #topic Discussion regarding any release blockers 15:16:34 #info frankbrockners asks if we have top 10 type of list of blockers 15:18:03 #info It is important for community to be disciplined to use JIRA to track issues with different severity/criticality 15:21:51 #info Installers PTLs might need to be contacted in order to find out if and which scenarios are under risk 15:21:57 May-meimei: Did you get my pm? Your key is expired so I can't send it via email 15:22:05 #info What can be done in order to sort remaining issues out 15:24:57 #action dmcbride to send mail to installer, test, infra PTLs and suggest having daily status meetings 15:26:05 #topic Infra/CI status update and plans for D-release 15:27:41 #info The main concern during Colorado release was CI Evolution 15:27:42 CI Evolution, phase #1/2 for example 15:27:59 CI evolution, phase #3/4 post Colorado 1.0 release 15:28:27 David is asking about phase #3/4, i think 15:31:06 #info The main issue for not having CI Evolution not being ready is lack of human resources 15:33:40 #info MS for Infra updates complete December 15th 15:35:37 #info The work with CI Evolution will be done on sandbox first 15:36:12 #link https://wiki.opnfv.org/display/INF/CI+Evolution 15:42:27 #info Separating builds from the rest of the chain and enabling/aligning commit gating/smoke test are the first steps towards CI Evolution 15:42:49 #info Once we have an alignment on these, work with scenario promotion can start 15:43:58 #action Put more detailed plan for CI Evolution including any prerequisites 15:44:02 #undo 15:44:02 Removing item from minutes: 15:44:07 #action fdegir Put more detailed plan for CI Evolution including any prerequisites 15:44:35 #topic Tracking OPNFV contributions in OpenStack 15:44:38 https://wiki.opnfv.org/display/COM/Tracking+OPNFV+contributions+in+OpenStack 15:44:51 #link https://wiki.opnfv.org/display/COM/Tracking+OPNFV+contributions+in+OpenStack 15:47:41 #info One question is if we are able to do this for other upstream projects? 15:48:09 #info OpenStack is first candidate to start with and try to design a mechanism which is applicable to other communities as well 15:49:28 #action aricg to propose this in releng and then send it to tech-discuss for further discussion 15:49:49 #action aricg to check how apex is doing this 15:50:26 #link https://wiki.opnfv.org/display/apex/Upstream+Tracking 15:51:20 #topic New Lab CI Process Discussion 15:51:49 #info There is a discrepancy between wiki and pharos repo regarding labs 15:52:41 #info we are now doing gerrit replication to improve clone speeds. If your DC would like a local copy of all opnfv repos send request to helpdesk. 15:52:45 #info One option could be to have all the lab information on gerrit and include generated documents on Wiki 15:52:49 thx aricg 15:53:14 #info The question is: what is the primary source for lab information 15:54:10 #info jmorgan1 says the labs will document information in Pharos repo by Colorado.3.0 15:55:22 #info morgan1, I will help you update some of the labs from the rst files 15:55:42 #info jmorgan1, I will help you update some of the labs from the rst files 15:57:46 #info We need to have an onboarding document for new labs/pods/resources coming online 15:58:37 #action jmorgan1 to start up a wiki page for resource onboarding 15:58:54 #topic Bitergia Jenkins Dashboard 15:59:09 #link https://opnfv.biterg.io proto-type page 15:59:33 click on Jenkins all the way on the right at the top 15:59:38 #info What information we want to display on Bitergia Dashboard when it comes to Jenkins? 16:00:14 thanks, Julien-zte 16:00:56 #info Please put ideas on etherpad linked below 16:00:58 #link https://etherpad.opnfv.org/p/jenkins-bitergia-dashboard 16:00:59 Julien-zte: i'll be updating the JIRA tasks today and we can work on them 16:01:12 OK jmorgan1 16:01:29 I can use ZTE for test for demo 16:01:40 That's fine with me. :) 16:02:11 #info This activity aims to collect job, scenario, slave statistics 16:02:15 #endmeeting