OVH: Deletion of endpoints for Object Storage and Cloud Archive

[emaktech]

I have seen the following message from OVH recently:

Now: Announcing the new global regions.
The new global regions are automatically added to existing projects, and can be used for Object Storage and Cloud Archive services, via the endpoints for both specific and global regions.
For this reason, now is the right time to make the required changes to your applications and orchestration tools. For information purposes, the configuration files generated by the client interface for the CLI and rclone are up-to-date. You can download them again, if required.
It is also worth modifying the sync configurations for containers, as well as the address by domain name (CNAME or TXT DNS records). If your domains target our IP addresses directly (A record), you need to switch to the CNAME record.
All new Public Cloud projects will have their Object Storage and Cloud Archive services uniquely directed to the new global regions.

18th February, 2020: Deletion of endpoints for Object Storage and Cloud Archive in specific regions.
Certain Swift endpoints will be removed from the service catalogue (announced by Keystone) for specific regions, and will then only be available for global regions.

So my question is, if we are, for example, mounting the svfs filesystem with region=BHS1, will this mean that svfs will be broken as of February 18th? Hopefully somebody knows. I looked through the code and am clear on where the region is passed along to the OVH API...

[juju2143]

I think you'll want to change BHS1 to just BHS. From what I see they just dropped the numbers in the region names, so logically you'll want to do the same. Anyway it worked for me, but I don't know if it's the right thing.

[emaktech]

I think you're right @juju2143 . I wasn't sure because I was getting timeouts while testing it that way the other day so I wasn't sure. It seems to be working just fine now just passing region=BHS as an argument!