OVHcloud Public Cloud Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
Object Storage container-sync
Incident
Report for Public Cloud
Resolved
An issue prevents swift container sync from replicating data across the regions, we are working on a fix
Update(s):
Date: 2016-11-08 15:27:19 UTC
After we wrote a fix for the initial issue (old-style container-sync
broken), we tried to enable the new-style container-sync. We found out
that:
- it works (yeah!)
- it breaks old-style container-sync.
The way the feature is coded, old-style and new-style container-sync
cannot work together. Instead of wasting time to fix a feature the
coredevs clearly does not want to maintain (and so, will break again),
we ask you to upgrade your container configuration to use the new-style
container-sync.
To upgrade to new-style, I first recommend to unconfigure the
container-sync on both source and destination containers:
curl -X POST -H 'X-Auth-Token: {TOKEN}' \\
-H 'X-Remove-Container-Sync-To: 1' \\
-H 'X-Remove-Container-Sync-Key: 1' \\
https://storage.{REGION}.cloud.ovh.net/v1/{ACCOUNT}/{CONTAINER}
Enabling new-style container-sync is very similar to old-style. With
old-style you had to put the URL of the destination container in
X-Container-Sync-To. With new-style, instead of an URL, this is now a
pseudo URL with realm name and cluster name instead of the domain.
Example:
- old-style> X-Container-Sync-To:
https://storage.bhs1.cloud.ovh.net/v1/AUTH_account/container
- new-style>
X-Container-Sync-To: //OVH_PUBLIC_CLOUD/BHS1/AUTH_account/container
To know the realm and cluster name of a region, you can check its /info
page: https://storage.bhs1.cloud.ovh.net/info (container-sync ->
realms). You can see the \"current\" infra, and also all realms/cluster
accessible from container-sync.
Official documentation:
http://docs.openstack.org/developer/swift/overview_container_sync.html#using-the-swift-tool-to-set-up-synchronized-containers
Date: 2016-11-04 08:56:09 UTC
We found a last minute bug in testing environment. Container sync should be fixed at the beginning of next week.
Date: 2016-11-03 09:29:42 UTC
We found two regressions in the recent versions of Swift. Old style container sync, while not officially deprecated, is not maintained, not even tested, by the core dev of Swift.
We wrote a fix for the two regressions, it is currently in preproduction, should be deployed very soon in production.
As there seem to be no will of maintain the old style container sync, we will ask all customers to move to new-style container sync as soon as we will enable it in configuration.
Update(s):
Date: 2016-11-08 15:27:19 UTC
After we wrote a fix for the initial issue (old-style container-sync
broken), we tried to enable the new-style container-sync. We found out
that:
- it works (yeah!)
- it breaks old-style container-sync.
The way the feature is coded, old-style and new-style container-sync
cannot work together. Instead of wasting time to fix a feature the
coredevs clearly does not want to maintain (and so, will break again),
we ask you to upgrade your container configuration to use the new-style
container-sync.
To upgrade to new-style, I first recommend to unconfigure the
container-sync on both source and destination containers:
curl -X POST -H 'X-Auth-Token: {TOKEN}' \\
-H 'X-Remove-Container-Sync-To: 1' \\
-H 'X-Remove-Container-Sync-Key: 1' \\
https://storage.{REGION}.cloud.ovh.net/v1/{ACCOUNT}/{CONTAINER}
Enabling new-style container-sync is very similar to old-style. With
old-style you had to put the URL of the destination container in
X-Container-Sync-To. With new-style, instead of an URL, this is now a
pseudo URL with realm name and cluster name instead of the domain.
Example:
- old-style> X-Container-Sync-To:
https://storage.bhs1.cloud.ovh.net/v1/AUTH_account/container
- new-style>
X-Container-Sync-To: //OVH_PUBLIC_CLOUD/BHS1/AUTH_account/container
To know the realm and cluster name of a region, you can check its /info
page: https://storage.bhs1.cloud.ovh.net/info (container-sync ->
realms). You can see the \"current\" infra, and also all realms/cluster
accessible from container-sync.
Official documentation:
http://docs.openstack.org/developer/swift/overview_container_sync.html#using-the-swift-tool-to-set-up-synchronized-containers
Date: 2016-11-04 08:56:09 UTC
We found a last minute bug in testing environment. Container sync should be fixed at the beginning of next week.
Date: 2016-11-03 09:29:42 UTC
We found two regressions in the recent versions of Swift. Old style container sync, while not officially deprecated, is not maintained, not even tested, by the core dev of Swift.
We wrote a fix for the two regressions, it is currently in preproduction, should be deployed very soon in production.
As there seem to be no will of maintain the old style container sync, we will ask all customers to move to new-style container sync as soon as we will enable it in configuration.