clusterEreviewmeeting: Cluster-E-meeting-notes-29Jun09.txt

Cluster E Meeting Notes
June 29, 2009, 1pm -4pm
GPO: Chip, Aaron, Heidi
Rutgers: Ivan, Ray, Meiling Zhang (NEC)

Goals: review progress, GPO suggested plans, project suggested plans

Agenda:
  - WiMax Project
    - project review & plans
    - GPO milestone review
    - begin roadmap discussion
  - Cognitive radio platform status update
  - GENI goals
  - Cluster E roadmap topics and discussion
  - OMF project review
    - project review & plans
    - GPO milestone review
    - continue roadmap discussion

=======

WiMax project slides - Ivan

System:
  Chassis includes control module and 3 radio "channel" cards
  Outdoor unit with RF subsystem
  PC controller running NEC software and researcher software
    plan is to merge chassis and ODU
  Fully WiMax compliant

1st goal is to demonstrate proof-of-concept: done

Cards:
  Works with Intel PC cards (need to make base station pretend to be
  Sprint) 
    The right way is to create a provisioning server to tell cards to
      accept 'GENI' base stations
  No handsets in US, maybe Korea or China

Installation:
  Single antenna installed at WINLAB tech center 1Q09, 'illegally'
  mounted   on building, needs to be certified by a Professional
  Engineer; could be a cost issue for other deployments 

  Research license requires deployment to be less than 6ft above roof

  FCC license awarded for two sites (rt 1 and campus) quickly (~4wks),
  checked BBN and NSF references
  Constrained to use within 10km

  Actual coverage 5-10km

Controller:

  PC controller, "ASN" - access service network; planning to keep
  NEC-provided controller in place, will expose as many interfaces as
  possible; Rutgers NEC group has source will expose any and all
  capabilities necessary;

  WINLAB writing software for controller handling control plane
  functions, scheduler shaper, and TUN device that handles mapping
  between clients and slices.

  Currently working on virtualization; using a Click router to handle
  virtualization; want to move beyond that to using a custom virtual
  driver that handles mapping of slices to queue performance

  Still moving towards supporting slices.

Spiral 1 Milestones

  Base station API and L2 controls - done

  Virtualization: need to do click-based router, integration &
  evaluation

  Full OMF integration: ...

  Demo will be a little ahead of what was promised

  Slice-based algorithms require some research...

Spiral 2 goals (Ivan)
  - L2 connectivity from Rutgers to PHL PoP
  - Run R6 interface over GENI backbone
  - measurements
  - improve operator mgmt GUI
  - better documentation

GPO: Spiral 1 status (Harry)

  - Should produce a top-down diagram of network integration; problems
    getting from MAGPI to Internet2

  - Collaborations with O&M: no contact yet; project has XML data
    export that is documented; Ivan will send to Heidi/Harry for
    forward to GMOC 

  - Collaborations with security: no progress yet; action to call
    Schwab and explain project approach to access control

  - Outreach: Ivan doing tutorial on FI school, 'huge' summer
    internships 

Cognitive Radio (Ivan)

  Orbit includes without software control plane: USRP, Rice WARP
  Platform, U. Colorado, USRP2, RST SDR system, WINLAB WINC2R system

  Goal: look at fairly large scale deployment of cognitive radios; no
  one is looking at this now and that is where the benefits are; 

  Very active in spectrum allocation issues; seeing more take up these
  issues in industry

  Unique design goal is to have four radio channels that can be
  independently managed, say, 1 for spectrum sending, two
  transmitters, and 1 receiver

  Want to be able to do experiments currently possible with ORBIT
  using more than 50 cognitive radios

  Toyota funding work in spectrum sensing in car-to-car networks; RF
  and AtoD are more important than folks appreciate

GPO's Spiral 2 Goals (Chip)

  Support for continuous experiments

  Identity management - possibly using InCommon; 

    Ivan: should be straightforward to add new identity technologies;

    Ray: easy for different projects to pick different approaches to
    all these topics, GPO should take a stronger hand to get better
    interoperability

  Improved integration: maybe better with NICTA, OneLab

    Ray: wireless is often on the lower side of the integration
    hierarchy, requires someone to take responsibility of the wired
    piece 

  Instrumentation: should have lots of instrumented things and
  beginnings of how to archive and find measurements; need some good
  ideas around this

    Ivan: Driver should be a person who has a keen interest in
    processing accumulated data.  Lots of data being dumped.

    Ray: two types of researchers in GENI: 1 that sees the Internet as
    an uncontrolled system to be observed and the other that is
    interested in controlled and repeatable experiments

GPO: Spiral 2 Roadmap Goals (Harry)


  2.1 a - Experiments & users: now working on coming up on a set of
  tutorials; 

    Suggest organizing something like the EU's 5-day Future Internet
    summer school, pay folks to give tutorials, bring in students,
    have regionally, limit to 200 miles driving with hands-on project
    workshop

  2.1 b - when can WiMax testbed be used?

  2.1 c - Making WiMAX available to GENI users earlier than planned

  2.1 d - Intel WiMAX cards?  Maybe register GENI as a carrier?

  2.1 e - accessing servers?

    Ray: we have a plan for accessing PlanetLab nodes.

  2.2 - Identity management

    Ivan: willing to integrate with any framework's identity
    framework, prefer to pick only one though

  2.3 Interoperability

  2.4 Instrumentation

  2.5 Interoperability

    Already working with Enterprise GENI to let OMF work with a
    OpenFlow controller.

    Ray: suggest creating a shim or pick the best and force the others
    down.  Will reduce the combinatorial challenge.

=========

OMF Project Review & Future Work Plans 
Max Ott

  Reviewing project SoW & achievements (see slides):

  Extend OMF to support multiple heterogeneous testbeds
    - Deployed OMF beyond ORBIT
    - Refactoring components and aligning names with GENI
  Disconnection tolerant framework
  GEC4 Demo: Disconnected demo
  Provide VLAN connectivity via NLR & MAGPI East
  Establish OMF operating environment for testbeds, verify with
    experiments, & demo

OMF Future Work (Max)
  - Federation
  - Resource Description
    - want a formal model that supports multiple levels of abstraction  
  - Everything needs to be observable
    - measurements are crucial
  - Policy & Authorization Framework

Also working on:
  - Onelab2 (EU, FIRE) 
    - includes PlanetLab integration via geni-wrapper
  - 4WARD (EU)
  - NaDa (EU, FIRE)
  - Continuous Bridge Monitoring (Australia)
    - using Motes, UMTS

Federation
  - using a pub-sub, message-oriented architecture based on XMPP 
  - need distributed policies, use of SAML & XACL

Year 2 plans:
  - Extend OMF to support experiments across multiple testbeds
  - Extend OMF to support experiments driven by context, such as
    location
  - Continue working with WiMAX base station
  - Develop a resource description model for our resources (based on
    NDL/OWL/G.800) 

  Re: shibboleth - no pushback from OMF, should work, better if others
  use it too

Controlling mobile experiments with spatial and temporal triggers,
(Marco) 
  - define markers on a Google Earth map, trigger experiment actions
    when triggers are hit
  - e.g., using ultrasonic sensors in cars to sense whether spaces are
    vacant 
  - another project doing speed estimation

Year 2 stretch goals
  - experimenting with user mobility
  - better integration of OpenFlow
  - support teaching labs based on testbed experiments

GPO Spiral 2 Goals (Harry)

  - New experiments: mobile parking sensing network; Chip: would like
    to see outside teams and more diverse infrastructure

Meiling Zhang (NEC) update
  - NEC Japan very interested in GENI
  - Working to make base station software easier to obtain by
    researchers
  - Would like to see more roadmap for Spiral 2
  - Should be able to add virtualization and authentication/AAA in
    WiMAX; if NEC Japan sees more progress, they're more likely to
    increase commitment