15:59:26 #startmeeting OPNFV Pharos 15:59:26 Meeting started Wed Jan 20 15:59:26 2016 UTC. The chair is trevor_intel1. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:26 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:59:26 The meeting name has been set to 'opnfv_pharos' 15:59:49 #info Trevor (Intel) 15:59:58 #info Narinder Gupta 16:01:11 #info Fatih Degirmenci 16:01:37 # info Jack Morgan 16:02:24 Lets start with POD stuff (as usual) ... or other suggestions? 16:02:48 JIRA scrub and release docs 16:03:04 Jack: ok will get there 16:03:40 #topic Lab resources and POD status 16:03:44 trevor_intel1 looks like newly added node in pod5 has some network issue 16:03:53 jack? 16:04:45 narindergupta: what is the issue? 16:05:19 jmorgan1: looks like eth2.724 vlan is not functionainifg and can not get ip on dhcp 16:05:20 trevor_intel1: this is the jump host btw 16:05:30 jmorgan1: while other nodes can 16:05:32 narindergupta: can't find an email about this 16:05:53 trevor_intel send it to michael i will copy you now 16:05:56 narindergupta: ok, i'll take a look at it after this meeting 16:06:05 ok 16:06:12 narindergupta: please include me for intel lab items 16:06:20 jmorgan1: 16:06:21 narindergupta: ALL support emails should at least go to Jack and me 16:06:22 sure 16:06:28 narindergupta: michael will be moving on to other projects after this month 16:07:12 narindergupta: how is this issue impacting you? 16:08:03 external network connectivity is not there 16:08:03 this isn't the jump host for pod 5, just a node actually 16:08:07 Jack: Is this something we can solve quickly? 16:08:30 trevor_intel1: i think so, probably a switch configuration 16:09:11 Jack: ok good 16:09:23 What else for Intel PODs? 16:09:35 Jack: Please give a status upate 16:09:46 Jack: anythign to note 16:10:00 Jack: e.g. POD 3 16:10:12 Tim will investigate pod 2 after its move to new enviornment 16:10:30 Jack: has he given a timeline? 16:10:37 intel pod 3: currently working on getting kvm4nfv up and running as well as ovsnfv 16:11:04 then will get vsperf working - goal is by EOW 16:11:15 trevor_intel1: no timeline for pod 2 investigation 16:11:29 Jack: that is a concern 16:11:33 +1 16:11:48 also, intel pod 1 will be migrated to new enviornment this week 16:12:23 I don't see Tim online 16:12:29 intel pod 2 has been ready since last Friday 16:12:29 trozet: ping 16:13:11 this is pretty important since test teams will need to troubleshoot and this will require CI not to run during those times 16:13:27 fdegir: +1 16:13:31 and this was one of the reasons why we tried so hard to get 2 PODs per installer 16:13:46 fdegir: indeed 16:14:02 stable and latest :) 16:14:18 well, lessons learnt 16:14:29 so who will bug Tim about this? 16:14:30 we must make sure to explain why are the things in this way 16:14:32 and not the other 16:14:49 I nominate jmorgan1 :) 16:15:05 trevor_intel1: i mentioned to Tim yesterday about this, he said he would look at it 16:15:19 Jack: needs more than a mention 16:16:13 send an email to community list? 16:16:41 some people filter them out if something in the mail doesn't match to the filter 16:16:42 Jack: yes and can explain concern expressed in this meeting then keep following up. 16:17:13 so putting person to to and cc:ing tech-discuss might help you to pass from filters 16:17:14 Jack: ping Tim directly too 16:17:44 trevor_intel1: yes, so i talked to him yesterday in this channel and he said he would look into it 16:17:46 what else for Intel PODs? 16:18:07 I haven't heard any good or bad feedback from Compass team regarding pod8 16:18:11 no news is good news? 16:18:15 May-meimei: ping? 16:18:48 jmorgan1: did you get any problem report for pod8? 16:19:06 fdegir: in this case I think we need an explicit statement of good or bad news :) 16:19:13 fdegir: no, but i checked jenkins for pod 8 and it shows it as connected / working 16:19:42 jmorgan1: you can take a look at this link to see if they really use it 16:19:44 jmorgan1: https://build.opnfv.org/ci/computer/intel-pod8/builds 16:19:55 jmorgan1: and they use as far as I can tell 16:20:49 fdegir: that doesn't look good? 16:21:03 trevor_intel1: depends where you're looking at it 16:21:15 trevor_intel1: if they are genuine development issues, it means they're catching problems 16:21:23 fdegir: hasn't built in at least 8 days? 16:21:24 trevor_intel1: if they are caused by POD, it is not good 16:21:56 trevor_intel1: I think an explicit mail regarding pod8 to compass team would clarify the status 16:22:36 Jack: can you do that too please? 16:23:05 trevor_intel1: sure, but will put it on your B release tab ;) 16:24:02 What about other labs? 16:24:16 Ericsson? 16:24:21 POD 2 16:24:41 all the other PODs are fully operational 16:24:50 Ericsson POD2 came back online last night 16:24:57 switch was replaced 16:25:12 Huawei SC POD 1? 16:25:45 looks good: blue balls here and there 16:25:47 https://build.opnfv.org/ci/computer/huawei-us-deploy-bare-1/builds 16:26:12 just to highlight the fact that pod8 will mostly be red since we reserved it for latest 16:26:31 fdegir: ok that makes sense 16:26:40 one more thing for Intel Lab, currently getting Storperf and Bottlenecks access to Intel POD 9 16:27:13 jmorgan1: please ping me if they want it to be connected to jenkins 16:27:24 fdegir: will do 16:27:40 Jack: anything with POD 7? 16:28:07 trevor_intel1: I've not heard from Jonus and emailed him again yesterday 16:28:10 please reserve it for another team 16:28:21 if Jonas comes after you, redirect him to me 16:28:27 I though we already decided that 16:28:38 to assign it 16:28:43 yep 16:28:44 re-assign 16:28:55 Intel POD 1 isn't being used by Apex, btw 16:29:08 Intel POD 7 reassigned 16:30:07 Jack: to who? 16:30:07 Im done 16:30:40 trevor_intel1: to next person who needs it, we have two empty PODs now POD 1 & 7 16:31:07 trevor_intel1: I can check with CPERF team, and ATT&T asked for POD access 16:31:44 Jack: what about LSO/LSOAP? 16:32:04 trevor_intel1: don't know, I've not gotten any request from them 16:32:27 Jack: I need to read emails 16:32:36 ok lets move on 16:32:51 #topic Pharos documentation 16:33:21 We made progress but some way to go still 16:34:32 I sent out a patch re. organizing the directorys ... Chris Price just gave -1 (his comments are good) 16:35:40 We will upload templates for lab topology and pod descriptions today 16:36:25 really good to hear 16:36:34 and sorry for not being able to help with them 16:36:34 Then its working to improve the docs and work into the new doc toolchain 16:36:54 fdegir: please watch for them so you can review 16:37:05 will do 16:37:12 Ryota knows that stuff inside out 16:37:20 so you can add him as reviewer as well 16:37:39 fdegir: I have him and Sofia as reviewers 16:38:01 then you're pretty well covered there 16:38:10 but I'll definitely take a look at 16:38:27 That is all I have to report on docs now ... planning to focus on that rest of this week (and next if needed) 16:38:40 Any other comment on documentation? 16:39:02 not from me 16:39:07 What other topics for today? 16:39:20 jira is there I think 16:39:20 I don't want to keep anybody from Rls B work 16:40:01 fdegir: agree but I don't think we will will get it cleaned until release B stuff is under control 16:40:32 trevor_intel1: I was talking about what jmorgan1 wanted to chat 16:40:40 trevor_intel1: if it is what you said then that's fine 16:41:01 i suggested some values for components and versions, but need them added 16:41:36 Jack: I think that is on me to do 16:41:40 then we should do a task scrub to assign task to a relase (version) and component 16:42:11 yup, jira scrub can be done whenever,just stating my thoughts/plans 16:42:35 Jack: agree 16:43:01 Jack: anything specific you would like to review now? 16:43:44 not particulalry, but was hoping to create a how to submit a jira task for Pharos lab support document once the fields are entered 16:43:44 narindergupta: anything else for today? 16:44:09 trevor_intel1 no thats was one of reason yardstick and func test ffailed 16:44:12 Jack: please bug me this week to do it 16:44:36 trevor_intel1 apart from that everything is working ok so far. 16:44:53 narindergupta: please work directly with Jack to resolve 16:45:10 trevor_intel1: yeah will work with him 16:45:24 narindergupta: call and talk if needs 16:45:37 trevor_intel1 sure 16:45:45 Any other topics or will close the meeting 16:46:02 thanks all 16:46:11 #endmeeting