Skip to content

Meetings

Jump to bottom Edit New page
Daniel Baluta edited this page May 29, 2014 · 23 revisions

May 29, 2014

  • make chapter titles more specific
  • comparison between real hardware and virtualization
  • time to install
  • money
  • space
  • 1.1.3 - mininet cannot test kernel modules.
  • 1.2.1 Introdu the Virtual Lab (vLab)
  • avoid personal phrases - vLab is my solution -> vLab is a solution.
  • does it make any sense to mention PacketTracer?
  • try to find some images to illustrate the text.
  • Chapter 6 : Rename to Conclusion and Future Work.

May 14, 2014

  • HACKATHON date May 18, EG106b
  • running commands from vlab prompt should resolve host parameters.
  • configure interfaces (host and switches) via ssh.
  • move functionality from vLab into Host class.
  • Objective: create a simple setup with 2 host + 1 switch. Ping should work.
  • Consistency check between topo.json and vm.json --topo, --vm
    • add option to specify configs from command line parameters
  • Make a draft for Table of Contents [Next Thursday, May 22]

May 8, 2014

  • HACKATHON date May 10, EG106b.
  • add ssh feature
    • AlexC link for paramiko ssh client [DONE]
    • extend cmd prompt to use ssh (e.g should be able to run: h1 ping h2) [PARTIALLY DONE]
  • implement test network
    • add "physical" devices from qemu monitor (read topo.json and send commands to hosts). [DONE]
    • configure interfaces via ssh. [PARTIALLY DONE]
    • configure switches on host - brctl [PARTIALLY DONE]
  • Objective: create a simple setup with 2 host + 1 switch. Ping should work.
  • TBD: create tests for vLab.
  • Add script in init to notify host when the guest is fully booted up [DONE]
    • echo "Booted $hostname" | nc <host_ip> <host_port>

April 23, 2014

  • mininet like command prompt to send commands to VMs (including starting an xterm on socat)
    • extend python cmd class.
  • configure test network
    • configure 'hardware' devices for VMs (qemu monitor).
    • configure guest interfaces [use hardcoded values for ifaces names, e.g eth1, eth2
    • make a simple setup with 2 host + 1 switch.
  • make TODO list for HACKHATHON
    • date for H. 3 or 10 May.
  • 15 May, start writing Documentation.

April 9, 2014

  • analyze tools needed from busybox (ssh client/server - dropbear, strace, ip) [done]
  • add mgmt interface at startup time (init script + qemu starting script) [DONE]
    • mgmgt interface configuration is read from vm.json
  • mininet like command prompt to send commands to VMs (including starting an xterm on socat)
  • ideas on how to configure mgmmt and test interfaces.
    • generic entry in vm.json for configuring interfaces
  • next meeting April, 23
  • first HACKATHON on May, 3.

April 2, 2014

  • implement simple test (in example/ dir) [DONE]
  • create VmConfigLoader instance and start VMs from config using VLab class
  • implement VLab class (vlab/vlab.py) [DONE]
  • this is the main class for our project
  • reads configuration with vmConfigLoader (buildFromVMConfig)
  • implement start - stargs all objects read from vmConfigLoader
  • tool for serial connection on all started vms
    • mininet like command prompt to send commands to VMs (including starting an xterm on socat)

March 19, 2014

  • add VMConfig
  • load .json config files
  • implement some sort of getNextConfig() iterator
  • implement simple main function that"
    • reads config
    • creates VMHandler
    • creates Node
    • starts topology

March 12, 2014

  • start designing testcases [TODO daniel create wiki page]
  • write Documentation about general architecture [Daniel]
  • start Implementation [DONE]
  • write skeleton files for main objects (Node, Switch)
  • bin/vlab - main executable file
  • vlab/*.py - source files for py vlab package
  • examples/ - sample config files for basic configuration (2 nodes + switch)
  • how do we know test interface name in qemu host?
  • choose some hardcoded solution (e.g consider that interface name is eth0,1, etc). Possible fix would be to use virtual interfaces on top of physical interface in host (MACVTAP).

March 5, 2014

  • vm.json - define hosts (fs, devices, kernel) [Costash] [DONE]
  • interface types (important data like MAC interface address], file system shares
  • use monitor interface
  • draft for init script run when starting the guest system
  • start designing testcases [TODO daniel create wiki page]
  • write Documentation about general architecture [Daniel]

February 26, 2014

  • UML diagram with main classes for vLab [Costash] Started - [see https://github.com/IxLabs/vlab/wiki/Doc]
    • methods and data
  • define configuration files
    • topo.json - network topology (we have a draft for this) [DONE]
    • vm.json - define hosts (fs, devices, kernel) [Costash] [skipped for next week]
  • write Documentation about general architecture [Daniel] [skipped for next week]
  • manual commands to start 2 hosts + 1 bridge [Costash] [DONE] ** done commands for hosts

February 19, 2014

  • json vs xml (choose one as default + make a translator)
  • we choose json as default description language
  • TODO:
  • make a draft for json file format [Costash]
  • we should use mininet API (classes, etc)
  • script to configure 2 hosts + 1 switch + links [Costash]
  • how should we do reviews (Daniel)
  • Visual Network Description - http://www.ramonfontes.com/vnd/
  • MiniEdit - http://gregorygee.wordpress.com/category/miniedit/

November 18, 2013 [kickoff meeting]

  • add Costash to vLab project [done]
  • do we need a mailing list? [talk to RD][DB]
  • analyze ways of defining configuration file (xml, json) [Costash]
  • replace screen with tmux? Checkout features for both [DB, Costash, AC]
  • if needed, schedule another meeting until EOY [DB]
Add a custom footer
Add a custom sidebar
Clone this wiki locally