1
0
-1

Hi,


I am trying to install ONAP Amsterdam release. But the openstack I use currently supports Keystone v3 API. I can see in Vetted vFirewall Demo - Full draft how-to for F2F and ReadTheDocs#Fulldrafthow-toforF2FandReadTheDocs-FixestoPullandTest  it says "v2 deprecated in favor of v3". But in robot scripts, I can't see any code which sends request to keystone v3, instead I found that we are adding '/v2.0' if not found in keystone_auth_url from https://git.onap.org/testsuite/tree/robot/resources/openstack/keystone_interface.robot?h=amsterdam#n64. So according to this can I assume robot scripts are not stil ready for v3? Or am I missing something here?

    CommentAdd your comment...

    2 answers

    1.  
      1
      0
      -1

      Hi Daniel Rose


      I have tried by adding v3 to auth_url also, but it is just appending /v2.0 to the v3 as below:

      Arguments: [ 'keystone' | '/v3/v2.0/tokens' | data={'auth': {'passwordCredentials': {'password': 'uQ12aA9uQ12aA9uQ12aA9uQ1uQuQ1', 'username': 'SVC-VDSI'}, 'tenantId': '0d87283f6eed45bb87bae04686811734'}} | headers={'Accept': 'application/json', 'Content-Type': 'application/json', 'X-FromAppId': 'robot-ete', 'X-TransactionId': 'robot-ete-c4830c1f-7e5b-49a7-bc44-5f3a55c10dcf'} ]


      So it seems it just checks for v2.0 if it didn't find it, it just appends v2.0  to it.

      I will  raise the ticket. Thanks Daniel!

        CommentAdd your comment...
      1.  
        1
        0
        -1

        the default if nothing is provided is v2 but i believe keystone will return a v3 and that should be working. If thats not the case open a ticket

          CommentAdd your comment...