Protocol Testbed Development

From Wiki

Jump to: navigation, search

This page includes the development status of Protocol Testbed. The project includes mainly three components.


Contents

News

  • 2006.11.07 Backend Scripts have been released
  • 2006.12.08 Initial version of Web-based front-end is done (see some of screenshots in below)
    • Kernel image downloading
    • Source-level Kernel compilation (including automatic patching)
    • Filesystem support (we can make a target filesystem on the fly) (FreeBSD and Linux)
    • Boot the target systems using POE (Power Over Ethernet)
    • Ethernet booting with Linux and FreeBSD kernel image and filesystem
    • SQL database integration
  • When we will integrate Web-based front-end and backend scripts?

Architecture

  • Network Boot Server - deploys a kernel and filesystem to a system on the fly.
  • Backend scripts
  • Topology generator

Features

  • Network Boot Server
    • Linux and FreeBSD kernel and filesystem loading using PXE
    • Remote power on using PoE (Power over Ethernet)
    • Uploading custom kernels, filesystems and patches
    • MySQL database integrated
    • Web-based GUI by using PHP
  • Backend Scripts
    • Tuning scripts
    • Background traffic generators
    • Graphing scripts
    • Toy utilities

Download

  • Backend Scripts download!
  • Web-base GUI (We will release when we finish integrating backend scripts with Web-based GUI.)

Testbed Configuration

  • left: sender1 and sender2 (Linux highspeed flow senders ), sender3 and sender4 (Linux background flow senders)
  • middle: dummy1 (FreeBSD dummynet router 1), dummy2 (FreeBSD dummynet router 2)
  • right: receiver1 and receiver2 (Linux highspeed flow receivers), receiver3 and receiver4 (Linux background flow receivers)
  • one control machine (Linux is fine)

How to install Backend Scripts

  • You need a dedicated control machine (which can run ssh command to all machines in the testbed)
  • Install any linux OSes on all senders and receivers
  • Install FreeBSD 5.2.1 or 5.3 at dummynet router 1 and 2. See Dummynet Installation for installing dummynet router 1 and 2.
  • Generate a ssh-key and distribute them to all machines, so that the control machine can access all the machines using ssh without password.
  • Modify "testbed.conf"
  • See the detailed commands in the "plan_all.sample" and make your own "plan_all" file and run it.

Web-based Front-end Screen Shots

Image:01.clients.gif Image:02.kernels.gif Image:03.filesystems.gif Image:04.users.gif Image:05.upload_kernel.gif Image:06.upload_kernel_source.gif Image:07.compile_kernel.gif Image:08.upload_fs.gif

Links


Maintained by Sangtae Ha (sangtae.ha AT gmail DOT com)

Personal tools