14:05:43 #startmeeting Rally 14:05:44 Meeting started Mon Nov 21 14:05:43 2016 UTC and is due to finish in 60 minutes. The chair is andreykurilin. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:05:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:05:48 The meeting name has been set to 'rally' 14:06:42 hi folks! 14:07:40 #topic [andreykurilin] status of rally gates 14:07:54 status: they are broken now 14:07:56 lol 14:08:10 it is not really good news, but it is not our fault 14:08:53 Aodh(one of telemetry services) made uncompatible change at the end of previous week 14:09:09 and they are not compatible with trusty 14:09:29 I temporary turned off telemetry in our gates 14:09:49 but it doesn't unblock us:( 14:10:02 Since heatclient made another incompatible change 14:10:18 :( 14:10:50 there is a patch to g-r to add this release to backlist, also heat team is working on proposing new release with right deprecation and compatibility layer 14:11:01 So we will have unblocked gates soon 14:11:26 to prevent such situations in future, imo, we need to do the same as manila guys did 14:11:55 they removed all "redundant services" from their gates, so no one affects them 14:12:20 let's do the same for all our jobs: identify and disable redundant services for partial job 14:13:08 any thoughts? 14:13:13 amaretskiy ^ 14:14:17 #vote +1 for removal of all unused services on gates 14:14:48 nice 14:14:54 me too 14:15:05 cool 14:15:18 #topic Policy for "create_and_list" scenarios 14:15:58 we have a lot of create_and_list scenario . for example NovaServers.create_and_list_servers 14:16:23 But all such scenarios don't check that created entity presents in obtained list 14:16:59 I case of several ceilometer scenarios I found that list doesn't return anything 14:17:20 it is a bad behaviour 14:18:01 so let's make all new scenarios check list and add this check to old ones 14:18:32 why not simply improve existing scenarios? 14:18:40 one by one 14:18:50 yes, we need to improve existing scenarios 14:18:59 and avoid additing new ones with bad behavior 14:19:31 Also it relates to next topic "update" scenarios. They should include check that entity is updated 14:20:18 ok 14:20:27 if there are no comments, let's move to the next topic 14:20:35 #topic Keystone v3 support 14:21:51 I had a great news! Last week I finished a chain of patches with compatibility layer for Keystone V2 & V3 . After we will merge them, all scenarios will be keystone v3 compatible 14:22:07 and we will be able to move all our jobs to latest keystone api 14:22:08 great! 14:22:13 instead of using old on 14:22:36 #topic Open discussion 14:22:43 anything else to discuss? 14:22:43 no topics from me 14:22:59 astudenov: ? 14:23:01 nothing from me 14:23:03 ok 14:23:06 let's finish 14:23:09 #endmeeting