parallelvirtualcluster/docs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Compare commits

base: parallelvirtualcluster:ac7b25dac154c1919dfc9ed07bffe74bd643937c
Branches Tags
parallelvirtualcluster:master
..
compare: parallelvirtualcluster:836a61708efd376577481459a0ee3d36b069bcf2
Branches Tags
parallelvirtualcluster:master

2 Commits
ac7b25dac1 ... 836a61708e

Author SHA1 Message Date
Joshua M. Boniface
836a61708e Try adjusting width randomly 2023-09-16 23:52:09 -04:00
Joshua M. Boniface
d3de778ca3 Remove unneeded column 2023-09-16 23:50:23 -04:00
2 changed files with 11 additions and 10 deletions
Expand all files Collapse all files

20
docs/deployment/fencing.md
View File

@ -78,17 +78,17 @@ The conditions in which a node can be successfully fenced are limited, and thus,
The following table covers some common scenarios, and whether fencing and automatic recovery can be exepected to occur.
| Situation | Fence Possible? | Autorecovery Possible? | Notes |
| Situation | Fence & Autorecovery? | Notes |
| --------- | --------------- | ---------------------- | ----- |
| Node OS lockup (load, OOM, etc.) | ✅ | ✅ | A key design situation for the fencing system |
| Node OS kernel panic | ✅ | ✅ | A key design situation for the fencing system |
| Node primary network cut | ✅ | ✅ | Only affecting primary links, not IPMI (see below); a key design situation |
| Node full network cut | ❌ | ❌ | All links are down, e.g. full network failure including IPMI |
| Node power loss | ❌ | ❌ | Impossible to determine if this is a transient network cut or actual power loss without IPMI |
| Node hardware failure (CPU, memory, etc.) | ✅ | ✅ | IPMI interface should remain up in these scenarios; a key design situation |
| Node hardware failure (motherboard) | ✅ | ✅ | If IPMI is **online** after failure |
| Node hardware failure (motherboard) | ❌ | ❌ | If IPMI is **offline** after failure |
| Node hardware failure (full chassis) | ❌ | ❌ | Full power loss, etc. if IPMI is offline |
| Node OS lockup (load, OOM, etc.) ✅ | A key design situation for the fencing system |
| Node OS kernel panic | ✅ | A key design situation for the fencing system |
| Node primary network cut | ✅ | Only affecting primary links, not IPMI (see below); a key design situation |
| Node full network cut | ❌ | All links are down, e.g. full network failure including IPMI |
| Node power loss | ❌ | Impossible to determine if this is a transient network cut or actual power loss without IPMI |
| Node hardware failure (CPU, memory, etc.) | ✅ | IPMI interface should remain up in these scenarios; a key design situation |
| Node hardware failure (motherboard) | ✅ | If IPMI is **online** after failure |
| Node hardware failure (motherboard) | ❌ | If IPMI is **offline** after failure |
| Node hardware failure (full chassis) | ❌ | Full power loss, etc. if IPMI is offline |
Care should be taken to understand these scenarios and which situations can be recovered from automatically, and which require manual human intervention to confirm the situation ("is the node actually physically off?") and manual recovery.

1
mkdocs.yml
View File

@ -4,6 +4,7 @@ theme:
name: readthedocs
titles_only: yes
logo: "images/pvc_logo_black_transparent.png"
width: "100%"
markdown_extensions:
- toc:
permalink: yes