17:31:00 #startmeeting glare 17:31:01 Meeting started Mon Aug 8 17:31:00 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:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:31:06 The meeting name has been set to 'glare' 17:31:17 o/ 17:31:33 o/ 17:31:56 So, we are in the process of creating a new project 17:32:13 I created all LP stuff today 17:32:40 #link https://launchpad.net/glare 17:33:35 then I proposed a patch to project config 17:33:38 #link https://review.openstack.org/#/c/352519/ 17:33:46 mfedosin: quick question ... is the plan that you will detach glare from glance immediately and have an independent release in newton? 17:34:06 rosmaita: I hope so 17:34:10 irc #openstack-glare (guessed from no notification in glance irc channel) 17:34:20 ok 17:34:43 mfedosin: one other thing ... any second thoughts from the replies on the ML? 17:34:44 and yeah, I create a channel for Glare 17:34:51 #openstack-glare 17:35:23 rosmaita: is there anything interesting? 17:35:38 I haven't read it today 17:35:46 mfedosin: not really, same stuff 17:36:11 so, yeah - nothing new 17:36:45 I created a small stub for Glare https://github.com/Fedosin/glare 17:37:12 but it doesn't work yet, it's kind of experiment 17:37:46 also, we updated json-schema generation 17:38:11 it will be used for schema-driven ui in App-Catalog 17:39:29 docaedo: sskripnick came back and now he's writing a doc about app-catalog reference architecture 17:40:09 mfedosin: yep, we chatted in #openstack-app-catalog earlier today 17:41:34 I think that's all at this moment 17:41:46 i ve 2 ques 17:41:55 We tried to make all the pieces together. 17:42:19 and implement app-catalog based on glare v1 17:42:42 here's the link 17:42:49 #link http://r-ci.tk:8100/ 17:42:57 nikhil: sure 17:43:28 1. what about the patches in glance (many are marked WIP)? (we should come up with a plan on moving them as convenient with the glare team) 17:43:47 2. what about the experimental v3 API for newton? 17:44:09 (we need to document to avoid it's usage from glance in newton and encourage people to start using glare v1) 17:44:12 1. I'll abandon this patches next week 17:44:17 these 17:44:33 what's experimental v3 api? 17:44:35 (since the plan is diff projects , we need to keep the two team coordinated) 17:44:43 do you mean v0.1? 17:44:56 https://github.com/openstack/glance/tree/master/glance/api/v3 17:45:13 yeah, that's termed as v0.1 :) 17:45:14 it's empty :) 17:45:34 if it's possible I would ask not to remove this code in Newton 17:45:55 https://github.com/openstack/glance/blob/master/glance/api/glare/v0_1/glare.py ? 17:45:55 this code won't be a part of new project 17:46:03 yes 17:46:05 sure, let's keep everyone on the same page 17:46:13 it's not a problem to remove or not remove 17:46:22 just that people know the plans 17:46:39 my plan is - create a repo with v1 code only and abandon all patches 17:47:03 okay 17:47:16 in Ocata I'll propose a patch that removes glare's code from glance completely 17:47:31 mfedosin: can you add a doc/ page in glance for the glare plans and current state ? 17:47:52 +1 that would be very helpful 17:47:52 hmm, okay 17:47:58 mfedosin: we can add some document that says when the specific code will be ported 17:48:19 but I'll be on vacation this week 17:48:28 mfedosin: ok, let me start that page 17:48:30 is it okay if I do it next week? 17:48:38 mfedosin: I wil link it for your review and you can add more info to it 17:48:56 nikhil: sure, it will be great 17:49:08 mfedosin: that way we keep the glance team on the same page (literally) on where the conversation / plans are 17:49:21 i think that's a good strategy, it will show people not to ask that question i asked about second thoughts 17:49:37 yeah, positive side effects 17:50:01 :) 17:50:21 also, I want to say that there is not so much common code 17:50:47 so, this removal won't be painful 17:50:54 ++ 17:51:03 only functional tests are hard 17:51:20 (on not so common code, except for requirements etc) 17:51:20 glare uses the same infrastructure as glance 17:51:46 mfedosin: I don't want to meddle but I think glare should not have functional tests for newton 17:52:00 why not? 17:52:08 they are already done 17:52:11 we've discussed hard over the last cycles where such tests belong 17:52:32 and there's a bit of back and forth if the functional tests should be in repo or simply in tempest 17:52:52 this might be a good time for glare to keep the code base simple and avoid extra maint. 17:53:22 there was a ask from glane team for functional tests just because it's setup that way 17:53:25 maybe, but sometimes it good to have these test near your code 17:53:26 I would say -1 on removing tests that already exist, but long term moving them to tempest makes sense 17:53:43 I don't want to deploy and run tempest every time 17:54:00 yeah, I don't want to meddle but it's good to not have functional tests in the tree 17:54:05 keep them in CI if needed 17:54:31 * nikhil stops fruitless advice 17:54:37 I'll keep that in mind. 17:55:09 also, I think we should rework our external locations a little bit 17:55:19 I wrote an email today 17:55:37 it may be interesting for glance as well 17:55:59 Stuart proposed a huge feedback, but I haven't read it yet 17:56:24 it's called [Glance][Glare] External locations design 17:57:13 oh I also have not caught up on -dev ML yet today but that sounds interesting 17:57:53 docaedo: it was designed specially for app-catalog 17:58:11 * docaedo feels honored 17:58:41 docaedo: you're our main customer 17:59:10 we implement all features mostly for you 17:59:26 if there are no more questions I suppose we can finish for today 17:59:27 hahaha wow 17:59:33 lucky app-catalog! 17:59:41 thank you for coming :) 17:59:42 mfedosin: thanks! 17:59:53 #endmeeting