16:00:36 #startmeeting Infra WG Weekly Meeting 16:00:36 Meeting started Mon Nov 20 16:00:36 2017 UTC. The chair is fdegir. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:36 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:36 The meeting name has been set to 'infra_wg_weekly_meeting' 16:00:42 #topic Rollcall 16:01:12 #info David Blaisonneau 16:01:16 #info Aric Gardner 16:01:20 #info Tianwei wu 16:01:32 #info Agenda is its on the usual place 16:01:41 #info Trevor Bramwell 16:01:41 #info Jack Morgan 16:01:43 #info David McBride 16:01:49 #link https://wiki.opnfv.org/display/INF/Infra+Working+Group 16:01:54 #chair jmorgan1 16:01:54 Current chairs: fdegir jmorgan1 16:02:31 #topic Zuulv3 Prototype 16:03:09 #info We brought up 1 VM to start the prototype 16:03:17 #link https://etherpad.opnfv.org/p/opnfv-zuul-prototype 16:03:57 #topic Huawei Lab Migration 16:04:17 #info Huawei lab will be migrated during this week 16:04:18 #info Tim Irnich 16:05:15 huawei pod7 pod12 and virtual 5 to 7 are in xi' an lab 16:05:47 these pods will be offline during the time of migrating 16:05:48 #info PODs that will be impacted are pod7 pod12 and virtual 5 to 7 16:06:11 #info The PODs will be offline during the migration 16:07:09 #info Impacted projects are Compass and Joid - needs to be verified 16:07:39 #action hw_wutianwei and fdegir to contact the affected projects 16:08:01 #info An ARM based POD will be added as well 16:09:10 #info To connect the new PODs to Jenkins, a ticket is needed to be sent to LF Helpdesk 16:11:57 #topic CI Resources for JOID 16:12:28 #info narinder` sent a ticket to opnfv-helpdesk 16:12:43 #info Joid doesn't have any resources to run baremetal jobs 16:13:04 #info intel-pod18 needs to be connected to OPNFV Jenkins 16:13:47 #info To connect this POD to OPNFV Jenkins, workaround needs to be applied for port 80 16:14:37 #info Once the POD is connected to Jenkins, it needs to be labelled with joid-baremetal 16:15:14 #info And finally the slave needs to be added to slave-params.yml 16:15:15 #link https://gerrit.opnfv.org/gerrit/gitweb?p=releng.git;a=blob;f=jjb/global/slave-params.yml 16:15:51 #action narinder` to work with aricg/bramwelt to fix the slave 16:16:42 #topic XCI at Plugfest 16:17:50 #info XCI session is scheduled for Day 3 16:17:54 #link https://wiki.opnfv.org/display/EVNT/Euphrates+Plugfest+Schedule#EuphratesPlugfestSchedule-Day3(December6th)Schedule 16:19:05 #info Practices/principles to follow in order to be part of XCI need to be agreed on 16:19:20 #info Infra/CI practices such as PDF/IDF/SDF & dynamic CI, having people/hw, etc. which will be documented 16:23:40 #topic Sending Out MoM 16:23:58 #info Meeting minutes are sent to tech-discuss - see the last week's minutes 16:24:00 #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-November/019274.html 16:25:03 #topic How to use special hw and run tests on them 16:25:34 #info Some features require special hw or specific configuration which need to be handled 16:26:02 #info Discussion is needed to find out how to work on this 16:26:29 #info One option could be incorporating this into ongoing discussion to refresh Pharos spec 16:27:55 #info This is needed in order to easily find out which features are offered by which labs/PODs 16:28:48 #info Based on the information provided by the labs, we can automatically decide where a certain deployment should go or enable test frameworks to pick right test cases 16:31:32 #info Pharos spec can have some basic use cases and the above things could be additions on top of the base spec 16:33:34 #info A topic for plugfest has been added to the agenda: Testing hardware/software interactions brainstorming 16:33:40 #link https://wiki.opnfv.org/display/EVNT/Euphrates+Plugfest+Schedule#EuphratesPlugfestSchedule-Day4(December7th)Schedule 16:33:47 #info The day/time might change coming days 16:34:05 #action timirnich to follow up the topic during plugfest 16:35:34 #topic Define test requirements for gating scenarios for the release 16:36:26 #info This is simply improving release criteria by using the results from test runs 16:41:12 #info Tooling support is needed 16:42:15 #info Release Criteria needs to be discussed and brought up to TSC for approval once things are clarified within community 16:43:31 #action dmcbride to followup the topic to ensure this gets discussed during the plugfest 16:44:00 #topic Action Item Review 16:44:15 #info Open: Move PDF from Octopus repo to Pharos repo 16:44:33 #info Open: Talk about OPNFV Zuulv3 prototype within LF Infra/Releng to see how it fits into overall LF strategy/backlog 16:45:19 #info Open: Review the no of PODs installers have 16:45:53 #info Open: Update documents on CI POD requirements 16:47:20 #info Open: Clean up securelab access including creating new ldap group for lab owners 16:47:49 #info The encryption will be done per lab basis as needed and the above action item can be closed once the PDFs moved to pharos repo 16:48:15 #info After some time, securedlab usage should be blocked 16:48:52 #info Open: Clean up non-active Pharos committers - lab owners will be made Pharos committers 16:49:32 #info Open: Pharos project needs to define hardware details to be included 16:49:35 #info Done: Send email to Lab owners to request them to input lab information into dashboard 16:50:13 #info Done: Infra WG needs to decide how to manage documentation - we have two proposal 16:50:30 #action jmorgan1 to decide how to handle pharos/hw infra documentation 16:51:15 #info Done: start email thread on transitioning docker build script to the releng project 16:52:29 #info Open: schedule a Plugfest discussion on logging facilities 16:56:35 #info Joe Kidder 16:56:50 jmorgan1: this is how it looks on mailman: https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-October/018782.html 16:57:04 jmorgan1: did you send as an attachment to the mail? 16:57:23 #endmeeting