Test bed requirements Clause Samples
The 'Test bed requirements' clause defines the standards and conditions that a testing environment must meet for evaluating products, systems, or software. It typically outlines the necessary hardware, software, configurations, and operational procedures that must be in place to ensure accurate and reliable testing. For example, it may specify the minimum system specifications, required network connectivity, or data sets to be used during testing. The core function of this clause is to ensure consistency and validity in testing processes, thereby reducing errors and ambiguities that could affect test results.
Test bed requirements. In this use-case, at least two physical servers are required in order to transmit at least one flow which benefits from the optical circuit shortcut. Furthermore, additional hardware resources are required for the control and management planes. Therefore, the test-bed hardware requirements are: • Two devstack compute physical nodes: each with 1CPU/2GB And additional hardware requirements for the control and management planes: • Virtual observer: 1CPU/1GB • Physical observer: 1CPU/2GB • devstack controller: 2CPU/4GB • ODL: 2CPU/4GB The required software include: devstack controller and compute nodes with OVN support, physical and virtual observer (which includes sFlow collectors), and ODL. The benefit of optical bypasses in the data plane is expected to be significant when the Ethernet switches, which directly connect to the optical switch, are highly loaded. To that end, other servers are required in order to generate background traffic to overload the corresponding switches. Alternatively, one can logically slice the physical switch in order to both overload the switches and overcome the lack of TU/e switches resources, as described in the following sub-section.
Test bed requirements. Figure 6 shows the topology of the testbed which is used for the demonstration and experimental evaluation of the VDC use-case. The data plane is composed of 2 ▇▇▇▇▇▇▇ switches and 4 TU/e ToR switches interconnected as shown in the picture with the blue lines. Each ToR switch is interconnected to 2 OpenStack Compute Nodes (i.e. servers), for a total of 8 available compute nodes. 6 of them are interconnected through 10Gbps link, while 2 of them are interconnected through 1Gbps link. These interconnections are represented in the picture through the red lines. At the control and orchestration plane, a server is dedicated to the OpenStack Controller Node while another server runs the OpenDaylight SDN Controller. Each entity is also interconnected through a management and control network which is required for the interaction between OpenStack Controller Node and OpenStack Compute Nodes and for the interaction between OpenDaylight and the network data plane elements, as shown by the dotted back lines. The OpenDayligth controller interacts also with all the Compute Nodes for the configuration of their OVS instances, but these interactions are not represented in the picture for readability reasons.
Test bed requirements. The testbed must be able to support communicating VM instances that run on separate server nodes, supported by a virtual network. There must be sufficient resources to replicate this virtual infrastructure on separate hardware to the initial instances. The following diagram illustrates the test case: