14:59:51 <Jeffrey4l> #startmeeting kolla
14:59:52 <openstack> Meeting started Wed Jul 18 14:59:51 2018 UTC and is due to finish in 60 minutes.  The chair is Jeffrey4l. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:59:53 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:59:55 <openstack> The meeting name has been set to 'kolla'
15:00:39 <caoyuan> o\
15:00:44 <donghm> o/
15:00:44 <Jeffrey4l> #topic rollcall
15:00:46 <mandre> o/
15:01:01 <caoyuan> o/
15:01:06 <donghm> o/
15:01:30 <Jeffrey4l> #topic Announcements
15:01:42 <Jeffrey4l> any news from community?
15:02:29 <Jeffrey4l> #topic kolla rocky milestone
15:02:43 <Jeffrey4l> rocky milestone 3 is around the corner.
15:03:01 <Jeffrey4l> tag will be created during next week.
15:03:15 <Jeffrey4l> before that, we'd better merge the bps
15:03:38 <Jeffrey4l> so please update the pb patch and ask the core member ASAP.
15:04:04 <Jeffrey4l> technically, after the milestone 3, bp is not allowed to be merged.
15:04:21 <Jeffrey4l> expect a FFE is requested
15:04:55 <Jeffrey4l> on the other hand, i found the pb status on launchpad is out of update.
15:05:00 <pbourke> o/
15:05:10 <Jeffrey4l> some pbs are already done, but the status is not updated.
15:05:12 <Jeffrey4l> #link https://blueprints.launchpad.net/kolla-ansible
15:05:26 <Jeffrey4l> #link https://blueprints.launchpad.net/kolla
15:05:31 <Jeffrey4l> so please open the link
15:05:51 <Jeffrey4l> and check the bp you are familiar with, and update its status
15:06:28 <Jeffrey4l> if you are not sure, please paste it out.
15:07:13 <Jeffrey4l> let us work on this for 10 min
15:07:57 <Jeffrey4l> pbourke, do you know the status of https://blueprints.launchpad.net/kolla-ansible/+spec/prometheus
15:08:30 <pbourke> Jeffrey4l: unfortunately not
15:08:43 <pbourke> I know the basics are there but unsure how much more is required to call it complete
15:09:14 <sadasu> hello! sorry I am late
15:09:24 <Jeffrey4l> ok. i left a comment and will check with Mark too
15:09:31 <Jeffrey4l> hi sadasu ;D
15:10:13 <mandre> Jeffrey4l: shouldn't https://blueprints.launchpad.net/kolla/+spec/add-ssl-internal-network be moved to kolla-ansible?
15:10:25 <Jeffrey4l> mandre, yes
15:11:15 <Jeffrey4l> i do not know how to handle this https://blueprints.launchpad.net/kolla/+spec/kolla-on-power-server
15:11:16 <mandre> i have no idea how to move a spec between LP projects
15:11:21 <ktibi> o/
15:11:50 <Jeffrey4l> it intent to support power server for ubuntu, but we have support power server through centos
15:12:37 <Jeffrey4l> mandre, done. there is a "re-target blueprint" on the right top corner.
15:12:37 <mandre> Jeffrey4l: I'd say it's implemented
15:12:55 <ktibi> Jeffrey4l, What I need to change anything here ? https://blueprints.launchpad.net/kolla/+spec/bp-elasticsearch-upgrade
15:13:27 <mandre> imo the goal was to support ppc64le, we don't really care what the base distro is
15:13:50 <Jeffrey4l> mandre, yeah, agree
15:14:02 <Jeffrey4l> marked it as  implemented
15:14:12 <mandre> Jeffrey4l: thanks for the tip, now I see the 're-target' link
15:16:31 <Jeffrey4l> okay, time is up
15:17:08 <Jeffrey4l> i also moved several bp from kolla to kolla-ansible
15:17:52 <Jeffrey4l> then please continue update the pb status ensure the list is used ;)
15:17:56 <Jeffrey4l> let us move
15:18:08 <Jeffrey4l> #topic kolla ptg
15:18:16 <Jeffrey4l> #link https://etherpad.openstack.org/p/kolla-stein-ptg-planning
15:18:45 <Jeffrey4l> thanks mgoddard for initial this page
15:19:13 <Jeffrey4l> there are two months before the ptg.
15:19:27 <Jeffrey4l> we need prepare the topics during it.
15:19:35 <mandre> I've added moving the healthchecks to kolla images to the PTG agenda under Cross-Community goals - TripleO
15:19:44 <Jeffrey4l> mandre, thanks.
15:19:57 <mandre> that's something we decided a long time ago but never acted upon
15:20:57 <Jeffrey4l> a nice feature
15:21:05 <mandre> so probably worth revisiting the topic at the PTG
15:21:30 <Jeffrey4l> yeah
15:21:43 <Jeffrey4l> then let us focus on the page
15:21:46 <mandre> we're using them in TripleO, but there is no reason for the script to leave in a tripleo repo
15:22:10 <mandre> to *live*
15:22:16 <Jeffrey4l> we should add content for 1. done in rocky 2. plan during stein
15:23:13 <Jeffrey4l> mandre, yes
15:23:36 <Jeffrey4l> let us takes 12 mins on the planning
15:24:06 <Jeffrey4l> and back to IRC at 15:35 utc
15:35:17 <Jeffrey4l> ok, thanks guys
15:35:41 <Jeffrey4l> we will continue review the planing on the next meeting
15:35:47 <mandre> so, one thing... I've started looking at optimizing the images a bit, there are already a couple of patches that merged in that sense
15:36:31 <Jeffrey4l> iirc, they are small changes?
15:36:44 <mandre> one thing that was obvious with the CI script I added to look at the packages installed, is that httpd and related packages are big
15:36:55 <mandre> and are installed over and over again in the different images
15:37:17 <mandre> I know we discussed using a httpd base image in the past
15:37:33 <mandre> I don't recall why we never implemented it
15:38:13 <Jeffrey4l> no clue for this ;(
15:38:20 <mandre> I posted a patch where I play a bit with the idea, https://review.openstack.org/#/c/583361/
15:38:39 <mandre> even for just a couple images it seems to reduce the total size of the images quite a bit
15:38:51 <Jeffrey4l> but since we have so many image depends on httpd, it is worth to have a httpd base image
15:39:29 <mandre> yeah, that's my feeling as well
15:39:56 <mandre> pbourke: perhaps you remember why we gave up with the idea of an httpd base image before?
15:40:33 <pbourke> mandre: I dont remember it being discussed before
15:40:51 <mandre> maybe it was just my imagination
15:41:01 <Jeffrey4l> lol
15:41:32 <Jeffrey4l> anyway, the direct LGTM
15:42:05 <Jeffrey4l> should we move on?
15:42:23 <mandre> one more thing about the httpd base image
15:42:33 <Jeffrey4l> yep
15:42:49 <mandre> do you think it's feasible to merge it in the rocky time frame? or perhaps be backported?
15:43:51 <Jeffrey4l> i am ok to merge it before m3 tag
15:44:23 <mandre> so I should hurry up
15:44:48 <Jeffrey4l> yeah :D
15:45:09 <Jeffrey4l> because it is kind of big change
15:45:22 <mandre> yeah, hence me asking
15:45:43 <Jeffrey4l> ok, let us move
15:45:54 <Jeffrey4l> #topic open discuss
15:46:04 <Jeffrey4l> any volunteer?
15:46:21 <Jeffrey4l> mandre, i wanna to know the status of testing python3
15:46:39 <Jeffrey4l> what's the current rdo team plan?
15:46:50 <donghm> Hello, there patch sets to implement ironic upgrade logic ready for review, can someone review its, thank a lot.
15:47:01 <donghm> https://review.openstack.org/#/c/577773/ https://review.openstack.org/#/c/575594/
15:47:16 <sadasu> I was wondering about what I should be doing with https://review.openstack.org/#/c/567278/
15:47:19 <Jeffrey4l> cool
15:47:30 <mandre> I haven't followed closely, I think amoralej sent a few status updates on the rdo list
15:47:46 <sadasu> I have a comment from Eduardo saying that the change I am proposing does not need a spec
15:48:32 <Jeffrey4l> mandre, okay, i will try to find out. kolla should also prepare build images with py3
15:48:38 <mandre> Jeffrey4l: but I was able to build keystone and glance on a fedora28 base with the python3 repos rdo provided
15:48:46 <mandre> so there is progress
15:49:08 <Jeffrey4l> great
15:49:36 <mandre> last status update https://lists.rdoproject.org/pipermail/dev/2018-July/008818.html
15:50:27 <Jeffrey4l> sadasu, i am OK to merge this spec. maybe we should sync with Eduardo later.
15:50:53 <Jeffrey4l> mandre, thanks
15:51:14 <sadasu> ok. Sounds good. I am looking into gate failures for https://review.openstack.org/#/c/552119/
15:52:36 <Jeffrey4l> sadasu, check this http://logs.openstack.org/19/552119/8/check/kolla-build-centos-source/a196a10/logs/build/000_FAILED_neutron-server-networking-cisco.txt.gz
15:53:00 <sadasu> Jeffrey41: will do. Thanks!
15:54:09 <Jeffrey4l> np :)
15:54:33 <Jeffrey4l> seems we have done today.
15:54:46 <Jeffrey4l> let us save 5 min for out life ;)
15:54:54 <Jeffrey4l> thanks guys for coming
15:54:58 <Jeffrey4l> #endmeeting