14:00:13 #startmeeting glance 14:00:13 Meeting started Thu Jul 7 14:00:13 2016 UTC and is due to finish in 60 minutes. The chair is nikhil. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:17 o/ 14:00:17 The meeting name has been set to 'glance' 14:00:19 o/ 14:00:23 #topic roll call 14:00:31 o/ 14:01:06 let's give a couple of mins for people to show up 14:01:09 o/ 14:01:13 o/ 14:01:33 o/ 14:01:37 ok, let's get started 14:01:39 #topic agenda 14:01:42 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:01:45 o/ 14:01:50 o/ 14:01:51 small agenda today 14:02:18 let's make sure we raise any important concerns if any 14:02:28 #topic Glare updates ( mfedosin ) 14:02:57 hello 14:03:23 so, we implemented artifact type for murano and tested it 14:03:42 several small bugs were found and fixed 14:04:08 and in general murano is ready to switch to glare v1 when it's merged 14:04:30 tomorrow I'll attend a meeting with Heat team 14:04:41 and will try to implement artifact type for them 14:05:13 also Serg Skripnick implemented some POC for app-catalog 14:05:22 o/ 14:05:38 true 14:06:06 we implemented a lot of functional tests for glare and now it's pretty stable and works really nice 14:06:50 for sure there are many bugs, but all required functionality and common scenarios work 14:07:03 :thumbsup: 14:07:26 spec was reviewed and we got +2 from Brian 14:07:42 rosmaita: thanks for you support 14:07:49 :) 14:08:04 so, all people are waiting when it's merged 14:08:27 btw, I added a small doc about installation of glare in devstack 14:08:33 there is a link in the spec 14:08:39 but I'll copy it here 14:08:54 #link https://review.openstack.org/#/c/283136/ 14:09:14 #link https://docs.google.com/document/d/1KyY8VB00XvehtpBcLDo_Andx0BDgG-C7E_TdhfvcGv4/edit 14:10:06 I wrote it mostly for myself, but all required commands are there 14:10:35 nikhil: is there any chance that you'll review the spec? 14:10:52 Is there an offical doc for the installation guidelines? 14:11:15 mfedosin: yes, I will review it. I have thought about some overlap with glance and will test those with your installtion link. 14:11:15 I guess we can't release doc for non-merged functionality 14:11:27 what kairat__ said 14:11:37 bunting: yeah, it's a temporary doc 14:11:48 Makes sense 14:12:27 so, we have end of N-2 next week 14:12:42 15th of July afair 14:13:25 as far as I know no features are allowed to be merged after that, right? 14:14:06 july 29th is spec freeze 14:14:18 2weeks before newton-3 is feature freeze 14:14:56 nikhil: it's good to hear 14:15:05 newton-2 is next week, but we will try to release it on tuesday not thursday ie. on 12th 14:15:42 ppl from other projects want glare to be merged in n-2 14:16:04 so they will be able to implement poc in Newton 14:16:19 I mean Murano, Newton and App-Catalog 14:16:46 since all code is done and tested 14:17:19 can we do it on Monday, for example? 14:18:30 you want multiple thousands of lines of code to be merged in one day? 14:19:01 there was a month for review of code 14:19:05 o/ 14:19:51 there is not so much code btw 14:20:06 and will split it in 10 small patches 14:20:37 o/ jokke_ 14:20:38 currently there are 7, but we added sqlalchemy db, locks and schemas 14:20:45 jokke_: o/ 14:22:14 afaict, there is no review on glare patches today 14:22:27 we can begin with spec :) nikhil jokke_ your feedback is very welcome 14:22:45 can't speak for others, but I would be hesitent to +W those 14:22:58 I can try to push the spec by newton-2 though 14:24:39 personally, with different events in june I didn't get enough time for consolidated reviews. our june focus was to move forward on specs and different types of proposals. 14:25:09 nikhil: again, if glare v1 is not available till the end of n2 then none of external projects will be able to use it in Newton 14:25:45 hm, that probably pushes adoption even furhter to O cycle 14:25:52 i have a deja vu feeling =) 14:25:58 this is news to me and am unable to understand why they think so 14:26:33 last couple of cycles there were very similar concerns (most of them about glance v3 though) 14:27:35 well I do understand that they can't merge any changes that depends glare before glare is actually merged, but I don't see why they can't start the work while we are reviewing the code, latest after the spec has been approved and there is likelyhood us merging the code in Newton 14:27:58 mfedosin: I think we need to have all the glare stakeholders at glare meeting on monday to discuss all such issues. 14:28:36 the glance v3 fallout seems to be hitting us back badly. clarification on the difference seems necessary. 14:29:06 nikhil: I don't mind to discuss it with stakeholders on Monday 14:29:20 but app-catalog is going to switch to glare 14:29:40 now they use outdated html pages 14:30:02 and people have to push edits on review to add things there 14:30:32 they have been waiting glare so badly for last six month 14:31:11 what comes to the sudden urgency about this, there is two things that needs to be kept in mind a) merging that code needs to happen so that it's comfortable for glance community as glare is part of glance b) what I was surprisedly asking already right after summit, glare is not part of glance priorities this cycle 14:31:14 and what's the problem to merge the code now? glare is a separate service, it doesn't affect glance at all 14:31:26 all of this isn't a strong enough reasoning to compromise on our reviews 14:31:45 I don't think it's realistic expect that it becomes suddenly priority when there is few weeks left of the development cycle 14:32:49 nikhil: what have you been doing all last month? why I haven't seen reviews from your side? and now you want more time for what? 14:32:58 that said, I'd be more than happy to see it being stable and merged sooner rather than later, but I can't be speaking on behalf of the whole community 14:33:21 I would like for the community to be civil about priorities, process, lite-specs, etc. things. the appropriate time to discuss that was pre-summit, summit and a bit of time after that. 14:33:53 I don't have to explain my schedule to everyone 14:34:09 jokke_: when adoption begins we can address issues much quicker, now we're in development vacuum - only functional tests are there. so I agree with you 14:34:23 if you have attended events and the follow up stuff, you know what we have been focusing on. 14:35:50 nikhil: one question - what are we waiting for now? 14:36:00 I fail to understand why there isn't a single review on the glare code? 14:36:47 if I have to review many specs, I can't spend entire day on one single feature 14:37:04 i suspect it's because of the '[WIP]' in the commit message title? 14:37:11 (why no reviews, i mean) 14:37:29 I tried to encourage sudipto, abhishek and other new members interested in glance to review glare 14:37:44 we split the code as requested, one single patch is convenient for updates 14:37:56 because it does not ddos reviewers 14:37:57 1. there were reviews - we addressed them 14:38:17 after many conversations with new members and many motivation pushes to them, they have disappeared giving me their feedback privately. 14:39:36 rosmaita: for myself, I will not review the WIP patch, because it means the patch is no ready IMO. just my personal idea. 14:39:59 wxy: my point exactly 14:40:23 there is a set of stable patches that are ready for review https://review.openstack.org/#/c/330458/ 14:40:31 sorry, that's not true 14:40:32 https://review.openstack.org/#/q/status:open+project:openstack/glance+branch:master+topic:bp/glare-api 14:40:50 Honestly I've had three main reasons where the later 2 are directly impacted by the first 1) limitations of my time 2) The spec has not been agreed on / merged making it difficult to review if we are implementing by the desing 3) as Brian mentioned [WIP] has been generally the indication "This is not ready for review, pushed to gerrit to see how tests behaves against the change" 14:41:01 rosmaita: there's confusion on what is WIP and what is ready for review 14:41:15 we prepared these patches specially for community reviews 14:41:26 so for me reviewing something that has the points 2) & 3) is not good use for the limited time I have in my disposal 14:42:39 so we discussed this at virtual summit 14:42:41 this doesn't seem like a productive debate 14:42:46 and concern was the saem 14:43:04 that we will be lack of reviews if sped won't be merged 14:43:23 now we failed with the same case AFAIU 14:43:55 #link https://etherpad.openstack.org/p/newton-glance-virtual-midcycle 14:44:02 scroll till the end 14:44:41 mfedosin, kairat__: I will re-review the spec after this meeting again 14:44:42 we had reviews before July, 5th 14:44:55 jokke_: thanks :) 14:45:45 kairat__: it's rarely (or small part) about the process. we really need to work as a community. 14:46:05 having said that, I think for spec good work has been done. we've really good number of reviews there. 14:47:11 and many +1s have come rather recently which is why I am positive about spec before newton-2 but not the code 14:47:50 for instance, no one from others teams who want to use glare (in a rush) have bothered to review the code 14:48:04 do you remember that there are plans to make v1 stable in n3 14:48:18 it will be almost impossible without any adoption 14:48:37 to add to that, they are imposing a deadline on glance team without discussion even at the summit or after, which is unacceptable 14:49:32 we probably need to move on ... what is the summary of the above discussion? 14:49:53 I think there is no summary 14:49:55 (or do we need a cooling-down period before summarizing) 14:50:08 we're waiting for nikhil to review the spec 14:50:16 also, on lack of reviews, I want to stress that we do have a separate meeting and we need to use it to move forward community discussions 14:50:54 mfedosin: maybe send a reminder of the glare sync to ML for interested parties? 14:51:11 until now, most of the feedback given to me was that people don't understand glare completely 14:51:36 the spec will fix that, it is extremely thorough 14:51:51 +1 to rosmaita 14:51:56 I can share some of my findings that seem critical (but is untested) in the -glance channel right after this meeting. 14:52:04 lets give this bit cooldown, and continue offline ... we have 9 min, so nikhil how about moving on? 14:52:05 that;s why we wrote use cases in spec 14:52:17 if someone is vague about glare after reading that spec, they probably should take up a different line of work 14:52:50 rosmaita: it will be clear when I state some of my concerns on why people think so 14:53:09 (I was of same opinion that spec should clarify all things) 14:53:53 #topic Project mascot for glance 14:54:11 so a new initiative and it's around marketing 14:54:44 we need to finalize on this by jul 27th 14:54:57 here is my suggestion: http://largestfastestsmartest.co.uk/wp-content/uploads/2006/09/wpc0bc5e54_0f.jpg - don't know if it's a good marketing tool, though 14:55:30 so, I need initial suggestions by tuesday so that if there's overlap with other projects we get time 14:55:48 criterion: anything from the natural world—an animal, fish, plant, or natural feature such as a mountain or waterfall 14:56:01 Should it be related to glance if possible? 14:56:02 nikhil: that's nice and well planned heads up for such 14:56:04 (my suggestion is both glancing and glaring) 14:56:31 #action all: send nikhil suggestion for project mascot 14:57:28 #topic open discussion 14:57:53 i think item 3.2 will require a bit of time, but the idea is that we should structure db changes a bit in this release to help with eventual rolling upgrades 14:58:14 for item 3.3, i would like to take this to the api-wg in an hour unless there are objections 14:58:29 https://bugs.launchpad.net/glance/+bug/1585917/comments/3 14:58:29 Launchpad bug 1585917 in Glance "member-create will raise 500 error if member-id is greater than 255 characters" [Undecided,Confirmed] - Assigned to Abhishek Kekane (abhishek-kekane) 14:58:49 unless people think this schema proposal is absurd 14:59:34 rosmaita: what we have currently is absurd too 14:59:45 nikhil: is it ok if i float the idea with api-wg, or do you want me to wait a week? 14:59:51 rosmaita: works for me 14:59:59 rosmaita: api-wg 15:00:02 ty, i will see what they say 15:00:11 rosmaita: +1 to reach api-wg 15:00:28 rosmaita: if you can link me when they are discussing, that would be helpful. 15:00:28 rosmaita: I think it's ok to ask their feedback even if we're not decided yet 15:00:34 #action rosmaita to take member schema proposal to api-wg 15:00:34 and we're out of time 15:00:40 thanks all! 15:00:40 thanks all for joining 15:00:47 #endmeeting