14:01:16 <nikhil> #startmeeting glance_artifacts_sub_team
14:01:17 <openstack> Meeting started Mon Sep 21 14:01:16 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:19 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:21 <openstack> The meeting name has been set to 'glance_artifacts_sub_team'
14:01:23 <mfedosin> hey
14:01:27 <mfedosin> o/
14:01:33 <kairat> o/
14:01:34 <nikhil> hi
14:01:42 <nikhil> #topic agenda
14:01:45 <mfedosin> Alex it on another meeting so he's not available
14:01:47 <nikhil> there's no set agenda for today
14:01:52 <nikhil> ah ok, np
14:02:05 <nikhil> do we have any discussion items or should we have open discussion?
14:02:17 <mfedosin> let me remind you about our bugs :)
14:02:29 <nikhil> ah yes
14:02:37 <nikhil> I think I should be able to block RC1 on that
14:02:42 <nikhil> if not we can request a RC2
14:02:44 <mfedosin> Murano really needs these fixes and Alex is worrying
14:02:49 <nikhil> ok
14:02:51 <dshakhray> o/
14:02:55 <nikhil> I will review them today
14:02:56 <mfedosin> thanks :)
14:03:07 <mfedosin> cool!
14:03:20 <mfedosin> couple of words about future work
14:03:36 <nikhil> #action nikhil to send reminder for RC1 bugs to cores
14:03:55 <mfedosin> Alex started to write an article about his vision of artifacts in v3
14:04:15 <nikhil> awesome, ready for a preview yet?
14:04:21 <mfedosin> we have been discussing it all week
14:04:37 <mfedosin> I don't know about a preview :)
14:04:52 <mfedosin> he just asked me to tell it to you
14:05:03 <mfedosin> but there are many open questions
14:05:16 <nikhil> I see, something I need to discuss with him then
14:05:33 <nikhil> ok, any important ones you can share for now?
14:05:52 <mfedosin> no, nothing special
14:06:19 <mfedosin> I made a picture of our database model
14:06:31 <kairat> nikhil, if would perfect if you take a look on Artifacts API spec
14:07:04 <mfedosin> yes, I forgot to mention it - Kairat update the spec
14:07:10 <mfedosin> *updated
14:07:11 <kairat> https://review.openstack.org/#/c/177397/
14:07:23 <nikhil> surely! I will follow up on the udpates!
14:07:41 <mfedosin> I think we should move it in Mitaka folder when it's open
14:07:50 <mfedosin> I'l read it Kairat :)
14:08:03 <kairat> it was done already, I moved it
14:08:08 <nikhil> mfedosin you can propose a open mitaka review and then add this move as dependency
14:08:21 <nikhil> oh right, we opened it eariler
14:08:39 <nikhil> I am still on liberty land
14:08:46 <nikhil> some specs need updating for rel and notes
14:08:54 <nikhil> so a bit distracted from mitaka atm
14:09:01 <mfedosin> jeez... I'm behind the times.
14:09:20 <nikhil> anyways, I think we did that to start preapproved specs discussion
14:09:29 <mfedosin> so It definitely worth to review it then
14:09:37 <nikhil> and it would be nice to get Artifacts API into it if at all possible
14:10:50 <mfedosin> It's better to discuss it with Alex, but I have one concern about proposed implementation
14:11:03 <mfedosin> about API exactly
14:11:23 <nikhil> looks like a good update
14:11:33 <mfedosin> the problem is there will be many apis
14:11:39 <nikhil> I think I may have some comments on the performance impact section to start with
14:11:56 <nikhil> mfedosin what do you mean?
14:12:02 <kairat> +1
14:12:12 <kairat> cannot get the question
14:12:15 <mfedosin> each plugin can implement its own api
14:12:17 <nikhil> many different types of proposals or many API for a single operation?
14:12:24 <nikhil> I see
14:12:36 <kairat> you mean db api?
14:12:38 <nikhil> yes, that is a big worry
14:12:41 <mfedosin> implement and reimplement
14:12:49 <mfedosin> no, actually just api
14:12:59 <nikhil> he means server API
14:13:09 <mfedosin> of course there will be CRUD and listing
14:13:32 <mfedosin> but the whole logic may be contained in a plugin
14:15:43 <mfedosin> just an example with images as artifacts
14:16:10 <mfedosin> we have two plugins: images_v1 and images_v2
14:16:33 <mfedosin> and you want to show some image meta
14:17:31 <mfedosin> if you use v1 you will have response in headers but in v2 as json
14:18:21 <mfedosin> so I think it should be discussed more precisely
14:19:18 <kairat> mfedosin, we have artifact_type versions to cover that case, do we?
14:19:31 <mfedosin> yes, exactly
14:19:46 <kairat> so that's the problem here then
14:20:09 <mfedosin> it's not a problem technically
14:20:26 <mfedosin> it's the thing we must describe very detailed
14:20:51 <mfedosin> that big part of the logic is contained in plugin
14:21:10 <nikhil> yes
14:21:23 <mfedosin> and the whole response and behaviour may depend of what plugin you use
14:21:24 <nikhil> it is possible to write it as a plugin
14:21:35 <nikhil> I am just thinking what is more maintainable
14:21:52 <nikhil> yeah, that too
14:22:41 <mfedosin> So, we have to focus on this in our spec.
14:23:20 <mfedosin> also, one question...
14:23:52 <mfedosin> is there some possibility that v3 will be used by default? :)
14:24:11 <nikhil> for?
14:24:22 <kairat> mfedosin, don't think it will be soon
14:24:27 <mfedosin> Nova I think
14:24:38 <nikhil> so, images v2 is being planned as a the DefCore images API
14:25:07 <nikhil> that means all clouds that need the brand OpenStack must pass Images tests against v2 standards
14:25:12 <mfedosin> and it's a good question - if we can make v3 images almost compatible with v2...
14:25:19 <nikhil> now we can think of v2 on top of v3
14:25:30 <nikhil> yeah, if we can do that
14:25:48 <nikhil> then basically we have v2/v3 as default for images (v2 on top of v3)
14:25:59 <mfedosin> because I have some thoughts how to do that
14:26:07 <nikhil> and for all other data assets  v3
14:26:20 <nikhil> sure, that's a good discussion to ahve
14:26:39 <nikhil> I think we should start that next week onwards after RCs are done
14:27:49 <mfedosin> btw, do we have some artifacts dedicated meetings on the summit?
14:28:05 <nikhil> not yet
14:28:23 <mfedosin> I suppose we should have one :)
14:28:24 <nikhil> we have 3 fishbowl, 5 workroom and 1 full day meetup
14:28:27 <mfedosin> or even two
14:28:49 <mfedosin> awesome! it's enough for everything
14:28:57 <nikhil> so, we can have 1 half of meetup for artifacts and start with 1 workroom proposal
14:29:33 <mfedosin> we need discuss two things actually
14:29:37 <nikhil> let's see  of more things come up or not
14:29:42 <nikhil> sure?
14:29:46 <mfedosin> 1. Architecture of v3
14:30:08 <nikhil> you mean design of v3 API right?
14:30:09 <mfedosin> 2. Шnteraction of images in v2 and v3
14:30:13 <mfedosin> yes
14:30:16 <nikhil> yes
14:30:20 <nikhil> absolutely
14:30:26 <nikhil> awesome
14:30:31 <nikhil> we are out of time for today
14:30:37 <mfedosin> okay, we are out of time
14:30:40 <mfedosin> thanks!
14:30:41 <nikhil> let's focus on RC bugs for now
14:30:47 <nikhil> thanks all for joining!
14:30:51 <nikhil> #endmeeting