16:00:08 #startmeeting OPNFV Pharos 16:00:08 Meeting started Wed Nov 18 16:00:08 2015 UTC. The chair is trevor_intel. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:08 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:08 The meeting name has been set to 'opnfv_pharos' 16:00:27 #info Trevor Cooper (Intel lab) 16:00:28 #info Fatih Degirmenci 16:00:50 #info Daniel Smith 16:00:53 #info Narinder Gupta 16:02:22 Can we start with allocation of resources and then do status updates after? 16:03:50 #topic Lab resources 16:04:19 First lets update on LF and then move to project needs 16:04:47 fdegir: Sounds like the 4 extra servers are being used now? 16:05:01 trevor_intel: not yet unfortunately 16:05:19 I need to update teh Wiki to reflect usage of LF resources 16:05:27 aricg, pbandzi and me sat down last week during the summit to configure the resources 16:05:37 fdegir: but do we know how they will be used? 16:05:50 trevor_intel: yes 16:05:53 infoing in 16:06:04 #info rebuild LF POD1 to use for bare metal deployments 16:06:20 #info LF POD2 will continue to be used for bare metal deployments 16:06:31 #info 2 of the 4 new blades will be used for nested deployments 16:06:38 #info remaining 2 will be used as build resources 16:07:03 #info the delay is due to a potential disk issue with one of the blades - investigation is ongoing 16:07:23 Ok so we get one full-metal POD back 16:07:29 that's correct 16:07:48 Are tehy dedicated to 2 of teh installers ... Fuel and Apex? 16:08:14 yes, at the moment 16:08:20 but this hopefully will change coming weeks 16:08:34 as long as we can put cleanup/reconfig scripts in place 16:08:43 yes ok 16:08:49 we only have pbandzi who can do ucs stuff 16:09:06 so that's kind of a problem - when he is off or busy, we get stuck 16:09:11 I will update the Wiki to reflect this 16:09:21 ok 16:09:23 LF lab support is still an issue 16:09:32 yes 16:09:39 aric was interested in learning ucs stuff 16:09:46 but I don't know if he works for beer 16:09:50 We had talked about training some extra prople and seems that is urgent 16:09:54 :) 16:10:02 I want to learn as well 16:10:07 and had a quick crash session 16:10:09 I am gonig to raise it to TSC and get some action on this 16:10:21 pbandzi has ucs simulator which we asked him to make it publicly available 16:10:25 so this can help 16:10:39 Ahh interesting ... ok my AR 16:10:53 #info A UCS simulator is available and needs to be made available by pbandzi 16:11:05 #action Trevor to escalate issue of LF support and get training 16:11:09 #action fdegir to talk to pbandzi regarding making UCS simulator publicly available 16:11:39 We also need to update Wiki re. CI resources 16:11:46 https://wiki.opnfv.org/pharos/hw_resource_allocation 16:11:58 yes 16:12:10 I kind of started working on intel machines 16:12:15 and ericsson ones 16:12:27 will move on to LF ones once they're ready 16:12:32 and then the community ones 16:12:39 and will try to keep the page up to date 16:13:29 What about the Huawei CI production POD? 16:13:37 that's the thing 16:13:42 it looks like it's in production 16:13:53 so we should talk to people so they update the page 16:13:58 or 16:14:08 I'm not sure if you like the idea of moving that page to gerrit 16:14:13 so people update it in gerrit 16:14:25 and it gets reviewed by looking at actual status on jenkins 16:14:43 rather than anyone updating the page - even though we have history there 16:14:46 Interesting idea 16:15:05 ok, I'll move the page to gerrit into pharos repo 16:15:07 The Wiki page is very visible ... 16:15:11 and send it to you for review 16:15:17 hang on ... 16:15:18 we can scrape the page to wiki automatically 16:15:29 so it can be visible on the wiki as well 16:15:32 I think we should get the Wiki cleaned up and in shape and accurate first 16:15:37 or 16:15:52 we should capture the initial status first 16:15:57 your call 16:16:22 Lets capture the initial status first ... then move to gerrit ( I think its a great idea) 16:16:31 this is the initial status 16:16:34 whatever is there 16:16:49 and we update and reflect the current status 16:17:05 There is https://wiki.opnfv.org/pharos/hw_resource_allocation for LF 16:17:22 yes 16:17:29 https://wiki.opnfv.org/pharos_rls_b_labs for community labs 16:17:56 the 2nd link is mixed with CI and dev resources 16:18:08 Well its a differnt view 16:18:19 Its how community labs are used 16:18:31 right 16:18:38 and some are bing used for CI 16:18:53 Can we move to project resources? 16:19:11 yes 16:19:23 #topic Project resouce allocation 16:19:42 There are some projects that need lab resources ... I will list them ... 16:20:16 IPv6 needs a full POD wtih IPv6 support 16:20:36 OVSNFV need a full POD with traffic generator 16:21:06 kvm4nfv needs x2 dedcicated machines (no installers) and a traffic genrator 16:21:35 Bottleneck needs some dev and proj CI but not clear yet on details 16:22:00 STORPERF same as Bottleneck 16:22:26 That is all I am aware of as far as current gaps 16:23:08 2 POD + 2 servers 16:23:16 the ones that are obvious 16:23:21 Pretty much yes 16:23:35 Should I allocate from Intel lab? 16:23:57 do you know if these 2 PODs + 2 servers are for dev or for CI? 16:23:58 The other issue is with traffic genrators 16:24:16 cause for example for kvm 16:24:21 they need to run some tests through CI 16:24:33 I'm not sure if they already have dev resources 16:24:39 Tehy don't 16:24:50 then it might be 4 servers for kvm 16:25:20 or 1 + 1 16:25:31 but they say they only need standalone with no installer ... so why do they need CI? 16:25:40 they patch the kernel 16:25:51 and we build it in CI when their patch comes to gerrit 16:25:59 and then that kernel needs to be applied to a machine 16:26:17 and the machine booted and cyclictest(?) and perhaps some other tests need to be run 16:26:32 so they need build and it should be contolled by jenkins central 16:26:38 yes 16:26:46 they need build + test via jenkins 16:26:52 apart from their dev work 16:27:06 but the machines they run tests on can be the same as dev I think 16:27:15 nope 16:27:30 because machine goes down when the kernel is applied 16:27:36 so if they do this during dev work 16:27:42 it makes is useless for CI 16:27:44 and vice versa 16:27:51 so it must be dedicated 16:28:00 and it can't even be shared with other CI or dev purposes 16:28:14 because you never know when they send a patch to gerrit or do the development locally 16:28:30 let me find the etherpad 16:28:42 Ok so I need to clarify this with them ... will do that. If we gave them a full POD in Intel it should be enough? 16:28:54 https://etherpad.opnfv.org/p/nfv-kvm-test 16:29:10 there are 5 servers in a POD? 16:29:22 yes 16:29:24 ok 16:29:30 CI can take 2 of them 16:29:34 and the rest can be for dev 16:29:42 Ether pad is really good! 16:30:14 this is the crucial sentence: The built-out kernel can be booted on both host and guest. 16:30:16 So it may be the same with OVSNFV? 16:30:22 probably 16:30:32 so if they mess up the kernel 16:30:43 the machine might not be possible to boot unless fixed manually 16:30:57 kvmfornfv is really good project btw 16:31:22 just to add another update for kvm 16:31:47 i submitted a patch to enable builds for kvm: https://gerrit.opnfv.org/gerrit/#/c/3369/ 16:31:52 So I could allocate one POD each in Intel lab 16:31:56 and once this gets merged, we will move on to tests 16:32:09 so it would be good if you can allocate pods whenever you have time 16:33:00 ovsnfv is a bit behind comparing kvmfornfv 16:33:04 I need to bug them again 16:33:07 FYI Dan Smith did update the Wiki re Ericsson dev resources https://wiki.opnfv.org/pharos_rls_b_labs 16:33:10 from CI point of view 16:33:32 yep, saw that 16:33:56 pod2 will be configured coming days or so 16:34:05 and might be available 2 weeks perhaps 16:34:20 pod1 is online 16:34:24 We had said to allocate POD 7 to Fuel and 8 to Compass 16:34:29 and used by yardstick 16:34:47 You are talkign Ericsson PODs? 16:34:50 right, POD7 16:35:03 yes - we might bring up an additional pod 16:35:05 but 16:35:17 please do not change your pod7 allocation as of yet 16:35:38 if I get hold onto an ericsson pod for fuel, I can come back to you and we release pod7 16:35:39 Can I cahnge POD 8 and 9? 16:36:04 to give to teh two projects 16:36:14 what will happen to compass? 16:36:37 Its supportedin Huawei lab 16:36:54 ok 16:37:18 I think in Intel lab when we said Compass it means a test environment 16:37:28 I will check with Huawei to make sure 16:38:08 Ok so I don't know about IPv6 and also need more clarification from Bottleneck and STORPERF 16:38:33 Do you have any opnions on allocation for these projects? 16:39:00 unfortunately not 16:39:16 ok np I will dig 16:39:41 #topic MAAS 16:39:52 narindergupta: hi 16:40:29 trevor_intel, hi 16:40:53 trevor_intel, yeah i was looking into JIRA issues but i do not permisson to mark it resolved 16:41:16 Do you mean MAAS PoC? 16:41:26 trevor_intel, yes 16:41:58 I see Fatih added "Pilot" to the Epic ... but perhaps we should start a new one? 16:42:00 trevor_intel, also looking for next action item decided in OPNFV summit. what needs to done next? 16:42:29 narindergupta: Kick off the pilot and plan it 16:42:33 I was supposed to create 3 stories 16:42:39 trevor_intel, i think yes we should start a new one would be better and close the existing one. 16:42:41 that's why changed the epic 16:43:13 ok 16:43:21 fdegir: but the pilot is a new Epic? 16:43:31 yep 16:43:39 changed back the poc epic 16:43:53 and we need a new epic for pilot as you say 16:43:59 +1 16:44:03 and 3 stories 16:44:15 ok who will create teh new epic and 3 stories? 16:44:22 can do that 16:44:27 and you fix it afterwards 16:44:33 fdegir: go for it :) 16:44:41 sounds good 16:44:41 writing here to record it in the minutes 16:44:49 #info Epics: MAAS Pilot 16:45:05 #info Story 1: Use MAAS for lab booking and status visualization 16:45:31 #info Story 2: Use MAAS and MAAS APIS for configuring jumphost automatically from Jenkins 16:45:56 #info Story 3: Use MAAS for deployment of OPNFV 16:46:07 We need to get into using Jira and keeping it updated (this is a requirement by our release manager) 16:46:18 need to add detailed info to stories and DOD/acceptance criteria 16:46:20 I need to lead by example! 16:46:30 +1 to that :) 16:47:05 So I will do my best to get that habit going 16:47:43 There will be a demo of "rebar" tomorrow in the T&P meeting 16:47:50 rebar? 16:48:26 This is like an orchestrator / workflow engine for lab infrastructure if I understand it 16:48:43 Chris Price introduced me to the company last week 16:48:54 can you record it? 16:48:55 "RackN" 16:49:00 I have 3 meetings at the same time 16:49:01 I will 16:49:05 Only 3? 16:49:07 and need to skip t&p unfortunately 16:49:20 + 2 not accepted :) 16:49:23 You can get one extra monitor? 16:49:43 and 2 extra pair of ears 16:50:29 narindergupta: So you are the man for the pilot 16:51:22 fdegir: true 16:51:32 trevor_intel, sounds good lets do it 16:51:47 #topic Templates 16:51:50 narindergupta: I have a question 16:51:55 fdegir, sure 16:52:04 cyril_auboin_ora: hi 16:52:13 narindergupta: quick one: about story 2, configuring jumphost 16:52:18 that's I know 16:52:26 like install specified OS + packages 16:52:33 what about switch etc configuration 16:52:36 can maas do that? 16:52:42 cyril_auboin_ora: do you have any update today on the templates? 16:53:25 fdegir, no maas can not do switch confoiguration 16:53:46 narindergupta: ok 16:54:03 fdegir, but if you have scripts which can do that then we can always run during commisoning time 16:54:26 fdegir, in maas you can upload the scripts and that will be sxecuted while discovering the device. 16:54:31 narindergupta: right 16:54:36 this is actually a requirement on labs 16:54:45 to provide automatic reconfiguration scripts for their lab 16:54:54 who know when we can have them 16:55:09 fdegir, :) 16:55:31 I have a hard stop in a few min and will drop off 16:55:39 but anyway, narindergupta if we can start this pilot asap 16:55:42 like right now :) 16:55:45 it would be good 16:56:03 ok trevor_intel 16:56:11 fdegir, lets define it and i will talk to Artur and we can start 16:56:20 ok narindergupta 16:56:29 btw trevor_intel, it was good seeing you last week in sf 16:56:47 and was good that you brough all lab reps together 16:57:41 fdegir: yes it was good to spend some time just to focus on this. I wish we sould do F2F more often. 16:58:06 Now to get back to chasing lab reps remotely :) 16:58:13 bye all 16:58:16 bye 16:58:21 #endmeeting