Require keystone v3 auth_url when creating software deployment metadata

[Yanyan Hu]

When using POLL_SERVER_HEAT as the software_config_transport method, os-collect-config service needs keystone v3 API to get
authentication. Therefore, the auth_url information of software deployment metadata should also be initialized to v3 version rather than default v2.0 one.

Otherwise, the heat collector of os-collect-config will always yield the following error when trying to get authenticationusing keystone client:

Jul 4 03:46:43 sfc-3-server-lzu435zpeyhu os-collect-config: 2014-07-04 03:46:43.253 610 WARNING os_collect_config.heat [-] Authorization failed: The resource could not be found. (HTTP 404)
Jul 4 03:46:43 sfc-3-server-lzu435zpeyhu os-collect-config: 2014-07-04 03:46:43.254 610 WARNING os-collect-config [-] Source [heat] Unavailable.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/104754

[Steven Hardy (shardy)]

Personally I think this should be fixed via version discovery in the client (e.g os-collect-config) rather than by updating the endpoint heat sets in the metadata.

The issue is we're moving towards unversioned endpoints in the keystone catalog, so we really (eventually..) want to eliminate all usage of versioned endpoints in favor of better version discovery in the clients.

There's code in keystoneclient already which can help with this, and a patch which adds support for v3 keystone to python-heatclient:

https://review.openstack.org/#/c/92728/16/heatclient/shell.py

So while we probably can fix this in heat, I'm not sure if we actually should?

[OpenStack Infra (hudson-openstack)]

Change abandoned by Yanyan Hu (<email address hidden>) on branch: master
Review: https://review.openstack.org/104754
Reason: Has been fixed in os-collect-config side.

https://review.openstack.org/#/c/107611/

[Qiming Teng (tengqim)]

Marking it as 'invalid' here in Heat since it has been fixed from tripleO side.

[Yanyan Hu (yanyanhu)]

This is not a bug of heat. Related bug has been reported and fixed in os-collect-config.

https://bugs.launchpad.net/os-collect-config/+bug/1341936
https://review.openstack.org/107611