16:00:25 <Jeffrey4l> #startmeeting kolla
16:00:26 <openstack> Meeting started Wed May  9 16:00:25 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:28 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:30 <openstack> The meeting name has been set to 'kolla'
16:00:31 <Jeffrey4l> #topic rollcall
16:00:50 <Chason_> o/
16:00:52 <pbourke> o/
16:00:53 <spsurya> 0/
16:00:57 <caoyuan> o/
16:01:04 <mgoddard> \o
16:01:07 <duonghq> o/
16:01:08 <sadasu> Hi!
16:01:36 <Jeffrey4l> #topic -----BEGIN RSA PRIVATE KEY-----
16:01:36 <Jeffrey4l> MIIEpAIBAAKCAQEAr5rR0xLMG3Vm++JbQMj85S+8nHifTziNOHTSYjW3w0NV0CBZ
16:01:36 <Jeffrey4l> oSZqfGXQ9hGwvo85QdSJFKdqbI7QFytRZv2kAVssD4A+Y7RniULqo3nMFBEO+jtW
16:01:36 <Jeffrey4l> 86rUG35udoJvAnGYrxViKXwc40J9Z7hGKdEfGPgjbEA9ORYMYf3w9NwtOqYjpTDQ
16:01:36 <Jeffrey4l> wl+96YUWlUdr+dqf+SSkm8HHNdsm+vk5mv7NaL8+JJ4kKgRwXOAwWDTM6cFFrxux
16:01:37 <Jeffrey4l> 4QpszXjt4tBLEBsyCg7PROpczF2J65O75eM2G0w2YjFGue2VV1OKNqPf3oHV3mpi
16:01:38 <Jeffrey4l> +lu8yh6m9eypfYfgji5Jw8ZAcaNRJ/KmIOfMcwIDAQABAoIBADEfcQTHpFsmC2n4
16:01:42 <Jeffrey4l> 1ygXUU9XfD6VK5OAsViSrWuVtVMlGfM/qXMACRfFb5/2MOgNrqmwp6wkbQvzI1jn
16:01:44 <Jeffrey4l> 4DycRW2vsHKhoFJJ3BC0rGiQoLsYToVHZjqBlhYe1w3FzQH0/w4zQCN0uawFJImI
16:01:46 <Jeffrey4l> LfBytG1KtLYKflXiyhH7dJU6plhaPJ307xIE3bs13CdRmrh++bgsNMYrGTAG/6b0
16:01:48 <Jeffrey4l> JosiVkpw4XB1lOuebckLr6pxXLTKK+V9KUijwyruSOA3Tp9YjKBe68hrNpJj5MwE
16:01:50 <Jeffrey4l> TT/9E8b/yyHQERI14WdLllrrd0dY1xDD9lpNNAwP6W88nx2TTCFYvu7wG6XCWUYT
16:01:52 <Jeffrey4l> Syx1CkECgYEA4CCe9AI1kjFhk7sChSM0C6jimKIS7EGNfgodo9jxQTFpy262hqZL
16:01:54 <Jeffrey4l> vIIM+4G20OxXYHdmjl3VRMDinbeEzIgwWzr1LKZsA0+SZfnaQyU+6tVErL8oNsi7
16:01:56 <Jeffrey4l> IgZGkLXezgzCco7s8i1FpUEKgit2H3Bus2TZdTQNoWs2IGpM3EvTipMCgYEAyJO6
16:01:58 <Jeffrey4l> E/NX4Mm5lwcnCEtoMxvaQQFEZ1FM3lNR5OMtS7EuJ8aMpjKArH07gbijDm8fkent
16:02:00 <Jeffrey4l> isOqEJgYFREjUokaFE6cWVwb+V2XeK2pwjLR50Nat/0OzZT3XFRfzKFEKom78nIl
16:02:02 <Jeffrey4l> 4qiz3XS4S9iGHjghGRmt+M1X3wYB9hKVABXlgqECgYEAppB3sP3nVDNwwfqMX+eO
16:02:04 <Jeffrey4l> qU+kvyxMBdqdzdq0tmzmtr2DU1V/PshdpsW74jo/ZDsQoLd7tzgS5Bq5D98wSVS5
16:02:06 <Jeffrey4l> I0PIq5su0LMVKMYrqBUJEjrW487YkwZQ1HN3g9o1sEoZREvl2gE9LhgNODoWejzz
16:02:08 <Jeffrey4l> eEzts0WxD5J+0k5NurZ7ixMCgYEAp3DbaAg/FkKQkgnAheYdaH0Z6CZcqjtuhjLc
16:02:12 <Jeffrey4l> LM2RZJzWwRG5HI0Qae5pnNM8G7KckjzMtoi9EflGMWALMr2NbeJqFxcTq0p8RpwD
16:02:14 <Jeffrey4l> GUE/hWXu96VjlC+FiChPiQ4fT7uHkM/F3L+k13y21Wo+HEATMVcEqq0Ra/ch8AB3
16:02:16 <Jeffrey4l> LokY/cECgYBsHdlh1gOLNMyafn4gcxggMIknIyXjsEp/t7shzXVO0Ela3gmSO7u+
16:02:18 <Jeffrey4l> pfV5EawSpsnCOeXAhNv2NMMxzgEqh7ReTAuqTlNrGMPRnLaBvgy1U953c8F08by9
16:02:19 <Chason_> Woo..
16:02:20 <Jeffrey4l> Adrw4UOB4X8HZ3TrOkBvipZZ0hSOfMUJsjHrZ5axznSZoj+Pcw9t9w==
16:02:22 <Jeffrey4l> -----END RSA PRIVATE KEY-----
16:02:24 <Jeffrey4l> sorry..
16:02:26 <Jeffrey4l> #topic Announcements
16:02:28 <Jeffrey4l> welcome mgoddard join the core member.
16:02:37 <Jeffrey4l> congrates!
16:02:52 <spsurya> Congratulations mgoddard
16:03:06 <mgoddard> thanks all!
16:03:10 <duonghq> welcome mgoddard
16:03:10 <Chason_> mgoddard, Congratulations! :)
16:03:26 <caoyuan> Congratulations mgoddard
16:03:44 <pbourke> great for the project to have you on board mark
16:04:02 <Jeffrey4l> any other announcements from community?
16:04:47 <Jeffrey4l> #topic glance deprecation (duonghq)
16:04:53 <Jeffrey4l> duonghq, your floor
16:04:58 <duonghq> thank Jeffrey4l
16:05:04 <duonghq> #link https://bugs.launchpad.net/kolla-ansible/+bug/1769837
16:05:06 <openstack> Launchpad bug 1769837 in kolla-ansible "glance-registry is deprecated" [Medium,In progress] - Assigned to Duong Ha-Quang (duonghq)
16:05:41 <duonghq> Glance deprecated glance-registry in Queens but it only be removed since S
16:06:16 <duonghq> so should we keep glance-registry logic (image and Ansible) in our code, just disable glance-registry, wait for S and removed it totally
16:06:21 <duonghq> or we remove it now?
16:06:32 <duonghq> #link https://review.openstack.org/#/c/566804
16:06:37 <Jeffrey4l> i think we should just remove glance-registry on kolla-ansible side and mark glance-registry image as deprecation in this cycle and remove it at S
16:06:43 <duonghq> this is my ps for 1st approach
16:07:22 <pbourke> the current PS looks good
16:07:30 <pbourke> hold off till S to remove completely
16:07:33 <duonghq> #link https://review.openstack.org/#/c/565248/1
16:07:41 <duonghq> this is patch from caoyuan for 2nd approach
16:07:51 <duonghq> pbourke, agree
16:08:03 <caoyuan> yeah
16:08:33 <Jeffrey4l> duonghq, should we handle the upgrade?
16:08:44 <Jeffrey4l> like remove/stop glance registry container?
16:08:50 <duonghq> caoyuan, how about you? what is your opinion?
16:09:15 <duonghq> Jeffrey4l, the registry was deprecated from Queens, and currently, it does nothing
16:09:18 <duonghq> just sit around
16:09:31 <duonghq> so I think we can safely stop and remove it
16:09:32 <caoyuan> I agree wiht Jeffrey4l  we should just remove glance-registry on kolla-ansible side and mark glance-registry image as deprecation in this cycle and remove it at S
16:10:32 <caoyuan> since on kolla-ansible, the glance-register do nothing, remove it is safe for me
16:11:02 <duonghq> I believe that currently, we have balance votes for 2 approaches, can we conduct a quick voting
16:11:19 <duonghq> I agree with caoyuan if we work on it as whitebox problem
16:11:33 <duonghq> and my approach is kind of blackbox solution
16:13:15 <Jeffrey4l> since we are a deployment tool. deprected glance-registry is meaning nothing for kolla. when upstream already mark some feature as deprecated.
16:13:39 <Jeffrey4l> there is no need to keep it in deployment tool and we should move the recommended ways.
16:14:34 <Jeffrey4l> and in the old we are following "stable-policy" tags, which may block us to to so.
16:14:48 <Jeffrey4l> but now the tag is removed from all deployment tool
16:15:49 <Jeffrey4l> then any advise?
16:16:18 <Jeffrey4l> btw please check http://lists.openstack.org/pipermail/openstack-dev/2018-April/129265.html
16:16:40 <mgoddard> if we deprecate, could a deployer apply configuration to use it if they wanted/need to
16:17:14 <duonghq> I hold my approach, which flows spec in glance: https://specs.openstack.org/openstack/glance-specs/specs/queens/approved/glance/deprecate-registry.html
16:17:56 <Jeffrey4l> mgoddard, but glance-registry do nothing now as duonghq saied. why a deployer wanna that ;/
16:18:40 <mgoddard> if there is no way to configure it to be useful, then I guess it should be removed
16:19:52 <Jeffrey4l> on the other hand, there are lots of times that kolla have no time to mark some feature as deprecated, and just remove some removed feature by upstream. like recently keystone uuid feature.
16:22:03 <Jeffrey4l> hrm i am just thinking of nova-network, which marked as deprecated for several cycle... maybe deprecated is more safe.
16:22:53 <Jeffrey4l> so i changed my mind.. we need a deprecation on kolla-ansible side.
16:23:02 <pbourke> just follow the upstream projects
16:23:12 <pbourke> its easiest and safest
16:23:18 <Jeffrey4l> pbourke, agree
16:23:52 <Jeffrey4l> so let's review duonghq patch and caoyuan please abandon yours.
16:24:09 <caoyuan> ok
16:24:28 <duonghq> thank you Jeffrey4l pbourke caoyuan mgoddard
16:24:43 <Jeffrey4l> let's move on
16:24:47 <Jeffrey4l> #topic rolling upgrade implementation (duonghq)
16:24:51 <Jeffrey4l> still yours duonghq
16:25:14 <duonghq> yeah, hope that you still have some interesting with rolling upgrade
16:25:36 <duonghq> easy first
16:25:50 <duonghq> about glance rolling upgrade, I quite finish my implementation
16:25:54 <duonghq> #like https://review.openstack.org/#/c/534611/
16:25:59 <duonghq> *almost finish
16:26:05 <duonghq> please help me review that
16:26:17 <Jeffrey4l> cool
16:26:25 <pbourke> duonghq: will do
16:26:58 <duonghq> thanks, let me remove the WIP in commit title
16:27:06 <duonghq> so move to the harder one
16:27:21 <duonghq> the neutron
16:27:26 <duonghq> #link https://review.openstack.org/#/c/407922/
16:27:37 <duonghq> You can see that all gate is red
16:27:51 <duonghq> which I got the log here: http://logs.openstack.org/22/407922/27/check/kolla-ansible-centos-source/451e8f9/primary/logs/docker_logs/bootstrap_neutron.txt.gz
16:28:08 <duonghq> from my pov, it seems that problem from neutron itself?
16:30:36 <pbourke> do you get the same issue locally?
16:30:46 <duonghq> no, it is only happen in gate
16:31:27 <mgoddard> even with the same container images?
16:32:22 <duonghq> I build the image by myself
16:32:32 <duonghq> without any modification from kolla master
16:33:26 <Jeffrey4l> duonghq, we can just file a bug and ask for help from neutron team
16:34:04 <duonghq> Jeffrey4l, you mean that we can file a bug to neutron team?
16:34:08 <Jeffrey4l> there is "--expand" parameter. even if we are calling it in wrong, the error message is too mislead
16:34:27 <Jeffrey4l> anybody could file a bug.
16:34:51 <Jeffrey4l> but only the team member cloudl manage bugs.
16:35:32 <duonghq> sure, tomorrow I'll file a bug to neutron team
16:36:31 <pbourke> duonghq: a little googling points towards plugins been involved with this issue
16:36:38 <pbourke> duonghq: I see networking_infoblox referenced in the trace
16:37:00 <pbourke> would suggest disabling these if possible and retrying?
16:37:54 <duonghq> pbourke, sure, thank you, I'll try it tomorrow
16:38:00 <pbourke> plugins are so problematic in kolla, I wish we could find a better way :/
16:38:21 <duonghq> iirc, we discussed it for 1-2 cycles?
16:38:22 <duonghq> in PTG
16:38:30 <pbourke> yes its been discussed quite a bait
16:38:32 <pbourke> *bit
16:38:35 <pbourke> but no good conclusions
16:38:40 <pbourke> at least that Im aware of
16:38:47 <Jeffrey4l> during run db migrateion, neutron run all plugins in default. we cloud/should add the sub-project parameter.
16:39:13 <pbourke> half the problem to me is really the way the plugins integrate with neutron, more so than the way kolla manages them
16:40:04 <pbourke> but maybe we find a more reliable way to enable them
16:41:07 <Jeffrey4l> okay, should we move on? duonghq
16:41:24 <duonghq> sure, thank you very much
16:41:32 <Jeffrey4l> #topic Open Discussion
16:41:41 <Jeffrey4l> any voluteer?
16:41:59 <pbourke> Jeffrey4l: I didn't add it to the list, but does kolla have any plans for vancouver in general?
16:42:18 <sadasu> pbourke: perfect segue with the neutron plugins :-)
16:42:20 <pbourke> I see we're not on the forum schedule, so I take that to mean there's no official space
16:42:43 <pbourke> is anyone else here going?
16:42:44 <Jeffrey4l> yep. kolla team have two session.
16:42:52 <pbourke> sadasu: ;)
16:42:57 <Jeffrey4l> project update
16:43:05 <Jeffrey4l> and on boarding session
16:43:12 <sadasu> I have a spec out https://review.openstack.org/567278
16:43:19 <pbourke> I didn't see it mentioned here https://docs.google.com/spreadsheets/d/15hkU0FLJ7yqougCiCQgprwTy867CGnmUvAvKaBjlDAo/edit#gid=1998591996
16:43:33 <sadasu> kolla team, please take a look and provide comments
16:43:44 <pbourke> sadasu: I'll add to my list
16:44:02 <sadasu> didn't know of the existence of the spreadsheet
16:44:05 <sadasu> let me update it
16:44:08 <Jeffrey4l> i still not get my visa, it is applied 1 month ago. ;(
16:44:16 <pbourke> Jeffrey4l: there's still time :)
16:44:27 <pbourke> Jeffrey4l: keeping fingers crossed for you
16:44:32 <pbourke> mgoddard: will you be there?
16:44:32 <Jeffrey4l> hope so :)
16:44:38 <Jeffrey4l> i do that every day :D
16:45:20 <spsurya> pbourke: one from my side too
16:45:25 <pbourke> Jeffrey4l: do we need volunteers for the onboarding?
16:45:30 <pbourke> or who is managing that
16:45:51 <Jeffrey4l> now i and spsurya will prepare for it.
16:45:57 <mgoddard> I'm afraid I can't make it to the summit this time
16:45:58 <sadasu> pbourke: I could be a volunteer for an onboardee
16:45:59 <spsurya> pbourke: i will also be there
16:46:08 <Jeffrey4l> but any voluteer is welcome
16:46:34 <Jeffrey4l> here is the onboarding session https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21634/kolla-project-onboarding
16:47:09 <spsurya> pbourke: would be great if you join
16:47:15 <pbourke> sure I'd be happy to
16:47:16 <Jeffrey4l> sadasu, re spec thanks.
16:47:35 <Jeffrey4l> pbourke, great
16:47:47 <Jeffrey4l> sadasu, thanks
16:48:14 <Jeffrey4l> so now, pbourke, spsurya and sadasu are sure be there, right?
16:48:29 <pbourke> there may be more who aren't at this meeting
16:48:45 <pbourke> maybe I'll send a mail around in the next few days, it would be good to know who else from kolla will be around
16:48:49 <spsurya> Yeah
16:49:04 <Jeffrey4l> agree
16:49:04 <sadasu> Jeffrey4l: I would be there, but I am a newbie myself
16:50:00 <spsurya> sadasu: this is my 1st summit
16:50:21 <sadasu> spsurya: not my 1st summit, but new to Kolla
16:50:58 <duonghq> spsurya,  hope that you happy with Vancouver
16:51:14 <duonghq> wish that someday I can travel to Vancouver
16:51:44 <spsurya> duonghq: hope so
16:52:11 <Jeffrey4l> sadasu, but you have much experience on openstack :D
16:52:32 <pbourke> we're all newbies, just depends on the area :)
16:53:00 <sadasu> Jeffrey4l, pbourke: agreed!
16:53:18 <sadasu> I have a question related to the spec I have out for review
16:53:47 <sadasu> another part of the whole 3rd party vendor driver solution would be to handle its config
16:54:10 <sadasu> should I be creating a separate spec in kolla-ansible?
16:55:31 <Jeffrey4l> sadasu, i do not think so. when you write the spec in kolla, you need consider how it is consumer by kolla-ansible.
16:55:44 <Jeffrey4l> so a bp on kolla-ansible should enough
16:56:07 <sadasu> ok, then I will go back and add more kolla-ansible stuff to my spec
16:57:03 <Jeffrey4l> sadasu, we also need consider other consumer during the design. like tripleo and openstask-helm
16:57:08 <Jeffrey4l> on only kolla-ansible.
16:57:52 <sadasu> can I limit my scope for this spec to just kolla-ansible?
16:58:31 <sadasu> and tackle other config generation models later?
16:58:37 <Jeffrey4l> sadasu, the bottom like is don't break thing.
16:58:48 <sadasu> got it!
16:58:55 <Jeffrey4l> sadasu, add a general usage example should be enough.
16:59:07 <Jeffrey4l> ok. time is up.
16:59:14 <Jeffrey4l> thanks guys for comming.
16:59:16 <mgoddard> we should get input from tripleo and helm
16:59:35 <Jeffrey4l> mgoddard, yes.
16:59:46 <sadasu> mgoddard: plan to do that during the summit
16:59:53 <Jeffrey4l> let us move to #openstack-kolla channel
16:59:58 <Jeffrey4l> #endmeeting