14:02:54 #startmeeting 3rd Party CI 14:02:54 Meeting started Wed Dec 14 14:02:54 2016 UTC. The chair is fdegir. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:54 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:02:54 The meeting name has been set to '3rd_party_ci' 14:03:13 so, can we do tool based updates this week 14:03:20 starting with bifrost and openstack-ansible 14:03:25 and anything else later on? 14:03:49 I take this as yes 14:03:51 fine by me 14:03:51 #topic Bifrost Status 14:04:00 who has update regarding bifrost? 14:04:18 well not so much an update, but latest diskimage-builder changes broke the suse job 14:04:38 so i posted a patch but until it's accepted the job will remain broken 14:05:01 that was what I was going to ask 14:05:04 sorry, no time in the latest weeks to work on it 14:05:15 but apart from that, bifrost seems pretty stable comparing to last month for example 14:05:21 yes! 14:05:37 a question to you all 14:05:53 should we set up 3 daily jobs against baremetal, running ubuntu, centos, and suse? 14:06:07 so we can get some feeling regarding baremetal provisioning as well 14:06:26 If we have resources, a good choice 14:06:27 it will provide valuable info, as the behaviour of bifrost can be different on baremetal 14:06:39 yep, if there are resources to dedicate, sounds very good 14:06:59 I'll check this 14:07:14 yolanda: you were talking about Julia implementing multiple network (?) support for bifrost 14:07:17 any update about that? 14:07:37 fdegir, last news i had, is that bifrost already offers support to pass custom network data info 14:07:47 so we could generate by our own, and pass it to bifrost 14:07:59 but i hadn't have time to play with that, i have been very involved in downstream job 14:08:23 ok, so we just need to verify it 14:08:47 anyone else wants to add anything about bifrost? 14:08:56 I hope I can try bifrost on centos when my ci system runs well. 14:08:59 Julien-zte: hw_wutianwei: have you tried bifrost in your lab? 14:09:02 :) 14:09:07 just asked and got the answer 14:09:07 i was wondering if we can make the CI a voting one for openstack? 14:09:12 would that be valuable? 14:09:13 I have tested ubuntu, it is ok 14:09:32 hwoarang: well, that was kind of not a popular thing for puppet-infracloud 14:09:38 hwoarang: but Julia was positive to this 14:09:46 hwoarang: I'll ping her right now 14:09:49 I'd try it in baremetal 14:10:14 well for bifrost, i believe we provide a good feedback. i got the impression that the upstream one doesn't do a full VM provision 14:10:19 i think we cannot make it voting 14:10:25 as it's thid party ci 14:10:33 you can provide +1 or -1 but it won't block changes for landing 14:10:42 yeah sorry i meant +/-1 14:10:46 ah ok 14:10:51 my bad 14:10:59 just to make it more visible that "look you broke something" 14:11:37 chatting with Julia 14:11:41 will post the answer here 14:12:08 ok thanks 14:12:49 she says ok and I asked her to add opnfvci user to the appropriate group 14:12:59 good news 14:13:39 she wants me to put it into the agenda of next ironic meeting 14:14:24 thanks for reminder hwoarang 14:14:33 sounds reasonable. lets see! 14:14:45 this will be a good reference for other infra projects going forward 14:15:00 I think we can move to openstack-ansible 14:15:09 #topic openstack-ansible status 14:15:14 fdegir, i use this feedback we provided from opnfv heavily on the bifrost reviews 14:15:31 i helped to caught failures on patches, specially on distros that are not xenial 14:15:47 I'm wondering what others are feeling - non-opnfv/openstack people 14:15:49 like the selinux issues, package naming mismatch, etc 14:15:55 do you have any inside? 14:16:00 do they look at our results? 14:16:10 Julia does 14:16:16 i bet Julia does yes 14:16:26 good, then we are not just a noise for them 14:16:40 she also alsed to update teh logs on artifacts.opnfv.org 14:16:52 a while ago but never got around to actually see how to do that... 14:16:57 *asked 14:17:08 then we need to improve that 14:17:21 #action hwoarang to fix bifrost logs on artifacts.opnfv.org 14:17:23 hehe 14:17:29 oh busted 14:17:40 first action ever! 14:17:56 so, openstack-ansible? 14:17:58 anyone? 14:17:59 sadly no o-ansible progress on my end. very busy with internal stuff 14:18:10 i use the openstack-ansible to deploy the production environment of openstack, but there are some problem in network configuration. 14:19:18 hw_wutianwei: you can perhaps share more details regarding what type of network config problems you are having 14:19:46 in case if someone else had the issue and knows something about it 14:19:56 or if someone else experiences them while they work with it 14:20:13 the openstack instance cann't get ip by dhcp 14:21:22 do you use for baremetal or for containers? 14:21:45 I use for VM 14:22:19 3 infra nodes +2 compute nodes 14:23:43 not sure what the deployment is but could it be that cloud-init or glean is not running or something? 14:24:08 the network configuration is too much to send here, so i will send a link tomorrow 14:24:55 that would be good hw_wutianwei 14:25:06 I think that's all for openstack-ansible 14:25:16 hw_wutianwei, next time, we can use http://paste.ubuntu.com/ to use the log 14:25:34 Julien-zte: ok 14:25:39 anyone wants to add anything? 14:25:40 fdegir, need resources to try openstack-ansible? 14:25:50 Julien-zte: you need resources? 14:26:03 people resources? 14:26:12 maybe I will pay some time in openstack-ansible 14:26:16 Julien-zte: of course 14:26:22 Julien-zte: any help is appreciated 14:26:49 from what we discussed previously, bifrost is stable now? 14:26:54 Julien-zte: yes 14:27:03 can it be used in baremetal and VM? 14:27:04 at least for provisioning virtual machines 14:27:26 and it works for baremetal as well but as yolanda mentioned above, there might be different suprises on baremetal 14:27:41 that's a good result. 14:27:45 you can see the build history on our jenkins 14:28:11 they are pretty stable - except some usual issues due to development of other components, such as diskimage-builder 14:28:12 I will try and discuss with daisy team to use bifrost to deploy vm:) 14:28:22 https://build.opnfv.org/ci/view/3rd%20Party%20CI/ 14:28:26 good 14:28:28 Julien-zte: +1!!! 14:28:37 so I have 2 things to add 14:28:47 jmorgan1 will migrate intel labs and this might impact us 14:29:02 it remains to be seen how much and when this impact will be 14:29:04 thanks fgedir, I received the daily ci log just has no time to check 14:29:17 we might lose all our ci and development resources that are located in intel-pod4 14:29:25 or jmorgan1 can have an exception for us 14:29:26 I hope our labs will be on hand as soon as possible 14:29:37 second item is next meeting 14:29:43 I'll be away on december 28th 14:29:57 and if you will be around, you don't need me to have the meeting 14:30:15 but I will probably schedule another one for january 4th just in case 14:30:20 i'm on holiday until 7th january 14:30:40 anyone else having vacation? 14:30:46 In China, only 1st-3rd is holiday 14:30:55 yeah i am back on the 3rd 14:31:07 ok 14:31:12 then we keep the regular schedule 14:31:44 and for the ones that are taking vacation, the next meeting will be on january 11th 14:32:05 Julien-zte: please have the meeting if you need one on 28th of december but we won't be around 14:32:23 with that 14:32:31 get it 14:32:35 I wish all of you Merry Christmas and Happy New Year 14:32:44 good to you all 14:32:49 thank you all for the work and effort you put 14:32:52 have a nice christmas! 14:32:55 and I think we made ourselves visible 14:33:20 I think we can do more and we will do more 14:33:35 take care until the next time 14:33:38 #endmeeting