21:08:44 #startmeeting Solum Team Meeting 21:08:45 Meeting started Tue Dec 9 21:08:44 2014 UTC and is due to finish in 60 minutes. The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:08:46 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:08:49 The meeting name has been set to 'solum_team_meeting' 21:09:07 #topic Roll Call 21:09:11 Devdatta Kulkarni 21:09:20 murali allada 21:09:22 Akshay Chhajed 21:09:25 ed cranford 21:09:27 Just started it as I don't see adrian here today 21:09:34 gil pilz 21:09:53 Hi Akshay, hi gil 21:10:12 #link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2014-01-14_1600_UTC Today's Agenda 21:11:01 That agenda is from last week. 21:11:24 Dimitry Ushakov 21:11:34 But most of the items were continued from last week anyways 21:11:46 i was trying to use https://github.com/rackerlabs/vagrant-solum-dev for dev environment.... but it didn't work 21:11:58 Roshan Agrawal 21:12:04 akshayc: oh okay.. lets get to that in a bit 21:12:07 akshayc: we can help you with that 21:12:16 in the open discussion part of the meeting 21:12:22 #topic Announcements 21:12:26 Melissa Kam 21:12:39 The main announcement is that the Solum team will be meeting here at this time 21:12:45 every Tuesday. 21:13:00 Adrian had sent out an email to that effect after last week's meeting 21:13:11 ok 21:13:27 hope that it works for currently active folks 21:13:49 does anyone else have any other announcements? 21:14:10 not me 21:14:13 if not, lets go to the next topic 21:14:20 #topic Review Action Items 21:14:32 dimtruck to follow up on bugs 1359516 and investigate for any specific issues in replacing simple_server with mod_wsgi 21:14:34 Launchpad bug 1359516 in solum "Needs to handle http header 'X-Forwarded-Proto'" [Undecided,Confirmed] https://launchpad.net/bugs/1359516 21:14:58 dimtruck: any update on this? 21:15:14 well i threw a review at that bug 21:15:19 yes sir - there is a patch out that ed put in 21:15:21 yup! 21:15:24 datsun180b: that was it 21:15:30 could you share the link? 21:15:43 #link https://review.openstack.org/#/c/140162/ 21:16:10 thanks datsun180b for the patch 21:16:35 dimtruck: could you summarize the findings and the course of action that we have decided on this? 21:17:04 basically - solum overwrites the scheme for the url that it uses to populate solum tables 21:17:24 it overwrites it based on the local server instead of fqdn 21:17:42 ok.. 21:17:51 so - datsun180b put a patch to respect the X-Forwared-Proto, which has the proper scheme passed in 21:18:02 got it 21:18:06 it can be set by whatever proxy sits in front of solum api, such as nginx or apache 21:18:31 nice.. so this task is done then? we can remove it from the list of action items 21:18:38 yes! 21:18:49 cool 21:19:11 I will move this one to the next meeting if you want: dimtruck to report back results of multi-node devstack with solum setup 21:19:18 nope! 21:19:24 this is actually also done 21:19:30 cool.. awesome!! 21:19:35 we've discussed that we can do it 21:19:39 we just use barbican 21:19:44 what is the outcome? is it documented somewhere? 21:19:45 everything else works as advertised 21:19:57 hahaha, ok - if you want DOCUMENTATION, we can move it to next week :P 21:19:58 what do you mean by we just use barbican? 21:20:10 essentially our issue was key storage 21:20:16 right 21:20:24 that's what was preventing us from doing it multi-node 21:20:42 however, with barbican we won't have this issue because of distribution 21:20:45 right.. so you are saying that if we continue to use barbican multi-node setup will be fine 21:20:49 right 21:21:02 okay 21:21:28 if you can add a documentation to solum repo in either contrib or etc then we can close this one 21:21:43 will do! 21:21:49 thanks dimtruck 21:22:00 next one was: adrian_otto to cut the final Juno release 21:22:13 I know that muralia was working with adrian_otto on this.. 21:22:26 probably it is not ready yet.. right muralia? 21:22:36 yes, I know that he was working on it when I got in touch with him on Friday 21:22:56 okay. lets carry it to next week. 21:23:12 the next two tasks are done 21:23:23 moving on to next topic 21:23:33 #topic Blueprint/Task review 21:24:04 are there any specific blueprints or launchpad bugs that anyone wants to discuss about? 21:24:39 https://bugs.launchpad.net/solum/+bug/1302552 this one 21:24:40 Launchpad bug 1302552 in solum "Tech Debt: Convert bash scripts in contrib into python code and add tests" [Medium,Triaged] 21:24:52 I have an update on the bugs. recently I went through our existing bug list and marked some of them as 'low hanging fruit' 21:25:22 akshayc: yes.. that one is kind of being worked on by ravips 21:25:34 did you have any specific question(s) about it? 21:25:49 oh i ravi's on that, starting with 21:25:50 #link https://review.openstack.org/#/c/132381/5 21:26:05 nothing specific... just general question as it was already assigned to someone 21:26:31 yeah, the LP bug should be marked as belonging to Ravi for now 21:26:41 ah okay.. 21:26:58 apparently i can't do it myself, i just tried 21:27:09 akshayc: if you are interested in that bug then I would suggest syncing up with ravips 21:27:48 the four or five reviews look mostly okay 21:27:56 i will review the above link by datson180b 21:28:10 akshayc: cool. 21:28:55 akshayc: that bug will be a good step to start. there are other low hanging fruits as well, but they may require some understanding about the terminology 21:29:26 are there other bugs that anyone has in mind? 21:29:35 i was going through the available material 21:30:00 'other bugs' meaning high priority or low-hanging fruit? 21:30:11 low-hanging fruit 21:30:20 as they are good to get started with solum development 21:31:07 the cli needs some error message improvement 21:31:08 we don't have to answer that question right now.. but if you know of any, please create the bug if it is not already created and mark it as such 21:31:33 i think the worker handlers could use a once-over to make sure they're not using any db connections directly (shell is, i know) 21:31:39 mkam: right.. are these bugs created in launchpad already? 21:32:08 I think there should be some in there -- if not, I'll add them 21:32:24 datsun180b: that is not a low hanging fruit imo. it requires understanding of the architecture.. may not be a good step to start 21:32:33 that will be great mkam 21:32:40 * datsun180b takes stilts off 21:32:42 sorry 21:33:30 akshayc: keep an eye out on the bug list to find new low hanging fruit bugs that mkam will add soon 21:34:15 how about #link https://bugs.launchpad.net/solum/+bug/1346963 21:34:15 ok. 21:34:18 datsun180b: he he.. I think db connections from shell.py is certainly something we want to avoid. 21:34:19 Launchpad bug 1346963 in solum "Tech debt: "except Exception" present in codebase" [Wishlist,Triaged] 21:34:54 cool 21:35:23 datsun180b: that is a good one.. but as you have mentioned in the bug report, it may involve pushing changes to upstream 21:35:33 which again may not be a good point to start imo 21:35:56 lets continue to open discussion. 21:36:01 i disagree: those changes will require involving other solum and OS contributors 21:36:16 meaning personal engagement is part of the outcome of the bugfix 21:36:22 #topic open discussion 21:36:26 where are we RE: replacing simple_server with mod_wsgi 21:36:27 I have one topic 21:36:45 gpilz: dimtruck gave an update on that 21:37:08 i have a patch out here: #link https://review.openstack.org/#/c/140468/ 21:37:46 the patch introduces the use of gevent instead of simple_server 21:37:46 thanks 21:38:07 it's more production-like as it allows for multiple threads, for example 21:38:43 here's what i used as one of the docs for comparison between servers: http://nichol.as/benchmark-of-python-web-servers 21:39:18 dimtruck: could you include that as a reference in the commit message? 21:39:28 ugh - good idea 21:39:33 thanks! 21:39:35 i can patch my patch 21:39:41 thanks devkulkarni 21:39:42 on a somewhat-related tangent - are we wedded to WSME? 21:39:55 yeah i was looking into that as well 21:40:23 we're really not from code perspective - but is it causing you heartache? 21:40:56 yeah - I can't get it to model an attribute that could be one of two complex types 21:41:09 I'm not the only one who has run into this problem 21:41:22 I can work around it for now 21:41:35 but I really have to wonder about a framework that can't support such a common use case 21:41:58 gpliz: do you have an alternative suggestion? 21:42:21 dev: I'm not familiar with the solution space 21:42:24 in other words "no" 21:42:56 gpilz: oh okay.. I thought your work around involves using other framework and so I was just going to suggest that we can use that in addition to/in place of wsme 21:43:38 roshanagr1: you around? 21:44:21 gpliz: okay. my suggestion is if it is not a blocker then we can continue with wsme 21:45:04 dev: sure, i just wondered what our options might be 21:45:04 akshayc: you had issue with your vagrant setup.. do you have logs of it somewhere? 21:45:13 yep 21:45:14 gpilz: got it.. 21:45:34 ==> devstack: cp: cannot create regular file ‘/etc/nova/rootwrap.d/docker.filters’: No such file or directory 21:45:48 it failed here 21:45:56 do you have the stack trace? 21:46:03 guessing it's nova-docker 21:46:32 yep 21:47:01 akshayc: did you try going back to the commit which was before the commit that added docker-py to nova-docker? 21:47:13 yeah i forked it to make some changes we need 21:47:26 export NOVADOCKER_REPO=https://github.com/ed-/nova-docker.git 21:47:26 export NOVADOCKER_BRANCH=solum-pin 21:47:34 that's what i use right before "vagrant up" 21:47:38 o/ 21:47:57 hi adrian_otto 21:48:05 sorry I was absent earlier 21:48:16 akshayc: you want to follow datsu 21:48:26 ok.... 21:48:32 let us know how that goes 21:48:44 adrian_otto: no worries.. we are in the open discussion topic 21:49:03 I had one the topic of cli to discuss 21:49:20 good that you are here.. roshanagr1 just left the room before we could start discussing it 21:49:52 adrian_otto: any updates on the cli that the team should know about? 21:52:24 if there is nothing more to discuss, we can wrap up.. 21:53:17 I am going to end the meeting.. catch you in solum for further discussion 21:53:21 #endmeeting