@Rohit: I think having a separate /tempest/tests/compute/admin/test_flavors.py that contains all tests that are relevant for an admin (CRUD + list) and having /tempest/tests/compute/test_flavors.py contain tests that are relevant for a non-admin user (list only?) is the most appropriate solution.
@David: Yes, I agree it's not ideal (the documentation), but hopefully we can go through each API piece and identify those specs that are intended for admin only and move them into /tempest/tests/compute/admin/* with the ComputeAdminConfig object handling that configuration?
@Rohit: I think having a separate /tempest/ tests/compute/ admin/test_ flavors. py that contains all tests that are relevant for an admin (CRUD + list) and having /tempest/ tests/compute/ test_flavors. py contain tests that are relevant for a non-admin user (list only?) is the most appropriate solution.
@David: Yes, I agree it's not ideal (the documentation), but hopefully we can go through each API piece and identify those specs that are intended for admin only and move them into /tempest/ tests/compute/ admin/* with the ComputeAdminConfig object handling that configuration?