13:00:23 #startmeeting Cross Community CI 13:00:23 Meeting started Wed Jun 13 13:00:23 2018 UTC. The chair is fdegir. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:23 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:00:23 The meeting name has been set to 'cross_community_ci' 13:00:29 hello 13:00:33 it's me again 13:00:37 #topic Rollcall 13:00:52 please type in your name if you are joining to XCI meeting 13:01:14 #info Markos Chandras 13:01:16 #info Jack Morgan 13:01:21 #info Tianwei Wu 13:01:27 the agenda is on: https://etherpad.opnfv.org/p/xci-meetings 13:02:06 as usual, we start and other join on the way or we ping them when their topic comes up 13:02:13 #topic OpenCI Updates 13:02:23 #info Tapio Tallgren 13:03:01 #info Even though things look quiet, things are happening in the areas such as event driven CI/CD, terminology, and so on 13:03:17 #info If you are interested in following it up, you can join to the mailing list if you haven't done it yet 13:03:36 #info Also, we are thinking of setting up regular meetings like on a monthly basis 13:03:48 #info Manuel Buil 13:03:52 #link https://lists.openci.io/pipermail/discuss/2018-June/000053.html 13:04:00 any questions/comments about openci? 13:04:03 #info Joe Kidder 13:04:25 ok, moving to the next topic 13:04:37 #topic PDF and IDF Status 13:04:47 hwoarang: mbuil: I believe you are pretty close to the completion 13:05:00 that's true for virtual 13:05:26 #info PDF and IDF is pretty close to completion for virtual deployments 13:05:37 #link https://gerrit.opnfv.org/gerrit/#/c/57079/ 13:05:54 fdegir: for baremetal I need Trevor 13:06:00 hwoarang: should we attempt the reviews once you remove -2 from the change? 13:06:08 or can we start doing it already now? 13:06:08 sure 13:06:13 i should be able to help with baremetal 13:06:15 wait till i remove it 13:06:21 ok 13:06:33 moving to the baremetal now 13:06:35 i have some hardware to use for testing 13:06:40 #topic Baremetal 13:06:51 mbuil: what are you waiting bramwelt for? 13:07:01 reinstalling jumphost with ubuntu/opensuse? 13:07:04 jmorgan1: tell me more about it. lfpod4 is centos and xci does not really work in that distro 13:07:40 mbuil: what about ericsson-pod2? 13:07:42 mbuil: https://build.opnfv.org/ci/computer/ericsson-pod2/ 13:07:56 fdegir: I have also a few tasks I need to finish urgently before diving into baremetal support, so it is ok, I am not really blocked :) 13:08:06 mbuil: right 13:08:07 i have 6 servers to use for baremetal testing, i need to intall jumphost and add any vpn profiles needed 13:08:12 but you can switch to ericsson-pod2 13:08:22 no excuses.... 13:08:41 hahaha 13:08:46 it should have the pdf as well 13:09:17 if not, you can get machines from jmorgan1 13:09:28 i need to create a pdf as well 13:09:34 mbuil: can we assume we solved your issue? 13:10:02 all right. I hope I can start on Friday or during next week 13:10:10 fdegir: yep 13:10:24 #info mbuil will use ericsson-pod2 until lf-pod4 jumphost is reinstalled and when he has time/as soon as possible 13:10:25 :) 13:10:34 moving 13:10:48 #topic SDF Status 13:11:12 #info hwoarang sent the first version of SDF for feedback from the community 13:11:14 yeah what are we going to do about that 13:11:21 #link https://gerrit.opnfv.org/gerrit/#/c/57679/ 13:11:33 hwoarang: if no feedback, we continue with what we think is best 13:11:45 we can perhaps pull AlexAvadanii in 13:11:47 i think we should test the SDF 13:11:56 so are we going to host template+validator+individual sdf files to releng-xci-scenarios ? 13:11:58 and incorporate learning s from it 13:12:05 hwoarang: it will end up in pharos 13:12:28 ok but for now we will have to manage it ourselves 13:12:32 hwoarang: no, just work on a template like we did with pdf 13:13:01 jmorgan1: that's actually part of the ask 13:13:03 well the template is up there 13:13:25 until we actually start using stuff i can't know what's missing 13:13:36 #info Periyasamy Palanisamy 13:13:45 AlexAvadanii: in case if you have time and interest in SDF: https://gerrit.opnfv.org/gerrit/#/c/57679/ 13:13:56 agreed, next steps are to testing and incorporate leanrings 13:13:59 hwoarang: lets wait some more 13:14:02 ok 13:14:15 i can ping some people like aricg and bramwelt to get their feedback 13:14:27 fdegir: I will look at it later today :) 13:14:30 since they worked with PDF and IDF and offer some guidance 13:14:30 ok 13:14:36 bramwelt: that would be helpful 13:14:37 thanks 13:14:38 really, we need senario owners feedback (ideally) 13:14:47 jmorgan1: the thing is... 13:15:05 we on purpose picked k8s scenarios to have less to spend on arguing and focus on getting something realistic 13:15:11 and we own the k8s scenarios... 13:15:24 sure 13:15:39 but once you start working on k8-calico-onap, then you and electrocucaracha will become to owner of it 13:15:48 so it makes sense for you to look at it right now 13:16:05 #action jmorgan1 and electrocucaracha to review SFC RFC https://gerrit.opnfv.org/gerrit/#/c/57679/ 13:16:21 moving to the scenarios 13:16:34 #topic k8-calico-onap 13:16:39 jmorgan1: electrocucaracha: your turn 13:17:19 when will you amend the spec so we can review and submit it? 13:17:25 need to incorporate feedback into spec file, then work on playbooks - using Orange's examples 13:17:40 commit those to the repo and test 13:17:53 fdegir: hi! it's on my todo 13:18:02 AlexAvadanii: \o/ 13:18:06 thx 13:18:15 thx jmorgan1 13:18:19 biggest question is hardware resources needed - won't know until testing phase 13:18:34 jmorgan1: we will start with virtual deployments and i think we are fine 13:18:53 fdegir: yes, this is what I mean - how big the vm or how many 13:18:57 we will need bigger vms but since we can adjust the specs of them via pdf, it should be fine 13:19:20 i think we will end up with 3 vms: 1 opnfv/deployment host, 1 k8s master, 1 k8s worker 13:19:33 opnfv and k8s master have like 8GB of ram or so 13:19:40 worker needs to have at least 128GB ram 13:20:07 these numbers are based on: https://gitlab.com/Orange-OpenSource/kubespray_automatic_installation/blob/master/vars/pdf.yaml 13:20:11 they have 4 worker nodes 13:20:20 which we can do the same or just have 1 bigger worker node 13:20:51 jmorgan1: up to you to decide and we should be able to fit them to one of the CI nodes we have 13:21:04 and then we can fine tune it later on once it works 13:21:27 moving to the next scenario 13:21:31 #topic k8-odl-coe 13:21:38 epalper: how is it going? 13:23:04 i have raised few initial patches in xci scenario and ODL role 13:23:20 https://gerrit.opnfv.org/gerrit/#/c/58363/ 13:23:44 https://git.opendaylight.org/gerrit/#/c/72840/ 13:24:16 but yet to start testing with it due to other priority work 13:24:40 epalper: you might have noticed that the jenkins jobs are skipped for the first change 13:24:55 epalper: we can talk about how to verify it after the meeting 13:25:06 ok, sure 13:25:11 hwoarang thaught me how to do that 13:25:12 we also need to merge the spec https://gerrit.opnfv.org/gerrit/#/c/58021/ 13:25:24 yes 13:25:40 can do that tomorrow morning first thing if no additional comments 13:25:54 sure, i got few minor comments from mardim 13:26:05 will update the patch 13:26:14 ok, i'll review later today 13:26:24 sure, thanks 13:26:24 thx epalper 13:26:27 #topic k8-nosdn-istio 13:26:37 hw_wutianwei_: I've seen you sent the scenario 13:26:47 fdegir: 13:26:49 #link https://gerrit.opnfv.org/gerrit/#/c/58471/ 13:27:09 #link https://gerrit.opnfv.org/gerrit/#/c/58357/ 13:27:39 the second one is used to add k8-nosdn-isito scenario 13:27:56 the first one is used to deploy istio, but it failed to run functest. I would fix this 13:28:11 hw_wutianwei_: that was what i was going to ask 13:28:17 so the deployment works fine - which is good 13:28:23 and the only thing to fix is functest 13:28:39 I think so 13:28:42 ok 13:28:59 fdegir: but I am not sure the reasons 13:29:00 hw_wutianwei_: i think we should reach out to clover project and opnfv cloud native working group to start making some noise 13:29:30 they want/need k8s scenarios which we have all these different networking plugins and istio so they might reuse these 13:30:03 hw_wutianwei_: i'll check the patch time to time but ping me/us when you fix it so we start the conversation 13:30:23 so we need different sdns istio scenarios? 13:30:47 hw_wutianwei_: i think what we have now is good enough to start reaching out 13:31:03 once we know more and if there is interest, we can think of additional networking plugins 13:31:22 fdegir: ok 13:31:35 we need to look at what onap plans to do with istio 13:31:52 hw_wutianwei_: you can maybe search their wiki to see this 13:32:40 thx hw_wutianwei_ 13:32:43 fdegir: I will, but recently I am busy with other things 13:33:11 hw_wutianwei_: not urgent - once the functest is fixed for k8-nosdn-istio and you have time 13:33:40 #topic os-nosdn-osm and os-odl-osm_sfc 13:33:54 these are the new scenarios to bring OSM into OPNFV 13:34:06 last week mbuil and myself had some conversations with OSM developers 13:34:27 we even got OSM up and running using os-nosdn-nofeature scenario, onboarded and activated a sample cirros based vnf 13:34:44 so in parallel to onap scenario, we will work on osm ones 13:34:53 #link https://gerrit.opnfv.org/gerrit/#/c/58323/ 13:35:04 #link https://gerrit.opnfv.org/gerrit/#/c/58347/ 13:35:18 any comments/questions about osm? 13:35:56 #topic Congress, Masakari, and Blazar 13:36:26 #info Congress has been ready for a while and Taseer is waiting for a shabump which has not been successful unfortunately 13:36:42 #info Work with Masakari and Blazar are in progress upstream 13:37:03 #topic Existing Scenarios 13:37:16 mbuil: epalper: anything to say about os-odl-sfc and os-odl-bgpvpn? 13:38:03 #topic OSA SHA Bump 13:38:08 fdegir: not really 13:38:18 as mentioned, we have been having some trouble with it 13:38:55 i was not able to check upstream because gates are in a horrible state right now but the fact that suse is passing might mean that it's a random issue again 13:39:28 hwoarang: i can try reverify 13:40:39 or attempt previous shas which passed deployment but failed on functest 13:40:39 https://gerrit.opnfv.org/gerrit/#/c/57441/8 13:40:53 so we can focus on functest while upstream gates stabilize 13:41:06 ok 13:41:52 did reverify and rollback to older shas from master later today if this one fails too 13:42:03 #topic Intel Lab Maintenance 13:42:18 #info The lab will be in maintenance 6/13 5PM PST to 6/22 PM 13:42:24 please use laas when possible 13:42:46 #topic Meetings during summer 13:43:03 i assume most of us will be away during july 13:43:13 so i want to check with you what to do with the meetings 13:43:23 should we reduce to bi-weekly or even monthly? 13:43:28 probably monthly 13:43:31 i'd say 13:44:08 anyone else? 13:44:09 i'd prefer bi-weekly but i'm not taking time off in july 13:44:12 I'll be away in July so 13:44:53 ok 13:44:56 This meeting overlaps with a webex meeting every week so bi-weekly is better for me 13:45:19 i'll chat with you during the week to find out what to do and find chairs for those meetings 13:46:14 ttallgren: we can revisit general schedule after summer and see if we move to bi-weekly 13:46:20 ok 13:46:24 #topic AOB 13:46:29 anything else anyone wants to bring up? 13:46:53 I have 6 servers in our lab; any use right now? 13:47:26 I was trying to get the Apex+ VLAN tenant networks to work on those for the plugfest but failed 13:47:49 ttallgren: you can attempt osa on baremetal but pdf/idf stuff is not ready so it needs to be manual 13:48:14 ok 13:49:23 thank you all for joining and talk to you next time! 13:49:23 #endmeeting