docs
docs copied to clipboard
ovh
wrong publicUrl endpoint
I've downloaded the openrc.sh file from my ovh account. Using source openrc.sh reported me publicURL endpoint for compute service in GRA region not found. I had to edit the file and use GRA7. May be you should indicate to verify the OS_REGION_NAME var.
Same here. Just download the openrc.sh on GRA and got the same error. As it's my first interaction with OVH API, I'm a bit disappointed. I hope the quality will be good enough.
edit: 6 months later... I'm still using OVH's openstack system. Here my experience: The openstack Terraform provider is well supported. Just tweak a bit the private network config because it was not always fully ready when the rest of resources are created and need it. But except this, everything works very well: never a VM restart, never a network issue, never a Terraform failure. VM starts in seconds. Volumes have no failures. So I'm very pleased to have made this choice for now.
As you can see, OVH doesn't even take the time to respond. Good luck with OpenStack.
Hello
There is a mix-up or URLs here. If you want to access GRA object storage via S3 protocol, you should follow the doc here https://docs.ovh.com/gb/en/storage/getting_started_with_the_swift_S3_API/
If you are using the .openrc file to access the object storage via Swift protocol, you must take care as object storage is in the global GRA region while compute ressources (servers, keypairs...) are in the GRAxx region.
So, your openstack keypair list will only work if you use a .openrc file from GRAxx region. openstack object list <container> will only work with an .openrc from the GRA region.
Anyway, if you are using S3 (which I recommend), just consider the .openrc file from your GRAxx region and use the above documentation to access the object storage using S3.
@davidlandais thank you for your post! It's been 2.5 years and the cloud console still generates wrong openrc.sh file.
Thank's to your post I updated DE=> DE1 which fixed the publicURL issue. 😇
