16:00:07 #startmeeting OPNFV Pharos 16:00:07 Meeting started Wed Feb 3 16:00:07 2016 UTC. The chair is trevor_intel1. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:07 The meeting name has been set to 'opnfv_pharos' 16:00:17 #info Trevor Cooper 16:00:20 #info Jack Morgan 16:00:24 #info Fatih Degirmenci 16:00:32 * fdegir is commuting and will be slow typing 16:01:10 fdegir: driving?!!? 16:01:16 fdegir: what is the differene between now and any other day ;) 16:01:18 trevor_intel1: metro 16:01:40 fdegir: ok I feel a bit better 16:01:45 jmorgan1: there is no difference 16:01:51 fdegir: LOL 16:02:03 Topics? 16:02:18 1. POD status 16:02:34 2. Docs 16:02:44 3. Other release stuff? 16:02:59 Lets go over POD status ... 16:03:40 #info yesterday Debra reported out that there were issues with Intel PODs 2 and 8 16:04:25 We think there are no known issues 16:04:29 Jack? 16:04:46 Do you agree? 16:05:05 I mean POD 2 and 8 specifically 16:05:21 I think the issues with Intel POD 2 and 8 are resolved as I've not heard back from the POD users 16:05:49 Intel POD 2 (Apex) was solved by moving to intel POD 7 16:05:57 trevor_intel1: pod5 and pod6 bmc are not responding for few nodes 16:06:05 about pod8; they will be off next week 16:06:12 issue was Apex installer had problem with identifying network interfaces on different platforms 16:06:36 so if you don't get any info during next 2 days 16:06:37 #info There are currently no known issues with PODs 2 and 8 16:06:53 Intel POD 8 issue was the information in the Wiki was wrong, 1Gb MAC mixed with 10Gbe MACs 16:06:56 #info POD 2 was moved to POD 7 (Apex) 16:07:23 jmorgan1: so pod8 should be fine for compass then 16:07:47 fdegir: I'm assume so as I've not heard anything 16:08:01 ok 16:08:05 those systems in pod 8 have two type on 10Gbe nic (no 1gbe nic) 16:08:09 #info All issues need to be reported and tracked through Jira ... process is here ... https://wiki.opnfv.org/pharos_rls_b_support 16:08:39 i mixed up the two differnet 10Gbe mac, mix was just to switch them in the wiki 16:08:48 s/mix/fix 16:09:18 as narindergupta mentioned, he is having trouble with the bmc as of last Friday in intel pod5/6 16:09:31 im looking into it (PHAROS-101) in JIRA 16:11:33 make sense 16:12:05 Jack: what is time-line to resolve? Were you able to determine anything re. where the issue is yet? 16:12:39 I should be able to resolve them today 16:12:55 narindergupta: I don't think anything changed on our side 16:13:17 Jack: would it be worth doing a reboot? 16:13:18 trevor_intel1: could be hardware failure 16:14:09 trevor_intel1: may be hard power reset might solve. Looks like its keep the session active and ipmitool can not connect to it 16:15:29 trevor_intel1: already did a reboot 16:15:32 trevor_intel1: reboot won't work as it bmc. 16:15:49 ok 16:15:59 trevor_intel1: it may be hard power reset where pull out power and pull back in 16:16:01 Jack: I have reassigned the issue to you in Jira 16:16:14 trevor_intel1: i need to connect via the vpn profiles for intel pod 5/6, then i can troubleshoot 16:17:44 Jack: what of status of Jira 97 (POD 9 jump host)? 16:18:58 trevor_intel1: you mean PHAROS-97? it needs to be done 16:19:56 trevor_intel1: this issue is really pod user learning to use the pod 16:20:02 Jack: and 97 16:20:21 undo 16:20:25 #undo 16:20:25 Removing item from minutes: 16:20:39 Jack: 95? 16:20:51 trevor_intel1: the best thing to do is look at the comments in a JIRA task, that will give you the status 16:21:15 trevor_intel1: it needs to be done 16:21:41 Jack: There are no comments yet on this issue 16:21:56 trevor_intel1: right, so there is no status 16:22:10 Jack: that is why I am asking :) 16:23:16 Jack: The version says for rls B ... and we are in the release cycle ... so are they blocking issues and if so what is estimate to resolve? 16:23:24 trevor_intel1: all the open JIRA tasks need to be done, I have 12 of them 16:24:12 Jack: other than POD 5 and 6 ... are there blocking issues? 16:24:36 trevor_intel1: how do I know if its a blocking issue or not? 16:25:11 Jack: Needs to be clarified with the reporter 16:27:40 Are there any other POD issues to discuss now? 16:29:24 #Topic Pharos documents 16:30:02 #info Pharos docs have been organized and created for new doc toolchain 16:30:16 #info All docs build without error form what I can tell 16:30:32 #info Fixed Dell document issues 16:31:22 #info However there is a lot of improvements we can make to the documents 16:31:55 #Info Any volunteers who want to help improved the docs? 16:33:21 We need more lab reps in these meetings :( 16:36:01 fdegir: still there? Anything you need / would like to discuss now? 16:36:08 trevor_intel1: is there any way to enforce it? 16:36:11 Jack: Anything more? 16:36:28 narindergupta: Anything other than POD 5/6 issues? 16:36:42 trevor_intel1: ok 16:36:47 trevor_intel1: no 16:37:26 not from me except how to make sure we have more people workng with pharos 16:38:14 fdegir: this is the old problem 16:38:21 yes 16:38:49 maybemore drastic chamge needed 16:39:00 fdegir: ideas? 16:39:02 tsc/board enforcement 16:39:24 1 rep from each lab 16:39:24 fdegir: how do you see it working? 16:39:28 ok 16:39:47 we have this laas/maas/ reservation 16:39:53 pharos spec etc 16:40:07 which obviously require involvement 16:40:28 if certainlab doesn't provide representation 16:40:32 they're out 16:40:52 from ci or any future pharos stuff 16:41:13 you can't just put a pod and forget the rest 16:41:45 if resources come 16:41:53 they come with a person 16:42:11 agree but up to now at least the TSC and marketing wanted to build a certain perception (regardless of the reality) 16:42:39 that's the ammunition and problem at the same time 16:43:04 Which was maybe the right thing to get going ... but now it has to change if we are to be sustainable 16:43:21 100% agree 16:43:35 So lets make a proposal to the TSC? 16:43:45 fdegir: this should include maintaining pod status on the release resource page, specifically if a blocking issue comes up 16:43:50 we passed the point to do marketing and forget the reality 16:44:10 for c-release, this should be top item 16:44:26 fdegir: so some strictly enforced rules? 16:44:30 match the names to labs and expect commitment 16:44:52 I don't see other way unfortubately 16:45:16 positive thinking didn't work 16:45:22 :) 16:46:12 that's all I have 16:46:20 I think we need to come at it by being clear on a set of requirements (very specific) ... and then show the gap 16:46:31 yes 16:46:36 all this wiki mess 16:46:46 booking time for activities 16:46:50 mails 16:46:52 etc 16:46:55 must end 16:47:16 like what you started doing with intel lab issue handling 16:47:40 it is similar with other pharos activities 16:48:53 fdegir: Can you send me some bullet points of what requirements are from releng perspective (not solutions just the requirements)? 16:49:06 will do 16:49:13 fdegir: great, thanks 16:50:10 I am done for today, need to get back to docs and other urgent stuff 16:50:17 ok 16:50:20 thx 16:50:20 bye 16:50:35 happy commuting 16:50:44 #endmeeting