Changes between Initial Version and Version 1 of ShadowNet-Report-July-2012


Ignore:
Timestamp:
08/14/12 17:19:09 (12 years ago)
Author:
griff@netlab.uky.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ShadowNet-Report-July-2012

    v1 v1  
     1[[PageOutline]]
     2
     3= GENI Shadownet Project Status Report =
     4
     5Period: Post GEC 14 Report
     6
     7== I. Major accomplishments ==
     8
     9The following highlights our accomplishments
     10during the last reporting period.
     11
     12=== A. Milestones achieved ===
     13 * Milestone S4.c) Interoperate with the perfSONAR model. We completed the integration of our instrumentation tools (INSTOOLS) with the perfSONAR model supported in the LAMP/periscope project.
     14
     15 * Milestone S4.d) Support user access to the Juniper resources and archive services to the GMOC. We continued to support user access to the Juniper resources, and updated and improved our support for sharing of monitoring information with the GMOC through INSTOOLS.
     16
     17
     18=== B. Deliverables made ===
     19
     20 * The Shadownet CM code now supports the AM API and can partially support stitching for Juniper logical routers with the nodes from the Utah aggregate.
     21
     22 * We updated and enhanced the INSTOOLS code that provides sharing of measurement data with the GMOC archival service.
     23
     24 * We developed a prototype of the GENI One-Stop portal to provide access to all aspects of GENI.
     25
     26== II. Description of work performed during last quarter ==
     27
     28The following provides a description of the progress made during the last
     29reporting period.
     30
     31
     32=== A. Activities and findings ===
     33
     34Our activities this last reporting period have been primarily focused on
     35adding support for the AM API, incorporating early stitching efforts into
     36Shadownet, developing a one-stop portal prototype, and interoperating with
     37the LAMP/Periscope project as well as the GMOC archival services.
     38
     39To provide AM API support, we again started with the latest version of the
     40reference CM which was rewritten to support the latest version of the RSPEC
     41(versions 2 and 3) and added support for the AM API.  Using this as our
     42starting point, we re-wrote the code for the Shadownet component manager to
     43work with these new APIs and RSPECS.  As a result, the Shadownet CM can now
     44accept credentials from other control frameworks and fully supports the AM
     45API calls.
     46
     47In the demos of previous GECs, we created a topology with Juniper routers and
     48PCs from Utah and Kentucky aggregates. However, the links between Juniper
     49routers and PCs had to be added manually because of the lack of stitching
     50support. Working with the ProtoGENI group, we added code that enables us to
     51provide stitching  support for Utah aggregate nodes that have VLAN
     52connectivity to the ProtoGENI backbone switches co-located with logical
     53Juniper routers from the ShadowNet aggregate. In our most recent GEC 14 demo,
     54we created a topology that included both PCs from the Utah aggregate and
     55logical Juniper routers from Shadownet.  To accomplish this, we first set up
     56an experiment with PCs from the Utah aggregate and let these PCs connect to
     57special devices to create the VLAN connectivity. We then created a topology
     58consisting of logical routers and let each logical router connect to the
     59respective VLAN using the VLAN number obtained in the previous step.  VLANs
     60were automatically created between the PCs and the logical routers because of
     61the newly added stitching support.
     62
     63A relatively new focus this past reporting period has been on designing a new
     64way for users to interact with their GENI experiments.  In particular, we
     65started to build a prototype of what we call the GENI one-stop portal (GENI
     66OS Portal). The goal of the GENI OS Portal is to provide users with a single
     67unified interface to the tools in GENI.  It is built around the concept of a
     68slice and the topology represented by a slice -- i.e. the key abstraction
     69that all GENI tools share in common.  The portal can accommodate
     70various GENI tools as plugins to the portal.  Each plugin extends the set of
     71operations that can be carried out on slice resources. As plugins are
     72enabled, the set of operations allowed on the resources continues to
     73expand. All (plugin) operations are accessed via the portal's common
     74topology-based interfaces, regardless of the type of operation being
     75performed. As a result, the portal is able to provide access to all aspects
     76of GENI including slice creation, access to slice resources (e.g., ssh), file
     77management, experiment execution, instrumentation, measurement and
     78monitoring, archiving of experiment data, etc, all via tool-specific
     79plugins.
     80
     81While our INSTOOLs code has supported archival service to the GMOC for quite
     82some time, recent changes to the APIs, and in particular the RSPECs, required
     83us to update and enhance our code needed to archive and share measurement
     84data with the GMOC services. The archival service is a "live" service in the
     85sense that data is collected and streamed live to the GMOC archives.
     86The collected measurement data is first transformed into a GMOC-specific
     87format and then sent to the GMOC site for storage. The user specifies when to
     88start collecting data, and the measurement data is then continuously
     89transformed and sent to the GMOC server. The user can stop the process at
     90any time.
     91
     92Another major focus this past reporting period has been on integration with
     93the LAMP/Periscope project, incorporating the perfSONAR model used in
     94LAMP/Periscope into the INSTOOLS system.  A big part of the work involved
     95understanding the overlap between the two ways of doing instrumentation and
     96measurement and finding ways to combine the two, eliminating redundancy when
     97possible.  In many ways the two systems (INSTOOLs and LAMP) compliment one
     98another which simplified the integration, with INSTOOLS providing dynamic
     99instrumenation of a slice (a feature not in LAMP) and LAMP providing active
     100measurements (a feature not directly supported in INSTOOLs).  We have
     101combined the two and made them interoperate through the INSTOOLs portal which
     102now provides access to both active and passive data measurements.  This was
     103demonstrated at the GEC 14 conference as part of the GEMINI project which
     104combines the two into a single instrumentation and measurement
     105infrastructure.
     106
     107We continue to manage and operate the four Juniper routers located in Salt
     108Lake City, Kansas City, Washington DC, and Atlanta. We have been using the
     109routers in our testing and evaluations of the Shadownet CM, especially the AM
     110API and stitching support.  We continue to support and make available the
     111Shadownet resources for use by GENI users, complete with graphical user
     112interface support via FLACK and the INSTOOLs portal.
     113
     114=== B. Project participants ===
     115
     116The following individuals are involved with the project in one way or another:
     117 * Jim Griffioen - Project PI (Kentucky)
     118 * Zongming Fei - Project Co-PI (Kentucky)
     119 * Kobus van der Merwe - Project Co-PI (AT\&T)
     120 * Eric Boyd - Subcontract Lead (Internet2)
     121 * Brian Cashman - Network Planning Manager (Internet2)
     122 * Lowell Pike - Network administrator (Kentucky)
     123 * Hussamuddin Nasir - Technician/Programmer (Kentucky)
     124 * Charles Carpenter - Researcher/Programmer (Kentucky)
     125 * Emmanouil Mavrogiorgis - Research Staff (AT\&T)
     126
     127=== C. Publications (individual and organizational) ===
     128
     129 * James Griffioen, Zongming Fei, Hussamuddin Nasir, Xiongqi Wu, Jeremy Reed, Charles Carpenter, "The Design of an Instrumentation System for Federated and Virtualized Network Testbeds", Proc. of the First IEEE Workshop on Algorithms and Operating Procedures of Federated Virtualized Networks (FEDNET), Maui, Hawaii, April 2012.
     130
     131 * James Griffioen, Zongming Fei, Hussanmuddin Nasir, Xiongqi Wu, Jeremy Reed, Charles Carpenter, "Teaching with the Emerging GENI Network", Proc. of the 2012 International Conference on Frontiers in Education: Computer Science and Computer Engineering (FECS), Las Vegas, NV, July 2012.
     132
     133=== D. Outreach activities ===
     134
     135 * Zongming Fei gave a talk on "Teaching with the Emerging GENI Network" at the 2012 International Conference on Frontiers in Education: Computer Science and Computer Engineering in Las Vegas, NV on July 19, 2012.
     136
     137 * Zongming Fei and Hussanmuddin Nasir gave a tutorial at the GENI experimenter summer camp at Rochester Institute of Technology in May 2012.
     138
     139 * We gave a Shadownet Demo at GEC 14 that demonstrated the ability to stitch Shadownet resources into other aggregates, and showed an early prototype of the one-stop portal service.
     140
     141=== E. Collaborations ===
     142
     143Most of our collaborations continue to be with the Shadownet team.  In
     144particular, it involves participants from Kentucky,
     145AT<pre>&</pre>T, and Internet2, but we have also had several conversations
     146with our ProtoGENI and perfSONAR colleagues.
     147
     148
     149=== F. Other Contributions ===
     150