17:00:07 #startmeeting Solum Team Meeting 17:00:09 Meeting started Tue Dec 15 17:00:07 2015 UTC and is due to finish in 60 minutes. The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:13 The meeting name has been set to 'solum_team_meeting' 17:00:16 #topic Roll Call 17:00:21 Devdatta Kulkarni 17:00:22 ed cranford 17:00:29 morning ed 17:00:32 howdy 17:00:39 Ashish Jain 17:00:47 hi Ashish 17:00:53 Hi Dev 17:00:56 here is link to today's agenda: https://wiki.openstack.org/wiki/Meetings/Solum 17:01:05 #link https://wiki.openstack.org/wiki/Meetings/Solum 17:01:32 james li 17:01:42 hi james 17:01:52 Hi devkulkarni 17:01:56 we have Ed and Ashish as well 17:02:22 great to see you all today datsun180b, james_li, ashishjain 17:02:54 hi vijendar 17:03:01 Hi Dev 17:03:14 we have a quorum.. lets begin 17:03:23 here is agenda for today: 17:03:27 #link https://wiki.openstack.org/wiki/Meetings/Solum 17:03:56 #topic Announcements 17:04:14 (devkulkarni) I am doing a workshop tomorrow on contributing to OpenStack at Wipro in Pune on invitation from ashishjain. Will share my notes after the workshop. 17:04:31 wow thanks for the announcement devkulkarni 17:04:42 my pleasure ashishjain 17:04:57 hopefully the workshop goes fine 17:05:00 We all are very excited 17:05:10 I am excited too 17:05:13 yeah I am sure it will be an awesome workshop 17:05:47 vijendar, datsun180b, james_li, ashishjain: in the open discussion session lets brainstorm if there are any low-hanging-fruit bugs that I can take to the workshop 17:06:01 for folks to try submitting a patch for 17:06:12 the workshop is scheduled for 3 hours. 17:06:19 ok 17:06:30 it might be a stretch to do a patch submission from scratch 17:06:52 but if someone is interested, we should have some bugs handy 17:07:03 yeah, correct 17:07:13 I have a few ideas 17:07:30 would be interested to hear if you have any thoughts as well 17:07:36 I hope folks are able to setup devstack 17:08:01 ashishjain: yeah.. that in itself can be a big first achievement 17:08:08 solum vagrant development environment 17:08:10 yeah 17:08:27 If people have interesting apps and want to try deploy with solum, thats great too 17:08:37 james_li: great point 17:08:46 yeah good point 17:08:58 help solum ecosystem grow :) 17:09:08 yeah, trying out apps using solum can also be part of the overall openstack development experience 17:09:09 yep 17:09:23 yeah james_li 17:09:34 james_li: you might be thrilled to know that ashishjain and his team are very interested in solum 17:09:47 thats great! 17:10:04 ashishjain: may be you want to share some of your views on how and where your team/org sees value from solum? 17:10:18 Sure 17:10:25 I think it will be great for other team members to hear 17:10:29 cool 17:10:46 also, if you can give a brief background on Wipro that will be great to give some context 17:10:55 Alright 17:11:16 cool.. floor is yours 17:11:40 Wipro is a services company with a size of almost 150,000 employees 17:12:14 with our offices in almost 70+ countries 17:12:38 Their is no limit to the expertise we have got, as we have people working on almost every domain 17:12:53 and almost every aspect of software industry 17:13:41 We have been doing open source for quite sometime but mostly as a user of open source 17:14:01 but now the organisation is seriously venturing into giving it back to the various communities 17:14:35 and we have almost 5000+ members who are seriously focusing on open source software 17:15:03 we have got communities on big data(hadoop,spark), nodejs, openstack, docker and many more 17:15:27 and we have a dedicated group called open source Centre Of Excellence 17:16:04 All the above internal communities are being driven by COE 17:16:45 I belong to COE and as part of COE we plan to use OpenStack as our cloud for all the deployments 17:18:13 When I say deployment we look forward to running Big Data(Hadoop, spark), Middleware ( app servers), Log, Security, Monitoring and many more 17:18:21 on openstack 17:18:45 I see 17:18:45 As part of this we have done some work already as I discussed with you devkulkarni @tokyo 17:18:54 yep 17:19:28 where we were able to deploy some of our applications using nova-docker, heat, monitor it and even autoscale ( by feeding metrics to ceilometer) 17:19:44 Solum resembles at a lot to what we have already done and what we plan to do in future 17:20:01 that is really great to hear 17:20:03 and the road map also aligns with our road map 17:20:22 +1 17:20:37 good 17:20:52 vijendar, james_li, datsun180b: thoughts/comments? 17:20:55 moreover we would also love to have integrations possible to other frameworks for CI as we as CD 17:21:08 which devkulkarni has suggested is very much possible 17:21:25 that diversity flag is history 17:21:27 fir example jenkins, junit, maven, ant, amazon etc 17:21:35 fir=for 17:21:38 yes, that should be possible. 17:21:44 +1 datsun180b :) 17:21:52 and that is what is really exciting about solum 17:22:07 But I know their is lot to be done, atleast be able to deploy multi container app 17:22:09 great to know ashishjain :) 17:22:27 which will really make solum useful to lot of organisation 17:22:44 so thats all about our thoughts 17:23:00 thanks james_li devkulkarni vijendar datsun180b 17:23:03 ashishjain: yes, that is one of the major features which I want us to focus on in this cycle 17:23:22 thanks ashishjain for providing your perspective and thoughts about solum 17:23:33 my pleasure devkulkarni 17:24:04 alright.. let me move on to the next topic 17:24:18 #topic Review Action Items 17:24:38 all the three action items are pending.. I did not get chance to work on them 17:24:42 so I will just carry them forward 17:24:53 #action devkulkarni to figure out details about diverse-affiliation tag associated with solum. 17:25:02 #action devkulkarni to send a note to openstack-dev mailing list that our meeting on December 29th is cancelled 17:25:12 #action devkulkarni to figure out how to retire solum readthedocs site 17:25:59 #topic Blueprint/Bug Review and Discussion 17:26:13 there are couple of patches on which devstack tests are failing 17:26:20 #link https://review.openstack.org/#/c/249432/ 17:26:33 #link https://review.openstack.org/#/c/254344/ 17:26:50 Regarding 254344 their were 7 failures 17:27:04 1 was functionaltests.api.v1.test_app.TestAppController.test_app_delete_not_found 17:27:10 which has been fixed 17:27:12 beat me to it 17:27:34 and their are 6 more failures 17:27:41 ashishjain: I see 17:27:42 all on language packs 17:27:44 functionaltests.api.v1.test_language_pack.TestLanguagePackController.test_language_packs_create 17:27:50 this is the first one 17:28:02 ashishjain: this was the test about which we were talking about earlier, right? 17:28:03 and all of them fail because of same reason 17:28:10 yea devkulkarni 17:28:23 "etails: {"debuginfo": null, "faultcode": "Server", "faultstring": "list index out of range"}" 17:28:46 ashishjain: you also investigated the likely cause, right? 17:28:54 it is in language_pack_handler? 17:29:33 yeah 17:29:43 this fails here 17:29:54 https://github.com/openstack/solum/blob/master/functionaltests/api/v1/test_language_pack.py 17:29:57 line number 83 17:30:15 the reason is /opt/stack/solum/solum/api/handlers/language_pack_handler.py(57) 17:30:37 looking 17:31:27 in raw_content artifacts is empty 17:31:46 ashishjain: hmm.. looks like I had recently added a comment there 17:31:53 and the build is failing after I apply my change 17:32:18 moreover 17:32:51 If I run "create lp -> create app -> deploy app -> delete app -> delete lp" all is fine without any failures 17:33:10 the above is after I apply my patch 17:33:40 yes.. in language_pack_handler 17:34:26 yes their is a comment from you 17:34:51 and one more thing 17:35:19 the Workflow.delete which is being used to remove all entries is same as what was earlier in the code 17:35:56 hmm.. 17:36:11 https://review.openstack.org/#/c/254344/2/solum/api/handlers/app_handler.py 17:36:21 line number 58 17:36:27 has been moved to 17:37:21 one minute trying to load the heat changes 17:37:35 yeah, its in heat.py 17:37:54 correct 17:38:15 I am guessing that failing tests are probably using some data setup in a previous test 17:38:28 https://review.openstack.org/#/c/254344/2/solum/deployer/handlers/heat.py 17:38:33 line number 313 17:38:48 yeah looks like 17:40:04 ashishjain: I will try to apply your patch and run tests and see what is going on 17:40:24 probably sometime on thursday or friday 17:40:28 okay actually one more test will fail other than lp 17:40:36 which is not covered in the current patch 17:40:41 so just ignore that failure 17:40:41 oh okay 17:40:48 which one is that? 17:40:52 functionaltests.api.v1.test_app.TestAppController.test_app_delete_not_found 17:41:02 the fix is in my workspace 17:41:09 and have not uploaded it to gerrit 17:41:19 because I am yet to fix other failures 17:41:51 I suggest you amend the commit and upload it to gerrit 17:42:06 that way, when I try your patch, only the languagepack tests will be failing 17:42:11 okay, but it may again fail ( is that okay) 17:42:14 okay I will do that 17:42:23 yes, that is okay 17:42:38 sure will do it 17:42:48 cool thanks ashishjain 17:43:07 it's totally okay to resubmit patches 17:43:15 i think my record is in the 40s for a single review 17:43:30 cool datsun180b 17:43:34 +1 datsun180b :) 17:43:48 :) 17:44:06 the other patch which is failing devstack gate is https://review.openstack.org/#/c/249432/ 17:44:15 this is actually just a docs change patch 17:45:16 I am not seeing which tests are failing though: http://logs.openstack.org/32/249432/7/check/gate-solum-devstack-dsvm/5018285/logs/devstacklog.txt.gz 17:45:39 looks environmental 17:45:43 oh just saw this: http://logs.openstack.org/32/249432/7/check/gate-solum-devstack-dsvm/5018285/logs/devstacklog.txt.gz#_2015-12-09_17_08_13_674 17:46:03 Can not generate /tmp/solum//solum.conf.sample 17:46:26 may be we should just re-trigger the tests 17:46:29 that error comes from an re match group 17:47:19 i bet some code's trying re.match(needle, haystack).group() in one line 17:47:40 oh okay 17:48:04 I have just re-triggered tests 17:48:42 if the issue is environmental then probably retrying tests will fix it 17:49:56 alright.. I will keep an eye out for that patch 17:50:16 in the mean time lets move with next topic 17:51:00 Deleting DU image on app delete (#link https://bugs.launchpad.net/solum/+bug/1517588) 17:51:00 Launchpad bug 1517588 in Solum "delete-heat-stack-when-app-is-deleted" [High,In progress] - Assigned to Ashish (ashish-jain14) 17:51:20 basically, ashishjain and I were discussing about app delete 17:51:31 and in that context the question came up of what to do about the app's image 17:52:03 you can read about my comments on this here: https://bugs.launchpad.net/solum/+bug/1517588/comments/6 17:52:03 Launchpad bug 1517588 in Solum "delete-heat-stack-when-app-is-deleted" [High,In progress] - Assigned to Ashish (ashish-jain14) 17:52:45 datsun180b: I remember we had discussed about this topic earlier when you were drafting the app and workflow spec 17:53:05 does my comment on the bug align with what we were discussing back then? 17:53:41 i should think so 17:53:53 cool 17:54:00 cf docker's rmi command 17:54:18 yep 17:54:34 so that was the main point that I wanted to discuss on this topic 17:54:39 devkulkarni: you comment makes sense 17:54:56 devkulkarni: your* 17:54:56 cool.. thanks vijendar for the feedback 17:55:16 alright.. we have five minutes 17:55:30 let me quickly go through the remaining two points for today 17:55:44 3) Micro-service architecture spec 17:55:51 #link https://review.openstack.org/#/c/254729/ 17:55:56 devkulkarni: I will review it 17:56:05 awesome!! thanks james_li 17:56:22 devkulkarni: is it possible to add sample app file micro-service spec with multiple containers? 17:56:26 datsun180b, vijendar, ashishjain: you also take a look through the spec 17:56:59 vijendar: you mean, provide a sample app file? 17:57:04 devkulkarni: sure I am halfway through it will try to complete it soon 17:57:08 devkulkarni: I mean, sample app file 17:57:16 devkulkarni: correct 17:57:20 vijendar: good question.. 17:57:21 i need to start over reading it, got distracted last week 17:57:24 yeah I actually looked into [3] 17:57:49 yes, I will add one 17:57:50 it would be great to have a sample app file 17:57:56 ashishjain: agree 17:58:01 [3] is the current app file 17:58:05 devkulkarni: I was trying to visualize how the app file would look like with multi-service/micro-serivice 17:58:06 yeah 17:58:29 vijendar: awesome.. if you have any suggestions please feel free to add it 17:58:50 let me create a etherpad real quick for us to share and brainstorm on the app file format 17:58:50 devkulkarni: sure 17:59:20 vijendar, datsun180b, james_li, ashishjain: https://etherpad.openstack.org/p/solum-multi-container-app-file 17:59:36 devkulkarni: cool. thanks 17:59:38 vijendar: feel free to add your thoughts about sample app file to it 17:59:52 we can discuss about the spec next time 17:59:56 its almost time 18:00:02 #topic Open Discussion 18:00:30 please add any low-hanging-fruit bugs to https://etherpad.openstack.org/p/solum-low-hanging-fruit-bugs 18:00:41 we did not get a chance to discuss about the bugs today 18:01:07 but some of you who are in USA might want to take some time today to suggest some bugs for the workshop tomorrow 18:01:20 I will check the etherpad tomorrow morning 18:01:32 alright.. we are one minute past the meeting time 18:01:34 I will end now 18:01:48 thanks datsun180b, vijendar, james_li, ashishjain for attending today 18:01:51 see you next week 18:01:55 #endmeeting