Changes between Initial Version and Version 1 of UMLPEN-QSR-2Q2010


Ignore:
Timestamp:
08/15/10 11:15:22 (14 years ago)
Author:
Yan Luo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UMLPEN-QSR-2Q2010

    v1 v1  
     1[[PageOutline]]
     2
     3= UMLPEN Project Status Report =
     4
     5Period: April 2010 - June 2010
     6
     7== I. Major accomplishments ==
     8
     9=== A. Milestones achieved ===
     10We have worked with the UMass Lowell campus IT, our ISP (UITS from UMass) and BBN on the establishment and testing of an Internet2 L2 VLAN connection from our CANS lab (located in Ball Hall of UMass Lowell campus) to NOX at Boston. As of March 25, the ping test was successfully from Ball Hall to BBN's VLAN test node through NOX.
     11
     12We have implemented a clock synchronization scheme on the network processor based NIC. We tested the scheme through a packet forwarding experiment.
     13
     14We have enhanced virtual router templates and set up scripts.
     15
     16=== B. Deliverables made ===
     17A live L2 VLAN connection from CANS lab at UMass Lowell to NOX at
     18Boston.
     19
     20Source code for the clock synchronization on NIC.
     21
     22Enhanced virtual router templates and setup scripts.
     23
     24
     25== II. Description of work performed during last quarter ==
     26
     27=== A. Activities and findings ===
     28
     29==== 1. Internet2 VLAN connectivity ====
     30
     31During this past quarter, we have been working with UMass Lowell IT
     32network services staff led by Steve Dresche on establishing the VLAN
     33connectivity from Internet2 POP at Boston to the Computer Architecture
     34and Network Systems (CANS) Lab at UMass Lowell (Ball Hall 406). There
     35is only one existing connection to the regular Internet due to
     36historical reasons. Therefore, to have a dedicated new L2 connection
     37to Internet2 is a major undertaking for the university and the PI. We
     38had a series of meetings with the campus network services staff
     39including Steve Drescher (Director of Network Services) and Marcie
     40Byrd (network security specialist). UITS is eventually chosen as the
     41service provider. (UITS is part of University of Massachusetts
     42systemÕs network service provider, and the ISP of our current Internet
     43connection.)
     44
     45The network connection layout of connecting the CANS lab at UMass
     46Lowell to the Internet2 is shown in Figure 1 (below).
     47
     48[[Image(CANSLab-Internet2-VLAN.png)]]
     49
     50We coordinated with UMass Lowell network services, UITS, NOX, and BBN
     51to conduct a VLAN test to verify the connectivity. After some
     52debugging and tuning, we were able to successfully ping from the cisco
     53switch at Ball Hall 4C IDF to the test node at BBN, on March 25, 2010.
     54
     55==== 2. Clock synchronization on network processor based NIC ====
     56
     57''Overview of the Design''
     58
     59We leverage the timestamp registers on the PNIC and periodic message
     60exchange with the host to synchronize with the reference clock on the
     61host. In such a way, the processing cores on the NIC can perform
     62timing related tasks. The programmable cores on PNIC have times- tamp
     63registers which are incremented every 16 cycles (about 11
     64nanoseconds). The timestamp register is use- ful to track the time
     65elapse between events. However, the PNIC lacks an onboard real-time
     66clock. To address this issue, we rely on the system clock of the host
     67to maintain clock synchronization, assuming the host runs a NTP-like
     68protocol to keep itself synchronized with an atomic clock. The clock
     69synchronization operation be- tween the PNIC and host is as
     70follows. First, the host sends a special message with its current
     71clock value to the PNIC through a basic message passing API. Then the
     72PNIC recognizes this special "time"packet and extracts the clock
     73time Th from the packet. Next, a packet processing core of PNIC writes
     74Th to SRAM and reset the timestamp register . Finally, when the time
     75value is needed, the processor reads value t1 from the timestamp
     76register and calculates the current time T as T = Th+t1. The software
     77architecture of the design is shown in Figure 2 (below).
     78
     79[[Image(ClockSynch.png)]]
     80
     81
     82
     83''The Usage''
     84
     85We have developed requires software to be run on both the network
     86processor and the host cpu. We have developed macros in microcode on
     87the network processor that allow access to the timestamp register and
     88perform the necessary unit conversions. Through our APIs, the macros
     89that we've developed can be integrated into any microcode project on
     90the IXP2400 and 2800 network processors. On the host side, the job of
     91initializing the card is performed by a userspace Linux application
     92we've written. The network processor card we're using is the Netronome
     93NFEi8000, and the code we use to communicate with the card depends on
     94Netronome's API's. As long as a Netronome card is in use, our
     95timestamp initialization program will open up a new messaging instance
     96with the card and send the appropriate message to initialize the
     97timestamp registers.
     98 
     99Figure 2. Clock synchronization at NIC.
     100
     101==== 3. Enhancement of PEN virtual router templates and set-up scripts ====
     102
     103The PEN project is comprised of a number of scripts designed to work
     104in conjunction with ProtoGENI clearinghouse. These scripts are
     105designed to handle calls to virtual machines of type pcPEN described
     106in the Emulab database. We have enhanced the scripts for the new
     107ProtoGENI component manager API version 2. The scripts are available
     108in tarball format with detailed information regarding any
     109modifications which may be required to implement a PEN deployment at a
     110new site. Implementation of these scripts results in a physical host
     111capable of providing resource sharing through virtual machines. The
     112VMs provided at UMass Lowell provide support for the Netronome network
     113interface card, which is another feature of the PEN project.
     114
     115==== Plan for Demonstration at GEC7 ====
     116
     117Our GEC7 demo is on the PEN integration and usage within ProtoGENI
     118control framework. The main goal of our demo is to demonstrate the
     119integration of Programmable Edge Node with ProtoGENI control
     120framework, and the use case of the clock synchronization function
     121implemented on the NIC of PEN.
     122
     123=== B. Project participants ===
     124
     125Yan Luo, PI [[BR]]
     126Timothy Ficarra, student [[BR]]
     127Eric Murray, student [[BR]]
     128Craig Masley, student [[BR]]
     129Sanping Li, student [[BR]]
     130Julie Bissell, student [[BR]]
     131Amon Faria, student [[BR]]
     132Guofu Yuan, student
     133
     134=== C. Publications (individual and organizational) ===
     135
     136Yan Luo, Timothy Ficarra, Eric Murray and Chunhui Zhang, The Design,
     137Performance Evaluation and Use Cases of a Virtualized Programmable
     138Edge Node for Network Innovations, Accepted by International Journal
     139of Communication Networks and Distributed Systems, to appear 2010.
     140
     141=== D. Outreach activities ===
     142
     143=== E. Collaborations ===
     144
     145We are working with PrimoGENI team at Florida International University
     146on high performance conduit of simulation and emulation.  We are also
     147planning an end-to-end VLAN test between UML and FIU over the
     148Internet2 or NLR.
     149
     150=== F. Other Contributions ===
     151
     152The PI and five students attended GEC7 and gave a demo of the
     153integration of UMLPEN with ProtoGENI control framework and the clock
     154synchronization scheme implemented on NIC.  Julie Bissell, Amon Faria,
     155Guofu Yuan and Eric Murray attended the GEC7 (including the tutorial
     156sessions and the main conference), with the support from the REU
     157supplemental grant.
     158
     159