<div dir="ltr"><div dir="ltr">hi!<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">чт, 3 авг. 2023 г. в 18:22, Taltavull Jean-François <<a href="mailto:jean-francois.taltavull@elca.ch" target="_blank">jean-francois.taltavull@elca.ch</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<div lang="FR-CH">
<div>
<p class="MsoNormal"><span lang="EN-US">Hi openstack-discuss,<br>
<br>
I’m currently using Rally v3.4.0 to test our OpenStack Zed platform.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Rally has been deployed on a dedicated virtual machine and Rally tasks and Tempest tests, launched on this machine by Rundeck, run pretty well.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Now, I wish every OpenStack team member could launch whatever scenario or test he wants, when he wants, for example after having applied a service configuration change on the staging platform.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">And a question is arising: can several users launch different Rally scenarios or Tempest tests at the same time, from their own Linux account/environment, using the same Rally, the one which is deployed on the dedicated
machine ?<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> </span></p></div></div></div></blockquote><div><br></div><div>Rally Task framework itself does not have limitations for parallel executions.</div><div><span class="gmail-HwtZe" lang="en"><span class="gmail-jCAhz gmail-ChMk0b"><span class="gmail-ryNqvb">But it is worth considering a few nuances:</span></span></span></div><div><span class="gmail-HwtZe" lang="en"><span class="gmail-jCAhz gmail-ChMk0b"><span class="gmail-ryNqvb">- Database backend. Rally is configured to use </span></span></span>SQLite by default. It does not support simultaneous write operations, which can be an issue for using a dedicated rally instance for running parallel tasks. Switching to MySQL/Postgres should not have such an issue.</div><div>- File descriptions. If you run too many parallel tasks with a huge number of parallel iterations, you may face default linux limitation of open file descriptors.</div><div><br></div><div>I never ran Tempest simultaneously for the same cloud, so I cannot guarantee that there are no bugs, but it should be ok in general.<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div lang="FR-CH"><div><p class="MsoNormal"><span lang="EN-US"><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Thanks and best regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Jean-Francois<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><br>
<br>
<br>
<u></u><u></u></span></p>
</div>
</div>
</div></blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr">Best regards,<br>Andrey Kurilin.<br></div></div></div>