14:01:13 <devkulkarni> #startmeeting Solum Team Meeting 14:01:14 <openstack> Meeting started Wed Feb 8 14:01:13 2017 UTC and is due to finish in 60 minutes. The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:16 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:18 <openstack> The meeting name has been set to 'solum_team_meeting' 14:01:19 <caowei> hi dev 14:01:28 <zhurong> o/ 14:01:38 <devkulkarni> hi caowei, zhurong 14:01:51 <devkulkarni> great to see you 14:02:14 <caowei> me too 14:02:45 <devkulkarni> lets wait for a minute to see if others join 14:06:44 <devkulkarni> here is agenda for today's meeting: https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2017-02-08_1400_UTC 14:07:09 <devkulkarni> #topic Announcements 14:07:26 <devkulkarni> 1) PTL election results are out 14:07:59 <devkulkarni> http://lists.openstack.org/pipermail/openstack-dev/2017-February/111769.html 14:08:31 <devkulkarni> 2) Boston summit submission deadline extended 14:08:43 <devkulkarni> http://lists.openstack.org/pipermail/openstack-dev/2017-February/111758.html 14:09:15 <devkulkarni> 3) Boston summit submissions: We have submitted two talk proposals 14:10:27 <devkulkarni> Talk 1 focuses on Solum and Zun integration, Talk 2 focuses on comparing different container deployment strategies from our experiences in Solum 14:11:37 <devkulkarni> all the talks will be available I believe on Feb 16 for voting purposes 14:12:03 <devkulkarni> zhurong, caowei: will let you know when the voting opens 14:12:14 <zhurong> thx 14:12:27 <caowei> ok 14:12:51 <devkulkarni> have you submitted any talks? 14:13:29 <caowei> i have two problems 14:13:30 <caowei> 1. https://bugs.launchpad.net/solum/+bug/1662457 14:13:30 <openstack> Launchpad bug 1662457 in Solum "solum devstack keystone v3 support" [Undecided,New] 14:13:30 <caowei> 2. https://review.openstack.org/#/c/430080/ 14:13:47 <devkulkarni> caowei: looking 14:15:38 <devkulkarni> caowei: lets discuss the image_builder_service first as we have some comments on it on the patch 14:16:28 <devkulkarni> did you see zhurong's point about image_builder_service being referenced in pipeline resource and my comment on it 14:17:16 <caowei> yes , i saw 14:17:34 <devkulkarni> caowei: so what do you think 14:17:46 <devkulkarni> caowei: btw, good bug report about keystone v3 support 14:18:03 <zhurong> yep, we should support it 14:18:12 <devkulkarni> zhurong: can you triage the bug in your setup using the steps that caowei has outlined 14:18:16 <zhurong> this is not a bug, this indeed a BP 14:18:23 <devkulkarni> sure 14:18:58 <devkulkarni> zhurong: so you have also ran into this issue about keystone v3 I guess 14:19:24 <zhurong> I just keep the v2 enable 14:19:38 <zhurong> If disable V2, there will can not work 14:19:55 <devkulkarni> zhurong: sure.. 14:21:14 <devkulkarni> caowei: can you elaborate on your need for v3 a bit 14:21:53 <caowei> Kolla only supports Keystone v3 till now 14:21:56 <zhurong> devkulkarni I think we exactly need to support V3 14:22:03 <devkulkarni> caowei: ah I see 14:22:13 <zhurong> Not only for Kolla 14:22:44 <caowei> I agree 14:22:46 <devkulkarni> zhurong: sure. yeah, that makes sense eventually 14:23:03 <devkulkarni> caowei, zhurong: agree 14:23:22 <devkulkarni> we would need to understand what all things are required for supporting v3 14:23:52 <devkulkarni> do any of you know/have experience with v3? 14:24:43 <devkulkarni> lets do this.. we can create etherpad where we can list out things that need to be done to add v3 support 14:24:52 <zhurong> I will register a BP, And will to do it 14:25:28 <devkulkarni> https://etherpad.openstack.org/p/solum-keystone-v3 14:25:34 <devkulkarni> zhurong: that would be perfect 14:26:21 <devkulkarni> if any of us find any relevant information, we can add that to the etherpad 14:26:50 <devkulkarni> any more thoughts on the keystone v3 topic? 14:28:34 <zhurong> caowei, Kolla had disable v2? 14:29:01 <caowei> Yes 14:30:55 <devkulkarni> on the topic of builder service.. 14:31:07 <devkulkarni> caowei, zhurong: thoughts? 14:31:24 <caowei> most of projects support v3 14:32:56 <zhurong> I vote for stay the same 14:33:09 <zhurong> yep, we need to support V3 14:34:36 <devkulkarni> zhurong, caowei: sure. lets get back on this topic once zhurong has had a chance to create the BP and had a chance to research on what all is required to support v3 14:35:11 <devkulkarni> on the topic of builder service, what are your thoughts? 14:35:45 <zhurong> I vote for stay the same 14:36:51 <devkulkarni> you mean, keep the builder service. Yeah, that is a simpler option 14:37:23 <devkulkarni> I am fine with it as well.. but I thought caowei's kolla-ansible patch was running into some issues because of that 14:37:40 <devkulkarni> caowei: can you share that patch? 14:39:04 <devkulkarni> caowei: is it this: https://review.openstack.org/#/c/420407/ 14:41:11 <caowei> It can be kept, but we need to explain the reason. 14:41:12 <devkulkarni> zhurong: what are the arguments to keep the builder service? 14:42:09 <devkulkarni> agree caowei.. if we are not using it, then it unnecessarily complicates deployment tools 14:43:03 <zhurong> If caowei can do the clean work, I agree 14:43:09 <devkulkarni> caowei, zhurong: I think we can remove the builder service as long as we do not break the pipeline api 14:43:23 <devkulkarni> zhurong: yes 14:44:02 <devkulkarni> see, another view can be to remove the pipeline resource itself.. but that is too big a work right now 14:44:14 <devkulkarni> we should not worry about that 14:44:49 <devkulkarni> we should fold that resource in some how in our regular api 14:45:01 <devkulkarni> then we can cleanly remove any references to the builder service 14:45:13 <devkulkarni> so that the kolla-ansible role patch can be merged 14:45:33 <devkulkarni> does that make sense? 14:48:22 <devkulkarni> caowei: would you be able to take a stab at this? 14:48:46 <devkulkarni> basically, look at how we can fold the pipeline resource in our current api 14:49:04 <caowei> zhurong: I think I have no idea to clean all of them. 14:49:18 <devkulkarni> I think it should be doable 14:50:18 <devkulkarni> caowei: I think the changes would be restricted only to the parts of the code where we refer to the builder service 14:50:39 <devkulkarni> if you look here https://github.com/openstack/solum/search?utf8=%E2%9C%93&q=build_service_url 14:50:43 <devkulkarni> there are not that many 14:51:20 <devkulkarni> the main changes are actually to pipeline_handler.py and mistral_actions/builder.py 14:52:00 <caowei> I will try 14:52:10 <devkulkarni> see, the idea at that time was that the pipeline resource would talk to mistral which will invoke the builder service 14:52:47 <devkulkarni> the pipeline resource itself is I think available under our current api already (so, my earlier point of folding the pipeline resource within our api might be invalid -- please check) 14:52:58 <devkulkarni> the current picture is as follows 14:53:24 <devkulkarni> pipeline resource (available in solum api) -> mistral_actions -> builder service 14:54:10 <devkulkarni> if we get rid of builder service, we can make mistral_actions call back in our api itself to perform the image builds 14:54:30 <devkulkarni> at least, that's how it would be conceptually 14:56:13 <devkulkarni> caowei: we can try to at least get to the point where it would be possible in the future to add mistral integration in our build step if someone is interested 14:57:09 <devkulkarni> so, if you can provide a clean point for the mistral_actions/builder.py to invoke an endpoint in our api that would be sufficient 14:58:26 <devkulkarni> caowei, zhurong: another thought is we get rid of builder_service immediately without worrying about mistral stuff right now 14:58:38 <devkulkarni> we create a bug/bp to track the work 14:59:04 <devkulkarni> that way, the kolla-ansible patch can land 14:59:16 <devkulkarni> we are almost at the end of our meeting time 14:59:30 <devkulkarni> lets continue discussion after the meeting in solum channel 14:59:54 <zhurong> sure 15:00:03 <caowei> ok 15:00:08 <devkulkarni> #endmeeting