14:00:15 #startmeeting Glance 14:00:18 Meeting started Thu Feb 26 14:00:15 2015 UTC and is due to finish in 60 minutes. The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:22 The meeting name has been set to 'glance' 14:00:29 o/ 14:00:29 o/ 14:00:31 o/ 14:00:39 https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:00:48 o/ 14:00:50 o/ 14:01:06 o/ 14:01:07 o/ 14:01:43 #info K-3 FF proposal date is Mar 12 for Glance 14:02:15 o/ 14:02:19 That means, all the feature related code needs to be proposed & merged by that date 14:02:20 o/ 14:02:20 o/ 14:02:39 o/ 14:02:47 https://launchpad.net/glance/+milestone/kilo-3 14:03:19 Please take a look at that and try to review the linked features + Artifacts on priority 14:03:48 mfedosin: ativelkov : Can anyone of you add Artifacts related BPs to k3? 14:04:28 nikhil_k: sure. Do you want a single artifacts BP or separate BPs for each commit? 14:04:29 nikhil_k, sure, we're working on it 14:04:48 ativelkov: as many specs we've, 14:04:50 o/ 14:04:56 please update their milestone to be k3 14:05:11 this means two: one for semver and another one for eveything else 14:05:20 yes 14:05:24 ok 14:05:50 (unless discussions from here on call for any other one, I'm trying to be generic) 14:06:09 Also, we've had several requests about https://blueprints.launchpad.net/glance/+spec/sighup-conf-reload 14:06:39 I just wanted for someone with enough cycles to test that functionally and double check if we did not miss anything 14:07:57 #topic Question: grouping artifacts by type version in the list output (as proposed on mini-summit) 14:08:14 Who proposed that? 14:08:26 ativelkov: ? 14:08:28 ativelkov: looks like you? 14:08:30 (going by color) 14:08:33 yes 14:08:39 Just a quick question 14:08:57 on the mini-summit there was a proposal to group artifacts by the version of their type 14:09:17 I mean, in the "list artifacts" API output 14:09:38 in case if the type version is not specified 14:10:08 This remains an action item on me, so I wanted to clarify if that is a good idea or not 14:10:29 I stand +1 on that 14:10:51 I'm wondering if we necessarily have to do it by default 14:11:01 Why can't it be done on client side? 14:11:08 how about we provide a param for grouping 14:11:22 The problem with it is sorting and getting the marker for pagination iteration 14:12:04 if this is just a plain list, then the id of the last record is the marker for the next page request 14:12:28 if the output is grouped then there is no such thing as a "last record" 14:13:15 ativelkov: true, that makes things a bit complex 14:13:47 and the sorting order between items in different group cannot be easily defined if the client wants to compare them 14:14:12 ativelkov: ok, how bad would it be to do on glaceclient? 14:14:19 on the contrary, grouping may be always done on the client-side, as the records contain all the needed fields 14:14:35 nikhil_k: that's what I wanted to suggest: leave it for client(s) 14:14:37 And sorted() is rather fast once we have all the records 14:14:58 ativelkov: ah ok, so supported client and not the consumers. cool 14:15:32 sigmavirus24: the worry there is that, people might want to fetch more records out of the DB frquently 14:15:45 nikhil_k: yep 14:16:31 So, if everybody agrees, then I drop that action item: we'll leave API call to output just list of items, not groups 14:17:18 sure, please keep a note on the spec that mentions this drawback 14:17:28 ativelkov, was there a good usecase for grouping by default? 14:17:50 hemanthm: I don't know - this was said by somebody at the summit 14:18:16 I didn't remember the usecase behind that. 14:18:30 hemanthm: The general feeling was about usability. Not having to go through all the non relavant artifacts 14:19:00 ok, we can discuss the details offline if that's ok 14:19:07 nikhil_k: if you want to get only the relevant ones, you may always specify type version explicitly 14:19:14 nikhil_k: isn't that where filtering would be more useful? 14:19:33 e.g. GET /v2/artifacts/someType/v1.2/ 14:19:53 #info ativelkov to update the Artifacts spec to state that grouping of API results is too complicated due to pagination 14:20:32 kragniz: ativelkov : true but if you've multiple ones and are doing something between browsing and searching then this becomes relevant 14:21:18 can we move on? 14:22:16 I think we can discuss the details offline and/or on ML 14:22:37 sure 14:22:45 #topic Abandoning stale PS from review 14:22:57 https://etherpad.openstack.org/p/glance-cleanout-of-inactive-PS 14:23:02 http://comments.gmane.org/gmane.comp.cloud.openstack.devel/46352 14:23:38 Please reply to that thread if you've something to say 14:24:20 Guess jokke_ proposed that and is not around so, may be we'd move on 14:24:31 yeah, move on 14:24:51 #topic python-glanceclient release 0.16.0 14:25:04 http://osdir.com/ml/openstack-dev/2015-02/msg01858.html 14:25:09 http://docs.openstack.org/developer/python-glanceclient/#id1 14:25:50 (I think it was jokke_ again who proposed that topic ??) 14:26:13 or pkoniszewski 14:26:22 That's all the relevant info, (I think) we need 14:26:29 or krykowski 14:26:31 heh 14:26:39 #topic Questionable reviews 14:26:43 Ohai that's me 14:26:46 https://review.openstack.org/#/c/159068/ 14:27:08 sigmavirus24: sure 14:27:11 So https://review.openstack.org/#/c/159068/ is questionable because it presents a serious backwards compatibility issue with the glanceclient 14:27:21 o/ 14:27:41 It's also indicative of the fact that we either need to dedicate more time to bug triaging so people don't just pick up non-triaged bugs 14:28:18 The less tangential question here is: Do we even want to require a name for a created image? 14:28:37 it's weird not to have one, but as long as there's a uuid, who cares? 14:28:40 Commenting on that review/bug would be helpful 14:28:55 rosmaita: right and if the API doesn't require one, why should the client is the bigger question 14:29:15 I'd just -2 it as that was the original use case, name is not a required attr so we'd not force it 14:29:51 sigmavirus24: you are correct, the "official" glanceclient should respect the API, private glance clients can do whatever they like 14:29:54 The bug was never discussed either 14:29:58 rosmaita: right 14:30:18 ativelkov: kragniz other thoughts? 14:30:29 sigmavirus24: I do not think that discussions are mandatory on bugs before someone picks it up. Many times the bugs are filed because you're working on something 14:30:34 I agree with rosmaita 14:30:43 Well, I agree that if the name is not required, then we should not enforce it in glance cli. 14:30:54 seems a bit late for a v1 change of this kind IMHO 14:31:02 heh 14:32:03 looking at the api docs, name is not marked as optional ... but there is no uniqueness requirement, and an empty string is a string, so ... 14:32:12 I think that this discussion (allowing to create images without a name) happens periodically :) 14:32:12 So the other one, I added before Flavio and nikhil_k chimed in but everyone should still take a look at the bug: https://launchpad.net/bugs/1279832 and review: https://review.openstack.org/#/c/158982/ 14:32:14 Launchpad bug 1279832 in python-glanceclient "nova image-list can run slowly." [Wishlist,In progress] - Assigned to Shashwat Srivastava (shashwat-srivastava) 14:33:24 o/ 14:34:11 why does this keep happening to me? 14:34:16 Anyway, I think we can move on unless people want to discuss those further 14:34:17 sigmavirus24: thanks for the ping 14:34:22 flaper87: you're welcome 14:34:31 I'll ping you more often and regularly in the future =P 14:34:37 sigmavirus24: THANK YOU! 14:34:39 :D 14:34:41 hmm, flaper87 good point. may be I need a courtesy ping 14:34:51 nikhil_k: please please please 14:34:54 I'd really appreciate it 14:34:58 I do have a calendar reminder 14:35:02 I just don't have a calendar 14:35:03 we need a meeting bot that pings people in #openstack-glance 14:35:04 :P 14:35:09 cool 14:35:11 Just don't create an action item for that =P 14:35:18 #topic glance_store release 0.1.11 status 14:35:26 http://lists.openstack.org/pipermail/openstack-dev/2015-February/057386.html 14:35:36 https://launchpad.net/glance-store/v0/v0.1.11 14:35:40 List glance_store 0.1.11 in https://trello.com/b/GFXMXxsP/openstack-glance 14:36:15 * flaper87 clicks and clicks 14:36:20 * flaper87 loves those dogs 14:36:26 thanks to flaper87 , that trello board is readable in public (public read access is tested, if you cannot hit it please refresh or try a different tab/browser) 14:36:51 that's on on that from me 14:36:58 moving on.. 14:37:12 :) 14:37:29 #topic glance_store release 0.1.12 14:37:37 https://launchpad.net/glance-store/+milestone/v0.1.12 14:37:41 https://trello.com/b/GFXMXxsP/openstack-glance 14:38:03 We usually set a tentative date on the release so that people are aware 14:38:05 kragniz: we should add our socket leak fixes to the 0.16.1 client release? 14:38:15 I need to sync again with cindy to understand the status of the glance_store refactor 14:38:24 but It'd be lovely to have it in 0.1.12 14:38:39 If you need some specific ones in a particular release, the dates can be adjusted +2 days 14:38:45 Do we want a glance_store release before the Kilo release ? 14:38:48 mclaren: I was looking at 0.17.0 for those 14:38:57 like 2 weeks after K-3 ? 14:38:59 Another reason why the release can be delayed: there aren't enough commits to be released 14:39:07 * flaper87 literally made that up 14:39:21 kragniz: they unbreak nova though, so high priority in my view... 14:39:40 One release would be a bit before K3 14:39:58 Mar16th or so 14:40:04 mclaren: they're not backwards incompat and they're bug fixes so +1 on 0.16.1 if we can get them reviewed 14:40:08 * flaper87 confused are we talking about the client or glance_store ? 14:40:23 :P 14:40:25 flaper87: store 14:40:26 mclaren: yeah, good point 14:40:32 flaper87: some are talking about client 14:40:40 * flaper87 rolls eyes :P 14:40:45 sorry, speaking of turn... 14:41:17 re glance_store it sounds good to have 1 or even 2 minor releases before Kilo :) 14:41:42 There are still things that are a must fix before kilo goes out like the chunk/offset handling 14:41:48 zhiyan: has patches for that 14:41:59 flaper87: sure (just trying to not break any gates and keep things smooth at the release week) 14:42:23 if we can get those patches reviewed soon, it'd be awesome 14:42:34 I'll make that a priority for me 14:42:47 appreciate it 14:42:54 #topic Metadef Notifications 14:42:55 Thanks for you incoming review 14:43:09 TravT: wanna go? 14:43:20 This review is ready, we think: https://review.openstack.org/#/c/148546/ 14:43:36 krykowski: updated it last night with outstanding comments 14:43:47 nice 14:43:53 yup, its in really good shape ;) 14:44:34 krykowski: you might want to check the jenkins failure though 14:44:50 people _may_ not review something that has -1 on it already 14:45:06 hmm I don't see a jenkins failure 14:45:09 it has +1 from Jenkins 14:45:20 Jenkins is a good guy :) 14:45:35 TravT: krykowski : my bad, I confused you for flaper87 14:45:44 a grave mistake 14:45:52 sorry about that, we'r good 14:45:57 always a good idea to assume flaper87 has jenkins failures? 14:46:03 ;) 14:46:05 (and I'm asleep) 14:46:26 anyways, moving on.. 14:46:40 TravT: that was harsh =P 14:46:50 #topic glanceclient next few releases 14:47:23 TravT: heh, just something that I was looking at and switched the tabs before coming back to IRC window :P 14:47:37 https://launchpad.net/python-glanceclient/+milestone/v0.16.1 14:47:48 #info This is due next week. 14:48:12 https://trello.com/b/GFXMXxsP/openstack-glance 14:48:21 card name glanceclient 0.16.1 14:49:01 One more is created in LP scheduled to be released a few days before K3 14:49:06 https://launchpad.net/python-glanceclient/+milestone/v0.17.0 14:49:36 mclaren: Did you have something to mention for that earlier? 14:49:39 TravT: LOL, is that because I always do? :P 14:49:44 nikhil_k: yeah 14:49:51 flaper87: that was the joke ;) 14:49:58 flaper87: wondered if you were still listening ;-) 14:50:05 nikhil_k: can I just add to that launchpad ticket? (What's the process?) 14:50:08 sigmavirus24: no no, I'm serious, I always do :P 14:50:32 mclaren: yes, please feel free to add it to LP. We're using the trello board to see if there are any blockers 14:50:34 * flaper87 clicks on the client card 14:50:47 LP can get crowded sometimes 14:51:08 https://review.openstack.org/#/c/157516/ and https://review.openstack.org/#/c/156975/ 14:51:17 mclaren: do you mean target bugs to a release? 14:51:32 mclaren: you can do it from the launchpad bug page 14:51:37 we found that nvoa and cinder would fall over due to too many open fiel descripters 14:51:38 re client, I need to get back to this: https://review.openstack.org/#/c/140336/ 14:51:40 ("target to milestone") 14:51:45 but I don't think it should block the release 14:51:55 so, feel free to move that one to the next release 14:52:03 (if needed) 14:53:10 flaper87: please do so, if possible for 0.16.1 14:53:20 moving on.. 14:53:23 #topic Multivalue operator support 14:53:38 pkoniszewski: that's you 14:53:43 kragniz: looks like I added them telepathically :-) 14:53:45 thank you 14:53:53 mclaren: that was me :P 14:54:03 mclaren: mind controls kragniz ... good to know ;) 14:54:13 sigmavirus24: it's a problem 14:54:17 * flaper87 wonders who mind controls mclaren 14:54:21 so both patch sets are in a really good shape, actually both had +2 on (had to add two points to spec that zhiyan requested so it dropped) 14:54:43 I'd like to ask for final review there https://review.openstack.org/#/c/147264/ - specification 14:54:43 pkoniszewski: 2 tiny nits from me and then I'm +2 on the spec 14:54:45 (sorry) 14:54:53 and the code - https://review.openstack.org/#/c/148213/ 14:55:02 sure, leave them and i'll address it asap 14:55:06 thanks a lot! 14:55:16 * sigmavirus24 is going to look at the code now 14:55:28 thats all for me 14:55:36 thanks pkoniszewski, I think based on the momentum we can try to get them in this week 14:55:41 * sigmavirus24 is so glad to see zhiyan doing reviews again 14:55:48 == nikhil_k 14:56:02 me too :) 14:56:04 #topic Open Discussion 14:56:11 Folks, I am glad to introduce you our technical writer Olena :) 14:56:11 For spec ? Or code? 14:56:26 zhiyan: both 14:56:30 *cough* https://review.openstack.org/#/c/159129/ *cough* 14:56:35 Hi Olena ! 14:56:38 damnit, gate failure (facepalm) 14:56:38 hi Guys! 14:56:46 Revised spec you have a good eyes 14:56:48 Olena: HEY! :) 14:56:49 I am excited to join the Glance team 14:56:51 flaper87: high five jenkins in the face instead ;) 14:57:03 sigmavirus24: good idea, gooooood idea! 14:57:06 Olena: Hi :) 14:57:10 :D 14:57:11 =) 14:57:16 flaper87: http://giphy.com/gifs/cough-ToLQAiSdwq33G 14:57:22 Olena: welcome! 14:57:33 nikhil_k: huahuahauhauhau 14:57:43 Welcome! 14:57:50 welcome Olena! 14:57:50 good thing the other 2 are green 14:58:00 (jenkins green, not the other green) 14:58:00 Welcome Olena ! 14:58:02 I just want to point out that https://review.openstack.org/#/c/140151/ will be unnecessary for any one using requests 2.5.3 or higher but it is still absolutely necessary for anyone using anything less than that 14:58:04 Olena: maybe you can revise this page: https://wiki.openstack.org/wiki/Glance-where-are-the-docs 14:58:25 sigmavirus24: jeeeez, I wanted to get back to that one last week 14:58:32 I'll review it asap 14:58:38 flaper87: thank you 14:58:47 sigmavirus24: yes, thanks for bringing that up. 14:58:50 * sigmavirus24 needs to stop working upstream of openstack so he can complain about himself 14:58:51 and I will take a look as well 14:59:41 Olena: Thanks for your feedback on the docs that mfedosin shared with us a few days back! 14:59:56 oh, my pleasure 15:00:05 Olena: please do let know if we can help you get familiar with Glance 15:00:23 #openstack-glance is the place we're hiding in :) 15:00:38 =) okay 15:00:48 ok, thanks all for joining.. 15:00:51 o/ 15:00:55 nikhil_k: thanks! 15:00:58 Olena: and hi! 15:01:00 #endmeeting