14:01:35 #startmeeting Cross Community CI 14:01:35 Meeting started Wed Oct 31 14:01:35 2018 UTC. The chair is fdegir. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:35 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:01:35 The meeting name has been set to 'cross_community_ci' 14:01:39 lets go then 14:01:44 #topic Rollcall 14:02:00 #info Manuel Buil 14:02:15 #info Markos Chandras 14:02:45 i suppose we are alone this time again 14:02:50 #topic Baremetal Status 14:03:11 mbuil: i'll have few questions once you talk about the latest status 14:03:59 fdegir: so, patches were ready. Then I rebase one of them and jenkins is giving a -1 14:04:26 fdegir: need to investigate the problem, fix it and then we quickly merge them before it happens again 14:05:18 #info We have two patches missing. One providing network config for the baremetal nodes in Ubuntu and another one in opensuse 14:05:24 #link https://gerrit.opnfv.org/gerrit/#/c/60799/ 14:05:31 #link https://gerrit.opnfv.org/gerrit/#/c/63739/ 14:05:52 #info After rebasing, jenkins is giving -1. Needs investigation 14:06:29 #info to complete the opensuse work, we require a rabbitmq patch from OSA: https://review.openstack.org/#/c/614355/ 14:06:30 ok 14:06:37 that's it 14:06:39 sorry - was too fast 14:06:44 ok :) 14:06:50 so the first question i would like to ask is 14:07:12 what is the relation between the flavors we use and the pdf? 14:07:20 is it like; if it is noha, use the first 3 nodes 14:07:28 if it is mini, use the first 2 14:07:33 and for ha, use all 14:07:38 yes 14:07:39 is this correct understanding? 14:07:42 correct 14:07:43 ok 14:07:49 it seems i'm not that behind 14:07:55 the second question is about this part 14:08:07 https://github.com/opnfv/releng/blob/master/jjb/xci/xci-run-functest.sh#L53 14:08:15 fdegir: look at this: https://github.com/opnfv/releng-xci/blob/master/xci/var/idf.yml#L38-L44 14:08:16 maybe this is a question to both of you 14:08:37 now i know where i saw this 14:08:40 thanks for the link 14:08:51 so we are still dynamic when it comes to setting the flavor 14:09:07 without changing the pdf, we can assign roles to the nodes - which is very useful 14:09:12 fdegir: we don't need that anymore. I have a patch that removes that ==> https://gerrit.opnfv.org/gerrit/#/c/63737/ 14:09:37 mbuil: but... 14:09:46 the link i pasted is used by verify jobs 14:09:58 and what your change does is fixing it for daily 14:10:07 i suppose you need to fix verify jobs too, isn't it? 14:10:30 sorry 14:10:33 you fix both 14:10:56 fdegir: yes. The reason why I added that was because we needed to know where opendaylight was deployed 14:11:05 yeah 14:11:08 fdegir: but if you remember, you gave me an alternative solution which is simpler 14:11:20 kind of ;) 14:11:28 too many things happening and i'm forgetting things 14:11:30 and now it is done in the prepare.... playbook of each scenario 14:11:55 but this answers my question since i was going to say that line is osa specific, causing warnings during k8s deployments 14:13:54 hwoarang: anything you want to add for baremetal or are you ok for us to move on? 14:14:12 nothing on my end 14:15:07 ok 14:15:26 #topic Status of os-nosdn-osm and os-odl-sfc_osm 14:15:33 i'm not sure is avhvr is around 14:16:01 Manuel Buil proposed releng-xci: [baremetal] suse support for baremetal networking https://gerrit.opnfv.org/gerrit/63739 14:16:09 Manuel Buil proposed releng-xci: [Baremetal] Use physical interfaces for networking https://gerrit.opnfv.org/gerrit/60799 14:16:19 Manuel Buil proposed releng-xci: [baremetal] suse support for baremetal networking https://gerrit.opnfv.org/gerrit/63739 14:16:32 I had to rebase, sorry ^ 14:16:45 fdegir: if he is not around, I can give a status 14:16:57 mbuil: please do 14:17:58 #info The scenario os-odl-sfc_osm is finished and it deploys successfully using OSM version 4. However, there is a bug for SFC. The SFC config is not propagated into openstack 14:18:40 #info Harsha talked to OSM guys and they recommended to move to master branch where the bug is fixed. Now the scenario uses master branch and the deployment fails. Harsha is investigating it 14:19:14 Note that Harsha will not work during November because of his exams period 14:19:49 yep 14:20:01 but i think xci doing what is supposed to do in this case 14:20:05 finding bugs ;) 14:20:27 mbuil: thanks for the update 14:20:33 #topic CI Status 14:20:56 #info The daily jobs have been failing which needs investigation 14:21:27 mbuil: i think the place they fail is the place where you are doing changes as well with https://gerrit.opnfv.org/gerrit/#/c/63737/ 14:22:01 mbuil: so I will wait until after the above change is merged, attempt to run 1 os and 1 k8s daily job and then fix daily jobs if they continue to fail at that point 14:22:19 ok 14:23:10 #info Once the change https://gerrit.opnfv.org/gerrit/#/c/63737/ gets merged, the issue will be attempted to be reproduced and fixed accordingly 14:23:19 mbuil: this one is for you as well 14:23:46 so, once we get the daily jobs fixed and baremetal stuff in, i suppose we can start running daily jobs on baremetal 14:24:30 right. We will need the idf and pdf of the servers 14:24:47 i thought we had them for ericsson-pod2 14:25:01 we have the ericsson-pod2 pdf and idf 14:25:14 yes, so we can start using that for daily jobs 14:25:20 aaah, correct 14:25:35 and the question to all of us is that can you guesstimate the resource need? 14:25:47 for bareemetal dev work especially 14:26:01 sicne we are losing the pod to ci which you used for development 14:26:28 we were supposed to get lf-pod4 but i'm not sure if the networking issue is fixed there 14:26:32 need to check with bramwelt 14:26:39 fdegir: yes, it was fixed. We also have it 14:26:47 mbuil: i didn't know it 14:26:50 then we are good 14:26:55 tes 14:26:56 yes 14:27:35 #info After fixing the daily jobs and baremetal patches are merged, daily jobs will be switched to baremetal from virtual 14:27:54 #info The testing we do will be adjusted accordingly as well 14:28:09 that is all for CI stuff 14:28:15 anything to add? 14:29:16 i take this as no 14:29:21 #info Release Status 14:29:25 #undo 14:29:25 Removing item from minutes: 14:29:29 #topic Release Status 14:29:46 i think we should think of tagging the repos during next week 14:29:51 this includes sfc as well 14:30:01 right 14:30:15 we need to think about what to document 14:30:23 given that we have lots of updates lately 14:30:45 i'll try to do that and send reviews so at least i can contribute something - which i failed to do recently 14:30:45 fdegir: are we going to be able to run sfc tests in order to check that everything is fine and thus do the tagging? 14:30:59 mbuil: that's the plan 14:31:13 mbuil: that's why i was looking at daily jobs 14:31:31 mbuil: once they turn green, we can include sfc tests for sfc scenario before we add anyhting else 14:32:23 mbuil: and when we get a green sfc run, that sha could be tagged which then becomes your release candidate to get opnfv-x.y.z tag 14:32:39 and pinned in xci repo 14:32:44 ok 14:33:11 i think that was all i wanted to talk about 14:33:17 anything you want to add mbuil hwoarang > 14:33:19 ? 14:33:44 nope 14:35:09 ok then 14:35:29 thanks a lot for everything you've been doing and apologies again for not being around lately 14:35:36 but i'm coming back 14:35:41 have a nice day! 14:35:43 #endmeeting