Date

Attendees

Goals

  • Identify what needs to happen in order for the LUTF to integrate in the AT

  • Integrate LUTF in the build system

  • Understand what's involved to integrate the LUTF in the AT
  • Understand what's involved for the AT to deploy the LUTF
  • Understand what's involved for the AT to execute LUTF scripts
  • Understand what's needed to collect the results from the LUTF

  • Understand how we're going to run the MR tests which need multiple interfaces?

Discussion items

Item NotesWho
Create a separate section in Maloo for LUTF resultsLee
Define a YAML file format and then from that we can define how things look in Maloo 
Use Auster as a template for create an LUTF master script 
LUTF to use a similar config file to Auster. But we can create our own environment variables and parameters. We do not have to stick with the exact same variables Auster uses

Charlie

We will capture Console logsLee/Charlie
MR tests will require multiple interfaces. Charlie to talk to Minh or Trent to see what's involved in that 
No reprovisioning of nodes is required. One node will be used to run the LUTF testsCharlie
Look into the possibility of using a flag in the commit to decide to run LNet testsAmir
  

Action items

  • Charlie Olmstead to send Sonia and Amir an example config file
  • Lee Ochoa to send Sonia and Amir an example YAML result file so we can model the LUTF YAML file after it.
  • Charlie Olmstead to talk to Minh or Trent on the possibility of having a node with multiple VMs with 16 interfaces provisioned.

Tasks required for AT integration

Building

  • Build machines need to have SWIG installed
  • Python dev library. 2.7.5
  • Determine if anything else needs to be installed on the build machines.
  • Modify make files to do the following:
    • Run python script which runs swig to generate the glue code
    • Build the binary
    • Package the binary along with the scripts
      • The scripts will need to be checked into git
      • The LUTF code need to be checked into git.
      • Put the make files in Lustre/tests/utf

Master Script:

  • We’ll to create a script which takes the IP addresses of the nodes which will be involved in the test suite
  • This script will do the following:
    • Identify all the information the test suite needs and how we can get it from the AT
    • Add infrastructure in the UTF to pull out information (like NIDs) which the scripts require to execute.
    • Read the config file and get the IP address of the nodes
    • Run the LUTF on each of the nodes in agent mode
    • Run the LUTF on a separate node as master
    • Execute the test suites

YAML config

  • Generate a YAML file for the entire test run
  • The YAML file will need to point to where the results for each test result file is.
  • Pass that YAML file to the AT, which then sends it to Maloo
  • Talk to Lee to get a sample of the YAML file

Test machines

  • Make sure all the python packages that we need are installed.

1 Comment

  1. Lee Ochoa

    Here's a sample results.yml file from a Lustre test run. The import itself is a tarball containing this file along with all log files captured during the test plus a number of other files that are probably not relevant to this effort. Keep in mind this is just a sample of what maloo ingests today but we're in no way forced to follow this format.

    results.yml