<div dir="ltr"><div>Hi,</div><div><br></div><div>contributions to make python-tempestconf smarter - being able to discover more relevant configuration are always welcomed. <br></div><div>In regards of resource creation, I'd probably stick with the current resources (images and flavors) and wouldn't complicate it with more such as network ones. <br></div><div><br></div><div>I think it would be better if you would create any network resources you need prior python-tempestconf execution, I expect that something like that will have more logic (code) which increases maintenance requirements - it will be better also for you if you have more control over it.</div><div>Speaking about flavors, we already support ram and disk modifications so I think that we could add one more option through which a user could pass custom parameters (<i>like hw:mem_page_size</i> you mentioned) to the flavors.</div><div><br></div><div>Btw, check out ansible-role-os_tempest, it's basically a role/wrapper around tempest and python-tempestconf. It creates basic network resources and some other stuff in order to prepare for tempest execution.<br></div><div><a href="https://opendev.org/openstack/openstack-ansible-os_tempest">https://opendev.org/openstack/openstack-ansible-os_tempest</a></div><div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 19 Jan 2021 at 13:23, Luigi Toscano <<a href="mailto:ltoscano@redhat.com" target="_blank">ltoscano@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tuesday, 19 January 2021 12:49:19 CET Szabolcs Tóth wrote:<br>
> Hej!<br>
> <br>
> The official tool named python-tempestconf has a parameter named --create,<br>
> which allows to create the following resources:<br>
> <br>
> * CirrOS image (uploads the image based on the location defined with<br>
> --image parameter), * Flavors (based on default values -<br>
> DEFAULT_FLAVOR_RAM, DEFAULT_FLAVOR_RAM_ALT, DEFAULT_FLAVOR_DISK - which can<br>
> be changed with --flavor-min-mem and --flavor-min-disk).<br>
> <br>
> In order to verify our specific installation with Tempest, we need to create<br>
> the basic resources as<br>
> <br>
> * Flavors (with extra-spec parameters like hw:mem_page_size).<br>
> * Networks (one for fixed_network_name and one for<br>
> floating_network_name).<br>
> <br>
> * python-tempestconf is able to find an already existing network<br>
> created with router:external flag and set it as value for<br>
> floating_network_name.<br>
> <br>
> * Router and port (for routing traffic between internal and external<br>
> networks).<br>
> <br>
> I would like to ask the following:<br>
> <br>
> * Is there any particular reason why the basic resource create<br>
> functionality is limited to the image and flavor? <br>
> * Are there any plans<br>
> to extend the basic resource create functionality?<br>
<br>
The aim of python-tempestconf (which is not part of the QA/tempest project, <br>
but of the refstack project) is described as "for automatic generation of <br>
tempest configuration based on user’s cloud."<br>
<br>
This means that any resource creation is limited to what is needed for running <br>
"the basics" of tempest.<br>
<br>
>From an historical point of view, it is not meant to be able to discover <br>
everything, but to be used as starting point for your tempest settings, which <br>
means that tests may work with the output of tempestconf, but tuning may be <br>
needed and it is expected.<br>
<br>
> <br>
> * Ability to set extra parameters for the flavors.<br>
> * Creating networks, routers and ports (based on a user inputs, which<br>
> can be separate parameters or a specific file).<br>
> <br>
> Would the community accept contributions extending python-tempestconf into<br>
> this direction?<br>
<br>
I'd leave space to other python-tempestconf people, but IMHO this will stretch <br>
the scope of the project.<br>
<br>
-- <br>
Luigi<br>
<br>
<br>
<br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr"><div dir="ltr"><div>
<p style="font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:capitalize;font-family:"RedHatText",sans-serif">
<span>Martin</span> <span>Kopec </span><span style="color:rgb(170,170,170);margin:0px"></span>
</p>
<p style="font-weight:normal;font-size:12px;margin:0px;text-transform:capitalize;font-family:"RedHatText",sans-serif">
<span>Software Quality Engineer</span>
</p>
<p style="font-weight:normal;margin:0px 0px 4px;font-size:12px;font-family:"RedHatText",sans-serif">
<a style="color:rgb(0,136,206);font-size:12px;margin:0px;text-decoration:none;font-family:"RedHatText",sans-serif" href="https://www.redhat.com" target="_blank">Red Hat <span>EMEA</span></a>
</p>
<div style="margin-bottom:4px">
</div>
<p style="font-weight:normal;margin:0px;font-size:12px;font-family:"RedHatText",sans-serif">
</p>
<div style="margin-top:12px">
<table border="0">
<tbody><tr>
<td width="100px"><a href="https://red.ht/sig" target="_blank"> <img src="https://static.redhat.com/libs/redhat/brand-assets/latest/corp/logo.png" width="90" height="auto"></a> </td>
</tr>
</tbody></table>
</div>
</div></div></div></div>