Static Links between TPOs not belonging to the same TSS

Purpose

The main purpose of this feature is to be able to create a static link between two TPOs not belonging to the same TSS.

Instead of having a big site managed by only one TSS, more and more customers have multiple smallest sites managed by their own TSS(s). Consequently, this feature offer them the ability to create static links between TPOs managed by multiple TSSs which are totally independent.

As an extension of the classic TPO Static Links, this feature drastically reduces site to site bandwidth consumption.

General architecture

As shown in the figure, the two TPOs are not managed by the same TSS.  The two TSSs do not know each other, we are not talking about TSSs in replication. They are totally independent.

Vocabulary

Here we introduce a few new terms that are used to describe the different elements in these sections.

Vocabulary exposed in TPO static link is still applicable.

Remote TPO  cluster

This is a TPO cluster in the local TSS that is a copy of a TPO cluster belonging to another (remote) TSS.

Remote Master Place

This is a Master Place in the local TSS that is a copy of a Master Place belonging to another (remote) TSS.

Remote Slave Place

This is a slave place that points to a Remote Master Place.

Remote Distributed place

Conceptual object made up of the Remote Master place and all the Remote Slave places which point it.