17:00:49 <mfedosin> #startmeeting glance_artifacts_sub_team
17:00:55 <openstack> Meeting started Mon Feb  1 17:00:49 2016 UTC and is due to finish in 60 minutes.  The chair is mfedosin. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:56 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:57 <mfedosin> #link https://etherpad.openstack.org/p/glance-artifacts-sub-team-meeting-agenda
17:00:59 <openstack> The meeting name has been set to 'glance_artifacts_sub_team'
17:00:59 <docaedo> o/
17:01:03 <kairat_> O/
17:01:20 <mfedosin> glad to see you here today :)
17:01:32 <mfedosin> so, we have several topics to discuss
17:02:15 <mfedosin> but before I have to mention that I'm writing a document about glare architecture
17:02:42 <mfedosin> it's almost done and I'll publish it tomorrow after today's decisions
17:02:52 <nikhil> excellent, can't want to see
17:03:13 <mfedosin> you can see a picture from there
17:03:45 <nikhil> yes, the pic is pretty cool indeed
17:03:52 <mfedosin> last Friday Nikhil asked me to write some thoughts about glare...
17:04:06 <mfedosin> like brainstorming the architecture
17:04:18 <mfedosin> #link https://etherpad.openstack.org/p/mitaka-glare-api-brainstorm
17:04:38 <mfedosin> I did it, but here we can discuss it
17:04:51 <mfedosin> first think about public and private api
17:05:15 <mfedosin> I think it's unnecessary and we can have only one public api
17:06:00 <mfedosin> and if DefCore wants some standardization we can do it with images api only
17:06:23 <mfedosin> other plugins are optional
17:06:47 <mfedosin> nikhil, your thoughts?
17:06:52 <nikhil> yeah, mfedosin and I had a brief starter discussion on what the architecture looks like. I wanted to see how the "schema on schema" idea looks like.
17:07:15 <nikhil> My feeling is that we need to have a structured scope around the API (only public API)
17:07:20 <nikhil> and for that we need semantics
17:07:28 <nikhil> there are two ways of doing it
17:07:34 <nikhil> the oslo.vo is one way
17:07:35 <mfedosin> nikhil absolutely agree with you
17:07:53 <nikhil> but the primary origination of oslo.vo is
17:08:09 <nikhil> having a static feeling to dynamic language (ie python)
17:08:32 <nikhil> that helps with the DB upgrades and asynchronous calls (Bcast and multi cast) etc
17:08:53 <nikhil> I think it might be worth adding the scope of our requirements and bring that to the oslo.vo core team
17:09:03 <nikhil> given we choose to take that route
17:09:10 <mfedosin> also oslo.vo helps with architecture
17:09:16 <nikhil> if all works out that seems like a good idea
17:09:19 <nikhil> agreed
17:09:37 <mfedosin> I mean we can map Blob type directly to store with coercing
17:09:53 <mfedosin> you may see my example from the etherpad
17:10:33 <mfedosin> I think we need to investigate how oslo.vo behaves in our case
17:10:53 <nikhil> I need more time to absorb that example and fit it into bigger pic
17:10:58 <nikhil> yes
17:11:19 <mfedosin> but we can leave oslo.vo as the main priority for glare
17:11:51 <mfedosin> if it doesn't fir we can return to the idea of 'schema-on-schema'
17:12:07 <mfedosin> *fit
17:12:16 <nikhil> are there more comments that we might expect on the etherpad ?
17:12:30 <mfedosin> I asked kairat to look there too
17:12:36 <nikhil> ah cool
17:12:55 <nikhil> hopefully we can get something today
17:13:04 <mfedosin> but we discussed it today and he agrees we the direction
17:13:06 <nikhil> else, let's move forward with oslo.vo
17:13:46 <mfedosin> okay, about the documentation
17:14:06 <mfedosin> as I mentioned last week it's called What is Glare?
17:14:27 <mfedosin> and it provides an eagle view on the service
17:14:55 <kairat_> Does it describe current doc?)
17:14:56 <mfedosin> it will help community members to be more familiar with Glare
17:15:09 <kairat_> Current impl
17:15:34 <kairat_> or future implementation
17:15:36 <mfedosin> and also will describe some usecases for our customers
17:15:51 <nikhil> great
17:16:22 <mfedosin> kairat_: it's something between Alex wanted to see and something that will work :)
17:16:38 <kairat_> Heh
17:16:41 <mfedosin> so, I have a picture of that
17:17:09 <mfedosin> #link https://dl.dropboxusercontent.com/u/13626875/glare.png
17:17:35 <mfedosin> it's based on oslo.vo
17:18:28 <mfedosin> idea is that we have unified api for all plugins (or 'oslo versioned objects' if you want)
17:18:53 <mfedosin> then we have a unified api that all plugins must implement
17:19:18 <mfedosin> but each plugin may have it's own data_api
17:19:36 <kairat_> That's simple and great imo
17:19:43 <kairat_> Good to hear
17:19:51 <mfedosin> for example, for images it will be current Image tables
17:19:53 <nikhil> what is a data_api ?
17:20:09 <kairat_> Api to database
17:20:17 <mfedosin> nikhil: the same thing we have in glance-api.conf
17:20:24 <nikhil> ah
17:20:41 <nikhil> seems logical
17:21:43 <mfedosin> that's how heat does it https://github.com/openstack/heat/blob/master/heat/objects/stack.py#L25
17:22:25 <mfedosin> so, we need to think about 2 things
17:22:40 <mfedosin> 1. REST api - Alex almost did it for us
17:23:06 <mfedosin> we just need to add there requests for data upload/download
17:23:14 <mfedosin> and we're cool :)
17:23:15 <nikhil> yeah, not sure where  heat separates it's data but glance does for metadefs and imgaes
17:24:07 <mfedosin> 2. Interface for oslo.vo classes
17:24:50 <mfedosin> like 'save' data to db, 'get' from db, 'add_tag' and so on
17:25:55 <mfedosin> also there is a patch from Alex to move glance v3 api to Glare v0.1
17:26:19 <mfedosin> nikhil: if you have time please review it and let's merge it
17:26:27 <nikhil> sounds good
17:26:51 <mfedosin> #link https://review.openstack.org/#/c/255274/
17:27:16 <mfedosin> after that we will be able to start the development of glare v1 :)
17:27:39 <nikhil> ++
17:27:52 <kairat_> We need to merge glare xlient code as well
17:27:52 <mfedosin> and also - no Glance/Glare separation!
17:28:02 <mfedosin> we will stay in glance repo
17:28:22 <kairat_> But it is not a blocker
17:28:42 <mfedosin> kairat_: you will be a core member tomorrow
17:28:49 <kairat_> What about murano requirements
17:29:00 <kairat_> Oops, cool))
17:29:04 <mfedosin> you will be able to merge everything
17:29:10 <kairat_> Heh
17:29:14 <mfedosin> we will help you
17:29:43 <nikhil> hi I have a small request
17:29:44 <mfedosin> but let's begin with a standalone service
17:29:53 <nikhil> given we have a min or so
17:29:53 <mfedosin> nikhil shoot
17:30:02 <nikhil> can we move this meeting to 1730 UTC
17:30:08 <nikhil> in this channel
17:30:15 <nikhil> just checked and the slot is open
17:30:24 <nikhil> I have a conflict at this time
17:30:24 <mfedosin> I think it easy
17:30:28 <kairat_> Ok for me
17:30:37 <mfedosin> same for me
17:30:38 <nikhil> awesome, will send a review and email ML
17:30:44 <kairat_> Need to notify to dec mail
17:30:45 <nikhil> thanks guys
17:30:46 <mfedosin> nikhil please do
17:30:53 <kairat_> Dev mail
17:30:56 <nikhil> yeah
17:31:23 <mfedosin> okay, thank you all :)
17:31:37 <mfedosin> glare is coming!
17:31:44 <mfedosin> #endmeeting