Open Stack

> -----Original Message-----
> From: ext Matthew Treinish [mailto:mtreinish at kortar.org]
> Sent: Tuesday, June 16, 2015 4:49 PM
> To: openstack-dev at lists.openstack.org; All Things QA.
> Subject: Re: [openstack-qa] [QA] [tempest] UUIDs and names in tempest.conf
> file
> 
> So I need to point out that the openstack-qa list isn't used anymore. We
> only
> keep it around so we have a place to send for periodic test results. In
> the
> 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 -
> FI/Espoo) wrote:
> > Hi!
> >
> > 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. public_network_id,
> flavor_ref, image_ref, ...) are designed so that they require entity UUIDs
> but others (e.g. fixed_network_name, floating_network_name, ...) require
> entity names?
> 
> So this is mostly a historical artifact from before I even started working
> on
> the project, my guess is this was done because not all resources require
> unique
> names, but that's just my guess. Config options to tell tempest resources
> to use
> which were added more recently use a name because it's hard for people to
> deal
> with uuids. That being said there is a spec still under review to
> rationalize
> how we specify resources in tempest to make things a bit simpler and more
> consistent: https://review.openstack.org/173334 Once the details are
> ironed out
> 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 get_network_from_name
(/opt/tempest/tempest/common/fixed_network.py) for UUID/name conversion
available but as you said there is a need for more consistent test resource
management...

-VT