Changes between Initial Version and Version 1 of PersistentTestHostRequirments


Ignore:
Timestamp:
08/06/10 13:46:59 (10 years ago)
Author:
jwilliams@bbn.com
Comment:

initial cut of Persitant test host requirments.

Legend:

Unmodified
Added
Removed
Modified
  • PersistentTestHostRequirments

    v1 v1  
     1Hi Tim,
     2
     3 == hardware ==
     4 * access to the "commodity internet" would be very helpful for package installs and out-of-band monitoring, though not required.
     5 * VMs are OK, but let us know. Some VM's require their interface to have promiscuous mode enabled to allow for tcpdump'ing layer2 frames such as OpenFlow Discovery (LLDP) frames.
     6 * NIC interface into VLAN 3712. BBN and other campuses have used multiple Interfaces (physical interfaces, virtual interfaces, or a VM with vnics)  to support testing all Backbone connections from a single host.
     7 * no other firm requirement, even "spare" laptops has even been used.
     8
     9
     10== OS ==
     11 * Some variant of Linux - so far centOs and ubuntu have been used
     12
     13
     14== Software (we'll install with sudo access) ==
     15 * iperf
     16 * ganglia client
     17 * VLC
     18 * arping
     19 * tcpdump
     20
     21
     22== Ports ==
     23We can work with non-standard ports if you have any preferences.
     24 * iperf - port 5001  (Clemson preferred using 5001 for TCP and 5002 for UDP)
     25 * VLC - port 1234
     26 * SSH/scp - port 22
     27
     28
     29== Storage ==
     30 * ~ 750MB hardrive space (mostly for storing a test video file for streaming)
     31
     32
     33== OpenFlow ==
     34The expectation is that this host helps monitor & test the backbone connections . This host isn't required to be behind an OpenFlow switch but it's OK if it is. The expectation is that this host's traffic isn't actively controlled via OpenFlow.
     35
     36
     37== Reach-ability, bandwidth usage and testing ==
     38This host provides an easy sanity check for ensuring that the backbone connection is working, so the host should be "up" whenever possible.  Sustained traffic will also be minimal, usually very low periodicity ganglia messages  and the occasional ping.  Iperf and VLC will be used for testing and metrics, though we'll let you know when we plan on testing with these tools with any substantial Bandwidth (We've typically called this 50MBps, is this acceptable for you?).  Well share results with you.