Correct TOC in architecture page
This commit is contained in:
parent
6b324029cf
commit
3566e13e79
|
@ -1,23 +1,24 @@
|
||||||
# PVC Cluster Architecture considerations
|
# PVC Cluster Architecture considerations
|
||||||
|
|
||||||
- [Node Specification](#node-specification)
|
- [PVC Cluster Architecture considerations](#pvc-cluster-architecture-considerations)
|
||||||
* [n-1 Redundancy](#n-1-redundancy)
|
* [Node Specification](#node-specification)
|
||||||
* [CPU](#cpu)
|
- [n-1 Redundancy](#n-1-redundancy)
|
||||||
* [Memory](#memory)
|
- [CPU](#cpu)
|
||||||
* [Disk](#disk)
|
- [Memory](#memory)
|
||||||
* [Network](#network)
|
- [Disk](#disk)
|
||||||
- [PVC architecture](#pvc-architecture)
|
- [Network](#network)
|
||||||
* [Operating System](#operating-system)
|
* [PVC architecture](#pvc-architecture)
|
||||||
* [Ceph Storage Layout](#ceph-storage-layout)
|
- [Operating System](#operating-system)
|
||||||
* [Networks](#networks)
|
- [Ceph Storage Layout](#ceph-storage-layout)
|
||||||
- [System Networks](#system-networks)
|
- [Networks](#networks)
|
||||||
- [Client Networks](#client-networks)
|
+ [System Networks](#system-networks)
|
||||||
- [Advanced Layouts](#advanced-layouts)
|
+ [Client Networks](#client-networks)
|
||||||
* [Coordinators versus Hypervisors](#coordinators-versus-hypervisors)
|
* [Advanced Layouts](#advanced-layouts)
|
||||||
* [Georedundancy](#georedundancy)
|
- [Coordinators versus Hypervisors](#coordinators-versus-hypervisors)
|
||||||
- [Example System Diagrams](#example-system-diagrams)
|
- [Georedundancy](#georedundancy)
|
||||||
* [Small 3-node cluster](#small-3-node-cluster)
|
* [Example System Diagrams](#example-system-diagrams)
|
||||||
* [Large 8-node cluster](#large-8-node-cluster)
|
- [Small 3-node cluster](#small-3-node-cluster)
|
||||||
|
- [Large 8-node cluster](#large-8-node-cluster)
|
||||||
|
|
||||||
This document contains considerations the administrator should make when preparing for and building a PVC cluster. It is important that prospective PVC administrators read this document *thoroughly* before deploying a cluster to ensure they understand the requirements, caveats, and important details about how PVC operates.
|
This document contains considerations the administrator should make when preparing for and building a PVC cluster. It is important that prospective PVC administrators read this document *thoroughly* before deploying a cluster to ensure they understand the requirements, caveats, and important details about how PVC operates.
|
||||||
|
|
||||||
|
@ -291,12 +292,6 @@ Generally speaking, SR-IOV connections are not recommended unless there is a goo
|
||||||
|
|
||||||
Future PVC versions may support other client network types, such as direct-routing between VMs.
|
Future PVC versions may support other client network types, such as direct-routing between VMs.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
- [Advanced Layouts](#advanced-layouts)
|
|
||||||
* [Coordinators versus Hypervisors](#coordinators-versus-hypervisors)
|
|
||||||
* [Georedundancy](#georedundancy)
|
|
||||||
|
|
||||||
## Advanced Layouts
|
## Advanced Layouts
|
||||||
|
|
||||||
### Coordinators versus Hypervisors
|
### Coordinators versus Hypervisors
|
||||||
|
|
Loading…
Reference in New Issue