14:34:41 #startmeeting Fuel@OPNFV 14:34:41 Meeting started Tue Aug 23 14:34:41 2016 UTC. The chair is Greg_E_. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:34:41 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:34:41 The meeting name has been set to 'fuel_opnfv' 14:34:50 #info Dan Smith 14:35:02 #info Greg Elkinbard 14:35:48 #info Michal Skalski 14:36:01 Hey Greg (et al)... i have to run in a couple minutes.. so ill throw my stuff out there :) 14:36:06 #info stable/colorado branch has been created, please check into master and cherry pick the bug fixes into colorado branch 14:36:37 Dan: go ahead 14:36:57 DanSmithEricsson: Do you have time to try to connect the pod again? I think its just a trailing slash when you set jenkins home? 14:37:05 #info Niko 14:37:08 #info a new BM POD has been setup - there is an issue with connecting it to the JENKINS slave (ticket created/ ARIC looking at it).. some work is needed in the team to coordinate the CI usage, since we have gone abck and forth with LF POD and our own - and ar eusing them for Tshooting, not CI- so we are impacting the pipeline 14:37:22 eg: -j /home/jenkins 14:37:26 (aric - i tried with -j... just send me the example command you want 14:37:31 ok.. ill try that agagin 14:37:50 #info - to finish - there seems to be some work needed, so I would suggest that one of the PODs will sassigned to let the CI/CD run 14:38:03 and the others assigned for t-shooting - the CISCO DPDK issue needs to be sorted. 14:38:07 (im done- thatnks! ) 14:38:37 aric- as in the command in the ticket - there is no trailing slash 14:38:40 sudo /home/jenkins/opnfv/repos/releng/utils/jenkins-jnlp-connect.sh -j /home/jenkins -u jenkins -n ericsson-pod1 -s java -jar slave.jar -jnlpUrl https://build.opnfv.org/ci/computer/ericsson-pod1/slave-agent.jnlp -secret 3cae104e99af3957a38d1fc452c862ec50112595501bc948b3676ceb57ebd311 -j 14:38:47 ooop.. sorry 14:39:31 #info Adding new PODs to CI shall be brought up to Infra WG meeting 14:40:17 hmm. DanSmithEricsson some of your command got lost? 14:40:23 ./jenkins-jnlp-connect.sh -j /home/jenkins -u jenkins -n ericsson-pod1 -s fooo -t 14:40:34 see your own private window 14:40:47 #info - thanks Fatih - ok.. ill turn off the new POD then 14:41:02 and someone can bring it up in INFRA WG with the process for how this is done 14:41:05 DanSmithEricsson: ah just use the string after the -s 14:41:15 not all that other stuff 14:41:21 feel free to do that 14:41:23 (i asked about this and the document doesnt say about INFRA WG - just says the steps _ so some work on process is needed there) 14:41:25 we seem to be running scenarios for master not colorado branch 14:41:43 that document just explains the slave connection 14:41:52 what do we need to enable CI runs for Colorado branch? 14:41:54 it doesn't say the connected slaves will be used for CI purposes 14:42:01 fatih - understood.. howver there is a process that we need to point people to 14:42:10 there is a process 14:42:11 wip 14:42:17 so.. im not sure what the point is.. if there is a process then we can point peole to it 14:42:25 if there is discussion to usse the POD then that can be done 14:42:35 if you look at the link: https://wiki.opnfv.org/display/INF/Continuous+Integration#ContinuousIntegration-HardwareResources 14:42:36 i just built it - if there is things teams need to use it then lets run through that process 14:42:50 it's been there since june 20 14:42:54 and no comment has been provided 14:42:59 so it's not been settled 14:43:15 ok.. yup - that doesnt really have a process for onboarding.. so im not sure how i coudl know that this has to be done to INFRA 14:43:22 for my part - i have provided the resource to the FUEL group 14:43:23 How resources can be declared and approved as CI resources 14:43:23 Bring this subject to OPNFV Infra WG with the information regarding resources including which project(s) will run on them 14:43:37 and if the INFRA team needs to do this .. then lets take an action on this.. im not sure what the debate is right now 14:43:46 the POD can sit there until tomrrow and then the process can be run 14:43:55 it is making this the most important subject of the world 14:43:55 and teams will have it for use sometime next week i would imagine then 14:44:02 anyway 14:44:06 not at all.. thats why i said quick and i can leave 14:44:10 Greg_E_: the jobs have been created for colorado 14:44:17 the lab is there for you guys to use.. its up to you guys to sort out the process if there is checks to be done 14:44:19 Greg_E_: just need final touches 14:44:35 Greg_E_: https://build.opnfv.org/ci/view/fuel/ 14:44:56 Greg_E_: need to get functest and yardstick images built and pushed to the docker hub 14:46:27 fdegir: we seem to have the jobs for baremetal for colorado created, but not virtual 14:46:50 do we want to run virtual env CI as well? 14:47:00 Greg_E_: jobs are created but the jenkins view is not updated 14:47:06 fixing it now 14:47:06 ah 14:48:13 please refresh the page 14:48:33 I suppose I can exclude virtual-ha scenarios from the page 14:48:38 (have to run - Niko - seems like that POD wont be used for CI/CD - so you can go ahead and use it for whatever you like under the INFRA WG process has been run through.. the LAB INFO (Login /etc) is all on the page - its yours- have fun! 14:48:39 since we only run noha ones on virtual 14:49:18 DanSmithEricsson: thanks! 14:50:25 fdegir: that would be great 14:50:44 mskalski: done 14:50:54 mskalski: Greg_E_ : yardstick docker image has been built 14:50:57 DanSmithEricsson: you mean Pod1 know I am a bit confused 14:50:59 functest is building 14:51:09 once both images are available 14:51:19 please paste the link to the webstie then I am sure which one is the correct one 14:51:27 I'll run colorado os-nosdn-nofeature-ha on barematal manually first 14:51:30 I see bramaputra virtual enabled 14:52:06 Greg_E_: just the heading - please refresh 14:52:36 anyway, once a full run is completed succesfully, I'll enable all the triggers so things will run automatically 14:52:39 fdegir: ok, jobs for master and colorado are run on the same servers right? 14:52:51 mskalski: yes, ericsson-pod2 and lf-pod2 14:52:53 fdegir: thanks, looks good 14:53:51 it will be long queue ;) 14:54:43 that's right 14:55:05 just queued the first colorado job 14:55:10 we'll see 14:55:33 NIKO 14:55:39 again.. there are 3 PODsd 14:55:43 1 in LF - called LF POD1 14:55:47 tyher eare 2 in ERICSSON 14:55:51 one call POD2 that is in CI/CD 14:55:56 POD1 i buitl yesterday 14:56:03 did you look at the LAB layout on the PHAROS page? 14:56:13 https://wiki.opnfv.org/display/pharos/CI-ERICSSON-POD1 14:59:28 thanks :-) 14:59:58 I like you blood going high 15:00:23 im sorry what? 15:02:15 just kidding 15:10:32 #stopmeeting 15:10:45 #endmeeting