Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Remove env variable setup - should be handled by control plane now

...

  • DAOS can be installed using DAOS RPM package, also can be built locally following the instructions in the quickstart.md file.
  • Tests are in $PREFIX/lib/daos/TESTING/ftest, in RPM env, $PREFIX=/usr; in local built env, $PREFIX=myrepo/install.  At the top level is launch.py which simplifies running DAOS with avocado.  Sub-directories contain categories of tests e.g. the pool directory contains tests relating to pools.
  • A given group of tests is implemented as a combination of a python file (.py) and a yaml file (.yaml).  So for example in the pool directory there is a SimpleCreateDeleteTest.py and SimplecreateDeleteTest.yaml.  The python contains the test code that drives the test, and the yaml file contains the test parameters.  A single function in the python file can execute a large number of test cases because its run for different combinations of inputs as found in the yaml file.
  • Server will be launched with Control Plane API so not need to pass any environment arguments, But client side Control plane still to be developed so this Two parameter to be set prior running any Avocado test via launch script.
    • export CRT_PHY_ADDR_STR="ofi+sockets"
      export OFI_INTERFACE=ib0

  • For tests that run on multiple servers, these two files need to be accessible by remote server nodes:
    • daos_avocado_test.yaml
    • daos_server.attach_info_tmp

...