14:00:52 #startmeeting Solum Team Meeting 14:00:53 Meeting started Wed Apr 26 14:00:52 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:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:57 The meeting name has been set to 'solum_team_meeting' 14:01:12 hi 14:01:16 hi zhurong_phone 14:01:31 lets wait for a minute to see if others join in 14:01:50 sure 14:03:52 alright, lets get started 14:04:21 so we have several things to discuss 14:05:03 1) Boston summit, 2) Patches, 3) Openstack-wide things 14:05:35 zhurong_phone: do you have any other items in your mind that we should discuss? 14:05:54 np just patches 14:06:09 alright.. so lets talk about Boston first 14:06:55 as I mentioned to you in the email, we need to take a decision about our slots at the Boston summit 14:07:11 hopefully by friday we will have clarity 14:07:30 yep, deadline is Friday 14:08:02 one option is in the worst case we hear in the negative on the visa front then I will let organizers know to release our slots 14:08:18 what do you think? 14:08:38 that's the worst case 14:08:44 unless caowei is attending the summit and is willing to present 14:08:59 yep, that is the last option 14:09:11 caowei can not go there 14:09:19 ah ok 14:09:46 hopefully my can issued tomorrow 14:09:47 in that case it will come down to whether you hear positive or negative about your visa 14:10:03 zhurong_phone: yep. lets keep our fingers crossed 14:10:26 zhurong_phone: assuming that visa is there, then we don't need to release our slots 14:10:30 yes, I Will tell you the process 14:10:58 zhurong_phone: yes, please keep me in the loop on whatever you hear 14:11:17 sure 14:11:46 lets talk about the situation when you get the visa.. in that case, we will need to prepare for two things -- 1) Project status update talk and 2) Onboarding session 14:12:25 For the Project status update talk, have you received email about filling out a form regarding project related details? 14:12:41 what about onboarding session? 14:13:26 the onboarding session should not be that difficult. It is essentially showing the code, discussing the overall architecture, showing a demo, etc. 14:13:45 it is aimed for people who want to get started with a project 14:14:11 understand 14:14:29 I am not too worried about it. you can take our previous presentations to frame the discussion in the onboarding session 14:14:56 as far as code level details, you already understand it to an extent 14:14:58 yep, i think so 14:15:18 if there are any gaps in your understanding then we still have time to discuss and resolve those 14:15:46 we can setup a time in next week where I can go over the code details with you 14:16:00 if that would help 14:16:19 sure, if my visa is issued 14:16:40 that will great help for me 14:16:44 about the project update status talk -- did you receive email which asked to fill out a form? 14:17:13 zhurong_phone: yes, we can do the discussion only if your visa is issued 14:17:51 if the visa is negative then we need to just let the organizers know that we cannot come to the summit so they can release the slots 14:18:23 recently my computer is for my friend 14:18:49 oh, that's why you are attending the meeting from phone? 14:19:04 so I can not receive my email 14:19:09 oh 14:19:10 yep 14:19:34 do you know when would you get back your computer? hopefully you will get it soon 14:19:56 next two or few days 14:20:03 ah okay.. 14:20:28 for project status update, there is a form that has been sent out 14:20:40 and we will have National holiday in 5.1 14:20:56 once we know about your visa, we can work on that form 14:21:06 yep 14:21:09 I see. So next Monday you will be on holiday 14:21:25 I should be available over this weekend 14:21:45 ok, good news 14:21:53 and also during the week (next few days). so if we want to sync up that should be fine 14:22:15 alright, I think we have a plan 14:22:23 you are in USA, why not go to Boston? 14:22:56 good question. I was planning to, but my funding request was not granted 14:23:25 otherwise I would have traveled to Boston 14:23:39 what a pity 14:23:59 yeah. 14:24:28 so that's why I am unable to go to Boston this time. 14:25:13 hopefully your visa will go through and you will be able to represent us, like you did in Barcelona 14:25:46 yes, hopefully 14:25:51 :) 14:26:02 any other thoughts on this topic? 14:26:09 np 14:26:33 alright. lets keep in sync over next few days as we will have to take a decision 14:26:42 sure 14:26:47 cool 14:26:53 Lets talk about patches now 14:27:07 I reviewed your solum gate fix patch this morning 14:27:28 I have added my comments to it 14:28:58 let me check with my phone 14:29:09 I can tell you 14:29:43 One comment was about adding blueprint link to the commit message and adding a bug in launchpad for the skipped tests 14:30:26 and other comment was about the authentication step that we used to do for validating the admin_creds in the previous code 14:30:36 that part seemed to have been removed in the patch 14:30:52 we changed the way for auth 14:31:09 using session the general ways 14:31:14 I see 14:31:17 keystoneauth1 14:31:46 so is the validation of admin_creds happening as part of session creation? 14:31:53 yep 14:32:02 got it 14:32:09 the session is validate 14:32:20 I see 14:32:41 then, do we need to catch validation failed exception? 14:34:35 the v3 init have the unauthed exception 14:35:01 others place doesn't need this 14:35:14 I see 14:35:25 so that answers one of my comments 14:35:46 other comment/question about the skipped tests 14:36:27 I think it is fine for now to skip them as they are related to the construction of various clients 14:36:54 but lets add a launchpad bug to track why we are skipping these tests 14:37:00 the old unit test using username and password to authorize, I have changed this using session, so can't pass the old unittest 14:37:11 ah okay 14:37:20 Please add above explanation to the launchpad bug 14:37:38 It captures the reason why the tests are being skipped 14:37:45 ok, i will do this tomorrow morning 14:37:51 sounds good 14:38:02 also, add direct link to the blueprint 14:38:20 once those things are done I think the patch is good to go 14:38:32 sure, with this change we can support keystone v3 14:38:46 btw, thanks a LOT for fixing the gate and adding the v3 support 14:39:08 getting v3 support is awesome!! 14:39:16 devstack change keystone do not using port 14:39:33 this caused gate red 14:39:37 really? 14:39:56 yep 14:40:09 is this related to apache config changes? 14:40:26 all the services have been asked to convert to run under apache 14:40:34 np, just keystone change 14:40:40 I see 14:40:58 yes, we already satisfied 14:41:02 I don't remember seeing email on the dev list about it. may be I missed it 14:41:28 you can check the devstack patches 14:41:38 yes, I know that the running under apache is already done. 14:41:53 sure, I will take a look at the devstack changes 14:42:22 but this seems like a breaking change, so should have been publicly announced 14:42:35 may be there was email, I might have missed it 14:42:44 on the topic of apache 14:42:58 I am looking at https://review.openstack.org/#/c/456092/ 14:43:32 Is this ready? 14:43:49 this add the config file 14:44:04 yes, this is ready 14:44:21 alright 14:44:53 hopefully the gate will clear this 14:45:18 cae not merge 14:45:21 can 14:45:33 because of the gate 14:45:38 hmmm 14:45:41 yep 14:46:07 lets merge the keystone patch tomorrow and then I will re-approve the apache and glance v1->v2 change patch 14:46:19 ok 14:46:35 any other patch that we should discuss about? 14:46:49 np 14:46:57 cool 14:47:22 any other topic that you have on mind? 14:47:34 I just had two quick points 14:48:27 nothing from me 14:48:42 ok 14:48:54 so one point was about TC election results 14:49:12 the results were out last week 14:49:21 hopefully you saw the email 14:49:45 :( missed the email 14:49:48 if not, you can find it in the openstack-dev mailing list archieves 14:49:54 let me find that 14:51:02 http://lists.openstack.org/pipermail/openstack-dev/2017-April/115770.html 14:52:36 so apart from that the other point that I had was -- if guoguo and you had any further conversation? 14:53:42 np, recently didn't get connect with him 14:53:49 ok 14:54:06 I was just curious to know 14:54:23 but that is all I had for today 14:54:33 thanks 14:54:55 alright, lets end the meeting then 14:55:09 bye devkulkarni 14:55:13 lets keep in sync over next few days 14:55:20 sure 14:55:20 thanks zhurong_phone 14:55:27 have a good night 14:55:34 #endmeeting