From ee16ddbfcfbb9973608499eeda15502bfd367c48 Mon Sep 17 00:00:00 2001 From: Paul Wright Date: Wed, 16 Oct 2024 16:06:38 +0100 Subject: [PATCH 1/4] update link-cost --- cli/link-cost.adoc | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/cli/link-cost.adoc b/cli/link-cost.adoc index 24e0a0f..4b85f1a 100644 --- a/cli/link-cost.adoc +++ b/cli/link-cost.adoc @@ -1,3 +1,4 @@ +include::../partials/attributes.adoc[] // Type: procedure [id="specifying-link-cost"] == Specifying link cost @@ -79,4 +80,15 @@ You can view the traffic levels corresponding to each client. NOTE: If there are multiple clients on different sites, filter the view to each client to determine the effect of cost on traffic. For example, in a two site network linked with a high cost with servers and clients on both sites, you can see that a client is served by the local servers while a local server is available. --- \ No newline at end of file +-- + +A common use-case for specifying cost is to provide automatic failover. +As described above you might have two instances of a server with a high cost for the link to the backup server: + +* local server (effective cost = 0) +* remote server (link cost = 999) + +In this case, connections are always routed to the local server and fails over to the remote server when the local server becomes available. + +Some complex applications, especially stateful ones, require "orchestrated" failover, meaning you need control over the order in which traffic is redirected from one set of workloads to another. +{skupper-name} does not offer this type of orchestration, you need to implement that orchestration for those applications. \ No newline at end of file From e6620ef5ff78422eadbed53ed4298dd6c172b8f1 Mon Sep 17 00:00:00 2001 From: Paul Wright <5154224+pwright@users.noreply.github.com> Date: Wed, 23 Oct 2024 18:13:16 +0100 Subject: [PATCH 2/4] Update link-cost.adoc --- cli/link-cost.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/cli/link-cost.adoc b/cli/link-cost.adoc index 4b85f1a..282a439 100644 --- a/cli/link-cost.adoc +++ b/cli/link-cost.adoc @@ -83,12 +83,12 @@ For example, in a two site network linked with a high cost with servers and clie -- A common use-case for specifying cost is to provide automatic failover. -As described above you might have two instances of a server with a high cost for the link to the backup server: +As described in xref:deploying-a-single-logical-service-across-many-sites-for-failover[], you might have two instances of a server with a high cost for the link to the backup server: * local server (effective cost = 0) -* remote server (link cost = 999) +* remote server (link cost = 99999) In this case, connections are always routed to the local server and fails over to the remote server when the local server becomes available. Some complex applications, especially stateful ones, require "orchestrated" failover, meaning you need control over the order in which traffic is redirected from one set of workloads to another. -{skupper-name} does not offer this type of orchestration, you need to implement that orchestration for those applications. \ No newline at end of file +{skupper-name} does not offer this type of orchestration, you need to implement that orchestration for those applications. From 7bcb704f70c2e91e5c4c25fa547510a35d91c512 Mon Sep 17 00:00:00 2001 From: Paul Wright Date: Tue, 29 Oct 2024 17:41:27 +0000 Subject: [PATCH 3/4] fix link --- cli/link-cost.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cli/link-cost.adoc b/cli/link-cost.adoc index 282a439..2b8ed0a 100644 --- a/cli/link-cost.adoc +++ b/cli/link-cost.adoc @@ -83,7 +83,7 @@ For example, in a two site network linked with a high cost with servers and clie -- A common use-case for specifying cost is to provide automatic failover. -As described in xref:deploying-a-single-logical-service-across-many-sites-for-failover[], you might have two instances of a server with a high cost for the link to the backup server: +As described in xref:deploying-single-logical-service[], you might have two instances of a server with a high cost for the link to the backup server: * local server (effective cost = 0) * remote server (link cost = 99999) From 930b51c18ce55da809fd9da3765caedae3ef963f Mon Sep 17 00:00:00 2001 From: Paul Wright Date: Mon, 13 Jan 2025 11:30:39 +0000 Subject: [PATCH 4/4] update --- cli/link-cost.adoc | 2 +- partials/attributes.adoc | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/cli/link-cost.adoc b/cli/link-cost.adoc index 2b8ed0a..dfcc7c5 100644 --- a/cli/link-cost.adoc +++ b/cli/link-cost.adoc @@ -83,7 +83,7 @@ For example, in a two site network linked with a high cost with servers and clie -- A common use-case for specifying cost is to provide automatic failover. -As described in xref:deploying-single-logical-service[], you might have two instances of a server with a high cost for the link to the backup server: +As described in {single-link}, you might have two instances of a server with a high cost for the link to the backup server: * local server (effective cost = 0) * remote server (link cost = 99999) diff --git a/partials/attributes.adoc b/partials/attributes.adoc index fd9a998..049f6c7 100644 --- a/partials/attributes.adoc +++ b/partials/attributes.adoc @@ -16,6 +16,7 @@ :kube-ref-link: https://skupper.io/docs/kubernetes-reference/index.html[Skupper Kubernetes CLI reference] :pod-ref-link: https://skupper.io/docs/kubernetes-reference/index.html[Skupper Podman CLI reference] :cost-link: ../cli/index.html#specifying-link-cost[Specifying link cost] +:single-link: ../cli/index.html#deploying-single-logical-service[Deploying a single logical service] :skupper-operator-name: Skupper operator