Error finding OpenStack endpoints as service name are not the expected one

[micafer]

Summary

In some cases the service name set in the Keystone is not the expected by the OpenStack driver.

Detailed Information

In some sites CinderV3 volume uses the name "cinder" and not "cinderv3" as the site does support any older cinder versions.

[micafer]

In fact, why do we need to use the name?
As far as I know, the relevant field is the service_type.

[micafer]

One posiible solution is not to set the "service_name" in the OpenStackBaseConnection child classes.

libcloud/libcloud/compute/drivers/openstack.py

Line 113 in c899034

service_name = "cinderv3"

[micafer]

@tisonkun @PsiACE
Could you gime some comments on this issue, pelase?

[tisonkun]

@micafer Yeah. If service_type is the effective field for selection and service_name is not promised to be a fixed value, we can omit it in OpenStackVolumeV3Connection and perhaps OpenStackVolumeV2Connection as well.