15:00:37 #startmeeting kolla 15:00:38 Meeting started Wed Jul 4 15:00:37 2018 UTC and is due to finish in 60 minutes. The chair is Jeffrey4l. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:41 The meeting name has been set to 'kolla' 15:00:46 #topic rollcall 15:00:58 o/ 15:00:59 \o/ 15:01:01 o/ 15:01:10 o/ 15:02:11 #topic Announcements 15:02:27 no from me. now. any update from the community? 15:02:58 btw, there is no agenda in the wiki page. guess we will end today's meeting earlier. 15:03:09 #topic open discussion 15:03:23 anything wanna be talked? 15:03:46 Jeffrey4l, can you confirm the frezze feature date is the 23 jul ? 15:03:53 for kolla 15:03:53 i have a patch require another core review https://review.openstack.org/557872 , thanks. 15:04:37 o/ 15:04:57 hi pbourke 15:05:07 do you have any concern wanna be talked? 15:05:11 o/ 15:05:12 Jeffrey4l, good patch, I working right now on a deploy issue on keyring ceph ^^ Fetching Ceph keyrings ==> failed T_T 15:05:28 nothing from me today 15:05:59 cool 15:06:16 seem we could end the meeting today ;) 15:07:03 how are we looking in terms of features for rocky? 15:07:23 mgoddard, release note is a good place 15:07:48 https://docs.openstack.org/releasenotes/kolla/unreleased.html 15:08:02 and 15:08:02 https://docs.openstack.org/releasenotes/kolla-ansible/unreleased.html 15:08:10 mgoddard, ^^ 15:08:25 for comparison, ironic has a whiteboard 15:08:36 https://etherpad.openstack.org/p/IronicWhiteBoard 15:09:02 it tracks the status of features targeted for the next release, and lists priorities for reviewers to focus on 15:09:46 it's a bit messy, but L89 is priorities, and L138 has feature status reports 15:10:25 is this something that kolla could use to try to track the progress of features? 15:10:26 sound good. it track not only current release. 15:10:50 I'm sure something similar could be done with storyboard, but might be harder to setup 15:10:58 does kolla plan to move to storyboard? 15:11:23 we discussed it a few weeks back 15:11:24 mgoddard, no plan right now. but the whiteboard is a good idea 15:11:43 seems storyboard is not quite there yet in terms of features, I think the main one highlighted was around stable branch tracking 15:11:50 i start this link https://etherpad.openstack.org/p/KollaWhiteBoard 15:12:04 yeah, storyboard seems a little raw still 15:12:17 nice, thanks Jeffrey4l! 15:12:42 how will we use the whiteboard? 15:12:50 list of upcoming features with status? 15:13:16 mgoddard, we could learn from ironic. some important info + current cycle status 15:13:23 of course it needs to be kept up to date... normally the ironic PTL announces on IRC just before the meeting to update whiteboard status 15:13:59 Jeffrey4l: yeah, start fairly lightweight otherwise people will get tired 15:14:46 now is probably a good time to start thinking about things to discuss at the PTG 15:15:03 Jeffrey4l: will you be able to make it this time? Would be nice to meet you :) 15:16:14 mgoddard, i'd love too. visa is still a nightmare for me. tried twice. i am trying to apply now. 15:16:19 pbourke had the kolla update slides from vancouver - we could use those to populate the whiteboard feature list 15:16:29 Jeffrey4l: sure. good luck 15:20:25 I had a question about rolling upgrades 15:21:47 mgoddard, yes? 15:21:50 In the ironic rolling upgrade review, we are now pulling images in upgrade.yml. Previously it was required to pull before the upgrade. Is there a reason for this change in behaviour? 15:22:40 donghm, ^^ 15:23:53 #link https://review.openstack.org/577773 15:24:03 Hi mgoddard, as i commented in my patch set, in legacy upgrade, we should pull all images of the services 15:24:46 donghm, yes - what is the reason for the change? 15:25:09 in rolling upgrade, this is good for pull the images in separate service 15:25:32 why? 15:25:55 maybe we can discuss on IRC 15:26:58 one last thing :) 15:26:59 i think when you just want to upgrade a service to the new version to fix some bug 15:26:59 https://review.openstack.org/549775 15:27:05 sure :) 15:27:18 the bifrost CI job 15:28:18 3x +2 but no +A. egonzalez had concerns about load on zuul. He suggested creating a periodic job, or filtering only changes to the bifrost role. Any thoughts 15:28:21 ? 15:28:50 mgoddard, what do you think about his idea. 15:28:58 i think use filter is reasonable 15:29:13 yeah, I'm ok with that 15:29:17 and now kolla consumers lots of ci resource for each patch 15:29:50 where do the results of periodic jobs get displayed? 15:30:35 mgoddard, mail will be send if the jobs is failed. 15:31:02 mgoddard, check http://lists.openstack.org/pipermail/openstack-stable-maint/ 15:31:21 ah, great - thanks 15:31:29 I will go for that approach then 15:31:34 I will stop talking now :) 15:31:54 but seems it is only true to periodic-stable pipeline 15:32:17 oh, not master? 15:32:21 more info please check https://github.com/openstack-infra/project-config/blob/master/zuul.d/pipelines.yaml 15:32:43 it is matter will pipeline are you using. not the branch you are testing. 15:32:57 no idea why there is no mail for periodic pipeline 15:33:59 ok, could ask in infra channel 15:34:32 btw, for filter change, egonzalez should be saying change like https://review.openstack.org/575026 15:35:10 ok, thanks 15:35:49 I think setup_gate.sh is getting too big :) 15:35:54 a topic for another day 15:36:43 mgoddard, yeah. it is a result of history. and better be converted to zuul roles now ;) 15:37:27 yeah, or just separate scripts would be a good start 15:38:14 mgoddard, i merged you bifrost patch. we could improve it in following patches. 15:38:31 Jeffrey4l: nice, thanks :) 15:39:20 np 15:40:04 ok, any other topics? 15:41:17 guess no. 15:41:21 Jeffrey4l, I don't know if you see my question 15:41:25 thanks for everybody coming 15:41:32 let us end the meeting. 15:41:36 #endmeeting