14:02:10 #startmeeting Rally 14:02:11 hi 14:02:12 Meeting started Mon Jan 16 14:02:10 2017 UTC and is due to finish in 60 minutes. The chair is andreykurilin. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:02:15 The meeting name has been set to 'rally' 14:02:24 hi everyone! 14:04:51 I added one topic to agenda of this meeting 14:05:04 #topic Rally 0.8.0. Are we ready? 14:05:22 we don't have releases for a long time 14:05:39 and it is time to make it 14:05:50 redesign of verification component is almost finish 14:06:00 we need just to add some docs for it 14:06:09 I expect to finish it this week 14:06:14 Any known blockers? 14:07:28 I'm alone here?( 14:07:31 tags for verifications? 14:07:58 not sure that it is blocker 14:08:01 just noce to have 14:08:03 *nice 14:08:45 ok. then nothing from my side 14:09:24 I expect that we missed some bugs while redesign verification component, so I plan next release in 2 weeks after 0.8.0 :) 14:09:47 all such nice-to-have features will be done there 14:10:11 they are not blockers and we already spend too much time for 0.8.0 release 14:10:42 it contains too much features and writing release notes for it can become real pain 14:12:06 accept docs fro verification component, we should merge docs for hooks. it is another thing which is blocker 14:13:22 lets review docs for hooks 14:13:26 yes:) 14:14:10 Documentary is very important. we need to note all missed parts of rally 14:14:40 hooks were introduced several months ago and do not have merged docs yet:( 14:15:18 ok. so docs for verification and hooks are only two blockers for 0.8.0 14:15:31 it is really nice to hear that we do not have a lot of blockers 14:16:16 ok. so I hope next week we will discuss new release of Rally and plan features for the next release 14:16:30 #topic Open discussions 14:16:39 actually I do not have more topics to discuss 14:17:12 hi, andreykurilin 14:17:18 hi hai-shi 14:17:19 I have a question 14:17:22 cool 14:17:42 our team hope me to test neutron 14:17:52 not based the api 14:18:05 but the osclient can not resolve it 14:18:10 :( 14:18:12 hm 14:18:22 what kind of tests you are interested on? 14:18:44 our team hope to test the rabbitmq 14:19:04 and send the fake request to rabbitmq 14:19:20 but I can not finish it by rally 14:19:39 hai-shi: hm... I heard that someone has own rally plugin for testing rabbitmq 14:19:55 let me try to figure out who it was and try to ping he or she 14:20:19 PS: What is blockers for you while writing such scenario by your-self? 14:20:23 ok, could we add some plan about it in rally:) 14:21:29 hai-shi: so I'm ok about adding scenario which uses not only openstack clients 14:21:54 ok. 14:22:05 even more, I expect that in several months we finish validation refactoring and will be able to write scenarios not only for openstack 14:22:06 and question 2. in rally 0.7.0 14:22:22 we usually got failed task 14:23:05 when the task is failed, we could not get the right report 14:23:12 O_o 14:23:41 can you share json&report of such task? it is hard to say anything. I need to see it and try to debug 14:24:05 it is our env's problem 14:24:30 but rally should construct report in any case 14:24:40 could i add some time label to the report 14:24:44 ? 14:25:48 what kind of time label you are interested? something like when task was launched? 14:26:25 some thing like it:) 14:28:33 so, I'm ok about such extension 14:28:50 I think we should rework a bit overview tab of our report 14:29:38 got it. question 3)I hope we could count the sla by time(such as: a month, half year and so on) but this character should depend raas 14:30:36 sla's passing rate or fail rate:) 14:30:47 not sure that I understand you 14:32:52 hm, when we run rally to test, i hope we could get the number of failure tests by time 14:33:07 I'm not sure that i explain it clearly 14:33:59 you mean run long task with several scenarios and then get who many failed iterations were at particular time? 14:34:30 yeap:) 14:35:37 I think it is more like post-parsing things. It can be added when we work on some "rally portal" while working on raas, but now it sounds like separate thing 14:37:15 why? 14:39:12 ok, I think we can put such frame in our report. but it requires a lot of work with js and out current js guru moved to another initiative and have no enough time for Rally 14:40:12 :( got it. 14:41:28 we should try to find another guy 14:41:43 involve more contributors 14:41:44 eh... 14:41:49 ok. anything else? 14:42:05 question 4)compatiable with win or linux 14:42:19 i am not sure the question 14:42:28 that's all. 14:43:05 ok, rally is compatible with linux:) 14:43:11 we have ubuntu and centos gates 14:43:13 :) 14:43:51 in fact, i hope i could run rally in win too. 14:44:08 thanks, andrey :) 14:44:13 here can be a lot of problems. not related to rally at all, but openstack clients 14:45:06 last week I got windows vm to check compatibility and try to identify most critical issues and understand the possibility of running rally in windows, but unfortunately I had not time. 14:45:20 After releasing 0.8.0 I'll have more time for that investigation 14:46:09 got it. thanks a million 14:46:49 hai-shi: it is easier to setup an virtualbox vm with ubuntu for running rally 14:47:48 astudenov: yeap. you are right. But in some time, we need win to run some software:( 14:48:50 anything else to discuss? 14:49:05 no 14:49:09 no 14:49:59 ok. thanks for participation 14:50:22 see you at #openstack-rally (irc) and http://gitter.im/rally-dev/Lobby 14:50:26 #endmeeting