17:30:57 <mfedosin> #startmeeting glance_artifacts_sub_team
17:30:57 <openstack> Meeting started Mon Feb  8 17:30:57 2016 UTC and is due to finish in 60 minutes.  The chair is mfedosin. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:30:58 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:31:00 <openstack> The meeting name has been set to 'glance_artifacts_sub_team'
17:31:06 <mfedosin> o/
17:31:19 <mfedosin> #link https://etherpad.openstack.org/p/glance-artifacts-sub-team-meeting-agenda
17:31:40 * mfedosin waits for Nikhil to start
17:32:03 <mfedosin> sudipto: thank you for join us!
17:32:13 <docaedo> o/
17:32:13 <sudipto> mfedosin, happy to join! :)
17:32:39 <mfedosin> okay, I think we can start with midcycle updates
17:33:01 <mfedosin> it was last week and we discussed things about Glare
17:33:25 <mfedosin> #link https://etherpad.openstack.org/p/glance-mitaka-virtual-mid-cycle
17:33:29 <mfedosin> section Glare
17:34:00 <mfedosin> 1. We all agree that separation to public and private apis are bad
17:34:37 <nikhil> hi
17:34:51 <nikhil> my previous meeting overrun, sorry about delay here
17:34:57 <mfedosin> 2. To satisfy DefCore we make Images plugin and OpenStack Image API obligaatory for all Glare deployments
17:35:12 <mfedosin> nikhil: HI!!!!
17:35:23 <mfedosin> welcome
17:35:35 <mfedosin> we're talking about updates from midcycle
17:35:39 <nikhil> thank you :)
17:35:52 <nikhil> ah cool, I guess it was a healthy and productive discussion
17:36:29 <mfedosin> nikhil: I just copy here the decisions we made
17:37:05 <mfedosin> 3. We will use oslo.vo as a standard declarative framework to define Glare plugins
17:37:46 <mfedosin> and finally we decided not to merge current glare client for v0.1
17:38:11 <mfedosin> #link https://review.openstack.org/#/c/255220/
17:38:51 <mfedosin> because only Murano uses v0.1 and they have client merged in their muranoclient
17:40:08 <mfedosin> so, we confirmed everything that we already knew.
17:40:38 <mfedosin> next thing, as I promised I wrote a Glare FAQ
17:41:04 <mfedosin> #link https://docs.google.com/document/d/1D4Hik0-XNqwi43gxtybCs9-fMqh5IAIu8CHB33e46OQ/edit
17:41:30 <mfedosin> does this link work for you?
17:41:36 <nikhil> works for me
17:41:48 <mfedosin> it's very initial draft with terrible English
17:42:16 <mfedosin> Olena didn't have a chance to look there
17:42:27 <docaedo> link works for me too
17:42:33 <nikhil> so, iiuc it's open for collaboration right and not something you are planning to evolve yourself and publish new draft there?
17:42:39 <mfedosin> (Olena is a Glance technical writer)
17:43:18 <mfedosin> my idea is to publish it in OpenStack wiki
17:43:40 <mfedosin> and update it from time to time
17:43:54 <mfedosin> when new information appears
17:44:28 <mfedosin> feel free to live comments there, maybe you want to see other answers there
17:44:34 <kairat> so it looks like an intro to the project
17:44:47 <mfedosin> so you can leave your questions
17:44:53 <mfedosin> kairat is right
17:45:10 <mfedosin> I made it to help newcomers
17:45:39 <nikhil> so, searchlight has this information in the source tree
17:45:40 <mfedosin> last week we discussed this service with sudipto
17:46:17 <mfedosin> and I tried to put the answers to the questions he asked me.
17:46:36 <mfedosin> maybe we can merge it in glance repo
17:46:55 <mfedosin> I just want the community be okay with it
17:47:02 <nikhil> ++
17:47:24 <sudipto> mfedosin, nikhil is it possible to play around with some bit of the prototype in some way?
17:47:45 <mfedosin> but anyway it's a draft and you can add your comment there till the next week
17:48:00 <mfedosin> sudipto: v1 is under discussion
17:48:14 <mfedosin> and currently there is no prototype
17:48:25 <mfedosin> but we have unstable v0.1 api
17:48:54 <sudipto> ok
17:48:55 <nikhil> I guess the question is which prototype and the one which we want to work isn't ready yet :)
17:48:55 <mfedosin> and you can play with it to see how things work
17:48:56 <docaedo> I believe kzaitsev_mb is working on a prototype for the app catalog, he might have something people can poke at this week
17:49:46 <mfedosin> kzaitsev_mb works on the adapter between Glare and app catalog
17:50:06 <mfedosin> as I mentioned v0.1 is merged and ready for usage
17:50:28 <mfedosin> but we're going to evolve it to v1
17:50:45 <sudipto> ok
17:50:46 <mfedosin> which doesn't affect app catalog
17:51:06 <kairat> I guess latest bugs from kzaitsev_mb are related to trhis prototype
17:51:07 <mfedosin> so, please leave your questions there
17:51:48 <mfedosin> kairat: I'll ask him tomorrow
17:52:26 <mfedosin> next thing - I made an etherpad with Glare stable api draft
17:52:44 <mfedosin> #link https://etherpad.openstack.org/p/glare-v1-api
17:53:11 <mfedosin> it's a generalization of glance v2 api
17:53:27 <mfedosin> and glance v2 api included there
17:54:06 <mfedosin> but there is only one special moment - in v2 api image becomes active right after file upload
17:54:38 <mfedosin> we can't do it in Glare, because we support several blobs per artifact
17:54:59 <mfedosin> that's why I suggest you a trick...
17:55:41 <mfedosin> in Images plugin there will be an option 'activate_on_upload' True by default
17:56:26 <mfedosin> if file was successfully uploaded then it immediately transfers status to 'active' for image
17:57:23 <mfedosin> in other cases uses must explicitly call /actions/activate to make an artifact active
17:58:19 <mfedosin> if this set of calls is okay for you then I'll start to write a full spec about Glare api
17:58:43 <docaedo> what's the difference between activate and reactivate?
17:59:12 <mfedosin> activate transfers artifact from queued to active
17:59:22 <mfedosin> and it's available for every user
17:59:35 <mfedosin> reactivate may be available for admin only
18:00:08 <mfedosin> for example if someone publish malicoius artifact admin may want to deactivate it
18:00:20 <docaedo> I guess I was thinking would only need deactivate and activate?
18:00:22 <mfedosin> (remove from public)
18:00:57 <mfedosin> I want that reactivate may be availabe for admin only
18:00:59 <docaedo> but I guess in this case reactivate is the opposite of deactivate, and "activate" as you said is more about moving from queued to active
18:01:09 <docaedo> makes sense to me
18:01:12 <docaedo> thanks
18:01:27 <mfedosin> I'll describe it in FAQ
18:01:37 <mfedosin> okay, we are out of time
18:01:50 <mfedosin> thank you all for joining
18:02:02 <docaedo> thank you!
18:02:08 <nikhil> thanks
18:02:13 <kairat> Thanks
18:02:15 <sudipto> thanks!
18:02:16 <mfedosin> #endmeeting