14:00:46 #startmeeting Solum Team Meeting 14:00:47 Meeting started Wed Mar 15 14:00:46 2017 UTC and is due to finish in 60 minutes. The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:51 The meeting name has been set to 'solum_team_meeting' 14:01:20 hi 14:02:05 hi Swami.. Its solum team meeting time 14:02:33 I guess you are here for the following meeting? 14:03:03 Yes I was waiting for haleyb 14:03:21 devkulkarni: do you have any items to discuss in the DVR meeting. 14:03:39 Swami: no 14:03:41 hi zhurong_ 14:03:51 hi devkulkarni zhurong_ 14:03:54 Ok, no problem. 14:03:58 hi vijendar 14:04:01 I forgot the time change. 14:04:05 Swami: :) 14:04:30 vijendar, zhurong: thanks for joining today 14:04:42 lets wait for a minute or two to see if any one else joins 14:04:48 hi devkulkarni vijendar I still have some works, so I can not attend today's meeting, but I will check the logs 14:05:09 zhurong_: sure, sounds good 14:06:23 zhurong_: although, one of the main things that I wanted to discuss today was about our devstack environment, which I think you might have insights into.. we will need this in preparation for the Boston summit 14:07:57 vijendar: I can quickly update you on where things are 14:08:07 devkulkarni: sure 14:08:15 alright 14:09:09 So let me go through the agenda items that I had prepared for last meeting. That includes the main points anyways 14:09:52 1) We need to acknowledge the Pike goal of enabling WSGI app for API service 14:10:11 btw, here is the agenda that I am referring to: https://wiki.openstack.org/wiki/Meetings/Solum 14:10:53 do you know how far are magnum or heat on this goal? 14:11:32 devkulkarni: magnum has a patch in review 14:11:42 devkulkarni: let me share that with you 14:11:44 vijendar: oh cool.. can you share that 14:11:47 cool 14:12:22 devkulkarni: https://review.openstack.org/#/c/427723/ 14:12:30 looking 14:16:30 vijendar: I am trying to check where in https://github.com/openstack/solum we have to make such a change 14:16:40 btw, did magnum not use pecan? 14:16:54 devkulkarni: magnum uses pecan 14:17:06 I remember hearing at the Atlanta PTG that if pecan is being used then it is already a wsgi app 14:17:53 https://github.com/openstack/solum/blob/master/solum/api/app.py 14:19:02 devkulkarni: that seems right, because magnum related change is just a wrapper script 14:19:06 vijendar: comparing that with https://github.com/openstack/magnum/blob/master/magnum/api/app.py 14:19:16 they seem similar 14:19:48 right 14:20:14 the load_app method seems to be missing in solum app.py 14:20:22 but it seems we are using eventlet stuff in api layer, as per agenda item we need to remove it ...right? 14:20:42 yes, that is correct observation 14:21:03 does the goal state that? 14:21:17 it does not state that 14:22:05 https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html 14:22:27 vijendar: https://github.com/openstack/solum/blob/391191e0118a0390eefd69b31a5a6804064172e3/solum/cmd/api.py 14:23:39 right 14:23:55 but I remember that coming up for discussion in Atlanta 14:25:51 vijendar: https://specs.openstack.org/openstack/openstack-specs/specs/eventlet-best-practices.html 14:29:07 if we submit a patch similar to magnum, would this api.py would not come into picture... right? 14:29:35 vijendar: good question 14:29:49 let me check where is cmd/api.py is getting invoked 14:29:53 this api.py is to run solum api as a standalone server...right? 14:30:22 I think you are right.. in setup.cfg this might provided as a console_script 14:30:23 checking 14:30:42 https://github.com/openstack/solum/blob/master/setup.cfg#L50 14:31:01 devkulkarni: good 14:31:13 so now one thing is not clear is how are these console scripts handled under wsgi server 14:32:18 my understanding is under wsgi this will be bypassed 14:32:27 I think the console scripts might be getting triggered from our devstack setup 14:32:47 vijendar: I think you might be correct.. at least, the api will be bypassed 14:33:20 so we might have to make changes to devstack setup to only start remaining services and let wsgi server start the api 14:33:32 let me check plugin.sh in devstack 14:34:12 I can keep on eye on magnum changes for wsgi support and then we can just replicate the changes (hopefully) 14:34:41 vijendar: https://github.com/openstack/solum/blob/master/devstack/plugin.sh#L279 14:34:50 yep, that would be good 14:35:16 it will be helpful to follow the magnum patch series 14:35:41 we might have to change this: https://github.com/openstack/solum/blob/master/devstack/plugin.sh#L280 14:35:55 and this: https://github.com/openstack/solum/blob/master/devstack/plugin.sh#L289 14:36:19 ok 14:36:20 alright, so this is good 14:36:39 please keep us posted about changes that you are seeing in magnum around this 14:36:51 sure 14:37:34 cool.. other things that have happened recently are 14:38:02 Devstack to make glance version 2 as default (http://lists.openstack.org/pipermail/openstack-dev/2017-March/113314.html) 14:38:23 this is going to affect us since we are using glance version 1 in our build_app and unit_test_app scripts 14:39:12 3) Tempest to use Keystone version 3 as default (http://lists.openstack.org/pipermail/openstack-dev/2017-March/113487.html) 14:39:38 recently we merged zhurong's patch that added keystone v3 support in python-solumclient 14:40:00 we still need to figure out what needs to be done on the server side to enable keystone v3 support 14:40:00 devkulkarni: there was a change in magnum to do glance v1 to v2 14:40:21 vijendar: oh really...can you share that patch if it is easily accessible 14:40:41 devkulkarni: sure. but it was just two lines change that was merged yesterday 14:41:05 devkulkarni: https://review.openstack.org/#/c/445246/ 14:41:08 ah okay.. let me share with you the places in our code that need to be changed 14:42:34 vijendar: cool, this patch is good reference point for us 14:42:42 let me share where we need to make changes 14:43:09 https://github.com/openstack/solum/blob/master/contrib/lp-cedarish/docker/build-app#L54 14:43:44 https://github.com/openstack/solum/commit/1ef122b27c281a0ca93f4300c4f245e4fdd69fa2 14:43:50 check the commit message 14:44:31 so looks like we have more work for this 14:45:11 we might to figure out which glance v2 flags are relevant and then change worker/shell.py to pass them to build_app/build_lp accordingly 14:45:50 or, another option is to actually make change in devstack's plugin.sh to enable glance version 1 14:46:04 I remember reading in that email about it 14:46:10 let me quickly scan the email again 14:46:13 ok 14:47:27 vijendar: GLANCE_V1_ENABLED=True is what we need to set in settings/localrc for devstack plugin 14:47:52 although the email mentions that nova won't work with glance v1 anymore 14:48:26 in our devstack setup, we have moved away from using nova-docker to zun 14:48:43 as long as zun is able to work with glance v1, making above change in our devstack setup might be fine 14:49:12 I see 14:49:14 in real world setups though this might not work if nova/compute is running on ocata 14:50:10 lets see 14:50:24 I had a quick question about keystone v3 support 14:51:08 does magnum support keystone v3? if so, can you share the code on the server side that enables v3 support? 14:51:27 we have recently merged a patch that added keystone v3 support to python-solumclient 14:51:49 but now we need to figure out changes that need to be done on the solum api/server side 14:52:56 devkulkarni: I think magnum supports keystone v3 but not sure. I will check and confirm later 14:53:09 vijendar: okay, sounds good 14:53:45 vijendar: btw, our presentation for the boston summit did not go through.. but for the project we have got a fishbowl session 14:54:28 devkulkarni: yeah..I got an email :) 14:54:42 yeah 14:55:09 my travel plans for boston are not finalized yet.. but hopefully I can make it 14:55:20 we have one slot for fishbowl and one slot for a forum 14:56:12 ok 14:56:12 we are almost at the end of our meeting time 14:56:29 anything that you have on mind to discuss? 14:56:42 nothing from me 14:56:49 ok 14:56:56 I think we had great discussion today 14:57:10 please keep us in the loop on the wsgi app goal 14:57:27 sure 14:57:45 cool, I will end the meeting then. see you next week. 14:57:57 thanks for joining today vijendar, zhurong. see you next week 14:58:06 #endmeeting