From: ext Matthew Treinish [mailto:email@example.com]
Sent: Tuesday, June 16, 2015 4:49 PM
To: firstname.lastname@example.org; All Things QA.
Subject: Re: [openstack-qa] [QA] [tempest] UUIDs and names in tempest.conf
So I need to point out that the openstack-qa list isn't used anymore. We
keep it around so we have a place to send for periodic test results. In
future you should just send things to the openstack-dev ML with a [QA] tag
in the subject.
On Tue, Jun 16, 2015 at 05:25:30AM +0000, Tikkanen, Viktor (Nokia -
I have a question regarding usage of UUIDs and names in the tempest.conf
file. Are there some common ideas/reasons (except unambiguousness and
making test cases simpler) why some parameters (e.g. publicnetworkid,
flavorref, imageref, ...) are designed so that they require entity UUIDs
but others (e.g. fixednetworkname, floatingnetworkname, ...) require
So this is mostly a historical artifact from before I even started working
the project, my guess is this was done because not all resources require
names, but that's just my guess. Config options to tell tempest resources
which were added more recently use a name because it's hard for people to
with uuids. That being said there is a spec still under review to
how we specify resources in tempest to make things a bit simpler and more
consistent: https://review.openstack.org/173334 Once the details are
in the spec review and implementation begins we'll deprecate most of the
existing options in favor of the new format for specifying resources.
There were no activities with this spec since middle of April but anyway
thank you for the clarification.
Currently there seems to be a number of functions like getnetworkfromname
(/opt/tempest/tempest/common/fixednetwork.py) for UUID/name conversion
available but as you said there is a need for more consistent test resource
OpenStack Development Mailing List (not for usage questions)