Hi Alec and Francois, I have been doing a few upgrades of TRex for NFVbench, and I’ve included a few notes here that might be helpful. I can add that I tried this with TRex v2.50.
- First build TRex “as usual” - ./b configure - ./b build - Make sure the trex-core directory is available in the container - Info about shared directory can be found through ‘docker inspect nfvbench’ - (In container) Move old TRex to backup directory - docker exec nfvbench mv /opt/trex/v2.32 /opt/backup_v2.32 - (In container) Create symlink to new TRex - docker exec nfvbench ln -s /tmp/nfvbench/trex-core/scripts /opt/trex/v2.32 - (In container) Copy pyzmq from original TRex into new - docker exec nfvbench cp -r /opt/backup_v2.32/external_libs/pyzmq-14.5.0 /opt/trex/v2.32/external_libs/ - (In container) Update import of STLServiceARP in trex.py - File: nfvbench/nfvbench/traffic_gen/trex.py - “from trex_stl_lib.services.trex_stl_service_arp import STLServiceARP” Similar to what Francois mentions, I have also tried updating the python libraries, which indeed requires changing STLServiceARP to ServiceARP (and I think also fixing a typo with STLVmFlowVarRepeatableRandom). All-in-all I think your upgrade is fine. I haven’t seen any problems from upgrading this way. As Alec also mentions, the plan is to upgrade TRex in a (near) future release of NFVbench. Best Regards, Michael Pedersen From: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discuss@lists.opnfv.org] On Behalf Of Alec via Lists.Opnfv.Org Sent: Monday, February 25, 2019 11:29 PM To: François-Régis MENGUY <francoisregis.men...@orange.com> Cc: opnfv-tech-discuss@lists.opnfv.org Subject: Re: [opnfv-tech-discuss] #nfvbench - Request TRex upgrade for using it with virtio multiple queues Hi Francois, Upgrading TRex to a newer version has been done about a month ago in a private workspace but not upstreamed yet as it was using a private Trex branch provided by the Trex team. It was not the latest as of today but definitely a version that had the reorg of the Trex libraries. I don’t think there is anything else to do than what you have done already to make it work. Feel free to submit a gerrit for the Trex upgrade if you can and I’ll get it tested on my side. Thanks Alec From: <opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>> on behalf of François-Régis MENGUY <francoisregis.men...@orange.com<mailto:francoisregis.men...@orange.com>> Date: Monday, February 25, 2019 at 9:07 AM To: "Alec Hothan (ahothan)" <ahot...@cisco.com<mailto:ahot...@cisco.com>> Cc: "opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>" <opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>> Subject: [opnfv-tech-discuss] #nfvbench - Request TRex upgrade for using it with virtio multiple queues Hello Alec, In some contexts, particularly when Baremetal, SRIOV or PCI pass-through are not available on the infrastructure to be tested, it would be useful to be able to perform throughput measurements directly from a VM through its virtio-net vif , in the same way it is done by Yardstick. However, when deploying NFVBench in a qemu VM with a multiple queues virtio vif, it is not possible to take advantage of TRex multiple cores capacity with the current v2.32 TRex version used my NFVBench. Indeed, TRex v2.32 considers virtio-net as a single queue driver and replies “the number of cores should be 1 when the driver support only one tx queue and one rx queue. Please use -c 1”. From the version v2.49, TRex is able to take advantage multiple queues virtio vif, and thus, it would be interesting to upgrade NFVBench with a more recent TRex version. On my side I tried to upgrade locally to v2.53 but since v2.43 STL lib is merged with ASTF so it has an impact on the way NFVBench docker is deployed (path to lib is changed so copy to Pyton2.7 path needs to be changed and trex_stl_lib is also change to trex/stl). I managed to have an NFVBench instance working with this latest version but I’m not sure all is OK, especially with ARP since STLServiceARP moved in a common package and was renamed ServiceARP. On your side, do you think it will be a big impact to upgrade to the latest version of TRex ? Is it possible to do it on your side or explain me how you would manage such upgrade ? Best regards, FR Menguy _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22872): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22872 Mute This Topic: https://lists.opnfv.org/mt/30040225/21656 Mute #nfvbench: https://lists.opnfv.org/mk?hashtag=nfvbench&subid=2783016 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
