[RI2 Ch03] Update Lab Requirements (#2413)

* [RI2 Ch04] Update Content

* [RI2 Ch03] Update Lab Requirements

doc/ref_impl/cntt-ri2/chapters/chapter03.md

@@ -53,14 +53,6 @@ For all community-focused activities, access to the respective lab infrastructur
 <a name="3.2.2"></a>
 ### 3.2.2 Connectivity
 
-The network fabric in the lab must support the following networks:
-
-* Out-of-Band hardware management
-* Admin (host OS access)
-* Public (external / Internet facing network)
-* Private (cluster internal network)
-* Storage
-
 The network topology should provide at least 2 networks with preallocated IP addressing schemes for the out-of-band management network and the Public network. The Public network must be able to reach / access the public Internet, preferably directly or via an enterprise proxy. IPv4 as well as IPv6 addresses must be available. At least 1 network interface must be capable of performing PXE boot and that network must be available to both the jump / test host and each physical or virtual server.
 
 The network fabric shall comprise redundant layer 2 connectivity between hosts. The switching hardware shall support VLANs for separating networks as well as supporting line speeds corresponding to the speeds of the NICs listed below.
@@ -72,22 +64,26 @@ The network fabric shall comprise redundant layer 2 connectivity between hosts.
 The requirements on infrastructure hardware used to deploy and run the RI2 are as follows:
 
 1. One (1) physical or virtual server dedicated as a jump / test host
-1. Six (6) physical or virtual servers, serving as either master (controller) or compute/worker nodes
+1. Five (5) physical or virtual servers, serving as either master (controller) or compute/worker nodes
 
 The jump / test host allows to install and manage the operation of the RI2. For example, the host can be used to execute the installer software to deploy and configure the RI2 on the other physical or virtual servers. Once installed, the host may be used to run test tools or it may be used to generate test traffic intended for performance measurements. To support the latter, the server provided for the jump / test host shall meet similar hardware requirements as the master (controller) / compute hosts. If the jump host is used only for deployment or execution of functional tests after deployment, a VM with the resources as outlined below is sufficient.
 
 Each server shall meet the following minimum specifications:
 
 * CPU
-  *  2x x86_64 CPU sockets, providing 20 cores each, 40 simultaneous multi-threads (SMT), at 2.2 GHz
+  *  2x 20 core x86_64 CPUs, for a total of 40 cores (80+ threads with SMT)
 * Memory
   * 256 GB RAM
 * Storage
-  * 1.0 TB SSD via SATA 6 Gbps
-* Network Interfaces
-  * 4x 10 Gbps Ethernet Ports
-  * Out-of-band Management Port (physical server only)
-
+  * 1.0 TB SSD
+  * Additional bulk storage can be added as HDD
+* Network
+  * 25Gbps+ network solution
+  * Additional NICs/ports (10Gbps+) can be present
+  * Ideally at least 2 ports per socket (NUMA)
+  * NICs must be SR-IOV capable
+
+Note that the minimum specifications listed above map to the recommended specifications. Additional devices, such as FPGA, GPU, QAT, etc., may also be added depending on the configuration. For more details on the requirements per infrastructure profile, please refer to [RA2 Chapter 2](../../../ref_arch/kubernetes/chapters/chapter02.md).
 
 A virtual jump / test host can be a VM with the following specifications: