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:
[auth]
# Roles to assign to all users created by tempest (list value)
#tempest_roles =
[object-storage]
# Role to add to users created for swift tests to enable creating
# containers (string value)
#operator_role = Member
[orchestration]
# 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:
[auth]
tempest_roles = Member
[orchestration]
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 !
-David
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
