Perl 6 - the future is here, just unevenly distributed

IRC log for #openstack-rally, 2017-05-04

| Channels | #openstack-rally index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:08 yingjun joined #openstack-rally
00:46 winston-d_ joined #openstack-rally
00:46 tovin07_ joined #openstack-rally
01:03 dave-mccowan joined #openstack-rally
01:11 chhavi joined #openstack-rally
01:13 yolkfull__ joined #openstack-rally
01:18 winston-d_ hi, I have some questions about 'rps' runner.
01:19 winston-d_ Anybody here is familiar with how 'rps' runner works?
01:27 yanyanhu joined #openstack-rally
01:31 yamamoto joined #openstack-rally
01:33 dixiaoli joined #openstack-rally
01:49 ilbot3 joined #openstack-rally
01:49 Topic for #openstack-rally is now Gitter https://gitter.im/rally-dev/Lobby ☁ Review board: https://goo.gl/iYw2m0 ☁ Rally RoadMap: http://goo.gl/JZkmwY ☁ IRC logs http://irclog.perlgeek.de/openstack-rally ☁ Key persons to ask:  andreykurilin, boris-42, amaretskiy, rvasilets, stpierre  ☁ Documentation: https://rally.readthedocs.org/en/latest/ ☁ To publish changes to Rally:
02:13 yolkfull joined #openstack-rally
02:15 yolkfull_ joined #openstack-rally
02:17 yolkfull__ joined #openstack-rally
02:20 dave-mccowan joined #openstack-rally
02:23 yolkfull__ joined #openstack-rally
02:36 yamamoto joined #openstack-rally
02:46 chhavi joined #openstack-rally
02:55 zhubingbing_ joined #openstack-rally
03:04 openstackgerrit chenhb proposed openstack/rally master: [WIP]Refactor the related command of task report  https://review.openstack.org/460374
03:06 shasha_t- joined #openstack-rally
03:17 tovin07_ joined #openstack-rally
05:09 openstackgerrit chenhb proposed openstack/rally master: [WIP]Refactor the related command of task report  https://review.openstack.org/460374
05:11 shausy joined #openstack-rally
05:18 yamamoto joined #openstack-rally
05:33 Serlex joined #openstack-rally
05:40 rdas joined #openstack-rally
05:57 anshul joined #openstack-rally
06:21 yamamoto joined #openstack-rally
06:26 yamamoto joined #openstack-rally
06:45 pcaruana joined #openstack-rally
06:52 e0ne joined #openstack-rally
06:59 yamamoto joined #openstack-rally
07:29 tesseract joined #openstack-rally
07:48 aojea joined #openstack-rally
08:00 openstackgerrit Staroverov Anton proposed openstack/rally master: Move 'image-valid-on-flavor' validator to 'openstack/validators.py'  https://review.openstack.org/457263
08:15 openstackgerrit Staroverov Anton proposed openstack/rally master: Move 'required_neutron_extension' validator to '.../validators.py'  https://review.openstack.org/459268
08:24 openstackgerrit chenhb proposed openstack/rally master: [WIP]Refactor the related command of task report  https://review.openstack.org/460374
08:28 chhavi joined #openstack-rally
08:52 ushkalim_ joined #openstack-rally
08:55 openstackgerrit Staroverov Anton proposed openstack/rally master: [WIP] Move 'required_contexts' validator to '../validators.py'  https://review.openstack.org/462186
09:11 tosky joined #openstack-rally
09:12 tosky joined #openstack-rally
09:15 yamamoto joined #openstack-rally
09:31 e0ne joined #openstack-rally
09:34 openstackgerrit Staroverov Anton proposed openstack/rally master: [WIP] Move 'required_clients' validator to '../validators.py'  https://review.openstack.org/462167
09:34 rallydev-bot joined #openstack-rally
09:35 rallydev-bot [From Gitter] andreykurilin : @csavignan : hi! I see no problems with. go ahead and update requirements file
09:36 rallydev-bot [From Gitter] andreykurilin : INFO: rallydev-bot crashed this night, so we lost synchronization with IRC channel. But now everything should be ok.
09:36 rallydev-bot [From Gitter] andreykurilin : winston-d_: hi! How can I help you with RPS runner?
09:50 openstackgerrit Tuan Luong-Anh proposed openstack/rally master: Using fixtures instead of deprecated mockpatch module  https://review.openstack.org/462465
10:03 openstackgerrit Cedric Savignan proposed openstack/rally master: Adds Networking-bgpvpn scenarios  https://review.openstack.org/460465
10:20 openstackgerrit chenhb proposed openstack/rally master: [WIP]Refactor the related command of task report  https://review.openstack.org/460374
10:30 mvk joined #openstack-rally
10:40 openstackgerrit chenhb proposed openstack/rally master: [WIP]Refactor the related command of task report  https://review.openstack.org/460374
10:44 alexchadin joined #openstack-rally
10:49 mrhillsman joined #openstack-rally
10:53 jkilpatr joined #openstack-rally
10:59 winston-d_ andreykurilin: hi, I'd like to know how to properly set the 'duration' parameter for RPS runner.
11:00 winston-d_ andreykurilin: for example, I'd like to do a loadline test, which RPS starts at 1, ends at 64 and step is 1, what is the relationship between 'times' and 'duration'?
11:01 openstackgerrit Merged openstack/rally master: Move 'required_neutron_extension' validator to '.../validators.py'  https://review.openstack.org/459268
11:03 winston-d_ andreykurilin: a sample task YAML with RPS runner: https://paste2.org/FV80YAhW
11:06 winston-d_ I briefly skim the code, but not sure if I understand the way RPS runner works.
11:07 rallydev-bot [From Gitter] andreykurilin : winston-d_: Sorry, you should not read the code, we need to improve https://rally.readthedocs.io/en/latest/plugins/plugin_reference.html to cover all properties with good descriptions.
11:07 rallydev-bot [From Gitter] andreykurilin : ok
11:07 rallydev-bot [From Gitter] andreykurilin : `times` is a total number of seconds for genarating load.
11:07 rallydev-bot [From Gitter] andreykurilin : `duration` is a duration of  the particular step.
11:07 winston-d_ There are multiple factors may affect how many requests per second RPS runner can issue to a deployment, besides 'start/end/step/duration', there are also 'max_concurrency', # of CPUs, etc.
11:08 dave-mccowan joined #openstack-rally
11:08 rallydev-bot [From Gitter] andreykurilin : Example: start=X, end=Y, step=Z, duration=M, times=N, max_concurrency=K
11:09 winston-d_ So the unit for 'start/end/step' is request/sec, for 'duration' and 'times' is seconds?
11:09 rallydev-bot [From Gitter] andreykurilin : ok, forgot about max_concurrency) I do not know why we have that parameter
11:09 rallydev-bot [From Gitter] andreykurilin : heh
11:11 rallydev-bot [From Gitter] andreykurilin : so as for  start=X, end=Y, step=Z, duration=M, times=N, RPS runner will start genarating X request per second during M seconds, after M seconds is reached, RPS runner will increase number of request per second and it will be X+Z. That number of request per seconds will be used again for M seconds.
11:12 rallydev-bot [From Gitter] andreykurilin : Number of seconds will be increased each M seconds until N (total time) or the upper limit Z is reached
11:13 rallydev-bot [From Gitter] andreykurilin : if Z number of request per second is achieved, but N is not, RPS will generate Z request per second till the end
11:13 winston-d_ Ah, I see.  But 'constant' runner, the unit for runner is total requests, right?
11:13 rallydev-bot [From Gitter] andreykurilin : yes
11:13 openstackgerrit Staroverov Anton proposed openstack/rally master: [WIP] Move 'required_clients' validator to '../validators.py'  https://review.openstack.org/462167
11:13 winston-d_ Same parameter but different unit, I have to say it's confusing.
11:14 rallydev-bot [From Gitter] andreykurilin : winston-d_: we are trying to document as much as possible. constant runner has simple input data, so it was easy to auto-generate docs for it - https://rally.readthedocs.io/en/latest/plugins/plugin_reference.html#constant-scenario-runner (all parameters have clear descriptions there).
11:15 rallydev-bot [From Gitter] andreykurilin : As for RPS runner, it has complex logic and our jsonschema->docs convertor did not succed with it
11:15 rallydev-bot [From Gitter] andreykurilin : I'll try to fix it soon, so everything will have documentation
11:16 winston-d_ Thanks for the pointer to doc.  I was looking at https://docs.openstack.org/developer/rally/task/index.html#id2 and it doesn't have as much infor as readthedocs.io one.
11:16 openstackgerrit Merged openstack/rally master: [image] Extract the common function  https://review.openstack.org/461457
11:16 rallydev-bot [From Gitter] andreykurilin : winson-d: docs.openstack.org and readthedocs has the same content
11:17 rallydev-bot [From Gitter] andreykurilin : but I like readthedocs theme more:)
11:17 rallydev-bot [From Gitter] andreykurilin : I started(https://review.openstack.org/#/c/448027/) work on modifying task page at docs, so it will be more easier to find all info
11:18 winston-d_ I didn't the description for task runners at https://docs.openstack.org/developer/rally/index.html
11:19 winston-d_ I didn't find the description for task runners at https://docs.openstack.org/developer/rally/index.html
11:19 rallydev-bot [From Gitter] andreykurilin : winston-d_: task page is quite "empty" now. You should follow Plugins->Plugins reference
11:20 openstackgerrit Staroverov Anton proposed openstack/rally master: Move 'image-valid-on-flavor' validator to 'openstack/validators.py'  https://review.openstack.org/457263
11:21 winston-d_ hmm, yeah, it's hidden a few levels under the first level section title.
11:21 winston-d_ Thanks for the help!  Let me try to start a RPS runner.
11:22 rallydev-bot [From Gitter] andreykurilin : yes:(
11:22 rallydev-bot [From Gitter] andreykurilin : task page will look like "verification" page in near future - https://rally.readthedocs.io/en/latest/verification/index.html
11:22 rallydev-bot [From Gitter] andreykurilin : we made a good progress there, I think
11:23 rallydev-bot [From Gitter] andreykurilin : so please be patient and I hope in near future we will make our docs great again:)
11:24 winston-d_ Yes, that'll be much easier to read.
11:25 winston-d_ Anyway, I started a task with RPS runner and this is how it looks like now: http://paste.openstack.org/show/608847/
11:25 winston-d_ See the 'start/end/step' is '1/48/1' and 'times' is 300, 'duration' is 5.
11:26 winston-d_ But look the first 8 requests, they started at the same time.
11:26 winston-d_ I guess 'max_concurrency' plays a role here.
11:28 winston-d_ I was expected to see the first 5 seconds, only 5 requests would be sent to deployment.
11:33 openstackgerrit Staroverov Anton proposed openstack/rally master: [WIP] Move 'required_contexts' validator to '../validators.py'  https://review.openstack.org/462186
11:35 winston-d_ The 'times' parameter doesn't really seem like to control total duration of time (unit: seconds), but instead it still looks like has the unit of 'requests'
11:38 winston-d_ andreykurilin: http://paste.openstack.org/show/608848/ I added the result of this run.  As you can see, 'Count' = 300, which matches the value I set to 'times'
11:43 openstackgerrit Staroverov Anton proposed openstack/rally master: [WIP] Moving of 'required_cinder_services' validator to '../validators.py'  https://review.openstack.org/462042
11:47 catintheroof joined #openstack-rally
11:56 openstackgerrit Andrey Kurilin proposed openstack/rally master: Fix an issue with namespace of scenario  https://review.openstack.org/462516
12:30 rallydev-bot [From Gitter] andreykurilin : winston-d_: I think the problem is in our calculation of the number of request per second which should generate single rally process. By default rally tries to use all processes
12:30 rallydev-bot [From Gitter] andreykurilin : try to setup `max_cpu_count` to `
12:31 rallydev-bot [From Gitter] andreykurilin : to 1
12:32 chhavi joined #openstack-rally
12:36 openstackgerrit Staroverov Anton proposed openstack/rally master: [WIP] Move 'required_services' validator to 'openstack/validators.py'  https://review.openstack.org/458809
12:38 abalutoiu joined #openstack-rally
12:54 yamamoto joined #openstack-rally
13:03 alexchadin joined #openstack-rally
13:04 winston-d_ andreykurilin: how can I change the value of 'max_cpu_count'?
13:07 rallydev-bot [From Gitter] andreykurilin : winston-d_: in the same way as times, step and etc
13:24 yamamoto joined #openstack-rally
13:27 openstackgerrit Mathieu Velten proposed openstack/rally master: Magnum: Move keypair handling at the cluster level  https://review.openstack.org/450136
13:27 openstackgerrit Staroverov Anton proposed openstack/rally master: [WIP] Move 'required-param-or-context' validator to '../validators.py'  https://review.openstack.org/462550
13:35 openstackgerrit Cedric Savignan proposed openstack/rally master: Adds Networking-bgpvpn scenarios  https://review.openstack.org/460465
13:48 openstackgerrit Cedric Savignan proposed openstack/rally master: Adds Networking-bgpvpn scenarios  https://review.openstack.org/460465
14:09 openstackgerrit Merged openstack/rally master: Move 'image-valid-on-flavor' validator to 'openstack/validators.py'  https://review.openstack.org/457263
14:20 catintheroof joined #openstack-rally
14:23 catinthe_ joined #openstack-rally
14:26 e0ne joined #openstack-rally
14:31 e0ne_ joined #openstack-rally
14:36 winston-d_ andreykurilin: 'max_cpu_count' doesn't change anything: http://paste.openstack.org/show/608871/
14:38 winston-d_ still 3 threads began to work at the same time, and total request is 300, is much less than what it supposed to do. (300 seconds, scaling from 1 req/s to 48 req/s).
14:42 winston-d_ er, I meant to say 8 threads.
14:48 andreykurilin ok. rps runner generate each second new number of requests and it doesn't wait for finishing old launched iterations
14:49 andreykurilin this means that in case of long operations you can have the number of not finished iterations ~~> times
15:00 yingjun joined #openstack-rally
15:09 openstackgerrit Staroverov Anton proposed openstack/rally master: [WIP] Move required-api-versions validator to '../validators.py'  https://review.openstack.org/462592
15:11 winston-d_ I will try to do a few more rounds with different combination of all parameters.
15:11 winston-d_ right now, I am doing a round with max_cpu_count and max_concurrency both equals 1.
15:12 andreykurilin max_concurrency should not help in your case
15:12 winston-d_ But I still observed multiple requests being sent at the same time at the very beginning, with 'start' = 1.
15:17 openstackgerrit Staroverov Anton proposed openstack/rally master: [WIP] Move 'required-param-or-context' validator to '../validators.py'  https://review.openstack.org/462550
15:19 winston-d_ andreykurilin: if 'times' = 10, 'start' = 1, 'end' = 10, 'duration' = 1, max_cpu_count/max_concurrency = 1, what's the total number of request rally should send out?
15:20 winston-d_ andreykurilin: it'd be (10+1)*10/2 = 55, right?
15:20 openstackgerrit Staroverov Anton proposed openstack/rally master: Move 'required-param-or-context' validator to '../validators.py'  https://review.openstack.org/462550
15:23 winston-d_ andreykurilin: see this full running log: http://paste.openstack.org/show/608883/
15:24 winston-d_ rally only issued 10 requests, which proves that 'times' is controlling how many total requests should be sent out during the entire RPS run.
15:24 winston-d_ it shouldn't have the unit of second.
15:25 winston-d_ And no matter what value we provided to 'max_cpu_count' and 'max_concurrency', it looks like RPS always use 8 threads.
15:25 winston-d_ I don't think 8 is a magic number, instead my VM has 8 vcpus, I think that should be the reason I am seeing 8 threads.
15:26 winston-d_ Still, RPS runner seems like a mystery to me.
15:26 winston-d_ :/
15:45 yamamoto joined #openstack-rally
16:04 andreykurilin winston-d_: I'll try to digg into RPS runner tomorrow and experiment a bit
16:26 yamamoto joined #openstack-rally
16:45 e0ne joined #openstack-rally
16:46 mrhillsman joined #openstack-rally
17:04 jkilpatr joined #openstack-rally
17:05 rallydev-bot [From Gitter] shihai1991 : @andreykurilin HI, andrey. If some error could be used in cli or server,  we shoud use `4**` or `5**`?
17:08 rallydev-bot [From Gitter] andreykurilin : @shihai1991 hi! It depends on exception. If it is NotFound(ResourceNotFound and etc), it  should be 404. So actually, it doesn't metter for Exceptionwhere it is raisen. If it is problem with some input data - it is 4**.
17:11 aojea joined #openstack-rally
17:12 e0ne joined #openstack-rally
17:14 rallydev-bot [From Gitter] shihai1991 : In my opinion, we should avoid use the code which have been defined in common. And use other status_code to define the error.
18:30 rallydev-bot [From Gitter] r-sood : @chenhb-zte  @andreykurilin  @shihai1991 Link with custom scenario and KeyError http://paste.openstack.org/show/608896/
19:02 zhubingbing_ joined #openstack-rally
19:27 aojea joined #openstack-rally
19:40 rallydev-bot [From Gitter] andreykurilin : @r-sood: I have a quick fix for you
19:40 rallydev-bot [From Gitter] andreykurilin : It will work for both new and old rally releases
19:42 rallydev-bot [From Gitter] andreykurilin : @r-sood you should put `namespace="openstack"` into configure decorator
19:43 dave-mccowan joined #openstack-rally
19:45 dave-mcc_ joined #openstack-rally
19:48 rallydev-bot [From Gitter] r-sood : @andreykurilin  do you mean something like @context.configure(name="pe", namespace="openstack", order=1000)
19:48 harlowja joined #openstack-rally
19:50 aojea joined #openstack-rally
19:52 aojea_ joined #openstack-rally
20:00 rallydev-bot [From Gitter] andreykurilin : in your case it is `@scenario.configure(namespace="openstack")`
20:00 rallydev-bot [From Gitter] andreykurilin : @r-sood ^
20:02 rallydev-bot [From Gitter] r-sood : @andreykurilin Thanks! that worked
21:04 psuriset joined #openstack-rally
21:51 mvk joined #openstack-rally
23:39 jkilpatr joined #openstack-rally

| Channels | #openstack-rally index | Today | | Search | Google Search | Plain-Text | summary