That mistake was what was fixed. It should be working now. Regards, Mark
Mark Beierl SW System Sr Principal Engineer Dell EMC | Office of the CTO mobile +1 613 314 8106<tel:1-613-314-8106> [email protected]<mailto:[email protected]> On Jul 5, 2017, at 22:34, Lvjing (Jing Lu) <[email protected]<mailto:[email protected]>> wrote: Hi Mark, I found in master, the StorPerf Swagger UI posts jobs GET API with “metrics_type” parameter instead of “type”, which also cause the problem when checking job status. BR, Jing Lu From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of 吴之惠 Sent: Wednesday, July 05, 2017 5:04 PM To: Beierl, Mark <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: [opnfv-tech-discuss] [storperf]Met a problem when checking job status Hi Mark, Thanks for your help. It works now. BRs, Zhihui.Wu Beierl, Mark <[email protected]<mailto:[email protected]>>于2017年7月5日周三 上午1:28写道： Hello, Zhihui Wu The issue has been fixed in master. Doing a docker pull of the latest image (or using the scripts in ci) should work again. Regards, Mark Mark Beierl SW System Sr Principal Engineer Dell EMC | Office of the CTO mobile +1 613 314 8106<tel:1-613-314-8106> [email protected]<mailto:[email protected]> On Jul 4, 2017, at 09:54, Beierl, Mark <[email protected]<mailto:[email protected]>> wrote: Hello, This looks like a problem that exists currently in Master due to the Docker compose changes. Did you use the scripts from Danube or master? Use: git checkout danube.2.0 to get the daily.sh that corresponds to the Danube container. I will be fixing the issue with master today, if you prefer to wait and stick with master. Regards, Mark Mark Beierl SW System Sr Principal Engineer Dell EMC | Office of the CTO mobile +1 613 314 8106<tel:1-613-314-8106> [email protected]<mailto:[email protected]> On Jul 3, 2017, at 22:39, 吴之惠 <[email protected]<mailto:[email protected]>> wrote: Hi, Mark I run storperf test on an apex(Danube 2.0) virtual environment. Since it is a virtual environment with limited resource, I did some modifications: 1. modify the default flavor: change the RAM from 8192 to 2048 2. set CINDER_NODES = 2 3. set QUEUE_DEPTHS = 1 4. set WORKLOADS = rw Based on these modifications, I run the storperf ci scripts daily.sh. According to the storperf.log, test cases were completely executed. But the process was blocked on checking job status. I attach the storperf.log here. And I directly run the command curl -s -X GET "http://127.0.0.1:5000/api/v1.0/jobs?id=380f819c-b729-455e-b228-828a54c8b04e&type=status"; the return is { "_warm_up.queue-depth.8.block-size.16384.read.bw<http://warm_up.queue-depth.8.block-size.16384.read.bw/>": 0.0, "_warm_up.queue-depth.8.block-size.16384.read.iops": 0.0, "_warm_up.queue-depth.8.block-size.16384.read.lat.mean": 0.0, "_warm_up.queue-depth.8.block-size.16384.write.bw<http://warm_up.queue-depth.8.block-size.16384.write.bw/>": 17200.25, "_warm_up.queue-depth.8.block-size.16384.write.iops": 1075.115, "_warm_up.queue-depth.8.block-size.16384.write.lat.mean": 7445.6625, "rw.queue-depth.1.block-size.1024.read.bw<http://rw.queue-depth.1.block-size.1024.read.bw/>": 344.7083333333333, "rw.queue-depth.1.block-size.1024.read.iops": 345.30750000000006, "rw.queue-depth.1.block-size.1024.read.lat.mean": 969.1866666666665, "rw.queue-depth.1.block-size.1024.write.bw<http://rw.queue-depth.1.block-size.1024.write.bw/>": 147.875, "rw.queue-depth.1.block-size.1024.write.iops": 148.21291666666664, "rw.queue-depth.1.block-size.1024.write.lat.mean": 4475.600833333333 } The return doesn't include status information. Any ideas about it? Thanks! Zhihui.Wu <storperf.log> _______________________________________________ opnfv-tech-discuss mailing list [email protected]<mailto:[email protected]> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss <ss.png>
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
