Hi, contributions to make python-tempestconf smarter - being able to discover more relevant configuration are always welcomed. 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. 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. 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 (*like hw:mem_page_size* you mentioned) to the flavors. 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. https://opendev.org/openstack/openstack-ansible-os_tempest On Tue, 19 Jan 2021 at 13:23, Luigi Toscano <ltoscano@redhat.com> wrote:
On Tuesday, 19 January 2021 12:49:19 CET Szabolcs Tóth wrote:
Hej!
The official tool named python-tempestconf has a parameter named --create, which allows to create the following resources:
* CirrOS image (uploads the image based on the location defined with --image parameter), * Flavors (based on default values - DEFAULT_FLAVOR_RAM, DEFAULT_FLAVOR_RAM_ALT, DEFAULT_FLAVOR_DISK - which can be changed with --flavor-min-mem and --flavor-min-disk).
In order to verify our specific installation with Tempest, we need to create the basic resources as
* Flavors (with extra-spec parameters like hw:mem_page_size). * Networks (one for fixed_network_name and one for floating_network_name).
* python-tempestconf is able to find an already existing network created with router:external flag and set it as value for floating_network_name.
* Router and port (for routing traffic between internal and external networks).
I would like to ask the following:
* Is there any particular reason why the basic resource create functionality is limited to the image and flavor? * Are there any plans to extend the basic resource create functionality?
The aim of python-tempestconf (which is not part of the QA/tempest project, but of the refstack project) is described as "for automatic generation of tempest configuration based on user’s cloud."
This means that any resource creation is limited to what is needed for running "the basics" of tempest.
From an historical point of view, it is not meant to be able to discover everything, but to be used as starting point for your tempest settings, which means that tests may work with the output of tempestconf, but tuning may be needed and it is expected.
* Ability to set extra parameters for the flavors. * Creating networks, routers and ports (based on a user inputs,
which
can be separate parameters or a specific file).
Would the community accept contributions extending python-tempestconf into this direction?
I'd leave space to other python-tempestconf people, but IMHO this will stretch the scope of the project.
-- Luigi
-- Martin Kopec Software Quality Engineer Red Hat EMEA <https://www.redhat.com> <https://red.ht/sig>