Introduction
Objectives
This High Level Design Document describes the current LUTF design, code base, infrastructure requirements for its setup and the new features that can be added on top of the current design.
Reference Documents
Document Link |
---|
LNet Unit Test Infrastructure (LUTF) Requirements |
Document Structure
This document is made up of the following sections:
Design Overview: Describes the existing infrastructure, code base and components of LUTF.
Setup and Usage: Describes how to setup and run LUTF on test nodes.
New Features: Describes the new features to be added to the current design.
LUTF Design Overview
The below diagram shows how LUTF interacts with LNet
Figure 1: System Level Diagram
LUTF Master-Agent
The LUTF is designed with a Master-Agent approach to test LNet. The Master and Agent LUTF instance uses a telnet python module to communicate with each other and more than one Agent can communicate with single Master instance at the same time. The Master instance controls all the Agents connected to it. It controls the execution of the python test scripts to test LNet on Agent instances, collects the results of all the tests run on Agents and write them to a YAML file. It also controls the synchronization mechanism between test-scripts running on different Agents.
SWIG & DLC Library
SWIG is used to wrap the DLC library and make it callable from Python. This allows Python test scripts to call DLC APIs directly to test LNet