harvester / harvester

Open source hyperconverged infrastructure (HCI) software
https://harvesterhci.io/
Apache License 2.0
3.86k stars 326 forks source link

[Doc] Clarify networking hardware requirements #5148

Open tserong opened 9 months ago

tserong commented 9 months ago

Is your doc request related to a problem? Please describe or add related issue ID.

While reviewing https://github.com/harvester/harvester-installer/pull/653, @Vicente-Cheng pointed out:

Just would like to bring some points like the 2.5G NICs. If we have 2 x 2.5G NICs, maybe it could be set up as a production environment in a specific configuration.

Our docs currently just say "1 Gbps Ethernet minimum for testing; 10Gbps Ethernet required for production", but as Vicente suggested, there's more than one way to get nice fast ethernet.

Describe the solution you'd like

We should clarify the network hardware requirements in more detail, and provide some specific example production configurations. I assume the "10Gbps for production requirement" is there as a simple statement because we need to think about handling lots of traffic - traffic to the Harvester GUI, traffic to/from/between VMs, Longhorn storage traffic (...and anything else?). But if you split that up a bit, maybe it would be fine to have - for example - a mixure of 1Gbps and 2.5Gbps NICs bonded for networks for different types of data (see the example configuration in https://docs.harvesterhci.io/v1.2/advanced/storagenetwork#different-physical-interfaces)

Once we figure the details of that out, we'll probably also need to tweak the wording in the network card speed preflight check.

github-actions[bot] commented 7 months ago

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.

tserong commented 7 months ago

Still relevant