16:00:09 <Jeffrey4l> #startmeeting kolla
16:00:10 <openstack> Meeting started Wed Mar 14 16:00:09 2018 UTC and is due to finish in 60 minutes.  The chair is Jeffrey4l. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:13 <openstack> The meeting name has been set to 'kolla'
16:00:25 <Jeffrey4l> #topic rollcall
16:00:29 <duonghq> o/
16:01:04 <Jeffrey4l> hrm..
16:01:08 <mgoddard_> o/
16:01:19 <chason> o/
16:01:59 <sadasu> o/
16:02:46 <Jeffrey4l> ok. let us starting the meeting
16:02:49 <caoyuan> hi guys
16:02:53 <caoyuan> :)
16:02:55 <Jeffrey4l> #topic Announcements
16:03:12 <gkadam> hi all
16:03:16 * hrw here for logs. have to go out
16:03:44 <Jeffrey4l> 1. core nomination, i nominate caoyuan as core reviewer, feel free to +1 or -1 in the ML
16:04:25 <Jeffrey4l> 2. queens rc2 tag will be created in this week.
16:04:40 <Jeffrey4l> There are still fewer patch need be merged. will talk this later.
16:05:09 <Jeffrey4l> 3. community have changed the release mode, especially for trailing-cycle project
16:05:20 <Jeffrey4l> (kolla is a trailing cycle project)
16:05:35 <Jeffrey4l> more info can be found here
16:05:37 <Jeffrey4l> #link http://lists.openstack.org/pipermail/openstack-dev/2018-March/128215.html
16:06:13 <Jeffrey4l> as a result, tailing-cycle project can be release in 3 month after the coordinate release.
16:06:41 <Jeffrey4l> and othere projects ( like nova, neutron etc) can not merge feature after m2
16:07:00 <Jeffrey4l> this is a good for trailing cycle project
16:07:30 <Jeffrey4l> it will make us more time to test before release.
16:07:38 <Jeffrey4l> that's all from me,
16:07:51 <Jeffrey4l> any other community announcement?
16:08:32 <Jeffrey4l> guess no
16:08:36 <Jeffrey4l> let us move on
16:08:41 <Jeffrey4l> #topic kolla queens release rc2 requirements
16:08:57 <Jeffrey4l> this week is the deadline for rc2 tag.
16:09:06 <Jeffrey4l> and rc2 will be the final release.
16:09:25 <Jeffrey4l> There is still few patch need be merged for queens branch
16:09:40 <Jeffrey4l> here is i concern
16:09:59 <Jeffrey4l> Update ceph client.admin caps during upgrade
16:10:03 <Jeffrey4l> #link https://review.openstack.org/#/c/547012/
16:10:20 <Jeffrey4l> Migrate neutron-vpnaas-agent to neutron-l3-agent
16:10:25 <Jeffrey4l> #link https://review.openstack.org/#/c/530208/
16:11:00 <Jeffrey4l> is there any other patch should be merged for queens branch?
16:11:10 <ktibi> https://review.openstack.org/#/c/550685/
16:11:36 <Jeffrey4l> Security memcached: disable UDP ^^ yes. security releate
16:13:45 <Jeffrey4l> cool seems everythin else is OK for queens
16:13:48 <Jeffrey4l> next
16:13:58 <Jeffrey4l> #topic ptg summary recap
16:14:05 <Jeffrey4l> #link http://lists.openstack.org/pipermail/openstack-dev/2018-March/128044.html
16:14:18 <Jeffrey4l> thanks pbourke's summry
16:15:02 <Jeffrey4l> that is all we will do in the next cycle for kolla & kolla-ansible project
16:15:24 <Jeffrey4l> if you are interested one of them, feel free to take it
16:15:58 <chason> very nice summry pbourke
16:16:07 <gkadam> pbourke++
16:16:10 <chason> pbourke thanks :D
16:16:40 <Jeffrey4l> if there is anything unclear, please add it into the meeting agenda. and we can talk :D
16:17:55 <caoyuan> :)
16:17:56 <Jeffrey4l> ok next
16:18:02 <Jeffrey4l> #topic kolla-kubernetes project split
16:18:15 <Jeffrey4l> this is talked on the last meeting.
16:18:45 <Jeffrey4l> all of us are agree to split the kolla-kubernetes into tc govermence.
16:19:01 <Jeffrey4l> i tried to talk with tc team.
16:19:25 <Jeffrey4l> the anwser from tc is yes.
16:19:37 <Jeffrey4l> and i also pushed a split team pathc here
16:19:42 <Jeffrey4l> #link https://review.openstack.org/552531
16:20:09 <Jeffrey4l> there are still few question in the patch and i will try to resovle.
16:20:26 <Jeffrey4l> moreover, feel free to add comment on it.
16:21:17 <Jeffrey4l> on the other hand, once kolla-kubernetes is split, any one on the kolla team core can be join the kolla-kubernetes core team.
16:22:16 <Jeffrey4l> then we can re-create the kolla-kuberentes team soon and try to archive the 1.0 goas ASAP
16:22:47 <Jeffrey4l> if you are intrested kolla-k8s, please contact me ;D
16:23:37 <inc0> Jeffrey4l: I answered ttx question
16:23:41 <Jeffrey4l> any question?
16:23:47 <Jeffrey4l> thanks inc0
16:23:48 <gkadam> Jeffrey4l, interested
16:24:57 <Jeffrey4l> gkadam, yeah, this should be good for all kolla projects.
16:25:15 <Jeffrey4l> let us move on
16:25:18 <Jeffrey4l> #topic tarballs.o.o image
16:26:04 <Jeffrey4l> before kolla push a docker registry tar file to tarballs.o.o site
16:26:29 <Jeffrey4l> which is useful for CI jobs. and many end-user use the it too.
16:26:46 <Jeffrey4l> but recently , with zuul v3's support, kolla push image to hub.docker.com site directly.
16:27:05 <Jeffrey4l> so tarballs.o.o sites images are useless and out of update.
16:27:31 <Jeffrey4l> today, i ask for infra team to remove all the tar files in tarballs.o.o
16:27:39 <Jeffrey4l> and left a readme.md file there
16:27:50 <Jeffrey4l> #link http://tarballs.openstack.org/kolla/images/
16:27:50 <chason> Jeffrey4l  Is there a way that users can pull all images them needed from hub.docker.com?
16:28:18 <Jeffrey4l> chason, there is no one shot command.
16:28:36 <Jeffrey4l> either use kolla-ansible pull or write your own  scripts.
16:28:51 <chason> Jeffrey4l Maybe we can implement it. :)
16:29:08 <chason> I prefer tarballs
16:29:33 <chason> because of I can get all images in one step.
16:29:57 <Jeffrey4l> yes. a script in kolla project, which can generate all hub.docker.com image name.
16:30:08 <Jeffrey4l> feel free to implmeent it ;D
16:30:19 <chason> Jeffrey4l Haha, OK
16:30:42 <Jeffrey4l> it is very useful for the guys who can not access internet easily, especially for China guys :D
16:31:09 <chason> Jeffrey4l Exactly
16:31:23 <ktibi> or guys in a parano company !
16:31:46 <sadasu> newbie question. will the plugins-archive methodology work if tarballs.o.o are removed?
16:31:55 <Jeffrey4l> hrm, what's the story ktibi :D'
16:32:12 <chason> Sounds like there are many sufferers. :P
16:32:30 <Jeffrey4l> sadasu, we just remove the docker registry image. and move it to hub.docker.com
16:32:32 <pbourke> o/
16:32:47 <Jeffrey4l> nothing is lost in fact sadasu
16:32:50 <Jeffrey4l> sup pbourke
16:33:08 <pbourke> sorry im late, will catch up on scroll back and have one thing to bring up if there's time
16:33:10 <Jeffrey4l> so i don't think it break anyting
16:33:22 <Jeffrey4l> cool
16:33:36 <ktibi> Jeffrey4l, I work on infra with military restriction, so I've never seen internet :D
16:33:38 <Jeffrey4l> actually, we are run out of agenda now
16:33:39 <sadasu> Jeffrey41: thanks for confirming that
16:34:17 <ktibi> I use an usb key for download my kolla images :D
16:34:18 <gkadam> ktibi, :D
16:34:19 <Jeffrey4l> ktibi, got. so the tool is more useful then i tought
16:34:59 <Jeffrey4l> i heard someone burn the kolla images into a DVD. become usb device is not allowd ;/
16:35:39 <Jeffrey4l> ok. let us move on
16:35:53 <Jeffrey4l> #topic Open Discussion
16:36:08 <Jeffrey4l> any volunteer?
16:36:11 <pbourke> I wanted to just bring some attention to this spec
16:36:12 <duonghq> btw, I think we should have a tool to let user download all Kolla images with a specific tag form dockerhub?
16:36:25 <pbourke> https://review.openstack.org/#/c/550958/
16:36:40 <Jeffrey4l> duonghq, i think it is what chason and ktibi said. right?
16:36:58 <pbourke> would appreciate if people could have a read of it and the poc for keystone that is linked from it
16:37:30 <Jeffrey4l> i like your idea pbourke
16:37:58 <Jeffrey4l> i am agree that image shouldn't take any thing related to deployement
16:38:04 <Jeffrey4l> i will review it later.
16:38:05 <Jeffrey4l> thanks
16:38:06 <pbourke> thanks Jeffrey4l
16:38:16 <pbourke> it should be fairly low impact overall
16:38:27 <pbourke> that's all I have for today :)
16:38:41 <duonghq> added to my review list, I will take it tomorrow
16:38:52 <duonghq> thank Paul
16:39:26 <mgoddard_> I have some slides from a presentation I gave recently on kayobe: https://www.slideshare.net/MarkGoddard2/to-kayobe-or-not-to-kayobe
16:39:53 <Jeffrey4l> mgoddard_, great
16:40:07 <gkadam> mgoddard_, nice one!
16:40:14 <mgoddard_> #link https://www.slideshare.net/MarkGoddard2/to-kayobe-or-not-to-kayobe
16:40:52 <mgoddard_> I've also been working on a job for testing bifrost deployment
16:41:05 <mgoddard_> https://review.openstack.org/549775
16:41:13 <mgoddard_> It's now passing
16:41:21 <Jeffrey4l> mgoddard_, is there demonstration video?
16:41:59 <mgoddard_> Jeffrey4l: sadly not - no recording. It was a short demo
16:42:17 <ktibi> mgoddard_, great slides :D
16:42:42 <Jeffrey4l> mgoddard_, thanks
16:43:16 <Jeffrey4l> will kayobe join the openstack community/
16:43:43 <mgoddard_> Jeffrey4l: https://git.openstack.org/cgit/openstack/kayobe :)
16:44:01 <Jeffrey4l> aha, it is already there.
16:44:19 <mgoddard_> We're becoming an OpenStack-related project, just working on a deployment CI job
16:44:35 <Jeffrey4l> cool
16:44:38 <mgoddard_> https://review.openstack.org/551986
16:44:58 <mgoddard_> so kolla-ansible will see some additional CI testing
16:46:01 <Jeffrey4l> great
16:46:10 <Jeffrey4l> thanks mgoddard_
16:46:24 <Jeffrey4l> any othe discussion?
16:46:27 <duonghq> o/
16:46:36 <duonghq> #link https://review.openstack.org/#/c/552445/
16:46:47 <duonghq> this ps is the last ps of the blueprint
16:47:16 <duonghq> so afterthat, which work I should do before close the bp? (one patch for updated documentation?)
16:47:19 <Jeffrey4l> i will check it after the meeting. nice jobs
16:47:33 <duonghq> thank Jeffrey4l
16:47:46 <Jeffrey4l> duonghq, add a release note?
16:48:09 <chason> duonghq one patch for updated documentation is a good idea!
16:48:11 <Jeffrey4l> duonghq, doc should be added
16:48:21 <duonghq> Jeffrey4l,  the reno is added one patch before
16:48:32 <Jeffrey4l> cool
16:48:33 <duonghq> the patch is for projects added in Q
16:49:10 <duonghq> https://review.openstack.org/#/c/398685/22/releasenotes/notes/specify-task-become-84f83707f612bcf3.yaml
16:49:12 <duonghq> this file
16:49:52 <Jeffrey4l> should we add a nother reno to indicate that become support all tasks now?
16:50:30 <duonghq> so which category should the note should fall on?
16:50:45 <Jeffrey4l> how about features?
16:50:46 <duonghq> I don't have idea about this
16:51:21 <duonghq> the current feature is "Increase security by add "become" to only n....."
16:51:39 <duonghq> I think it's already cover the patch
16:51:40 <Jeffrey4l> wait. "the patch is for projects added in Q", not Q, it is Rocky
16:51:58 <Jeffrey4l> ^^ based on this, another reno is not required.
16:52:06 <ktibi> I have a point, but just to have your opinion
16:52:30 <Jeffrey4l> plase ktibi
16:52:34 <duonghq> Jeffrey4l,  the patch will be merged in R, but for services added in Q, sorry for the confusion
16:52:37 <duonghq> please ktibi
16:52:45 <ktibi> as I said above, I have strong security constraints. So I try to work on security in kolla and for now, I have work I guess
16:52:52 <Jeffrey4l> i see, thanks
16:53:01 <ktibi> like SSL on rabbitMQ or SSL on internal network
16:53:44 <Jeffrey4l> ktibi, that is awesome. we can ask help from security team if it is neccessary.
16:53:45 <ktibi> for now, kolla can't olve these problems
16:53:46 <duonghq> ktibi, awesome, could you draft bp for those
16:53:55 <duonghq> even a spec
16:54:00 <duonghq> and we will work on this
16:54:31 <Jeffrey4l> duonghq, +1
16:54:45 <ktibi> yes, I'll make a blueprint. but what do you think about that ? because some people say internal network must be without SSL (perf issue) ?
16:55:26 <duonghq> ktibi, Kolla should address as much as requirements from user as possible (especially security issues)
16:55:42 <Jeffrey4l> i think this is a choice left for operator.
16:56:08 <ktibi> duonghq, yes because I think a lot of company can't consider kolla for security reason :/
16:56:17 <Jeffrey4l> which one is important? perf or security. i think different environement may have different reasult.
16:56:34 <duonghq> Jeffrey4l, +1, and we should provide options for both cases
16:57:13 <Jeffrey4l> btw, in kubernetes ssl is necessary for all compomenet.
16:58:10 <duonghq> Jeffrey4l, [OT], should we re-prioritize our bps in next meeting for this cycle?
16:58:42 <Jeffrey4l> duonghq, sure. before that, we have to created the bp based on pbourke's summary
16:59:06 <duonghq> Jeffrey4l, sure
16:59:27 <Jeffrey4l> we run out of time.
16:59:40 <Jeffrey4l> thanks for coming.
16:59:49 <Jeffrey4l> let us end the meeting.
16:59:50 <caoyuan> np
16:59:51 <gkadam> Jeffrey4l, thanks!
16:59:54 <Jeffrey4l> have a nice day :D
16:59:54 <caoyuan> thanks
16:59:59 <Jeffrey4l> #endmeeting