17:00:12 #startmeeting Solum Team Meeting 17:00:13 Meeting started Tue Mar 29 17:00:12 2016 UTC and is due to finish in 60 minutes. The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:16 The meeting name has been set to 'solum_team_meeting' 17:00:20 #topic Roll Call 17:00:26 Devdatta Kulkarni 17:02:04 james li 17:07:29 Ashish Jain 17:07:35 hi ashishjain 17:07:35 hi devkulkarni good morning 17:07:36 lets wait for few minutes to give others to join 17:07:37 here is the agenda for today's meeting: https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2016-03-29_1700_UTC 17:07:38 I think vijendar is out today 17:07:38 james_li mentioned earlier on solum irc that he will be joining 17:07:38 okay 17:07:39 o/ 17:07:39 hi adrian_otto 17:07:39 hi 17:07:39 we have ashishjain also with us 17:07:39 just giving few minutes for folks to join 17:07:39 hi adrian_otto 17:07:39 hi ashishjain 17:07:39 here is the agenda for today's meeting: https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2016-03-29_1700_UTC 17:07:42 hi vijendar 17:07:42 sorry for joining late 17:07:42 o/ 17:07:46 alright .. I think we can get started 17:07:46 hi james_li 17:08:04 hi devkulkarni 17:08:08 #topic Announcements 17:08:14 1) PTL Elections 17:08:23 • PTL election results: http://lists.openstack.org/pipermail/openstack-dev/2016-March/090422.html 17:08:44 you can find the results of the PTL election for newton cycle ^^ 17:09:16 I will be continuing as PTL for our team for Newton cycle 17:09:28 we did not have elections this time around 17:09:59 congratulations devkulkarni for being appointed as PTL for solum 17:10:07 thanks ashishjain 17:10:17 :-) And there was much rejoicing!! 17:10:22 it was because of all of you's support 17:10:29 thanks adrian_otto :) 17:11:02 I hope we can continue to make our project stronger together in this cycle as well 17:11:13 2) Currently TC candidacy is open 17:11:17 http://lists.openstack.org/pipermail/openstack-dev/2016-March/090421.html 17:11:34 If any of you want to join the TC, this is your chance 17:11:38 what is TC candidacy? 17:11:47 ashishjain: TC is the technical committee 17:11:56 TC for solum? 17:11:59 it basically oversees all of the openstack 17:12:05 aah okay 17:12:06 no, TC is for the entire openstack 17:12:14 it has really broad agenda 17:12:23 what is the role these guys play? 17:12:27 okay 17:12:34 strategic, long term viability, policy, etc. issues are what is under their purview 17:12:48 okay 17:13:07 ashishjain: it is instructive to read about the position statements of the various candidates 17:13:42 it helps to get idea of what are the broad issues that the openstack community is thinking about and what each candidate is planning to resolve/address those 17:14:00 3) Devstack gate is broken 17:14:05 https://bugs.launchpad.net/solum/+bug/1563019 17:14:05 Launchpad bug 1563019 in Solum "devstack-gate-failure-due-to-screen-n-dhcp-log-not-found" [Critical,New] - Assigned to Devdatta Kulkarni (devdatta-kulkarni) 17:14:13 Yet another gate failure 17:14:44 let me talk about this more when we discuss bugs and reviews 17:14:57 4) Austin summit tracks 17:15:02 http://lists.openstack.org/pipermail/openstack-dev/2016-March/090606.html 17:15:10 Solum Fishbowl session: April 28, Thursday, 4:10 - 4:50 17:15:15 Solum Work room: April 28, Thursday, 5:00 - 5:40 17:15:21 http://lists.openstack.org/pipermail/openstack-dev/attachments/20160328/23a406bf/attachment.pdf 17:15:42 the organizing committee sent out the track and space allocation couple of days back 17:15:53 we have got one fishbowl and one work room session 17:16:02 both are back-to-back on Thursday 17:16:06 👍 17:16:10 yep 17:16:11 do you have plans for what to discuss? 17:16:31 adrian_otto: sort of.. https://etherpad.openstack.org/p/solum-austin-summit-planning 17:16:38 we started creating etherpad 17:17:17 all, please add to the etherpad any/all items that you think are important for us to address as a team 17:17:51 ashishjain: I think our presentation is also on Thursday, right? 17:17:59 yes 17:18:03 9:00 AM 17:18:10 so thursday is going to be hectic 17:18:46 we can discuss more about the summit in the open discussion 17:19:15 do any team members have any announcements to make? 17:20:00 alright, let continue to the next topic 17:20:12 #topic Review Action Items 17:20:23 (done) devkulkarni to tag Mitaka release: https://review.openstack.org/#/c/296032/ 17:20:36 the patch has been merged 17:21:04 there are two other patches that probably need to be merged this week 17:21:09 these are solum patches 17:21:25 lets talk about those next 17:21:38 #topic Patches for Review 17:22:11 We have two patches in our queue that are related to the mitaka release 17:22:14 - https://review.openstack.org/#/c/296644/ 17:22:23 - https://review.openstack.org/#/c/296643/ 17:22:38 both these patches are currently failing on the devstack gate 17:22:57 I spent yesterday trying to figure out the issue and a workaround 17:23:24 here is a bug report about this: 17:23:37 https://bugs.launchpad.net/solum/+bug/1563019 17:23:37 Launchpad bug 1563019 in Solum "devstack-gate-failure-due-to-screen-n-dhcp-log-not-found" [Critical,New] - Assigned to Devdatta Kulkarni (devdatta-kulkarni) 17:23:48 at a high-level the issue is this 17:24:25 the gate script tries to upload log file for screen-n-dhcp.txt but that file is not available 17:24:44 so it gets FileNotFoundException 17:24:59 The issue seems to be that the screen-n-dhcp.txt file is not created and the Jenkins plugin code that uploads all the log files to logs.openstack.org fails. 17:25:06 Most possible cause of this issue might be that the plugin code started doing strict checking for file existence since earlier too there used to be no screen-n-dhcp.txt generated but it was not a problem. For instance, check the following logs from a merged patch 17:25:20 http://logs.openstack.org/40/293640/6/check/gate-solum-devstack-dsvm/dd0b1f5/logs/ 17:25:24 (merged) https://review.openstack.org/#/c/293640/ 17:25:36 If you look, screen-n-dhcp.txt is empty file. But this seemed to be not an issue then. 17:26:08 that caused me to conclude that may be something changed in the Jenkins plugin code which is causing the gate failure. 17:26:34 As a workaround, following approaches were tried: 17:26:34 - enabling n-dhcp service via settings file in the Solum devstack plugin. The idea here was that if we enable n-dhcp, may be it will generate the corresponding log file. But this did not work. 17:26:49 - create a dummy screen-n-dhcp file with some dummy content in the post_test_hook. This seem to work as seen in the following patch: 17:27:10 https://review.openstack.org/#/c/298342/5 17:27:22 this approach seems to work 17:27:34 so here is the question for us 17:28:45 should we move forward with this workaround to unblock the mitaka release related patches? in parallel we can reach out to folks from the devstack team and suggest a solution 17:28:57 is this a devstack bug, or a solum issue? Why do we care about dhcp? 17:29:09 exactly 17:29:16 this seems like a devstack bug to me 17:29:23 I looked into the code of devstack 17:29:27 talk to the devstack team and see what they say 17:30:29 yeah, I was planning to do that.. in the mean time, what should we do with the workaround? 17:30:44 may be we can take a call on that afterwards? 17:31:00 I am just worried that the mitaka deadline is this week 17:31:22 and there are two patches related to that which we probably need to get merged 17:32:22 devkulkarni: let's check with devstack team first, if they don't have any fix/workaround, probably we can go ahead with our workaround for now? 17:32:39 ok 17:32:44 lets do that 17:32:54 I will reach out to them 17:33:18 apart from that there are no new patches to review 17:33:32 https://review.openstack.org/#/q/project:openstack/solum+status:open,n,z 17:34:27 #topic Bug review 17:34:34 New Bugs 17:34:44 https://bugs.launchpad.net/solum/+bug/1558152 17:34:44 Launchpad bug 1558152 in Solum "detailed-log-message-in-solum-deployer" [Undecided,New] 17:35:19 this one is about capturing more detailed output in deployer log 17:35:45 anyone wants to take this up? 17:36:34 devkulkarni: I can take 17:36:47 cool 17:36:53 thanks vijendar 17:37:26 are there any other new bugs that you have in mind? (which you are planning to register but have not yet?) 17:38:04 this is our current bug list: https://bugs.launchpad.net/solum/ 17:38:24 if you sort by Age you should see the latest bugs 17:38:36 there seems to be a bug with scaling 17:38:47 vijendar: oh okay 17:38:55 devkulkarni: is there any bug on that already? 17:39:06 vijendar: no, there is not. can you add it? 17:39:29 devkulkarni: sure. will do that 17:39:41 cool, sounds good 17:40:07 alright, lets move to open discussion 17:40:15 #topic Open Discussion 17:40:22 Austin summit planning 17:40:27 https://etherpad.openstack.org/p/solum-austin-summit-planning 17:40:51 I put some suggestions in there 17:40:57 yes, saw those 17:41:07 good suggestions about the demo 17:41:18 and identifying mitaka specific things 17:42:12 for demo, we were thinking of demoing the current capabilities with may be rax specific work that vijendar has done of integration with carina/magnum 17:42:41 also, ashishjain has worked on integrating jenkins for ci and solum for cd 17:42:52 that can also be demoed probably 17:43:51 we also have a contributor who is not here today, but she was looking at our horizon plugin 17:44:16 if that work moves forward to an extent where it can be demo-able then that is another option 17:44:37 of course we have our cli with the new 'app' and 'workflow' models 17:44:59 I don't remember if we have demoed that in Tokyo.. probably not 17:45:55 ashishjain: on the etherpad you have added 'multinode deployment' 17:46:12 yes devkulkarni 17:46:18 if you look at the item number 1 — 'Support for multi-container apps' 17:46:30 is that what you had in mind? 17:46:33 no 17:46:38 oh wait 17:46:45 basically installation of solum on multinode 17:46:49 you are actually saying deploying solum on multiple nodes 17:46:52 yep, got it 17:46:53 yes 17:46:59 yeah, that will be useful 17:47:29 we should pull in dimtruck in that discussion if he is available 17:48:45 vijendar, james_li: do you have any items in mind that we should cover during our work room session? 17:49:41 one thing that I was thinking was about horizon UI for solum 17:50:16 vijendar: it is item number 3 on the etherpad 17:50:24 you can +1 it 17:50:25 devkulkarni: ok..cool 17:50:38 sure 17:50:54 thanks :) 17:51:45 ashishjain: do you think you might be able to provide updates on the kolla-based deployment that was being worked on by one of your colleague? 17:51:53 not today, but during the summit 17:52:33 devkulkarni, that colleague is no longer with the org 17:52:40 ashishjain: oh ok 17:52:59 its been quite a while since he quit 17:53:06 ashishjain: was there any work that we can probably use? 17:53:10 hmm I see 17:53:58 there was a discussion thread upstream on projects trying kolla based deployments 17:54:45 I guess that's alright.. if there is some work that we can use, that would be awesome 17:55:14 but if not, and if there is no immediate interest from the team on it, then we can postpone it for some later cycle 17:56:36 I doubt if there was any progress made on it 17:56:52 So we will have to start afresh on that 17:57:03 hmm I see.. that's fine I guess 17:57:41 if there is any interest from your group and someone is available to move it forward, we can work with them 17:58:08 sure will let you know 17:58:19 cool, sounds good ashishjain 17:58:29 is there anything else that we should discuss today? 17:58:36 we are almost at the end of our meeting time 18:00:03 alright then 18:00:14 thanks everyone for attending the meeting today 18:00:17 #endmeeting