17:30:46 <mfedosin> #startmeeting glance_artifacts_sub_team
17:30:47 <openstack> Meeting started Mon Feb 15 17:30:46 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:48 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:30:50 <nikhil> hi
17:30:51 <openstack> The meeting name has been set to 'glance_artifacts_sub_team'
17:30:59 <mfedosin> #link https://etherpad.openstack.org/p/glance-artifacts-sub-team-meeting-agenda
17:31:19 <mfedosin> so, we don't have a lot of items today
17:31:44 <mfedosin> I promised to do many things last week, but Nova broke my plans :(
17:31:50 <mfedosin> Anyway we have news
17:32:03 <mfedosin> #topic Updates
17:32:17 <mfedosin> 1. Glare is officially here
17:32:43 <mfedosin> Alex patch was merged last week and it's the first commit in Glare service
17:32:54 <mfedosin> I congratulate you all
17:33:25 <mfedosin> 2. FAQ is almost done
17:33:33 <nikhil> \o/
17:33:51 <mfedosin> Last week on glance meeting we decided to put this doc into Glance repo
17:34:10 <sudipto> mfedosin, I put a couple of questions on the FAQ doc...wondering if you are referring to the google drive one.
17:34:25 <mfedosin> sudipto: I saw them
17:34:34 <mfedosin> but had no chance to answer :(
17:34:44 <kzaitsev_mb> mfedosin: can you please share a link to FAQ?
17:34:47 <mfedosin> as I mentioned Nova ate all my time
17:35:00 <mfedosin> kzaitsev_mb: sure, wait a sec
17:35:08 <mfedosin> you can find it in the agend btw
17:35:27 <sudipto> mfedosin, ok..np..
17:35:39 <nikhil> #link https://docs.google.com/document/d/1D4Hik0-XNqwi43gxtybCs9-fMqh5IAIu8CHB33e46OQ/edit?pref=2&pli=1
17:35:40 <mfedosin> https://docs.google.com/document/d/1D4Hik0-XNqwi43gxtybCs9-fMqh5IAIu8CHB33e46OQ/edit
17:35:47 <mfedosin> yes, thanks Nikhil
17:36:05 <kzaitsev_mb> oh, I see, I thought it would be a rst doc or smth =)
17:36:10 <mfedosin> sudipto: and thank you for your comments
17:36:26 <mfedosin> kzaitsev_mb: it wiil be published this week
17:36:33 <kzaitsev_mb> but I guess that'd be phase 2 =)
17:36:35 <kzaitsev_mb> cool
17:36:35 <mfedosin> I suppose on Wednesday
17:37:13 <mfedosin> 3. API spec and stuff
17:38:00 <mfedosin> we're working with kairat today and we are going to spend all tomorrow day brainstorming it
17:38:45 <kairat> o/
17:38:50 <mfedosin> we want to create a doc and supply it with possible use cases
17:38:55 <mfedosin> hi kairat
17:39:11 <kairat> Hi mfedosin, sorry for being late
17:39:31 <mfedosin> I'm talking about our decision to spent next day brainstorming API
17:39:38 <nikhil> kzaitsev_mb: that's the plan to create rst once it's in a non-draft phase. this is initial/informal thoughts.
17:40:11 <kzaitsev_mb> yep, makes sense
17:40:12 <mfedosin> About use cases, I wrote a small document today
17:40:17 <nikhil> anyway, we can connect remotely to that conversation?
17:40:44 <nikhil> oops, I meant "is there any way"
17:41:14 <mfedosin> nikhil: it will be awesome if you can
17:41:44 <nikhil> I would love to if possible. No big deal if it's a hassle.
17:41:47 <mfedosin> I would prefer to do it in IRC
17:41:54 <nikhil> ++
17:42:15 <mfedosin> but you can choose any possible mean of communication
17:42:28 <mfedosin> so, about use cases -> https://docs.google.com/document/d/1QiM_QSeP8Il05wRKJ3zfzj_xTh_jSHPoa8u1rWIkh2c/edit#
17:42:31 <nikhil> I think we *could* call a ad-hoc meeting on #openstack-meeting-cp if needed.
17:43:23 <mfedosin> there will be more, of course
17:44:03 <mfedosin> I created it about an hour ago and it's hard to write more in this amount of time
17:44:05 <nikhil> oh, that doc looks really good!
17:44:24 <mfedosin> nikhil: so, what time do you prefer?
17:44:40 <mfedosin> 1730 UTC is fine?
17:44:47 <nikhil> mfedosin: totally
17:44:55 <nikhil> anytime after 1400UTC if fine
17:45:01 <mfedosin> +1
17:45:07 <nikhil> I can go a bit earlier if needed.
17:45:31 <mfedosin> not necessary, I'll work from home tomorrow
17:45:46 <nikhil> mfedosin: can you please add some edit/comments rights to that doc? I can only view it for now.
17:46:06 <nikhil> great, this time is perfect for me.
17:46:23 <mfedosin> so, that's the plan
17:46:28 <mfedosin> nikhil: done
17:46:49 <nikhil> woks
17:46:53 <nikhil> works*
17:47:11 <mfedosin> there're all updates I have
17:47:31 <mfedosin> next topic is dedicated to our customers
17:47:58 <mfedosin> today we have kzaitsev_mb from app-catalog
17:48:08 <mfedosin> and brucet from Tacker
17:48:29 <mfedosin> #topic Customer Requirements
17:48:30 <brucet> You want some background for Tacker?
17:48:46 <mfedosin> brucet: hello sir and welcome
17:48:58 <mfedosin> thanks you for joining us
17:49:02 <brucet> Thx
17:49:19 <mfedosin> yes, I want to know what things you need from Glare
17:49:36 <mfedosin> except basic catalog of immutable metadata with blobs
17:50:04 <brucet> Just sent you email on this
17:50:09 <brucet> Will repeat here
17:51:14 <mfedosin> I see it
17:51:20 <brucet> We want to understand next things: what meta fields you have,
17:51:21 <brucet> brucet> By meta fields, I assume you mean descriptive metadata for the artifacts? If so, then there will be similar metadata to what’s used in Murano. The packages that will be stored in the repository are similar to what’s used for application packages in Murano.
17:51:32 <mfedosin> it's exactly what we want to understand
17:51:46 <brucet> OK. You want me to repeat here??
17:51:57 <mfedosin> brucet: yup
17:52:03 <nikhil> yes please
17:52:04 <brucet> OK first question above
17:52:42 <brucet> mfedosin> how many blobs (application packages) per artifact you suppose to use,
17:52:43 <brucet> brucet> Again, similar to Murano. A VNF is a specialized application used to perform operations on packets. The requirements are similar (not exactly the same) as for an application package in Murano.
17:53:28 <brucet> mfedosin> do you need artifact dependencies or custom logic, and so on…
17:53:29 <brucet> brucet> Artifact dependancies are described in an NFV orchestration template. Each NFV “package” will include an NFV orchestration template which describes dependancies. It would be somewhat redundant to include these dependancies in the repository as well.
17:54:14 <brucet> <mfedosin> Anything else?
17:54:21 <mfedosin> Thanks again! For the first time this information is enough.
17:54:27 <brucet> OK
17:54:47 <nikhil> AFAIU, the plan is to develop a mechanism using oslo.vo that will understand specific requirements of the metadata for each service
17:55:20 <nikhil> so, I think if we can get a list of the already used/req metadata then it would be useful.
17:55:21 <nikhil> thoughts?
17:55:55 <mfedosin> I'm okay with it
17:55:57 <nikhil> as in the movies example given here: https://docs.google.com/document/d/1QiM_QSeP8Il05wRKJ3zfzj_xTh_jSHPoa8u1rWIkh2c/edit?pref=2&pli=1
17:56:43 * nikhil shuts up to save on time.
17:56:44 <brucet> You want this type of example for Tacker?
17:57:03 <mfedosin> But anyway I want to work closely with the developers at the time of writing a plugin.
17:57:11 <nikhil> yeah, that would be quite useful I think.
17:57:15 <brucet> OK
17:57:17 <nikhil> mfedosin: ++
17:58:01 <mfedosin> brucet: it's not urgent and you can send me a email when you want
17:58:09 <brucet> OK
17:58:17 <mfedosin> cool :)
17:58:31 <mfedosin> kzaitsev_mb: do you have something to add?
17:58:32 <kzaitsev_mb> before the meeting ends — my 0.05$ in app-catalog we've made 1st steps to use glare. I believe it should be pretty straightforward for us
17:58:35 <sudipto> nikhil, on your last point on developing a oslo.vo - do you mean objects of each type of metadata having a preset of fields?
17:58:36 <kzaitsev_mb> #link https://review.openstack.org/#/c/276857/
17:58:49 <kzaitsev_mb> would love to get some feedback from you guys
17:59:05 <mfedosin> sudipto: that's right
17:59:09 <nikhil> kzaitsev_mb: this is great news!!
17:59:24 <nikhil> sudipto: what mfedosin said :)
17:59:36 <mfedosin> kzaitsev_mb: I love you
17:59:44 <mfedosin> awesome work
17:59:50 <nikhil> a day late, are you? :P :P
18:00:47 <mfedosin> unfortunately time is over
18:01:05 <mfedosin> thanks for joining us today
18:01:10 <brucet> Thx
18:01:11 <mfedosin> and see you next week
18:01:29 <mfedosin> btw, API spec will be published by that time
18:01:40 <mfedosin> kairat and me promise that :)
18:01:47 <mfedosin> #endmeeting