17:00:55 #startmeeting murano 17:00:56 Meeting started Tue Feb 23 17:00:55 2016 UTC and is due to finish in 60 minutes. The chair is sergmelikyan. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:57 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:59 The meeting name has been set to 'murano' 17:01:00 o/ 17:01:12 o/ 17:01:14 o/ 17:01:20 o/ 17:01:39 Hi folks :) 17:02:19 \o 17:02:24 o/ 17:02:32 o/ 17:03:49 left hand hi vs right hand hi :D 17:06:12 #topic Action Items Review 17:06:14 #1 kzaitsev_mb ask kolla folks about murano-glare plugin situation 17:07:10 yep 17:07:28 so current situation is very uncomfortable for packaging folks 17:07:38 both kolla and regular ones 17:07:59 the best option packaging-wise would be to move the plugin to a separate repo 17:08:17 2d best approach would be to move all the plugins to the repository the plug into 17:08:47 Sort of like searchlight does 17:08:58 didn't get second approach 17:09:07 you mean gather all plugins in the one repo> 17:09:08 ? 17:09:41 if glare plugin for murano would live besides glare — it would be easy for packagers to package/apply it 17:10:43 after all the code would need some glare-common dependencies (since it doesn't really import anything murano-specific, but does import a bunch of code from glance) 17:11:00 sergmelikyan: no i mean gather plugins in a repo they plug into 17:11:12 kzaitsev_mb: but it will import something Murano specific at somepoint.... 17:11:26 got it... 17:11:55 I am ok with first approach, kzaitsev_mb what do you prefer? 17:12:02 sergmelikyan: then a separate repo would probably be the best option, when that happens, since it would depend on murano-code and glance code 17:12:08 sergmelikyan: I'm not sure, tbh 17:12:50 the cons of the separate repo is that it feels like a giant overkill for such a small piece of code 17:12:52 I am wondering what mfedosin and ativelkov think about that 17:13:43 kzaitsev_mb: I guess this part will grow substantially when we will switch by default to the glare and will start to increase our catalog capabilities 17:13:53 We wouldn;t be able to change anything for kolla folks in M, but the problem is a bit wieder than just that 17:14:17 also kolla folks wanted to have a fishbowl in Austin 17:14:21 regarding plugins 17:14:43 to figure out if there is a single "right" way to do plugins in openstack 17:14:58 since plugins is a bit of a pain for them apparently =) 17:15:22 sergmelikyan: afaik glare currently doesn't allow any custom logic in plugins 17:15:45 not validation anyway. and custom db logic is also a WIP 17:15:58 so probably won't grow untill newton. 17:16:04 than it's really super small piece of code :( 17:17:23 I think, that we should go to the whiteboard and write out all the pros/cons of each option 17:17:29 and wight them somehow 17:19:00 maybe having a murano-glare-plugin repo, is not that bad after all 17:19:14 let's draft an etherpad? 17:19:32 + 17:20:09 agree, tho I have a feeling that having them in Glance tree is not an option 17:20:22 so we actually down to only one option anyway 17:20:35 but nothing bad in asking 17:21:18 sergmelikyan: I'll drop by artifacts-sub-team meeting next monday 17:21:29 mfedosin and nikhil might have some ideas ) 17:21:33 kzaitsev_mb: thank you, appreciate that 17:22:07 #action kzaitsev_mb drop by artifacts-sub-team meeting next Monday ad ask about storing murano-plugin with glare 17:22:17 (I try to attend it anyway, to get their attention at app-cat glare plugin =)) 17:22:40 #topic Open Discussion 17:23:08 #link https://etherpad.openstack.org/p/murano-glare-plugin-location 17:23:22 I'll fill it in later today/tomorrow 17:23:38 just so it's in the logs 17:25:18 thx 17:25:32 I will try to take a look :) 17:33:48 looks like we out topic for today :) 17:33:54 #endmeeting