17:00:46 #startmeeting murano 17:00:47 Meeting started Tue Jun 6 17:00:46 2017 UTC and is due to finish in 60 minutes. The chair is felipemonteiro. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:50 The meeting name has been set to 'murano' 17:00:53 #topic Roll Call 17:01:17 o/ 17:01:31 o/ 17:01:43 from my phone here :) 17:02:13 kzaitsev_: nice 17:02:53 my schedule shifted a bit so the meeting is now around the time I'm heading home :( 17:03:01 shouldn't be a long meeting as this time is currently incovenient to many 17:03:10 #link https://review.openstack.org/#/c/468182/ 17:03:16 linking for archives 17:03:42 usually infra reviews really fast, hopefully it gets merged before next meeting 17:04:30 well we can always just put that to ML and have next meeting on new time :) 17:04:38 #topic Open Discussion 17:05:10 kzaitsev_: i was attempted but i didn't reschedule today because of worse case situation where another project did the same thing with another open review 17:05:16 tempted* 17:05:45 this week is pike-2 week, so I'm going to request respective releases tomorrow 17:06:19 thanks 17:06:33 the policy stuff should be done before pike-3 17:06:51 my connection may disappear for a couple of moments. will be better in a min 17:08:27 wanted to ask you about api versioning in murano...i don't believe it's currently supported? 17:09:22 I believe there was a letter, that all libraries should release before p-2 so there'll be client release also 17:09:40 you mean micro-versions? 17:10:10 yes, api wg will require it going forward for pretty much most api changes 17:10:35 well, generally no. i don't think we implemented micro versions 17:11:19 something i'll look at for next release because many things in the api are unclear or inconsistent, imo it could undergo some cleaning up 17:11:24 there probably was some discussion back in the day. but i don't think there ever was a bp or smth 17:12:58 also looks like freerunner is attempting to get murano ci to work with xenial? 17:13:56 he's still with mirantis and in a different city than i am :) i'll try to ping him :) 17:14:04 to get some info 17:14:49 saw both yours and his CI patches. 17:15:13 also the cinder tests got super annoying lately :( 17:15:36 i experimented with putting it in infra (for murano) but i don't think it's viable. i do believe it can be done with murano dashboard ci and splitting classes across multiple gates. 17:15:49 haven't been focusing on it though because keep getting dragged into different things 17:16:13 but if freerunner fixes murano ci internally that would be ideal 17:17:12 freerunner: used to brag, he understands how to make infra run CI tests, but I never got down in the weeds of how to do that 17:17:18 :) 17:17:35 yes, cinder tests have been. some functions in murano's tempest plugin might need to be looked at for proper clean up. some places even use deprecated functionality and other gotchas if i remember correctly. 17:18:12 kzaitsev_: did it for patrole, our company project, very annoying, but absolutely necessary for testing framework 17:19:52 don't know if you saw, pbourke also has a spec up 17:20:00 i have yet to read through it, will try to get to it today 17:20:39 saw, reviewed a bit. need to go through the 2d ver 17:21:02 i'm mostly ok with it as long as it's optional. 17:21:56 yes because it opts to use Castellan which is external resource 17:22:17 ideally the encryption thing should be pluggable, so that we could get a dummy plugin or smth more complex 17:22:20 although i believe that once implemented documentation should be written to encourage its use for obvious reasons 17:22:32 although.. 17:23:38 no it's probably better not to tempt users :) if you want encryption — use Barbican :) if not — ok but not smth homebrewrd 17:24:02 will disappear for a sec 17:25:51 i haven't looked through castellan project, i figured it was a wrapper around barbican and other storage back-ends 17:30:43 kzaitsev_: anything else for discussion? appears no one else is joining us this week 17:31:32 nope. 17:31:48 was glad to hear from you :) 17:32:10 same, thanks for joining and congrats on the new job at...samsung? 17:32:29 yeah :) 17:33:03 will end a bit early then this week, hopefully our new meeting time gets approved for next week so we get better attendance 17:33:06 i keep my stackalytics account updated :) 17:33:25 i was curious as to whether you were in russia to determine your time zone :) 17:34:10 see you next wee 17:34:11 k 17:34:39 yep i'm in moscow :) 17:34:57 k. see you :) 17:35:17 #endmeeting