| Charles Chan | 4d5ee19 | 2019-09-09 23:08:36 -0700 | [diff] [blame] | 1 | Supported Hardware |
| 2 | ================== |
| Zack Williams | d63d35b | 2020-06-23 14:12:46 -0700 | [diff] [blame] | 3 | |
| 4 | Following is a list of hardware that people from the ONF community have tested |
| 5 | over time in lab trials. |
| Charles Chan | 4d5ee19 | 2019-09-09 23:08:36 -0700 | [diff] [blame] | 6 | |
| 7 | Supported Switches |
| 8 | ------------------ |
| 9 | |
| 10 | 1G/10G models (with 40G uplinks) |
| 11 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| Zack Williams | d63d35b | 2020-06-23 14:12:46 -0700 | [diff] [blame] | 12 | |
| 13 | - OCP Accepted™ EdgeCore AS5712-54X |
| 14 | - OCP Accepted™ EdgeCore AS5812-54X |
| 15 | - QCT QuantaMesh T3048-LY8 |
| 16 | - Delta AG7648 |
| 17 | - Inventec D6254 (verified by Inventec) |
| Charles Chan | 4d5ee19 | 2019-09-09 23:08:36 -0700 | [diff] [blame] | 18 | |
| 19 | 25G models (with 100G uplinks) |
| 20 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| Zack Williams | d63d35b | 2020-06-23 14:12:46 -0700 | [diff] [blame] | 21 | |
| 22 | - QuantaMesh BMS T7032-IX1/IX1B (with 25G breakout cable) |
| 23 | - Inventec D7054Q28B (verified by Inventec) |
| Charles Chan | 4d5ee19 | 2019-09-09 23:08:36 -0700 | [diff] [blame] | 24 | |
| 25 | 40G models |
| 26 | ^^^^^^^^^^ |
| Zack Williams | d63d35b | 2020-06-23 14:12:46 -0700 | [diff] [blame] | 27 | |
| 28 | - OCP Accepted™ EdgeCore AS6712-32X |
| Charles Chan | 4d5ee19 | 2019-09-09 23:08:36 -0700 | [diff] [blame] | 29 | |
| 30 | 100G models |
| 31 | ^^^^^^^^^^^ |
| Zack Williams | d63d35b | 2020-06-23 14:12:46 -0700 | [diff] [blame] | 32 | |
| 33 | - OCP Accepted™ EdgeCore AS7712-32X |
| 34 | - QCT QuantaMesh BMS T7032-IX1/IX1B |
| 35 | - OCP Accepted™ Inventec D7032Q28B (verified by Inventec) |
| Charles Chan | 4d5ee19 | 2019-09-09 23:08:36 -0700 | [diff] [blame] | 36 | |
| 37 | Commercially supported models |
| 38 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| Zack Williams | d63d35b | 2020-06-23 14:12:46 -0700 | [diff] [blame] | 39 | |
| 40 | Models listed here are not supported by ONF community. You should contact |
| 41 | switch vendor for commercial support. |
| 42 | |
| 43 | - OCP Accepted™ EdgeCore AS5912-54X |
| Charles Chan | 4d5ee19 | 2019-09-09 23:08:36 -0700 | [diff] [blame] | 44 | |
| 45 | |
| 46 | Supported Servers |
| 47 | ----------------- |
| Zack Williams | d63d35b | 2020-06-23 14:12:46 -0700 | [diff] [blame] | 48 | ONOS can be run on any x86 servers, with the following notes on CPU and memory |
| 49 | allocation **per ONOS instance**: |
| Charles Chan | 4d5ee19 | 2019-09-09 23:08:36 -0700 | [diff] [blame] | 50 | |
| Zack Williams | d63d35b | 2020-06-23 14:12:46 -0700 | [diff] [blame] | 51 | - CPU (Recommended: **32 cores**) |
| 52 | There are not much requirement on CPU. |
| Charles Chan | 4d5ee19 | 2019-09-09 23:08:36 -0700 | [diff] [blame] | 53 | |
| Zack Williams | d63d35b | 2020-06-23 14:12:46 -0700 | [diff] [blame] | 54 | In practice, we avoid running other CPU intensive processes/containers/VMs |
| 55 | on the same physical machine where ONOS runs. |
| 56 | |
| 57 | - Memory (Recommended: **65G RAM**) |
| 58 | The memory requirement highly depends on the deployment scale. |
| 59 | In general, we suggest that each ONOS instance should get **at least 16G RAM**. |
| 60 | |
| 61 | For production deployment at scale, we will definitely need not only more |
| 62 | memory but also some fine tuning on JVM garbage collection mechanism. |