Description
Per the keystone docs:
The OpenStack keystone service catalog allows API clients to dynamically discover and navigate to cloud services.
The catalog describes a list of services along with endpoints for same. For example:
GET /v3/auth/catalog{
"catalog": [
{
"endpoints": [
{
"id": "390de2ac62c5410fb53a7bf5e6bec533",
"interface": "public",
"region_id": "RegionOne",
"url": "http://identity.example.com",
"region": "RegionOne"
}
],
"id": "b2651a44a0bb44d5b5733052a1fc66f7",
"type": "identity",
"name": "keystone"
},
],
"links": {
"self": "http://identity.example.com/v3/auth/catalog"
}
}Notably absent from the catalog though is any mention of version information. It is possible to have multiple endpoints for the same service type using different names. For example, Cinder previously had a v2 API. It is possible to expose both of these using the same service type:
{
"catalog": [
{
"endpoints": [
{
"id": "cdec1b8a3134480c9e326edd8c1d4b13",
"interface": "public",
"region_id": "RegionOne",
"url": "https://volume.example.com/v2",
"region": "RegionOne"
}
],
"id": "8e5833137bc04a65a3f5dd500fe6bcc8",
"type": "block-storage",
"name": "cinder_v2"
},
{
"endpoints": [
{
"id": "5e444bf893b247a69bf1d6fcf3334a23",
"interface": "public",
"region_id": "RegionOne",
"url": "https://volume.example.com/v3",
"region": "RegionOne"
}
],
"id": "8e5833137bc04a65a3f5dd500fe6bcc8",
"type": "block-storage",
"name": "cinder_v3"
},
{
"endpoints": [
{
"id": "390de2ac62c5410fb53a7bf5e6bec533",
"interface": "public",
"region_id": "RegionOne",
"url": "https://identity.example.com",
"region": "RegionOne"
}
],
"id": "b2651a44a0bb44d5b5733052a1fc66f7",
"type": "identity",
"name": "keystone"
},
],
"links": {
"self": "https://identity.example.com/v3/auth/catalog"
}
}The expected behavior here is to fetch the version discovery document from the URL indicated for each endpoint (the root API) (for all services except Swift, unfortunately). This will return a document like so:
GET /v3/{
"versions": [
{
"id": "v3.0",
"status": "CURRENT",
"version": "3.71",
"min_version": "3.0",
"updated": "2023-08-31T00:00:00Z",
"links": [
{
"rel": "describedby",
"type": "text/html",
"href": "https://docs.openstack.org/"
},
{
"rel": "self",
"href": "http://volume.example.com/v3/"
}
],
"media-types": [
{
"base": "application/json",
"type": "application/vnd.openstack.volume+json;version=3"
}
]
}
]
}Gophercloud is not currently doing this, forcing deployments to use versioned service type aliases (i.e. volumev2 or volumev3) rather than the official service type. We should correct this.e