17:00:06 #startmeeting Solum Team Meeting 17:00:07 Meeting started Tue Oct 20 17:00:06 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:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:11 The meeting name has been set to 'solum_team_meeting' 17:00:15 #topic Roll Call 17:00:20 ed cranford 17:00:22 Devdatta Kulkarni 17:00:29 hi datsun180b 17:00:56 howdy 17:01:00 Adrian otto 17:01:06 hi adrian_otto 17:01:31 here is link to our agenda for today: #link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2015-10-20_1700_UTC 17:01:59 o/ 17:02:09 hi muralia1 17:02:11 hi devkulkarni, muralia1 and datsun180b 17:02:13 hi all 17:02:56 #topic Announcements 17:03:06 Solum Fishbowl session details 17:03:12 Thursday, October 29, 5.20 pm - 6.00 pm 17:03:17 http://mitakadesignsummit.sched.org/type/solum#.ViZd4aQrgmW 17:03:24 hi vijendar 17:03:34 hi 17:03:40 so we have one fishbowl session in the summit 17:04:05 i am putting together a presentation/talk for it.. 17:04:33 will be focussing on the goals, features, intro to team, community involvement, etc. 17:04:57 if you are in Tokyo it will be great if you all could attend 17:05:02 devkulkarni: are you attending, or will I present it for you? 17:05:14 adrian_otto: I am attending the summit 17:05:21 oh, that's terrific news! 17:05:29 yeah, I am very excited 17:05:31 :) 17:06:00 I will definitely be there 17:06:17 adrian_otto: awesome !! hopefully it does not clash with any of the magnum sessions 17:06:27 I had it moved so it woudl not 17:06:28 I saw there are something like 8 sessions for magnum 17:06:39 I see.. cool 17:06:48 magnum has 12 17:06:53 oh wow 17:06:58 nice 17:07:14 you will be pretty tired by the end of the summit I guess 17:07:40 seems to be the trend 17:07:47 :) 17:08:01 so the next announcement is the change in the location of our docs link 17:08:17 this is the new link: #link http://docs.openstack.org/developer/solum/getting_started/index.html 17:08:39 the readthedocs link is no longer updating 17:08:58 I have an action item to retire the docs job for readthedocs 17:09:05 because of the stackforge -> openstack change no doubt 17:09:17 adrian_otto: yes, that is exactly what it is 17:09:32 I have updated Solum's wiki page to point to the correct link 17:09:48 so, please bookmark the new link 17:09:53 can we pull down the obsolete content? 17:10:36 adrian_otto: probably we could.. I checked with openstack-infra to figure out what to do with the old job which publishes to readthedocs.. their suggestion is to retire it 17:10:49 so once we retire it, hopefully the link will no longer be active 17:11:47 next announcement/ask is: Proposal to cancel next week's meeting 17:11:57 +1 17:11:59 what do you all think if we cancel next week's meeting? 17:12:21 thx adrian_otto 17:12:30 muralia1, datsun180b, vijendar? 17:12:42 I am ok with cancelling 17:12:43 Fine by me 17:12:47 yes we should 17:12:49 Have fun in Tokyo 17:12:55 cool.. 17:13:20 I will send a note to the dev list that we are canceling next week's meeting and will reconvene the following week 17:13:48 Devdatta, I removed myself from https://review.openstack.org/#/admin/groups/231,members and added you. 17:14:05 that's solum-release 17:14:09 datsun180b: the next meeting on November 3 will be at 11.00am, right? 17:14:28 adrian_otto: ok.. so that is the group who can cut releases? 17:14:45 yes, sir 17:14:46 That sounds right 17:14:58 adrian_otto: sounds good 17:15:16 DST ends Sunday, 1 November in the US 17:15:19 11:00 AM US/Central = 1700 UTC on 2015-11-03 17:15:30 adrian_otto: will ping you about the steps required to do a release.. we are still fixing some bugs in cli and api so haven't pinged you about it yet 17:15:38 ok 17:16:03 datsun180b: ok, cool. thanks for confirming. 17:16:44 that was all the announcements from me 17:17:00 any other announcements from the team members? 17:17:27 alright.. moving on to the next topic 17:17:37 #topic Review Action Items 17:17:51 devkulkarni to figure out how to retire solum readthedocs 17:18:08 I did not get around to figuring this out yet, so will carry forward 17:18:17 #action devkulkarni to figure out how to retire solum readthedocs 17:18:35 there was no other action item 17:18:49 #topic Blueprint/Bug Review and Discussion 17:19:06 ok, so today we have several patches for review/discussion 17:19:19 first set of patches are from vijendar 17:19:27 1) Moving logs resource to workflow 17:19:35 #link https://review.openstack.org/#/c/237088/ 17:19:41 #link https://review.openstack.org/#/c/237189/ 17:19:48 #link https://review.openstack.org/#/c/237190/ 17:19:53 #link https://review.openstack.org/#/c/237200/ 17:20:15 vijendar.. you want to provide high-level overview of the patches? 17:20:29 sure 17:21:32 recently we implemented workflows and this patch is to move logs from assemblies to workflows 17:22:17 and other patches are relevant cli changes 17:22:25 +1 vijendar 17:23:17 ok 17:23:19 please take a look and let me know if any of you have any suggestions/comments 17:23:42 cool.. thanks vijendar for submitting these patches 17:24:05 team, once these patches merge, our migration to the new api model will be complete 17:24:52 it will be a great moment (probably worth a success tag :) ) 17:25:14 yes :) 17:25:15 hopefully we can merge these before the summit.. 17:25:26 sure 17:25:54 alright, the second one is related to our devstack setup and devstack gates 17:25:57 Support for extras.d going away; will affect our devstack setup 17:26:02 https://review.openstack.org/#/c/236212/ 17:26:09 to give some background on this.. 17:26:56 devstack is moving away from the model of enabling services.. it is changing to using the plugin model 17:27:20 the deadline to make this change is seven or eight weeks out 17:27:57 we have a new contributor, venkat-mahesh who had expressed interest in changing our devstack setup to use the plugin model 17:28:12 above patch is that contribution 17:28:31 whenever you get a chance, please review the above patch 17:28:59 we need to make this change soon otherwise our devstack setup and devstack gate will start breaking 17:29:47 any thoughts/questions on this topic? 17:30:22 nope. sounds good 17:30:35 alright.. 17:30:56 the next one is a related one 17:30:59 Update to Devstack setup 17:31:05 #link https://review.openstack.org/#/c/230222/ 17:31:33 recently I realized that our Devstack setup script had not kept up with our vagrant setup 17:31:58 above patch makes the required changes/updates to this script 17:32:13 please review it whenever you get a chance 17:32:16 devkulkarni: you mean gate devstack? 17:32:23 james_li: no, not the gate 17:32:53 james_li: this is the script that we provide if someone wants to get a solum environment within a devstack setup 17:33:04 instead of using vagrant environment 17:33:36 ok will look at the patch any way 17:33:53 recently we got new contributors in vijendar, pt_15, venkat-mahesh, for whom it is necessary to have a working environment 17:34:02 james_li: sounds good 17:34:11 vijendar I believe is using vagrant, right? 17:34:26 right 17:35:00 recently I have fixed several things in our vagrant setup 17:35:32 hopefully starting up vagrant environment should not fail now 17:36:45 there is one more item which I forgot to include on the agenda 17:37:26 last week I proposed a spec to refactor our deployer code 17:37:29 #link https://review.openstack.org/#/c/235587/ 17:37:48 please review it whenever you get a chance 17:38:40 note that the scope of the refactoring is limited to breaking up our current code in a way such that it will become easy to maintain and add new features 17:39:13 making a sweeping change to use a pluggability framework such as stevedore is not in the scope of this refactoring 17:40:17 I believe that our current deployer interfaces are sufficient enough to allow us adding newer features without having to go all out and use stevedore 17:41:20 so please review the spec and provide any feedback 17:41:27 hi pt_15 17:41:42 devkulkarni: hi! :) 17:41:53 pt_15: you are just in time for the next topic :) 17:42:17 pt_15: here is the link to today's agenda. #link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2015-10-20_1700_UTC .. I am about to start open discussion 17:42:30 #topic Open Discussion 17:42:41 1) Ideas for Outreachy program internships 17:42:47 #link https://etherpad.openstack.org/p/projects-for-outreachy-program 17:42:55 so to give some background on this.. 17:43:15 I had signed up as a mentor to participate in the Outreachy program 17:44:12 pt_15, who just joined the meeting, reached out to me with an interest in working on Solum.. So we are working together to figure out a project for her to work on as part of the Outreachy program 17:44:23 nice 17:44:40 I have identified list of potential projects here: #link https://etherpad.openstack.org/p/projects-for-outreachy-program 17:45:07 pt_15 already got couple of her patches merged into Solum repo :) 17:45:40 please feel free to add any other ideas/projects that you think can be done in two to three month internship period 17:46:12 these would be useful for others who might be interested, or for next round of the Outreachy program 17:47:46 pt_15: we can continue discussion about the topics that interest you in the solum channel after the meeting.. 17:48:08 there is one more item I want to cover in the open discussion 17:48:14 2) Devstack gate is currently broken 17:48:21 #link http://logs.openstack.org/88/237088/3/check/gate-solum-devstack-dsvm/9fcee3b/console.html#_2015-10-20_14_23_09_242 17:48:28 our devstack gate is currently broken 17:48:39 the issue seems to be in tempest_lib 17:48:52 this morning I reached out to openstack-qa 17:49:36 and mtreinish told me that he has pushed a patch which will fix the issue 17:49:52 he was going to release it to pypi 17:49:56 devkulkarni: yes, definitely! :) 17:50:48 so, I plan to re-trigger the gates on all the patches which are currently failing the devstack gate 17:51:08 hopefully the issue gets resolved soon 17:51:39 otherwise, I will check with dimtruck and/or mkam to see if something needs to be changed in our functionaltest setup 17:52:11 alright.. that is all I had for today 17:52:44 currently nova is broken on devstack 17:53:07 vijendar: what error are you getting? is it in n-cpu? 17:53:29 devkulkarni: correct. it is n-cpu issue 17:53:40 devkulkarni: were you able to resove that issue? 17:53:42 vijendar: I pushed a fix to nova-docker which took care of that issue for me 17:53:53 devkulkarni: cool 17:54:00 devkulkarni: thanks 17:54:12 vijendar: if you re-create your vagrant vm from scratch, that issue should go away 17:54:23 ok 17:54:33 cool 17:55:39 any other topics? .. otherwise will end in 1 minute 17:57:15 alright.. see you in two weeks 17:57:25 thanks everyone for joining today 17:57:30 #endmeeting