<opnfv-tech-discuss@lists.opnfv.org>
Cc: Fatih Degirmenci <fatih.degirme...@ericsson.com>, Jack Morgan
<jack.mor...@intel.com>
Subject: Re: [opnfv-tech-discuss] [VSPERF][NFVBENCH] streamlining the jump host
to data plane wiring
I had an irc chat with Fatih and went through the va
..@huawei.com>, Trevor Cooper
<trevor.coo...@intel.com>, "opnfv-tech-discuss@lists.opnfv.org"
<opnfv-tech-discuss@lists.opnfv.org>
Cc: Fatih Degirmenci <fatih.degirme...@ericsson.com>, Jack Morgan
<jack.mor...@intel.com>
Subject: Re: [opnfv-tech-discuss] [VSPERF][
ursday, September 28, 2017 at 2:16 PM
To: "Cooper, Trevor" <trevor.coo...@intel.com>, "Alec Hothan (ahothan)"
<ahot...@cisco.com>, "opnfv-tech-discuss@lists.opnfv.org"
<opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] [VSPERF][NFVBENC
VSPERF][NFVBENCH] streamlining the jump host
to data plane wiring
Hi Alec
I think that is a good goal. Since VSPERF is stand-alone (not dependent on
OpenStack) there is no need for a Jump Server in the Pharos sense. In our CI
and sandbox environments both hardware and software traffic gene
Hi Trevor and team,
I’d like to get some feedback regarding the way jump hosts are wired to the
data plane as that will have a direct impact on how software based traffic gen
like TRex is configured on the jump host.
My impression is that the wiring of traffic gen devices to the data plane has
