[openstack-dev] [qa] [devstack] Confusion about member roles in tempest/devstack

David Kranz dkranz at redhat.com
Mon Apr 6 18:25:14 UTC 2015

There have been a number of changes in tempest recently that seem to 
coordinate with devstack that are a bit unclear.

The following values are defined in tempest config as defaults:

# Roles to assign to all users created by tempest (list value)
#tempest_roles =

# Role to add to users created for swift tests to enable creating
# containers (string value)
#operator_role = Member

# Role required for users to be able to manage stacks (string value)
#stack_owner_role = heat_stack_owner

These are the values created in tempest.conf by devstack:


tempest_roles = Member

stack_owner_role = _member_

So a couple of questions.

Why do we have Member and _member_, and what is the difference supposed 
to be?

Experimentally, it seems that the tempest roles cannot be empty, so why 
is that the default?

The heat_stack_owner role used to be created in juno devstack but no 
longer. Is there a reason to leave this as the default?

Any explanations appreciated !


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150406/dcbe32ed/attachment.html>

More information about the OpenStack-dev mailing list