Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. C back-end infrastructure
    This allows for the setup of the TCP communication between the Master and Agent nodes (lutf.c).  


    1. Master mode:

      1. Starts a listener thread to listen to Agent connections (lutf_listener.c).

      2. Maintains a list of the Agents
      3. Start up a python interpreter (lutf_python.c).
      4. Provides a library which is SWIG wrapped and callable from python scripts (liblutf_agent.c).

    2. Agent mode:

      1. A thread is started to maintain a heart beat with the master. The master uses the Heart beat to determine the aliveness of the agents (lutf.c).
      2. Start up a python interpreter through Telnet (lutf_python.c).

     

  2. Python Test infrastructure

    1. Infrastructure Level 1:
      A python master script would facilitate the following:
      1. Deploy LUTF on all the Agent nodes and Master node.
      2. Provides a telnet server and client for Master<->Agent communication.
      3. Provides
      an Object Oriented infrastructure which facilitates running python tests scripts on the Agents and collecting results.Provides
      1. a mechanism to query IP addresses and the network interfaces (NIs) on the Agents. This information can further be fetched by the test scripts on demand using an API.
      2. Facilitates running individual python tests scripts on the Agents and collecting results.
      3. Facilitates running the auto-test script which is a test-suite of all the test scripts related to a feature.
      4. Facilitate synchronization between the tests 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.

...