Menu

#148 [PATCH] Add 3 Plugins to import and work with Infiniband networks in Tulip

For next release
closed
nobody
PATCH (2)
5
2015-10-21
2015-08-19
SSG
No

NCAR has created a patch for the seamless import of Infiniband network topologies and related data. This patch consists of 3 tulip plugins that utilize libibautils (included in thirdparty). It has been tested against 4.7.0 release and SVN revision 10831. It adds a new linking requirement of Google's RE2 library and is setup to gracefully avoid compilation if RE2 is not provided. It does not require linking against OFED. An example screenshot of an imported fabric is attached. This plugin set has been tested on several 4+k node Infiniband clusters. The tulip plugins are licensed as LGPLv3 to match tulip and libibautils is licensed under a BSD license. The three new plugins are described as follows:

Infiniband Topology Import:
This plugin will import the entire Infiniband fabric based on the output of the 'ibnetdiscover -p' command. Each Infiniband chip is created as a node and each physical cable is created as 2 directional edges.

Infiniband CSV Importer:
This plugin imports CSV files created by the commonly created by Infiniband Monitoring applications that produce aggregated hardware counter values. The generally come in the form of hex encoded GUID, decimal port number and then a value (or set of them). This plugin exists to correctly import or correlate the CSV to the existing IB fabric that has already been loaded into Tulip. The current use of this import to get the traffic measurements for running fabrics.

Infiniband Topology Import Routes:
This plugin imports the file ibdiagnet2.fdbs created by 'ibdiagnet -r' command. Currently, it fills out the ibRoutesOutbound field with number of routes outbound on a given cable (directional edge).

3 Attachments

Discussion

  • SSG

    SSG - 2015-08-25

    Updated Patch: Added minor bug fix to ensure that ibHca is populated on nodes.

     
  • Patrick Mary

    Patrick Mary - 2015-09-30
    • status: open --> closed
    • Attachments has changed:

    Diff:

    --- old
    +++ new
    @@ -1,2 +1,3 @@
     tulip_infinband_example.jpeg (260.5 kB; image/jpeg)
     tulip_infiniband.patch (117.3 kB; text/x-patch)
    +Infiniband_plugins.tar.gz (23.8 kB; application/gzip)
    
     
  • Patrick Mary

    Patrick Mary - 2015-09-30

    Thank you very for you interest in Tulip.

    May I suggest you a less intrusive and more durable way to build your Tulip
    plugins.
    With the files coming from your patch (v2), I have built a tarball
    (infiniband.tar.gz) which can be used to compile then install your Tulip plugins.
    This can be easily achieved using the following steps:

    • first extract the Infiniband plugins source in a directory of your choice
      $ tar zxvf Infiniband.tar.gz
    • change the current directory for the Infiniband build directory of your choice
      $ cd "path to Infiniband build directory"
    • configure the build with cmake, but first ensure the file FindQtX.cmake is present
      in the "path to Tulip install"/share/tulip directory. If not, copy it from the toplevel
      directory of the Tulip source files.
      $ cmake -DCMAKE_MODULE_PATH="path to Tulip install/share/tulip directory;path to Infiniband source directory" -DRE2_INCLUDE_DIR="path to re2 directory" -DRE2_LIBRARY="path to libre2.so" -DCMAKE_BUILD_TYPE=Release "path to Infiniband source directory"
    • compile the plugins
      $ make
    • then install them in the Tulip plugins dedicated directory
      $ make install

    Hope this helps.

     

    Last edit: Patrick Mary 2015-10-22
  • SSG

    SSG - 2015-10-21
     

Log in to post a comment.