CSIT/AArch64

From fd.io
< CSIT
Revision as of 09:15, 11 January 2018 by GabrielGanne (Talk | contribs)

Jump to: navigation, search

Recent Patches

add new topology parameter: arch Merged 2018-01-10 https://gerrit.fd.io/r/#/c/9474/
update nodes dependency Merged 2018-01-02 https://gerrit.fd.io/r/#/c/9584/
update vagrant to use ubuntu 16.04 images https://gerrit.fd.io/r/#/c/8295/
warn against virtualenv --system-site-packages Merged 2017-12-20 https://gerrit.fd.io/r/#/c/9428/

TEST for 2-nodes topology

(gg) based on my tests, in order to reproduce issues more easily across the team.

  • set up 2 aarch64 VMs (TG + DUT)
    • give them 3 interfaces
    • one for management, the other two down for the test
    • compile igb_uio (see known issue #1) and load it
  • write topology file with `arch: aarch64`
    • fill pci_address, and mac_address according to your setup
  • create virtualenv following csit README
    • virtualenv env
    • source env/bin/activate
    • pip install -r requirements.txt
    • export PATH with vpp_api_test, and PYTHONPATH

cmdline to run functional tests only with debug logs. You need the "__init__.robot" present in the folder you give to pybot.

pybot --debugfile /tmp/debugfile --exitonerror -L TRACE -v TOPOLOGY_PATH:topologies/enabled/topology.yaml tests/vpp/func/

TODO

  • identify ARM64 hardware to replicate CSIT repo
  • make Jira EPIC for CSIT func
  • make Jira EPIC for CSIT performance


  • disk-image-builder scripts
  • write a bootstrap-* script for aarch64
  • add VPP_REPO_URL* VPP_STABLE_VER* files ... (could be any public server for now)

known issues

  1. dpdk does not compiles igb_uio on aarch64 (it seems to require a kernel patch introduced in kernel 4.12: f719582435afe9c7985206e42d804ea6aa315d33). it has been re-enabled in dpdk v17.11 (f1810113590373b157ebba555d6b51f38c8ca10f)