======================================= #opnfv-meeting: Infra WG Weekly Meeting ======================================= Meeting started by fdegir at 15:00:17 UTC. The full logs are available at http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-09-07-15.00.log.html . Meeting summary --------------- * Roll Call (fdegir, 15:00:31) * Ray Paik (rpaik, 15:00:46) * Lincoln Lavoie (lylavoie, 15:00:51) * Jack Morgan (Pharos) (jmorgan1, 15:00:59) * Yujun Zhang (yujunz-zte, 15:01:09) * Agenda (fdegir, 15:01:19) * LINK: https://wiki.opnfv.org/display/INF/Infra+Working+Group#InfraWorkingGroup-Agenda (fdegir, 15:01:27) * Adding Huawei POD2 to CI PODs (fdegir, 15:01:58) * How can a resource can be declared as CI Resource (fdegir, 15:03:13) * LINK: https://wiki.opnfv.org/display/INF/Continuous+Integration#ContinuousIntegration-HardwareResources (fdegir, 15:03:15) * Intel POD8 is not connected to Jenkins at the moment (fdegir, 15:08:59) * Julien (Julien-zte, 15:09:45) * Because of this, Compass requests addition of Huawei POD2 as CI POD (fdegir, 15:09:54) * ACTION: aricg and May-meimei to fix Intel POD8 Jenkins connection (fdegir, 15:10:15) * Infra WG will monitor Huawei POD2 for 2 weeks and then take action (fdegir, 15:10:54) * Upcoming migration of Ericsson lab (fdegir, 15:11:23) * LINK: http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2016-September/012466.html (fdegir, 15:11:40) * ACTION: fdegir and Daniel Smith to follow this up (fdegir, 15:12:36) * The biggest impact will be on Fuel (fdegir, 15:13:32) * The builds might be impacted as well (fdegir, 15:13:57) * Discussion regarding any release blockers (fdegir, 15:16:21) * frankbrockners asks if we have top 10 type of list of blockers (fdegir, 15:16:34) * It is important for community to be disciplined to use JIRA to track issues with different severity/criticality (fdegir, 15:18:03) * Installers PTLs might need to be contacted in order to find out if and which scenarios are under risk (fdegir, 15:21:51) * What can be done in order to sort remaining issues out (fdegir, 15:22:05) * ACTION: dmcbride to send mail to installer, test, infra PTLs and suggest having daily status meetings (fdegir, 15:24:57) * Infra/CI status update and plans for D-release (fdegir, 15:26:05) * The main concern during Colorado release was CI Evolution (fdegir, 15:27:41) * The main issue for not having CI Evolution not being ready is lack of human resources (fdegir, 15:31:06) * MS for Infra updates complete December 15th (fdegir, 15:33:40) * The work with CI Evolution will be done on sandbox first (fdegir, 15:35:37) * LINK: https://wiki.opnfv.org/display/INF/CI+Evolution (fdegir, 15:36:12) * Separating builds from the rest of the chain and enabling/aligning commit gating/smoke test are the first steps towards CI Evolution (fdegir, 15:42:27) * Once we have an alignment on these, work with scenario promotion can start (fdegir, 15:42:49) * ACTION: fdegir Put more detailed plan for CI Evolution including any prerequisites (fdegir, 15:44:07) * Tracking OPNFV contributions in OpenStack (fdegir, 15:44:35) * LINK: https://wiki.opnfv.org/display/COM/Tracking+OPNFV+contributions+in+OpenStack (aricg, 15:44:38) * LINK: https://wiki.opnfv.org/display/COM/Tracking+OPNFV+contributions+in+OpenStack (fdegir, 15:44:51) * One question is if we are able to do this for other upstream projects? (fdegir, 15:47:41) * OpenStack is first candidate to start with and try to design a mechanism which is applicable to other communities as well (fdegir, 15:48:09) * ACTION: aricg to propose this in releng and then send it to tech-discuss for further discussion (fdegir, 15:49:28) * ACTION: aricg to check how apex is doing this (fdegir, 15:49:49) * LINK: https://wiki.opnfv.org/display/apex/Upstream+Tracking (fdegir, 15:50:26) * New Lab CI Process Discussion (fdegir, 15:51:20) * There is a discrepancy between wiki and pharos repo regarding labs (fdegir, 15:51:49) * 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. (aricg, 15:52:41) * One option could be to have all the lab information on gerrit and include generated documents on Wiki (fdegir, 15:52:45) * The question is: what is the primary source for lab information (fdegir, 15:53:14) * jmorgan1 says the labs will document information in Pharos repo by Colorado.3.0 (fdegir, 15:54:10) * morgan1, I will help you update some of the labs from the rst files (Julien-zte, 15:55:22) * jmorgan1, I will help you update some of the labs from the rst files (Julien-zte, 15:55:42) * We need to have an onboarding document for new labs/pods/resources coming online (fdegir, 15:57:46) * ACTION: jmorgan1 to start up a wiki page for resource onboarding (fdegir, 15:58:37) * Bitergia Jenkins Dashboard (fdegir, 15:58:54) * LINK: https://opnfv.biterg.io proto-type page (rpaik, 15:59:09) * What information we want to display on Bitergia Dashboard when it comes to Jenkins? (fdegir, 15:59:38) * Please put ideas on etherpad linked below (fdegir, 16:00:56) * LINK: https://etherpad.opnfv.org/p/jenkins-bitergia-dashboard (fdegir, 16:00:58) * This activity aims to collect job, scenario, slave statistics (fdegir, 16:02:11) Meeting ended at 16:02:15 UTC. Action items, by person ----------------------- * aricg * aricg and May-meimei to fix Intel POD8 Jenkins connection * aricg to propose this in releng and then send it to tech-discuss for further discussion * aricg to check how apex is doing this * fdegir * fdegir and Daniel Smith to follow this up * fdegir Put more detailed plan for CI Evolution including any prerequisites * jmorgan1 * jmorgan1 to start up a wiki page for resource onboarding People present (lines said) --------------------------- * fdegir (55) * Julien-zte (7) * jmorgan1 (7) * collabot (5) * aricg (4) * lylavoie (3) * rpaik (3) * yujunz-zte (1) Generated by `MeetBot`_ 0.1.4