interop/working_materials/keystone_capabilities_info.csv
Luz Cazares 9b0fec938f Keystone scoring for 2018.01 guideline
Scoring Keystone for guideline 2018.01
Changes: Update notes on the working materials folder.

Items To Be Discussed:
identity-v3-list-projects capability was marked required 2017.09.
But the only TC available was flagged since it needs 2 users.
Q. Should we move the capability back to advisory until TC is fixed?
   or until other suitable TCs are added?

Change-Id: Ic84cbe834474e579345e22256f2e956ad2b4b897
Note: waiting for additional comments from PTL.
2017-10-04 20:59:09 +00:00

3.6 KiB

1CapabilityProgramStatusMethodEndpointTest available?interop relevant?PTL CommentsFrom Defcore DiscussionScorer Comments
2identity-v3-tokens-createplatform/compute/objectrequiredPOST/v3/auth/tokens1yesThe returned token value is in the X-Auth-Token headertempest.api.identity.v3.test_tokens{test_create_token}This TC refers to API https://developer.openstack.org/api-ref/identity/v3/#password-authentication-with-unscoped-authorization. Should we add other test cases to tempest in order to validate API for: password-authentication-with-scoped-authorization and password-authentication-with-explicit-unscoped-authorization?
3identity-v3-api-discoveryplatform/computerequiredGET/v33yesmake requiredtempest.api.identity.v3.test_api_discovery{test_api_version_resources, test_api_media_types, test_api_version_statuses}
4identity-v3-list-projectsplatform/computerequiredGET/v3/users/{user_id}/projects1yesFlagged since require 2 set of user credentials.
5
6identity-v3-create-ec2-credentialsPOST/v3/credentials1yesShould we make ec2 compatibility required? unclear
7identity-v3-list-ec2-credentialsGET/v3/credentials1yesShould we make ec2 compatibility required? unclear
8identity-v3-show-ec2-credentialsGET/v3/credentials/{credential_id}1yesShould we make ec2 compatibility required? unclear
9identity-v3-delete-ec2-credentialsDELETE/v3/credentials/{credential_id}1yesShould we make ec2 compatibility required? unclear
10identity-v3-update-ec2-credentialsPATCH/v3/credentials/{credential_id}Should we make ec2 compatibility required? unclear
11identity-v3-catalog(make sure it works on all supported releases)returned with the token
12identity-v3-password-updatePOST/v3/users/{user_id}/password1yesUntestable without changing user's password, security risk. Also password policies are very particular to different companies, making a test that would pass on all is near impossible.tempest.api.identity.v3.test_users{test_update_own_password}
13
14identity-v3-list-groupsplatform/computeGET/v3/users/{user_id}/groups0yesno test available for this feature
15identity-v3-get-projectplatform/computeGET/v3/projects/{project_id}0yesadmin required
16identity-v3-list-rolesplatform/computeGET/v3/roles0noadmin required
17identity-v3-get-roleplatform/computeGET/v3/roles/{role_id}noadmin required
18identity-v3-list-domainsplatform/computeGET/v3/domainsnoadmin required
19identity-v3-get-domainplatform/computeGET/v3/domains/{domain_id}noadmin required
20
21identity-v3-tokens-validateplatform/computeadvisoryGET/v3/auth/tokensyesToken to be validated is passed in the X-Subject-Token header
22identity-v3-revoke-tokenplatform/computeDELETE/v3/auth/tokens1yesToken to be revoked is passed in the X-Subject-Token headerkeystone.keystone.tests.unit.test_revoke{test_revoke_by_user}
23identity-v3-get-catalogplatform/compute/objectadvisoryGET/v3/auth/catalog0yesTC added in Tempest
24identity-v3-get-auth-projectsplatform/computeGET/v3/auth/projects0yesequivalent as far as I can tell to identity-v3-list-projects. couldn't find a test specific for this, there are some tests related in keystone.tests.unit.test_v3_auth.py
25
26identity-v2-list-versionsGET/1yesDeprecated
27identity-v2-show-versionGET/v2.01yesDeprecated
28identity-v2-token-generationPOST/v2.0/tokens1yesDeprecated
29identity-v2-tenantsGET/v2.0/tenants1yesDeprecated
30identity-v2-list-extensionsGET/v2.0/extensionsDeprecated
31identity-v2-show-extensionGET/v2.0/extensions/{alias}Deprecated