No suitable endpoint - Githubissues

flemzord commented 7 years ago

Hello, I'm trying to use your plugin on the OVH cloud (OpenStack). But I have the following error:

FATA[0000] Error initiating gophercloud cinder client: No suitable endpoint could be found in the service catalog.

While I look at the openstack catalog, I have many URLs:

| cinder   | volume  | SBG1                                                                                         |
|          |              |   publicURL: https://volume.compute.sbg1.cloud.ovh.net/v1/08ce6b9efdd04e25a3f5de28a0fc7cf9   |
|          |              |   internalURL: https://volume.compute.sbg1.cloud.ovh.net/v1/08ce6b9efdd04e25a3f5de28a0fc7cf9 |
|          |              |   adminURL: https://volume.compute.sbg1.cloud.ovh.net/v1/08ce6b9efdd04e25a3f5de28a0fc7cf9

Maxence

j-griffith commented 7 years ago

I'm not that familiar with how OVH cloud implements OpenStack but it appears by your snippet that you only have Cinder V1 there? The docker driver is using Cinder V2 endpoint; do you have the V2 endpoint for cinder available in your cloud?

askz commented 7 years ago

Any update on this guys ? Would love to use this driver with OVH cloud too.

paali commented 6 years ago

I have a similar problem on different provider. openstack catalog list shows

| cinderv2   | volumev2       | fi-1 |
|            |                |   publicURL: https://volumes.fi-1.xyz.fi:8776/v2/<tenantid>
|            |                |  ...

We are buying OpenStack infra as a service so not much insight into internals of it. My goal is to use cinder directly as container volume storage in various cluster activities.

I would really like to have a solution that just utilises cinder directly. Especially since we are running on top of OpenStack anyways.

j-griffith commented 6 years ago

Can you please link your config.json file that you're using? I've tested this using v2 and v3 on an Ocata deployment without issues. Keep in mind that the endpoint specified in the config.json file is the Auth endpoint, NOT the Cinder endpoint.

On a related not, I've started work on updating this to use gophercloud/gophercloud (instead of the non-maintained rackspace/gophercloud) and also updating it to use the new Docker volume plugin helper version. If there's interest there's no shortage of work to be done here.

paali commented 6 years ago

{
  "Endpoint": "https://identity.fi-1.xyz.fi:5000/v2.0",
  "Username": "pauli.heikkinen@justadomain.com",
  "Password": "notMyPass",
  "TenantID": "ca35188a848xxxxxxxxxx22da6a6d123",
  "Region": "fi-1"
}

I could try v3 identity API.

If I had any experience on go I could help as this would really help me.

paali commented 6 years ago

Just an update. I got it almost working by building the driver from master branch myself. v3 identify works now just fine. docker volume create -d cinder myvolume works as well. Couldn't test attaching the volume yet since I'm on my local box but progressing anyways. Create and List at least seems to be fine.

j-griffith commented 6 years ago

Oh that's great! Although I wonder what's out of date in the binary that your recompile fixed.

TBH all of my runs are built from source, so I may try and pull the binary next. So far I've tested on a few different clouds including V2 and V3 keystone endpoints using both the older "https://x.x.x.x:5000/vX" and the "https://x.x.x.x/identity" formats.

j-griffith commented 6 years ago

@paali Let me know where you'r at and if I can close this. Will be working on updates in the next couple of weeks.

kumy commented 5 years ago

@flemzord I'm probably building the same setup as you. I successfully configured cdd to communicate with ovh openstack, but my volumes fails to attach (#21), since one year, did you success in your configuration?

j-griffith / cinder-docker-driver

No suitable endpoint #11