Skip to content

Commit

Permalink
Fix currently broken links to toolstack/features: HA, snapshots
Browse files Browse the repository at this point in the history
Signed-off-by: Bernhard Kaindl <[email protected]>
  • Loading branch information
bernhardkaindl committed Jan 27, 2025
1 parent 458b138 commit 7010a98
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions doc/content/design/multiple-cluster-managers.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ revision_history:
Introduction
------------

Xapi currently uses a cluster manager called [xhad](../../features/HA/HA.html). Sometimes other software comes with its own built-in way of managing clusters, which would clash with xhad (example: xhad could choose to fence node 'a' while the other system could fence node 'b' resulting in a total failure). To integrate xapi with this other software we have 2 choices:
Xapi currently uses a cluster manager called [xhad](../toolstack/features/HA/index). Sometimes other software comes with its own built-in way of managing clusters, which would clash with xhad (example: xhad could choose to fence node 'a' while the other system could fence node 'b' resulting in a total failure). To integrate xapi with this other software we have 2 choices:

1. modify the other software to take membership information from xapi; or
2. modify xapi to take membership information from this other software.
Expand Down Expand Up @@ -70,4 +70,4 @@ The `xapi.conf` file will have a new field: `cluster-stack-root` which will have

In `Pool.enable_ha` with `cluster_stack="foo"` we will verify that the subdirectory `<cluster-stack-root>/foo` exists. If it does not exist, then the call will fail with `UNKNOWN_CLUSTER_STACK`.

Alternative cluster stacks will need to conform to the exact same interface as [xhad](../../features/HA/HA.html).
Alternative cluster stacks will need to conform to the exact same interface as [xhad](../toolstack/features/HA).
2 changes: 1 addition & 1 deletion doc/content/design/ocfs2/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -461,7 +461,7 @@ Summary of the impact on the admin

OCFS2 is fundamentally a different type of storage to all existing storage
types supported by xapi. OCFS2 relies upon O2CB, which provides
[Host-level High Availability](../../../features/HA/HA.html). All HA implementations
[Host-level High Availability](../../toolstack/features/HA/index). All HA implementations
(including O2CB and `xhad`) impose restrictions on the server admin to
prevent unnecessary host "fencing" (i.e. crashing). Once we have OCFS2 as
a feature, we will have to live with these restrictions which previously only
Expand Down
2 changes: 1 addition & 1 deletion doc/content/xen-api/topics/snapshots.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ They can be used for:
- experiments (take snapshot, try something, revert back again)
- golden images (install OS, get it just right, clone it 1000s of times)

Read more about [Snapshots: the High-Level Feature](../features/snapshots/snapshots.html).
Read more about [Snapshots: the High-Level Feature](../../toolstack/features/snapshots/index).

Taking a VDI snapshot
=====================
Expand Down

0 comments on commit 7010a98

Please sign in to comment.