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 generators are directly connected to the DUT. Especially for post-deployment tools like NFVBench I think your idea makes sense as it will help with usability which is key. I also think this is something we can take to Dovetail where we will definitely need a well-defined wiring model for any kind of performance tests. Do you have a proposal in mind?
Thanks /Trevor From: Alec Hothan (ahothan) [mailto:ahot...@cisco.com] Sent: Tuesday, September 26, 2017 11:38 AM To: opnfv-tech-discuss@lists.opnfv.org; Cooper, Trevor <trevor.coo...@intel.com> Cc: MORTON, ALFRED C (AL) <acmor...@att.com> Subject: [VSPERF][NFVBENCH] streamlining the jump host to data plane wiring 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 been ad-hoc per pod until now (meaning they might be different based on the testbed). I have seen OPNFV diagrams where traffic gen devices are wired directly to a compute node and others where they are wired to a switch. If we have a more streamlined way of wiring the jump host to the data plane, it will make the automation run of software based traffic gen tools a lot easier. What I‘d like to suggest is to have a common jump host data plane wiring model for all pods so we can run the same automated scripts on any pod without having to deal with wild variations in wiring and data plane configuration. This does not necessarily mean to setup a complex model, on the contrary, I’d like to propose a simple wiring model that can accommodate most use cases (this will of course not preclude the use of special different wiring for other use cases). Would be interested to know the experience of VSPERF team in that regard and if we can come up with a joint proposal? Thanks Alec
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
