17:00:24 <docaedo> #startmeeting app-catalog
17:00:25 <openstack> Meeting started Thu Mar  3 17:00:24 2016 UTC and is due to finish in 60 minutes.  The chair is docaedo. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:26 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:28 <openstack> The meeting name has been set to 'app_catalog'
17:01:00 <docaedo> courtesy ping: kfox1111 kzaitsev_mb markvan
17:01:14 <markvan> howdy
17:01:17 <kzaitsev_mb> o/
17:01:30 <docaedo> hello gents!
17:01:39 <docaedo> Agenda for this week:
17:01:41 <docaedo> #link https://wiki.openstack.org/wiki/Meetings/app-catalog
17:01:48 <docaedo> #topic Status updates
17:02:06 <docaedo> I'll start with two quick things from me
17:02:24 <docaedo> I was finally working on the "recently updated" stuff, and added this last modified date field
17:02:26 <docaedo> #link https://review.openstack.org/286807
17:02:41 <docaedo> very minor, just exposes when an asset was last modified in the browser
17:02:59 <docaedo> and this one has more to it - Rotate recently added apps:
17:03:00 <docaedo> #link https://review.openstack.org/286927
17:03:17 <docaedo> I'd appreciate feedback on that last one when anyone has time to look
17:03:51 <docaedo> In the category of more pressing updates though, need to get at least one other person to look at
17:03:53 <docaedo> Integration test support for app catalog horizon plugin
17:03:55 <docaedo> #link https://review.openstack.org/#/c/276440/
17:04:09 <docaedo> because we have the +2s from infra here - Adding integration test support
17:04:11 <docaedo> #link https://review.openstack.org/#/c/276438/
17:04:27 <markvan> yup, that is the next step
17:04:31 <docaedo> but that is blocked until we've merged 276440 (great work markvan, really good stuff!)
17:05:01 <kzaitsev_mb> added myself as a reviewer to commits =) will definitely take a look, looks like a nice thing to have.
17:05:13 <docaedo> great thanks kzaitsev_mb
17:05:58 <docaedo> markvan: any other related updates? or other PRs we should make sure get attention?
17:06:18 <markvan> yeah, I have the linting ones ready as well
17:06:32 <markvan> #link https://review.openstack.org/#/c/283202/
17:06:43 <markvan> #link https://review.openstack.org/#/c/283201/
17:07:24 <docaedo> merging https://review.openstack.org/#/c/283201/ right now :)
17:07:44 <markvan> And now that the LBaaSv2 Heat resources are merged, I'm working on the LoadBalancer template for the app catalog
17:08:04 <docaedo> markvan: sweet!
17:09:52 <docaedo> any other updates before moving on to glare transition discussion?
17:10:22 <markvan> that's it from me... thx
17:10:28 <kzaitsev_mb> docaedo: unfortunatelly I don't have much.
17:10:34 <docaedo> no prob
17:10:38 <docaedo> #topic Glare transition review
17:11:09 <kzaitsev_mb> I still don't have public IP for my staging server and have been buse with m-3 and ff as of now =)
17:11:13 <docaedo> Let's spend a few minutes talking about the glare transition - as kzaitsev_mb noted on the channel a few days ago, next step is to get a PoC running on mirantis infra
17:11:23 <kzaitsev_mb> think things would get clearer starting tomorrow )
17:11:26 <docaedo> oh yeah there's all that OTHER OpenStack & Fuel stuff afoot ;)
17:11:49 <docaedo> One thing I am not clear about w/r/t glare
17:12:17 <kzaitsev_mb> I feel soooo lucky i'm not working on fuel right now =) all those FFE's and change of release model %)
17:12:25 <kzaitsev_mb> w/r/t — you mean CRUD?
17:12:27 <docaedo> How can updates to imported assets be handled? Otherwise there's no point in implementing glare without OpenStack ID-based authentication
17:12:54 <docaedo> I mean "with respect to" there, but yeah, mainly updates
17:13:33 <docaedo> Unless the intention is for the import script to dump the contents of the DB before importing again (i.e. someone merges updated assets.yaml, so clear out glare DB and re-import)
17:14:02 <docaedo> the way I understood the import script right now was that it skipped over things that had already been imported...
17:14:34 <kzaitsev_mb> yep, auth is something we haven't touched yet. We would probably need some kind of auth for a.o.o, since we would need to approve/update drafts/artifacts
17:14:47 <kzaitsev_mb> we've thought of this script as a 1-time thing
17:14:59 <docaedo> got it
17:15:04 <kzaitsev_mb> we should run before switching to glare
17:15:48 <docaedo> and that makes sense then, assuming "switching to glare" also means no more assets added via gerrit review, which matches what we discussed
17:15:57 <docaedo> just making sure then that we're still on the same page there
17:16:27 <kzaitsev_mb> A colleague of mine and I are working on a simple UI to pust new assets/updates to existing assets.
17:16:33 <kzaitsev_mb> it doesn't include auth yet
17:17:18 <kzaitsev_mb> just a couple of simple forms for administrating glare assets, which would give the basic functionality as of now
17:17:40 <kzaitsev_mb> the next step would probably be adding auth to a.o.o?
17:18:05 <docaedo> makes sense, will be nice for users to be able to use that or the API to add/update assets they own
17:18:16 <kzaitsev_mb> after we have a way to add/approve an asset from web-UI I mean =)
17:18:58 <docaedo> I would say just being able to add via API calls is good enough, as long as people can authenticate
17:19:10 <docaedo> I mean good enough for first steps
17:20:56 <kzaitsev_mb> docaedo: I'm a bit wary of adding v2 api straight away without any design, so this might probably involve adding a call for v1?
17:22:15 <docaedo> well here are the things we'd need to have working seamlessly before implementing glare on production:
17:22:48 <docaedo> -v1 API compatibility (so calls to /api/v1/assets serve the same content they do now)
17:23:08 <docaedo> -authentication with openstack ID
17:23:42 <docaedo> -members of app-catalog core would have admin IDs (so any core reviewer can disable an uploaded asset)
17:24:11 <kzaitsev_mb> (and approve drafts of new assets, I suppose )
17:24:32 <docaedo> kzaitsev_mb: yes, right, meant to say approve/disable assets)
17:25:02 <docaedo> I *think* that's it, aside from the hosting stuff (swift, database, etc. in a way infra team is comfortable supporting)
17:25:06 <kzaitsev_mb> should we include setting up db to the list?
17:25:56 <docaedo> yeah, but I guess I consider that piece (hosting of it, with database and swift) to be just one thing - which is getting the deployment/hosting sorted out
17:26:17 <docaedo> I'm not worried about that, think it's going to be relatively easy to arrange for it - though hosting brings up a new question/issue
17:26:39 <kzaitsev_mb> ok, if you're not worried — I'm not worrying either =)
17:26:40 <docaedo> which is - what about changes/updates to glare? the whole project is very much in motion, the API isn't even settled down yet -
17:27:16 <docaedo> so for me I'm inclined to say we should be deploying a fork of glare, or a "app catalog compatible" tag or something, rather than trying to follow the project and upgrade as it changes
17:27:28 <kzaitsev_mb> I would probably add a separate point about specifying a way to add/update an asset (API or web-form)
17:28:08 <kzaitsev_mb> docaedo: since it's part of glance — we could probably settle down with mitaka version, for example
17:28:16 <kzaitsev_mb> as soon as they tag/release it
17:28:17 <docaedo> but I thought glare already had that capability? so that's not something that needs to be implemented special
17:28:30 <docaedo> "that capability" being updating details of an asset
17:29:03 <kzaitsev_mb> docaedo: it does, I thought more of a user-firendly way of doing it.
17:29:40 <docaedo> kzaitsev_mb: that makes sense. My concern with the web-ui piece is just that it will be complicated
17:29:52 <docaedo> since it means now we have to have an authenticated web session
17:29:57 <docaedo> that also has to expire
17:30:04 <docaedo> and all the other fun stuff
17:30:54 <docaedo> so the auth side of glare I think is going to be the hardest problem to solve TBH (but maybe I'm wrong? .. if we're just going to implement an oath middleware maybe that's not so bad)
17:31:31 <kzaitsev_mb> that one requires some research, yes
17:31:45 <docaedo> that's why I would be satisfied if the only way to update things was via API first, user-friendly web-ui second
17:32:31 <kzaitsev_mb> I see, v1 compatibility is something I'm working on right now. gotta schedule auth to be next
17:32:59 <docaedo> cool, and definitely loop me in on that stuff, I can probably help
17:33:34 <docaedo> what I got from tokyo conversations was that we're going to have to write that auth plugin anyway (unless I'm totally mistaken which would be great!)
17:34:04 <kzaitsev_mb> sure, will do. I try to post any new updates I have to #app-catalog as soon as I have them.
17:34:58 <docaedo> thanks!
17:35:22 <docaedo> OK I am satisfied we're speaking the same language here on this stuff, shall we move on to open conversation?
17:35:31 <docaedo> *discussion
17:36:15 <docaedo> #topic Open discussion
17:36:58 <docaedo> Only thing I have for open discussion is that I'm going to send an email today noting my intention to add kzaitsev_mb as a core for app-catalog
17:37:31 <kzaitsev_mb> (sry for being a bit erratic today — I'm trying to answer release related questions in a couple of other channels +))
17:37:39 <docaedo> haha no prob
17:38:21 <docaedo> I don't have anything else for open discussion really, just want someone else to +1 the integration test work markvan has up so I can feel comfortable merging it
17:39:09 * docaedo waits two minutes to see if there's anything else to discuss...
17:41:26 <docaedo> TIME!
17:41:55 <docaedo> OK thanks for coming as always you guys, much appreciated :) Talk to you later, have fun with your releases and such!
17:42:03 <docaedo> #endmeeting