Skip to content

Commit 1cea2bb

Browse files
committed
Best Practices for storage network configuration
1 parent 84aad9b commit 1cea2bb

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

docs/advanced/storagenetwork.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -384,3 +384,19 @@ The storage network may malfunction because of issues with the external network,
384384
### Start VM Manually
385385

386386
After verifying the configuration, users could start VM manually on demand.
387+
388+
### Best Practices
389+
390+
- When allocating IP Range for storage network using the below formula,
391+
Required Number of IPs = (Number of Nodes * 2) + (Number of Disks * 2) + Number of Images to Download/Upload
392+
Consider allocating sufficient ip addresses keeping in mind the future needs of the cluster.
393+
When new nodes are added to the cluster or more disks added to the node after storage network configuration and if required number of IPs becomes
394+
greater than allocated, then it results in Longhorn pods (`instance-manager`, and `backing-image-manager`) not in running state.
395+
396+
Storage network has to be reconfigured with sufficient IP Range to solve this.
397+
398+
- Users are allowed to configure storage networks using mgmt cluster, but it is not the best or recommended configuration as same physical nics are
399+
shared by both storage network and other traffic over mgmt network.
400+
401+
- Consider using storage network on mgmt cluster only if you could segregate traffic using vlans effectively on same physical link or the cluster has some NIC
402+
constraints.

0 commit comments

Comments
 (0)