14:01:16 #startmeeting glance-artifacts 14:01:17 Meeting started Mon Jul 27 14:01:16 2015 UTC and is due to finish in 60 minutes. The chair is ativelkov. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:21 The meeting name has been set to 'glance_artifacts' 14:02:08 Hope this is the right channel ) 14:03:14 #link https://etherpad.openstack.org/p/glance-artifacts-sub-team-meeting-agenda 14:03:18 o/ 14:03:19 agenda is here 14:03:22 o/ 14:03:26 * kragniz lurks more 14:04:03 So, the design for "unified v3 api" is ready 14:04:38 I have a working prototype which is able to work with both artifacts and legacy v2 images as part of v3 API 14:05:00 awesome! 14:05:17 o/ 14:05:18 ativelkov: have you run it past the API-WG yet? 14:05:46 sigmavirus24: not yet. Not all the concerns from the original specs are addressed yet. 14:05:56 When I finish with them, will do that 14:07:03 The current implementation for images is done as a simple wrapper of v2 controllers, thus it inherits all the current problems of v2, such as race conditions, ugly domain model etc. However, if we have the API stable, we may improve the implementation later 14:08:08 Will try to present what I've got at the upcoming mid-cycle summit. There is a session planned, yet I don't know the exact day and time 14:08:23 how you suppose to do dependencies between artifacts and images? 14:08:47 mfedosin_: yes, but just one way in this case 14:08:58 If they are located in different tables with different ids 14:09:33 mfedosin_: this becomes as dynamic reference in this case 14:10:30 i.e. an artifact depends on an artifact with type "image" and a specific id. It is up to the image plugin (which is not actually a plugin but a part of Glance) to handle this request. 14:10:31 should the users know the inner implementation of our db? 14:10:44 mfedosin_: nope, they don't care 14:11:30 I mean somewhere in api it shoul be stated that id-dependencies between artifacts and images are forbidden 14:11:35 It's just a different implementation. It could affect the performance, but currently the images don't have their own dependencies, and thus there are no transitive dependency chains 14:11:59 mfedosin_: nope, they are not forbidden 14:12:22 ID-dependency is just a custom case of more generic dependencies 14:12:44 in case of "new" artifact data-structure they can be optimized to fetch all transitives in a single request 14:13:25 in case of images (or other artifact types which define their own DB driver) such optimization is not possible, however the API itself remains valid. 14:13:49 but do you remember when we talked about amazon format (ami-ari-aki) you suggested to organize dependencies between these three images 14:14:10 mfedosin_: right, but v2 images do not have dependencies at all 14:14:26 so? 14:14:59 So currently images may not depend on anything 14:15:00 It's kind of forbidden for images, right? 14:15:09 Right 14:15:23 We may add dependencies in legacy DB structure later 14:15:33 yep 14:15:43 or modify new dependency table to allow working with images 14:15:46 or something else 14:16:05 it's an implementation detail and may be deferred for future 14:16:08 we need to think carefully how to implement the transtion 14:16:22 agree with you 14:16:29 Sure. What we are looking now for is an ability to "wrap" v2 with v3 code 14:17:24 And we currently know how to do that 14:17:42 with oslo.versionedobject, I gyuess 14:18:06 mfedosin_: well, they are not directly imvolved 14:18:11 involved 14:18:31 as v2 images don't use 14:18:35 don't use it 14:19:11 but still, the base class for the plugin-type (I call it GlanceObject) will be o_vo.VersionedObject indeed 14:19:32 but it will not define any structure at all, leaving it up to the inheritors 14:19:41 hard to understand for the first time, but I think we are moving in the right direction 14:19:52 I'll give more details on the meetup 14:20:17 Will it be tomorrow? Afair... 14:20:46 it starts tomorros and lasts for 3 days 14:20:56 #link http://etherpad.openstack.org/p/liberty-glance-mid-cycle-meetup 14:21:00 this is the agenda 14:21:39 There is a topic "Glance v3 + other APIs" - thanks to nikhil_k for putting it there 14:21:58 There is no actual timeslot allocated yet 14:23:14 so, if you want to participate, state your interest in that etherpad 14:23:38 and put your tz there, so they can pick a better schedule 14:23:54 for sure I will :) 14:24:04 as nikhil_k is ooo today, the actual time allocation will probably happen tomorrow 14:24:18 Any other questions? 14:24:50 please review 200000 :) I added some missing exceptions handlings there 14:25:33 I will, though it's not artifact's related :) ping people in #openstack-glance for more attention ) 14:25:52 And artifacts too 14:26:28 there was my TODO to add them to 'upload' 14:26:38 And also I'm going on vacation next week for two weeks 14:27:07 so I'll not be able to participate these meetings 14:27:15 :( 14:27:33 but I will review code and make commits =P 14:28:08 Yeah, that's what we usually do on vaction: code review and comits 14:28:21 afaik, Alex will be in business trip all next week 14:28:52 Yup, but I'll still try to participate in Glance activities 14:29:13 so, if no other questions on artifacts, let's wrap up 14:29:32 ativelkov: one request: can you post what you have of the API spec/ 14:29:34 *? 14:29:52 * sigmavirus24 wants a head start on reviewing it 14:29:57 sigmavirus24: I'll try finalizing that doc this week 14:30:09 Thanks 14:30:12 Thanks all 14:30:13 #endmeeting