[Fuego] Fw: New to Fuego

[Joe]

   <!--#yiv4227272492 _filtered #yiv4227272492 {font-family:"Cambria Math";panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv4227272492 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv4227272492 #yiv4227272492 p.yiv4227272492MsoNormal, #yiv4227272492 li.yiv4227272492MsoNormal, #yiv4227272492 div.yiv4227272492MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", sans-serif;}#yiv4227272492 a:link, #yiv4227272492 span.yiv4227272492MsoHyperlink {color:#0563C1;text-decoration:underline;}#yiv4227272492 a:visited, #yiv4227272492 span.yiv4227272492MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;}#yiv4227272492 span.yiv4227272492EmailStyle17 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv4227272492 .yiv4227272492MsoChpDefault {font-family:"Calibri", sans-serif;} _filtered #yiv4227272492 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv4227272492 div.yiv4227272492WordSection1 {}-->
Hi all,
 
  
 
Just happened across this project yesterday with Tim’s presentation on youtube.  Interesting and far better than Phoronix IMHO.  I downloaded the container and have it running on a Windows laptop, with a VM of Centos using Docker and the Fuego container.  Some minor hiccups getting it going but I managed to fumble my way to the end after some minor edits to the Dockerfile.  So all in all that was pretty easy.  At the point now of adding a board and a custom test.  The “board” was going to be a VM with Centos, but the laptop is short on RAM, so I will have to see what I can do about another laptop.
 
  
 
A common use case we typically have is more than one board. We deal with DoD rugged systems that may have one or more high speed ADC, multiple GPUs and VPX SBCs. In some cases these systems have had mixed OS (Vxworks on a semi custom IO and Linux on the SBCs) Typically we rolled our own framework, tests, also we have board level temp and voltage/current monitoring over backplane I2C which one board can poke at all the other boards (and the power supply / fan cage) in the chassis.  There are other constrains to some environmental qualification testing as well but these are and can continue to be dealt with at the test level.
 
  
 
I have been involved with system testing for a “few years”. OK I will date myself, a few decades.  As Tim mentioned in his presentation many companies tended to roll our own frameworks, porting older tests to newer hardware if needed.  Frameworks were lightweight, using a command/status layer, some direct socket/verb level APIs, others using MPI, others still using peer to peer PCIe.  We tended to stay with “run everything serially first (benchmarks and test) then run concurrently (mainly just the tests)” and just wait for something bad to happen while doing shake/bake/EMI testing. All the while having a monitor “test” checking temps, volts and current around the various system components.
 
  
 
As Fuego seems board based and not “systems” based is there some trouble on the horizon for this use case?  I gather when one uses Fuego to run iperf or other network tests, the test is run between the host and the single board target? Not Nway between many targets?  I am sure there is  workaround I could figure out.
 
  
 
On another front, as Fuego appears more Linux related, are there any plans for other embedded OS’s? Some that come to mind are QNX, VxWorks, LynxOS, GreenHills and ur… umm Windows..did I really say that….
 
  
 
Thanks for reading and thanks in advance for responding. Cheers!
 
  
 
--
 
Joe Rolfe
 
  
   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20180512/101c8706/attachment.html>