16:11:38 #startmeeting Solum Team Meeting 16:11:39 Meeting started Tue May 6 16:11:38 2014 UTC and is due to finish in 60 minutes. The chair is adrian_otto. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:11:40 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:11:43 The meeting name has been set to 'solum_team_meeting' 16:12:02 my apologies for the late start today. I was distracted. 16:12:11 #topic Roll Call 16:12:14 Paul Montgomery 16:12:14 Adrian Otto 16:12:15 Ed Cranford 16:12:18 Noorul Islam K M 16:12:20 Ravi Sankar 16:12:21 murali allada 16:12:22 Roshan Agrawal 16:12:23 Arati Mahimane 16:12:25 Devdatta 16:12:26 tom blankenship 16:12:28 Pierre Padrixe 16:12:33 Julien Vey 16:12:42 rajdeep dua 16:13:08 Welcome everyone! 16:13:29 #topic Announcements 16:13:35 (none prepared) 16:13:43 We do have a Demo 16:14:06 https://wiki.openstack.org/wiki/Solum/solum_m2_demo 16:14:13 #link https://wiki.openstack.org/wiki/Solum/Demo is currently pointing to the M2 demo page 16:14:16 oh boy do we 16:14:43 so all team members should be aware of this 16:14:56 I ask that we all give it a try and shake out all the kinks 16:15:14 there was one known problem as of yesterday evening where the image build process was not completing 16:15:23 so new assemblies were not exiting BUILDING state 16:15:30 just a question, why are we refering to rackers git repo for the ui ? 16:15:36 can we rappatriate the solum-m2 demo ? 16:15:58 it better not still be pointing at mine 16:16:11 oh right rackerlabs is also a racker 16:16:26 stannie: rappatriate? 16:16:35 repatriate 16:16:46 sorry :) 16:16:53 he's suggesting we move it to somewhere not rax-affiliated 16:16:54 is there a plan to have a hosted demo version 16:17:02 it is easier for people to try 16:17:14 yes, of course we will. 16:17:17 ok 16:18:01 rajdeep: we are exploring that. There are some pitfalls with a hosted system we have not solved yet. It may be subject to abuse. 16:18:04 great! any projected dates 16:18:23 i think it is super important 16:18:34 until delete-assembly works having a hosted demo is going to look like an elevator that can only go up 16:18:39 for any paas to get some love from developers 16:19:00 the_instructions: I was able to delete an assembly yesterday 16:19:04 oh cool 16:19:13 is this the demo for Juno design summit? 16:19:32 I will have a video 16:19:48 so eanyone can just watch the video of the demo to get a sense of things in a couple of minutes 16:19:58 s/eanyone/anyone/ 16:20:04 nice! 16:20:21 and then longer term we can sort out how best to do a hosted demo 16:20:46 I am happy to talk about that more in Open Discussion today. 16:20:58 ok, other announcements from other team members? 16:21:34 #topic Review Action Items 16:21:42 (no action items recorded last week) 16:21:50 #topic Review Tasks 16:21:57 https://launchpad.net/solum/+milestone/2014.1.2 16:22:33 sort that list by importance 16:22:55 https://bugs.launchpad.net/bugs/1316316 will be fixed ASAP 16:23:34 we can't manage to have a working version of Solum :( 16:23:47 that same issue may also be related to https://bugs.launchpad.net/bugs/1315459 which is about a similar symptom where the Assembly state enters BUILDING and never exits (when using a Devstack system configured to produce VM's) 16:23:52 works on my machine! 16:23:56 * the_instructions ducks 16:23:57 the_instructions: xD 16:24:26 we have 10 High priority bugs 16:24:50 adrian_otto: we also have the "Never exists BUILDING state" with almost no logs :( 16:24:52 I worked on the Documentation Review: #link https://bugs.launchpad.net/solum/+bug/1313931 16:25:08 so I am assigning that to me 16:25:10 s/exists/exits 16:25:51 julienvey: are you referring to this : https://bugs.launchpad.net/bugs/1315459 ? 16:26:34 adrian_otto: yes 16:26:43 I'd like a volunteer to take that one 16:26:59 the localrc needed to reproduce that is in the bug ticket 16:27:09 I also have a system that exhibits the symptom 16:27:13 adrian_otto: actually not exactly the same one 16:27:17 that I can supply remote login access to 16:27:26 adrian_otto: we are stuck in BUILDING but not with the neutron error in the logs 16:28:04 julienvey: I know we have at least two root causes for that symptom 16:28:09 julienvey: I think https://review.openstack.org/#/c/92171/ fixes it. 16:28:41 i should hope it does 16:28:53 It is clear to me that Solum in its current form is too hard to debug 16:29:01 i haven't seen problems with neutron or with docker intermittently failing myself 16:29:01 adrian_otto: agree 16:29:21 I really want a unified log where I can look to see what's happening chronologically. 16:29:39 and I'd like for additional status to be exposed through the assembly rest resource 16:29:41 adrian_otto: we should work on this https://bugs.launchpad.net/solum/+bug/1302552 16:30:00 bash scripts don't have proper logs and are hard to debug 16:30:19 ^^ 16:30:20 and currently, almost everything happen in the scripts 16:30:24 yes I agree converting the bash scripts in python will help to have proper logs 16:30:46 julienvey: I agree :) 16:30:52 the_instructions: just saw your comment :) 16:30:58 and we would avoid to have to parse CLI outputs etc 16:31:01 92171 was just merged 16:31:15 julienvey: if we can address Angu's stated concern about making them executable from a script (I think this is doable) 16:31:16 while we could simple call python-glanceclient in a python 16:31:23 the_instructions: yay 16:31:36 julienvey: yes, sorry i didn't get more done toward that conversion, i've been focused on the demo 16:31:49 the_instructions: no problem :) 16:32:45 ok, so I targeted https://bugs.launchpad.net/solum/+bug/1302552 to juno-1 16:32:58 I agree that would be an improvement 16:33:56 and I would welcome any patches that add log messages (or at least STDOUT form the scripts) so it's easier to see what's happening 16:34:52 https://launchpad.net/solum/+milestone/2014.1.2 16:35:51 https://bugs.launchpad.net/solum/+bug/1307703 was unassigned, so I assigned that to paulcz (fix committed) 16:36:23 aratim: can you update us on https://bugs.launchpad.net/bugs/1315139 please? 16:36:35 https://bugs.launchpad.net/bugs/1315139 16:37:04 #link https://bugs.launchpad.net/bugs/1315139 https://bugs.launchpad.net/bugs/1315139 16:37:19 adrian_otto: yes, I have a patch for that - https://review.openstack.org/#/c/91674/1 16:37:20 my irc client is being tricky with me 16:37:49 Workaround: Use pecan instead of wsme for TriggerController's post method 16:37:53 I will address devdatta's comment on my patch and resubmit it 16:38:11 why is Jenkins unhappy with that patch? 16:38:14 also the devstack gate is failing so need to rebase 16:38:19 and devkulkarni 16:38:24 yes 16:38:37 the delete-assembly bug status update 16:39:07 working on it. realized that functionaltests are failing because I am not deleting assembly anymore immediately 16:39:25 also addressing noorul's comments 16:39:40 ok, so we are in good shape on each of those 16:39:56 does anyone have any worries about where we are currently? 16:40:51 https://bugs.launchpad.net/solum/+bug/1316338 is low hanging fruit 16:41:00 I should figure out how to mark it as such 16:41:36 adrian_otto: you could add a tag, as other integrated projects do 16:41:52 https://bugs.launchpad.net/nova/+bugs?field.tag=low-hanging-fruit 16:41:57 julienvey: good idea. I will do that 16:43:29 #topic Open Discussion 16:43:50 did we get any time slots for next week's summit? 16:44:10 devkulkarni: was about to ask the same question! 16:44:18 i thought we got two 16:44:23 yes, let me give you a link 16:44:46 #link https://wiki.openstack.org/wiki/Solum/Summit Solum at OpenStack Summit 16:45:22 I ask that everyone on the Solum team do everything possible to attend all three of these. 16:46:12 are any of you not attending in Atlanta? 16:46:13 Apart from that are we meeting as a team ? 16:46:15 I'll be there TWTh 16:46:41 I think the last slot is about team discussion 16:46:51 http://openstacksummitmay2014atlanta.sched.org/event/6e53527347d56d67120decd49bbac53b#.U2kR1-Z_vZB noorul 16:47:00 I propose we cancel next week's IRC meeting and conduct our business on Wednesday at the link above 16:47:28 sounds like fun 16:47:48 this will be a very exciting Summit for us 16:48:30 I will also mention that I have been very focused on keeping our bug/task list up to date, and fully prioritized 16:48:47 are all of you finding that resource to be helpful for clarity on where to focus your efforts? 16:49:15 adrian_otto: is there any homework that we need to do this week regarding the program/project mission statement before next week? 16:49:16 is there anything we could be doing better? 16:49:29 adrian_otto: Great work on this 16:49:37 +1 16:49:40 adrian_otto: +1 16:49:58 should we prepare some discussions point for the meeting on Wednesday ? 16:50:01 devkulkarni: excellent question. I will take an action item to revise that further 16:50:01 Oops, I meant, I second julienvey 16:50:08 maybe share an etherpad ? 16:50:22 julienvey: I will take that action 16:50:26 and open an ML discussion asking for input on the etherpad as we refine that and get it close to what we want to adopt 16:50:28 roshanagr: great 16:50:49 and add that to our list of etherpads at https://wiki.openstack.org/wiki/Solum 16:50:59 ok 16:51:00 #action roshanagr to revise mission statement wiki, and publish to ML requesting input on revised draft. 16:51:20 goal is to have us feeling "close" as we enter our Wednesday discussion 16:51:54 devkulkarni: good point 16:52:09 #action adrian_otto to add the solum mission etherpad to our wiki page 16:52:39 Environments: do we feel we need to meet tomorrow on IRC on the topic 16:52:49 roshanagr: to be clear, I'd like to transfer the etherpad to a wiki page for the mission 16:52:55 about the etherpad I was more thinking about future development discussions 16:53:00 and invite edits to that 16:53:42 adrian_otto: ok 16:53:44 julienvey: +1. i think we need a list of topics for our Wednesday discussion and i thought that's what Roshanagr was agreeing to start. 16:53:44 just mark it as DRAFT so there is no confusion about it's status until after we agree 16:53:59 yes :-) 16:54:03 oh 16:54:10 should I take back the other AI? 16:54:21 or will you accept both? 16:54:28 i think we need both :) 16:54:28 but I am happy to take the mission statement as well if there are no other takers 16:54:38 roshanagr: <3 16:54:39 I have it. 16:54:45 roshanagr: thanks! 16:55:02 #action roshanagr to make a list of topics for the Summit discussion on Wednesday, and circulate it for input. 16:55:35 ok, any other discussion, or would you like to wrap up a few minutes early today? 16:55:49 Environments 16:56:11 should we meet tomorrow, or just discuss at the summit? 16:56:25 meet tomorrow, and put it on our agenda for next week too 16:56:25 discuss at summit 16:56:38 cool. lets do both. 16:56:59 devkulkarni: We don't have anything new to discuss this week? 16:57:35 yeah, we can meet tomorrow too 16:57:54 just thought looking at the etherpad that there was not much work happened 16:58:02 roshanagr: please list he Environments meeting at https://wiki.openstack.org/wiki/Solum/BreakoutMeetings 16:58:13 adrian_otto: okay 16:58:15 so may be allow the team to think about environments till next week and then have informed discussion 16:58:32 I am happy to regroup on that the week after the summit if you feel there's not enough to discuss tomorrow 16:58:52 ok, w'eel do that 16:59:09 #agreed no Environments meeting tomorrow, we will discuss in Atlanta 16:59:34 #agreed no Weekly Team Meeting on 2014-05-13 16:59:48 next meeting is 2014-05-20 at 1600 UTC 17:00:11 thanks everyone! 17:00:17 #endmeeting