15:00:42 #startmeeting OPNFV Pharos 15:00:42 Meeting started Wed Oct 14 15:00:42 2015 UTC. The chair is trevor_intel. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:42 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:42 The meeting name has been set to 'opnfv_pharos' 15:00:56 #info Fatih Degirmenci 15:01:20 #info INTEL LAB Trevor Cooper 15:01:35 thansk for attending Fatih!! 15:01:39 thanks 15:01:41 #info Intel Lab Michael Wynne 15:01:42 np 15:02:43 #info Agenda proposed: 1) MAAS 2) Templates 3) Lab resource allocation 4) Requirements of Pharos lab 15:02:53 Comments on agenda? 15:03:22 looks good 15:03:23 We can wait a minute for others to arrive 15:04:11 Please record your attendance and if you are a lab owners which lab ... e.g. #info INTEL LAB Trevor Cooper 15:04:47 #topic MAAS PoC 15:05:01 #info DELL LAB Nauman Ahad (representing Wenjing and VIkram today) 15:05:02 narindergupta: can you give status? 15:05:35 nahad: welcome 15:05:49 trevor_intel: iben has to work on clearing the definition. 15:05:49 #info HUAWEI LAB Weidong Shao 15:06:04 #info Spirent - Iben Rodriguez 15:06:15 #undo 15:06:23 trevor_intel: and POC we have have integreted two labs with regional controller and ready to demo next week 15:06:39 #info Spirent VCT Lab - Iben Rodriguez - https://wiki.opnfv.org/pharos/spirentvctlab 15:06:51 #info iben will work on clearing the MAAS POC definition 15:07:22 narindergupta: is the progress reflected on Jira? 15:07:27 #info 2 labs have been integrated to MAAS POC with regional controller and ready to demo next week 15:07:53 #info narindergupta: and iben have not been able to communicate too much on status updates or update JIRA - but we have made updates to planning and getting started guide on wiki - link to follow 15:07:55 narindergupta: how long do you need for teh demo? 15:07:56 trevor_intel: unfortunately i am on travel this week so did not got time to update JIRA. I will be back on Friday then update. 15:08:14 30 minutes should be ok for full deployment 15:08:23 #link https://wiki.opnfv.org/pharos/maas_getting_started_guide 15:08:28 narindergupta: deployment of? 15:08:46 fdegir: deployment of jump host through regional controller 15:08:50 we can show using maas-rc to conenct to maas-cc in remote lab and deploy opnfv 15:08:52 narindergupta: ok I have added to the agenda of Test & Performance meeting 15:09:01 trevor_intel: thanks 15:09:05 ok 15:09:17 deployment of jumphost and deployment of opnfv 15:09:25 right 15:09:48 which one is the focus? 15:10:01 sorry for going back to my repeating question 15:10:08 fdegir: deployment of jump host with opnfv release 15:10:23 narindergupta: means Arno? 15:10:31 correct 15:10:36 but... 15:11:00 you already know my view on this 15:11:08 narindergupta: you will use INtel POD and Spirent POD for the demo? 15:11:25 we have two intel pods pod5 and pod6 15:11:40 spirent lab has regional controller 15:11:57 fdegir: means? 15:12:06 if we're going to demo this and if people ask "what is the benefit of having MAAS?" 15:12:22 is the answer "you can deploy OPNFV." 15:12:48 fdegir: IMO that is not a good answer 15:12:56 and I'll be one of the users who won't see the benefit of this 15:13:12 fdegir: no we will discuss other benefit like single view of all the labs and deploy from single tool 15:13:28 narindergupta: I like to hear that 15:13:40 will you have demo for that use case as well? 15:13:41 fdegir: also users can choose the lab and assign it and get it work on it 15:13:49 fdegir: yes 15:14:00 narindergupta: now I'm ambitious 15:14:07 looking forward to the demo 15:14:42 fdegir: cool thats the whole idea to integrete the labs who wants to take participate in CI of OPNFV tests can be integreted. 15:14:48 yes 15:14:48 narindergupta: I request that Jira is fully updated before the demo ... I will send out a link to jira epics so that people can look ahead and understand before seeing the demo 15:15:12 trevor_intel: sure i will work on this by this weekend and finish it. 15:15:19 my dream is to use MAAS API so CI can book the resources if the resources are shared between CI and development work 15:15:24 narindergupta: thansk! 15:15:49 and noone else can book it while it's in use by CI or developers 15:16:22 More on MAAS today? 15:16:27 fdegir: yes user can book the resource if they see it free 15:16:39 no we are good 15:16:40 I'm pretty happy with what I heard 15:17:13 #topic Templates 15:17:39 Any updated from Cyril or other Orange guys? 15:17:57 haven't seen/heard anything yet 15:18:42 Its been a while 15:19:05 I will ping them off-line and talk to Morgan if no response 15:19:18 ok 15:19:59 #topic Allocation of lab resource 15:20:15 fdegir: Can you give status update on teh lab survey 15:20:31 #info A questionnaire was sent last week to 10 lab responsibles 15:20:48 #info Out of 10 labs, 6 of them answered 15:21:01 #info Labs that hasn't answered as of yet are 15:21:21 #info Cable Labs, Dell, Huawei, Orange 15:21:49 #info Will send out the link to responses tomorrow to Pharos people 15:22:08 Huawei will get the info by Thursday China time 15:22:09 nahad: wshao: ping 15:22:15 We are working on drafting our answers for the survey and will send them by today 15:22:17 thanks wshao 15:22:18 fdegir: great, I will ping the owners of those labs today 15:22:37 thanks trevor_intel 15:22:46 nahad: for which lab? 15:22:48 Dell? 15:22:49 Dell 15:22:51 yes 15:22:57 I can perhaps type the next steps so everyone knows what are we trying to do 15:22:59 nahad: thanks 15:23:09 fdegir: please do 15:23:10 #infi Steps are 15:23:18 #info Steps are 15:23:38 #info Get lab availability from lab reps - waiting for survey results 15:24:02 #info Get project hw/sw requirements from community - Debra sent out the mail to collect the info 15:24:12 #info Get LF POD1 servers 15:24:25 #info Match resources to requirements to do the allocation 15:24:43 #info Report/document the outcome and act on it 15:25:10 my hope is that the survey will help us to identify high level capability of the labs 15:25:17 So far only Storperf has filled out the project survey 15:25:25 some labs will not make into the CI and freed for dev purposes 15:26:04 we also have requirements for kvm in a seperate mail 15:26:23 will talk to Jiang so he puts reqs to wiki 15:26:34 We have an action re. LF lab ... Usage of LF lab ( defined and documented) 15:26:57 fdegir: Is it clear yet how LF labs will be used? 15:27:16 I mean PODs 15:27:21 trevor_intel: I'm not happy with the current situation of LF labs 15:27:38 they're opened for broad acces 15:27:45 and some development work is done on them 15:27:58 on top of CI 15:28:06 to me, it should be hands off lab 15:28:15 fdegir: But until the usage is defined and documented we cannot control it! 15:28:16 and only CI and troubleshooting should be allowed 15:28:18 sorry, where is LF Lab physically hosted? 15:28:29 wshao: portland 15:28:40 trevor_intel: agree to that 15:28:54 I can come up with very high list of activities 15:29:04 and review it together and ask TSC to approve it 15:29:16 and then clean up the access to the LF infra 15:30:08 trevor_intel: how does this sound? 15:30:21 fdegir: very good ... lets start to put on Wiki ... I will make a page and send you the link after this ... to start the list. Then its available for others to give feedback 15:30:35 fdegir: Sounds very good, thanks 15:30:42 ok 15:30:51 asking aricg to provide the list of people 15:30:59 so we can check what they are doing there 15:31:21 fdegir: we can put that on the Wiki too 15:31:53 will do that once you create the page and once aricg comes up with the list 15:32:07 fdegir: ok 15:32:25 Anythign else on lab resource planning for now? 15:32:48 that's all from me 15:33:09 #topic Requirements of Pharos labs 15:33:31 #info Requirements of Pharos labs ... https://wiki.opnfv.org/pharos_rls_b_spec 15:34:32 I sent an email about the topic of a lab "ready label" ... this was somethign raised by OPNFV board 15:35:04 thanks for that mail 15:35:07 There were a few responses but we need more input 15:35:11 I have a question 15:35:20 we say dev resources/labs 15:35:59 I don't think it is not realistic and good to have all the labs providing resources for all the projects 15:36:14 so the labs can be purposes for different dev activities 15:36:20 purposed 15:36:30 if this is the case 15:36:39 fdegir: correct 15:36:41 can we still label the labs as "ready"? 15:36:56 it doesn't serve for everything 15:37:16 fdegir: that is why I am stuggling with the "ready label" 15:37:17 But it serves some projects 15:38:06 I think/hope the Debra's form on wiki and your mail will give some answers 15:38:17 If I make a virtual deployment usign one server available to the internet ... does that mean I am an OPNFV "lab"??? 15:38:35 and then we can perhaps define minimum for getting "ready" label 15:38:57 trevor_intel: that's my question :) 15:39:03 what's the minimum? 15:39:19 fdegir: indeed! 15:39:44 the guidelines, contacts, etc are in the list by default 15:39:54 but what they offer is the tricky part 15:40:59 trevor_intel: should we postpone this discussion to next week? 15:40:59 I updated the spec page to try and make at least the terminology clear between 1) Community lab 2) Dev lab 3) CI lab 15:41:15 once more answers come to your mail 15:41:28 Please look and see if you agree (update/edit/comment) 15:41:34 will do 15:41:37 fdegir: yes I agree 15:42:04 Only thing is the officers are impatient :) 15:42:12 officers? 15:42:42 OPNFV officials :) 15:42:50 I can understand 15:42:55 just before pharos meeting 15:43:06 Chris, Prodip, and Eric were on the stage 15:43:18 talking about pharos to hundred people 15:43:20 :) 15:43:46 :) 15:43:54 we're moving, we're not fast but moving some way 15:43:54 High expectations 15:44:10 yes 15:45:18 may I ask a couple of questions? (about pharos in general, so I can wait) 15:45:33 Ok I will try to answer the quesions as best I can ... can we aim to give a recommendation (from Pharos community) as to defintion of "ready" next week? 15:45:33 meaning I don't want to interrupt the current discussion 15:45:51 joekidder: lets just wrap this first 15:45:56 yep 15:46:04 trevor_intel: we can try 15:46:32 on the wiki perhaps 15:46:44 and see where we end up 15:47:33 #action All Pharos community reps to think about defintion of "lab ready" (see email sent by trevor yesterday on this topic) ... respod with comments and/or attend next weeks meeting to close on this. 15:48:11 Is "#action" correct? 15:48:16 yes 15:49:26 fdegir: You mean start to consolidate/capture feedback on Wiki? 15:49:37 trevor_intel: I can do that 15:49:58 So that next meetin we have something to work on 15:49:59 trevor_intel: yep 15:50:22 we can then associate reqs to lab classes 15:50:35 on that page you already created 15:50:52 https://wiki.opnfv.org/pharos_rls_b_spec 15:50:54 #action Trevor to create Wiki page on "ready label" and consolidate input on this question 15:50:56 as a draft 15:51:06 and then move to its final location 15:51:24 Yes I see that page as the portal for Pharos spec stuff 15:51:26 since we will have some references to community, dev, ci labs in the ready label stuff 15:51:37 we can cross reference 15:51:57 ok 15:52:18 Any further comments / questions on "lab ready" (for today)? 15:52:23 nope 15:52:35 joekidder: fire away 15:53:24 thanks. First question: do all the 5 servers in a pod have to be the same configuration? mainly compute and controller might be different 15:54:44 joekidder: also there is a "jumphost" that can be different 15:55:34 yes, we expect that could be different. 15:55:35 joekidder: I prefer them to be the same, but there is no strict requirement that the HW be identical. 15:55:36 trevor_intel: I don't think the Pharos spec says all servers need to be the same 15:56:03 ok. that's the first. thanks. 15:57:23 I was a bit confued over some of the questions in the survey. Should i ask them now or discuss later on the email thread? 15:57:36 considering the time for the meeting is about to end 15:57:50 The second question is what if I'm loading ubuntu on all servers... 15:57:55 nahad: try now maybe we can answer 15:58:10 Oh sorry. Joekidder sorry to interrupt 15:58:15 ...but the servers might have different kernels/drivers because they're different SoCs (if mixed arm servers) 15:58:20 nahad: its ok keep going 15:58:29 The question related to CI: 15:58:38 or it might be ARM and x86 (e.g. arm compute and x86 control) 15:58:52 Baremetal servers available 24/7 vs POD available 24/7 for CI 15:58:57 joekidder: wouldn't it make harder to troubleshoot stuff 15:58:58 I was a bit confused over this. 15:59:11 By POD we mean the POD is deployed and is just integrated to CI? 15:59:21 if we can get past the potential problems having different kernels/drivers 15:59:36 and with Baremetals available for CI, we have the jumpserver provisioned and connected to CI, not the other servers? 15:59:42 joekidder: that would be a good thing ... shows diversity, right? 16:00:00 nahad: POD=5+jumphost 16:00:11 nahad: jumphost connected to CI 16:00:22 where we initiate the deployment/testing from 16:00:40 all the 6 servers up &running 24/7 16:00:46 fdegir: assuming that each node is fine/stable with its kernel/drivers. More a question of whether this would confuse the heck out of the installer or whether the linux repo, if mixed, could support it. 16:00:47 but in both cases, isn't the jumphost connected to CI? 16:00:48 and noone else but CI can use them 16:01:02 for standalone servers 16:01:08 ok 16:01:14 I wouldn't call jumphost 16:01:31 nahad: That is for CI resources 16:01:33 it's general purpose server for CI builds/test etc 16:01:53 joekidder: that was what I was trying to ask 16:02:05 if installers have trouble due to this 16:02:46 nahad: which question was it? 16:02:50 fdegir: Do you agree that for Dev resources there is not the same requirement to connect to LF? BUT we do need connectivity requirement (is it defined yet?) 16:02:54 fdegir - I'm hoping that it might not be a problem. My original thought was that for each type of server, we might have the installer point to a different repo 16:03:14 fdegir: Q8 16:03:16 q8? 16:03:18 yes 16:03:18 yep 16:03:31 POD is the pharos POD spec 16:03:40 ok 16:03:44 5+1 16:03:54 the other one is as I said, general purpose servers 16:04:06 but only CI is allowed to use 16:04:08 So right now we have a jump server connected to CI. That jump server deployed foreman on 5 servers 16:04:15 oh ok 16:04:28 so by the POD we mean, only CI is allowed to use the rest of the 5 servers 16:04:31 fdegir: but I looked a little at some repos and they might have an arrangement that would support multiple architectures. Potentially. 16:04:45 nahad: yes in q8 context 16:05:06 ok. Thanks 16:05:09 np 16:05:33 joekidder: I think you asked this question on mailing list as well 16:05:34 and the first answer CI for baremetal servers 24/7 16:06:07 fdegir: yes, same question. I figured I'd ask it here...not sure it would get answered in email:) 16:06:07 and as you pointed there, genesis could be the forum where you could get satisfying answer 16:06:31 fdegir: good point/advice. I'll follow up with them! 16:06:37 for pharos, as trevor_says, it provides diversity 16:06:44 but if we can make it work 16:06:48 fdegir: but pharos doesn't care. Which is excellent. 16:07:12 I don't remember if pharos spec has this much details 16:07:16 would this be something to do with MAAS? That CI could provision servers to install OPNFV? I mean i was a bit confused that if we later use MAAS, it would deploy jumphost. But Jumphost should be connected to CI 16:07:38 trevor_intel is the one who can clarify this if and how much pharos cares 16:08:33 nahad: that's the same question I've been trying to get the answer from MAAS POC 16:08:49 I propose not to mix MAAS into this as of yet 16:08:58 until we see the demo and the outcome of the POC 16:08:59 oh ok. Thanks fdegir 16:09:12 the question is: can you dedicate CI resources 16:09:26 if so, what type; full POD or just 1 or 2 servers 16:09:43 Oh thanks. That really makes it clear :) 16:09:57 MAAS could be useful if we have resource outage and need to share the resources between ci and dev 16:10:15 so we can offload ci work to shared resources when the demand peaks using maas as booking system 16:10:36 ok 16:11:53 I suppose we're done for the day 16:12:08 joekidder: : I think we care to the extent that 1) follows the baseline Pharos spec AND 2) it "works". There are many implementation details are up to the lab owners 16:13:07 trevor_intel: thanks! 16:13:21 bye, all. 16:13:28 fdegir: yes 16:13:32 thansk all! 16:13:37 Thank you everyone. Bye! 16:13:41 #endmeeting