17:31:27 #startmeeting glare 17:31:27 Meeting started Mon Feb 29 17:31:27 2016 UTC and is due to finish in 60 minutes. The chair is mfedosin. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:31:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:31:31 The meeting name has been set to 'glare' 17:31:36 #topic agenda 17:31:47 o/ 17:31:51 #link https://etherpad.openstack.org/p/glance-artifacts-sub-team-meeting-agenda 17:32:19 #topic Updates 17:32:26 hello again 17:32:33 fyi, please see this small update to our meetings 17:32:34 glad to see you here 17:32:35 #info https://review.openstack.org/#/c/284487 17:32:55 thanks 17:33:07 thanks nikhil 17:33:31 from now our project is officially called Glare 17:33:48 \o \o/ o/ 17:34:06 so, let's begin with our api spec... 17:34:24 I guess anotehr small update is that 17:34:27 I updated it, based on api-wg requirements 17:34:36 we did meet the API WG last week in their weekly meeting 17:34:48 and pointed out the spec to them 17:35:07 they liked the detailed structure of the spec, so thanks mfedosin kairat_ and team!! 17:35:11 yes. and they liked it 17:35:35 I guess the next topic is a follow up of the same mfedosin ? 17:35:36 it was kairat_ idea to make it so detailed :) 17:35:51 kairat_: excellent work, man!! 17:35:55 yep, let's start it 17:36:09 #topic API-WG requirements 17:36:46 they had 3 main concerns, as far as I see 17:37:13 1. Deleting blobs should be performed with DELETE, not PATCH 17:37:57 I updated it in the spec and added that if user tries to do 'op':'remove' on blob, then 400 will be raised 17:38:36 I think it's a good idea 17:38:37 2. It was about metadata 17:39:28 they asked us to follow this... 17:39:32 #link https://specs.openstack.org/openstack/api-wg/guidelines/metadata.html 17:40:10 but since we don't support this property in glance, then we don't need to do so in Glare 17:41:18 other artifact types may have it, but I don't want to make a unified api call 17:41:57 3. Was about tags 17:42:22 they recommended to use POST for tags creation 17:42:59 but I suppose they were wrong, because api-wg guidelines require to use PUT 17:43:24 #link https://specs.openstack.org/openstack/api-wg/guidelines/tags.html 17:43:44 What was the motivation behind this? 17:43:48 also several typos were fixed 17:43:55 kairat_: for tags? 17:44:03 Yep 17:44:12 like we create object with POST 17:44:28 They just said: use post? 17:44:37 Ah 17:44:38 wait a sec... 17:44:40 Ok 17:45:30 "i am not sure what the data you are passing on this call looks like, or if there is any, but for creating resources i usually expect a POST to something." 17:45:41 Ok, got it 17:45:53 that's all we have from them 17:46:01 sudipto: wow!!! thanks 17:46:21 jfyi sudipto left a lot of comments there 17:46:33 mfedosin, sorry, running late on this, I am yet to complete the entire spec :( 17:46:45 but i will by tomorrow morning my time. 17:46:56 #link https://review.openstack.org/#/c/283136 17:47:55 sudipto: np 17:48:15 I'll address your comments today 17:48:16 * docaedo apologizes for joining late (on phone call), and gets busy reading scrollback... 17:48:31 docaedo: hi 17:48:42 you don't miss too much 17:49:12 docaedo: last Thursday we presented the spec to API-WG and they liked it 17:49:56 since we addressed all their comments we can ask for review again 17:50:23 cool, that's good news 17:50:43 so, from tomorrow we'll start implementing base artifact type 17:51:15 kairat was investigating how oslo.vo works all last week 17:51:28 I would say start design 17:51:44 #topic Glare Artifact type interface 17:51:58 kairat_: as you wish 17:52:24 kairat_: do you have any thoughts how it'll look like? 17:53:38 Yep, i have some 17:53:47 Will describe it later 17:53:54 is kairat_ leading the design discussion? 17:54:17 I think we have to implement all base artifact prop types 17:54:25 Yep 17:54:44 nikhil: he know oslo.vo better then us :) 17:54:51 *knows 17:54:54 The base artifact will be inherited from versioned object 17:54:55 kairat_: not sure if you know this tool.. 17:55:00 #link http://asciiflow.com/ 17:55:13 it would be nice to get some idea of what's going where 17:55:24 We also implement some custom field like blob 17:55:56 I've missed most of the meeting =( 17:56:19 is there still some time for me to voice a couple of concerns? =) 17:56:26 kairat_: sure, but tbh I'm a bit disconnected in how the work is going to happen 17:56:29 nikhil: thanks for link 17:56:49 nikhil: I can play it all day :) 17:56:54 kzaitsev_mb: hi 17:57:07 We will prepare some doc 17:57:07 you better leave comments in the spec 17:57:10 would be nice to know the plan and help with stuff including reviews :) (this could make things faster, imho) 17:57:19 kzaitsev_mb: don't worry, since you weren't here we volunteered you for all the work ;) 17:57:20 At least i would like to do that 17:57:30 kzaitsev_mb: we're still discussing :) 17:57:45 kairat_: cool 17:57:51 #topic Open Discussion 17:58:07 plan is next: 17:58:15 kzaitsev_mb: I meant, so voice away as things are still being discussed :) 17:58:21 create a doc (in Google or etherpad) 17:58:27 cool, so I actually have questions about artifacts locations. 17:58:35 and add our thought about base type 17:58:36 or the plugin locations 17:58:53 or whatever they'll be called =) 17:58:59 I think we should all agree on what to call these objects 17:59:10 kzaitsev_mb: heh, yeah. exactly 17:59:29 we will vote next time 17:59:31 1 min guys 17:59:53 murano is currently in a situation, where we store our plugin inside murano itself. this creates a bit of confusion, especially for packagers 17:59:56 we can continue in glance channel if you want 18:00:06 ++ 18:00:16 yep, I'd be happy to discuss the issue in #glance 18:00:24 +1 18:00:27 at least to voice it ) 18:00:31 kzaitsev_mb: we will add support of adding artifact types by python name 18:00:42 ftr, it will be #openstack-glance (whoever is following logs) 18:00:49 okay, let's go there 18:00:56 thanks for coming today 18:01:10 and sudipto - thanks for you comments :) 18:01:12 thanks! 18:01:24 #endmeeting