openstack keyston v3 API format

[wallnerryan]

• keystone v3 api expects domain inside project for scope, make sure to use public URL

"scope": {
      "project": {
        "name": "demo",
        "domain": { "id": "e73bb4bfe82940489f271cf96abf1528" }
      }

or

"scope": {
      "project": {
        "name": "demo",
        "domain": { "name": "foo" }
      }

also the public URL is the one we want as the internal API URLs may not be reachable for users.

Given the below list of srv[:endpoints] we want public as 192... is not reachable

{"url"=>"http://192.168.200.4:8004/v1/e9a2869893734aab8061c0ebb10e0876", "interface"=>"admin", "region"=>"RegionOne", "region_id"=>"RegionOne", "id"=>"6167aa49816642fca39c3cef4cacf9f0"}
{"url"=>"https://cloud.corp.com:8004/v1/e9a2869893734aab8061c0ebb10e0876", "interface"=>"public", "region"=>"RegionOne", "region_id"=>"RegionOne", "id"=>"d71643b135754519bbf6425a27bc6926"}
{"url"=>"http://192.168.200.4:8004/v1/e9a2869893734aab8061c0ebb10e0876", "interface"=>"internal", "region"=>"RegionOne", "region_id"=>"RegionOne", "id"=>"f754d907d5ce466b88658fe797e09822"}
{"url"=>"https://cloud.corp.com:8004/v1/e9a2869893734aab8061c0ebb10e0876", "interface"=>"public", "region"=>"RegionOne", "region_id"=>"RegionOne", "id"=>"d71643b135754519bbf6425a27bc6926"}

[chrisroberts]

👍 The change will break v2 compat, however, which I'd like to prevent. I'll see if I can break this down to support multiple version authentication schemes.

[wallnerryan]

@chrisroberts the changes are within class Version3 < Authenticate my understanding is that it would only affect v3 ? Happy to help update where appropriate

[wallnerryan]

This PR also doesnt fix things when i was trying to use the below which sfn seems to also take, but its unclear to me why these 2 are useful.

export OPENSTACK_TOKEN=6a8ce137d235409fbf53404cb743d3a4
export OPENSTACK_USER_ID=3d1e491f6ab89e8d0818e2741c08119648cf25abd37294d61c1da51ecd063a7f