<div dir="ltr">Mike, <div><br></div><div><br></div><div><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex" class="gmail_quote">I understand your concern about keeping the number of different benchmark scenarios in Rally not too big so that users don't get confused. But what I really like now about benchmark scenario names in Rally is that they are highly declarative, i.e. you read them and you have a clear idea of what's going on inside those scenarios. You see "boot_and_delete_server" => you know that Rally will boot and then delete a server, "boot_server" => only boot a server.</blockquote></div><div><br></div><div><br></div><div>"do_delete" is as well quite clear for understanding. </div><div><br></div><div>This will solve 2 more issues. </div><div><br></div><div>1) Now we have benchmarks that are creating a lot of resources. And it's not clear are we deleting everything or just single resource. </div><div>2) Inconsistence in naming (there are part of benchmarks that deletes resources but don't have delete in name) </div><div><br></div><div><br></div><div>In any case this reduce huge duplication of code with should be nice IMHO. </div><div><br></div><div>Best regards,</div><div>Boris Pavlovic </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jan 18, 2015 at 7:18 PM, Mikhail Dubov <span dir="ltr"><<a href="mailto:mdubov@mirantis.com" target="_blank">mdubov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Boris,<div><br></div><div>I understand your concern about keeping the number of different benchmark scenarios in Rally not too big so that users don't get confused. But what I really like now about benchmark scenario names in Rally is that they are highly declarative, i.e. you read them and you have a clear idea of what's going on inside those scenarios. You see "<span style="font-size:13px">boot_and_delete_server" => you know that Rally will boot and then delete a server, </span>"<span style="font-size:13px">boot_server" => only boot a server.</span></div><div><br></div><div>That's very convenient e.g. when you navigate through Rally report pages: you see the scenario names in the left panel and you know what to expect from their results. It seems to me that, if we merge scenarios like "<span style="font-size:13px">boot_server" and "</span><span style="font-size:13px">boot_and_delete_</span><span style="font-size:13px">server" together, we will lose a bit in clarity.</span></div><div><br></div><div>Besides, as you pointed out, "<span style="font-size:13px">Nova.boot_server" and "</span><span style="font-size:13px">Nova.boot_and_delete_server" are used for two different purposes - seems to be indeed a strong reason for keeping them separated.</span></div></div><div class="gmail_extra"><br clear="all"><div><div><div dir="ltr"><div><div dir="ltr"><font color="#666666">Best regards,</font><div><font color="#666666">Mikhail Dubov</font></div><div><font color="#666666"><br></font></div><div><span style="color:rgb(102,102,102);font-family:arial;font-size:small">Engineering OPS</span><br></div><div><font color="#666666">Mirantis, Inc.</font></div><div><font color="#666666">E-Mail: <a href="mailto:mdubov@mirantis.com" target="_blank">mdubov@mirantis.com</a></font></div><div><font color="#666666">Skype: msdubov</font></div></div></div></div></div></div>
<br><div class="gmail_quote"><div><div class="h5">On Sat, Jan 17, 2015 at 8:47 PM, Boris Pavlovic <span dir="ltr"><<a href="mailto:boris@pavlovic.me" target="_blank">boris@pavlovic.me</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hi stackers, <div><br></div><div>I have an idea about removing almost half of rally scenarios and keep all functionality. </div><div><br></div><div>Currently you can see a lot of similar benchmarks like: </div><div><br></div><div>NovaServers.boot_server # boot server with passed arguments<br></div><div>NovaServers.boot_and_delete_server # boot server with passed arguments and delete</div><div><br></div><div>The reason of having this 2 benchmarks are various purpose of them: </div><div><br></div><div>1) Nova.boot_server is used for <b>volume/scale testing</b>. </div><div>Where we would like to see how N active VM works and affects OpenStack API and booting next VMs. </div><div><br></div><div>2) Nova.boot_and_delete_server is used for <b>performance/load</b> testing. <br></div><div>We are interested how booting and deleting VM perform in case on various load (what is different in duration of booting 1 VM when we have 1, 2, M simultaneously VM boot actions)</div><div><br></div><div><br></div><div><b>The idea is to keep only 1 boot_server and add arguments "do_delete" with by default False. </b><br></div><div><b><br></b></div><div>It means that:</div><div><br></div><div> # this is equal to old Nova.boot_server<br></div><div>NovaServers.boot_server: [{"args": {...} }] </div><div><br></div><div># this is equal to old Nova.boot_and_delete_server<br></div><div>NovaServers.boot_server: [{"args": {..., do_delete: True}] </div><div><br></div><div><br></div><div>Thoughts? </div><div><br></div><div><br></div><div>Best regards, </div><span><font color="#888888"><div>Boris Pavlovic </div></font></span></div>
<br></div></div><span class="">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></span></blockquote></div><br></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>