Skip to content

Revise service availability table - #113

Closed
marcusboberg wants to merge 1 commit into
masterfrom
Revise-service-availability
Closed

Revise service availability table#113
marcusboberg wants to merge 1 commit into
masterfrom
Revise-service-availability

Conversation

@marcusboberg

Copy link
Copy Markdown
Contributor

Change initiated by Rob McCuaig: Updated the service availability table and added a note about the Backup service's accessibility and data storage.

The introduction of the X* notation clarifies that the Backup service is available from all locations, even though backup data is not stored within the same data center. This distinction helps avoid confusion between service accessibility and data residency.

Change initiated by Rob McCuaig: Updated the service availability table and added a note about the Backup service's accessibility and data storage.
@rjhaverkamp

Copy link
Copy Markdown
Contributor

I'm not sure if this actually clarifies things. The openstack api in sto1 is also accessible from all datacenters. Same with object storage etc.

For the backup server we've only listed DCO since that's where the backup data is stored. With the other products that's somewhat obvious since it's generally implied that storage/compute is tied to a physical site even if you can reach it from different places.

@icepic

icepic commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

We have backup in both DCO and STO2 these days.

@rjhaverkamp rjhaverkamp closed this Jul 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants