14:00:40 #startmeeting tripleo 14:00:41 Meeting started Tue Jun 27 14:00:40 2017 UTC and is due to finish in 60 minutes. The chair is EmilienM. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:44 #topic agenda 14:00:45 The meeting name has been set to 'tripleo' 14:00:51 * review past action items 14:00:53 * one off agenda items 14:00:55 * bugs 14:00:57 * Projects releases or stable backports 14:00:59 * CI 14:01:01 * Specs 14:01:03 * open discussion 14:01:05 Anyone can use the #link, #action and #info commands, not just the moderatorǃ 14:01:07 Hi everyone! who is around today? 14:01:09 /o/ 14:01:12 o/ 14:01:13 o/ 14:01:14 o/ 14:01:38 o/ 14:02:13 o/ 14:02:20 #topic review past action items 14:02:22 #link http://eavesdrop.openstack.org/meetings/tripleo/2017/tripleo.2017-06-20-14.00.html 14:02:30 EmilienM to send email about how to use RSS to monitor Tempest results in TripleO CI 14:02:33 EmilienM to start looking how to convert 3-nodes jobs in oooq 14:02:35 EmilienM to postpone open specs to Queens, unless code has already been started during Pike and made good progress 14:02:44 o/ 14:02:55 Hi 14:02:55 o/ 14:02:55 I'll postpone the first one again 14:02:55 \o 14:03:03 o/ 14:03:08 the second one is on the roadmap, after some discussion with weshay and trown 14:03:10 /o 14:03:14 \o 14:03:24 and the third is still WIP 14:03:37 #topic one off agenda items 14:03:40 #link https://etherpad.openstack.org/p/tripleo-meeting-items 14:03:45 mhenkel: hi, please go ahead 14:04:26 0/ 14:04:39 I worked on https://review.openstack.org/#/c/475048/5 and removed the big firstboot script 14:05:13 I replaced it by 2 pre_network templates (one for dpdk and one for kernel module based installations) 14:05:17 mhenkel: ok, I'll review it again - also anyone who has time to review, feel free to help 14:05:39 thanks 14:06:03 mhenkel: is there anything specific to discuss or you just need reviews? 14:06:34 EmilienM: no, I think I cleaned everything up as much as I could 14:06:47 ok 14:06:56 there is still the need to bring up the vhost0 interface before os-net-config takes over 14:07:14 therefore I unfortunately need some lines of bash 14:07:19 #action review contrail patches https://review.openstack.org/#/c/475045/ https://review.openstack.org/#/c/475048 14:07:34 moving on 14:07:37 #topic bugs 14:07:40 #link https://launchpad.net/tripleo/+milestone/pike-3 14:07:55 do we have any outstanding bug to discuss this week? 14:08:57 great let's move on 14:09:00 #topic projects releases or stable backports 14:09:09 no updates on my side regarding release & backports 14:10:10 moving on then 14:10:16 #topic CI 14:10:37 the only info I have regarding CI is that we're working on moving container scenario jobs into the gate (voting) as soon as they work 14:10:44 so far we have scenario002 and scenario004 AFIK 14:11:02 do we have anything to discuss about CI? 14:11:03 The undercloud deploy has been broken, locally and in CI 14:11:06 any review is needed? 14:11:16 shardy: which job? 14:11:41 gate-tripleo-ci-centos-7-undercloud-oooq ? 14:12:11 EmilienM: no the undercloud-containers job 14:12:13 I know the undercloud upgrade has been broken from newton to ocata, but ccamacho / me are on it 14:12:18 https://github.com/openstack/python-tripleoclient/commit/4b1daab4eb7e29dafabc68ed82a3022399cbe013 just landed which aims to fix it 14:12:32 shardy: yeah this one doesn't get much love 14:12:43 shardy, it's voting job, how was it broken? 14:12:49 iirc this job / feature wasn't officially supported, that's why we didnd't have in gate right? 14:12:57 https://bugs.launchpad.net/tripleo/+bug/1700417 has some details 14:12:59 Launchpad bug 1700417 in tripleo "CI: Undercloud containers job timing out" [Critical,Fix released] - Assigned to Steve Baker (steve-stevebaker) 14:13:00 yeah, im still checking logs to get the root cause 14:13:20 sshnaidm: it's not 14:13:23 gate-tripleo-ci-centos-7-undercloud-containers-nv 14:13:30 let's make it voting then? 14:13:58 https://review.openstack.org/#/c/475750/ broke it because it was merged with red CI 14:14:05 more details in the bug of how 14:14:17 shardy: should we make the job voting? 14:14:29 EmilienM: yes I think so, as soon as it's stable again 14:14:53 #action EmilienM to make gate-tripleo-ci-centos-7-undercloud-containers job voting in tripleo gate and make sure we run it where useful 14:15:08 anything else CI related for this week? 14:15:15 we didn't promote today because one of periodic jobs started 5 mins later than others and caught different DLRN hash.. not sure what can we do in such case 14:15:23 we should try to get that oooq version of that job voting, but what ever get's the job done now is ok 14:15:46 weshay: yeah but I'm afraid this is not in the high prio backlog 14:15:53 so it will break again if we don't make it voting 14:15:58 aye 14:16:05 sshnaidm: hm, yeah, we should probably get a better way to do these periodic jobs in a more coordinated way. 14:16:09 imho, upgrade jobs should be high prio to be in oooq 14:16:20 we want to see upgrade jobs in oooq before anything else imho 14:16:33 sshnaidm: long term we could have a main job trigger all the promotion jobs with a single hash. 14:17:00 sshnaidm: I don't understand why it didn't catch a more recent DLRN hash 14:17:05 adarazs, I think it's possible in rdo cloud only 14:17:08 sshnaidm: it takes hashes from consistent, right? 14:17:14 EmilienM, because it changed in these 5 mins 14:17:19 ahh 14:17:28 can't we write it somewhere? 14:17:33 I love race conditions 14:17:42 too me! 14:17:52 sshnaidm: maybe not, pabelanger was saying something about these pipeline jobs where jobs can trigger other jobs. maybe only in zuul v3? 14:18:04 EmilienM, not sure.. 14:18:25 adarazs, yeah, the life will be happy with zuul v3 :) 14:18:29 sshnaidm: please file a bug in Launchpad, so we can track this one 14:18:40 adarazs: there's the concept of a child job in zuul right now 14:18:42 EmilienM, ok 14:18:48 panda: so we could probably use that. 14:18:50 we could use that 14:19:01 with zuul 2.5 ? 14:19:41 tbh, I'm a bit confused (by lack of knowledge probably) why we have this race 14:19:48 oh I see 14:19:50 nevermind 14:19:56 scenario001 picked another repo than 002 for ex 14:20:20 mhh, yeah, hard to write it somewhere 14:20:40 EmilienM, I think we can live with this until we move periodics to 3party 14:20:42 sshnaidm: let's think about it offline 14:20:45 sshnaidm: ++ 14:20:50 anything about CI this week? 14:21:30 moving on... 14:21:32 #topic specs 14:21:35 #link https://review.openstack.org/#/q/project:openstack/tripleo-specs+status:open 14:21:43 #action EmilienM to continue the postponing to Queens 14:21:48 anything to discuss about specs this week? 14:22:35 #topic open discussion 14:22:48 I forgot to mention it in the off items but there is a cross project effort about documentation 14:22:57 https://review.openstack.org/#/c/472275/13/specs/pike/os-manuals-migration.rst 14:23:10 I'll send an email about it as well but I'd like to do a short i18n-themed deep dive in next week's slot (July 6th) if that works. Basically follow the Life and Journey of a String through tripleo-ui + infra + Zanata and back, what can go wrong/debugging tips, how we interact & work with the I18n team, things like that 14:23:10 I'm working on it for TripleO but I'll probably ask for some help around 14:23:24 jpich: that would be aweosme 14:23:40 jpich: feel free to send email on openstack-dev and do it at your convenience 14:23:54 Cool! Will do. Probably all of this is already documented but in 20 different places 14:24:10 jpich: it would be fun to share screen and see real examples in code 14:24:16 but I'm sure that's what you wanted to do :P 14:24:34 Yep, though I can focus on different things if there's interest :) 14:24:43 really cool 14:24:50 I'll send the email 14:24:51 anything else for this week folks? 14:25:06 I'd like to have another deep-dive about containers 14:25:18 with more deep stuff this time.. 14:25:20 sshnaidm: which specific area would you like? 14:25:28 how deep? :) 14:25:38 EmilienM, of course everything we meet in CI :) 14:26:24 we can prepare more specific topics in next etherpad 14:26:27 sshnaidm: feel free to share this feedback with folks who did previous deep dive (aka jistr) maybe we can schedule another one 14:26:40 EmilienM, ok 14:26:59 allright! anything before we close the meeting? 14:27:24 thanks everyone have fun and see you online 14:27:27 #endmeeting