Changes between Initial Version and Version 1 of ORCAAUG

10/23/09 12:15:25 (13 years ago)




    v1 v1  
     3== Project Number ==
     7== Project Title ==
     9Deploying a Vertically Integrated GENI “Island”:  A Prototype GENI Control Plane (ORCA) for a Metro-Scale Optical Testbed (BEN) [[BR]]
     10a.k.a.  ORCA/BEN or ORCABEN
     13=== Technical Contacts ===
     15Principal Investigator:   
     16Ilia Baldine (RENCI)[[BR]]
     18Co-Principal Investigator:   
     19Jeff Chase
     21 (Duke)[[BR]]
     22BEN Operations Staff and IT Contact:  Chris Heermann (RENCI) [[BR]]
     23Software Staff:  Yufeng Xin  (RENCI) (NDL support)  [[BR]]
     24Software Staff:  Daniel Evans  (RENCI) (network element driver development) [[BR]]
     25Software Staff:  Aydan Yumerefendi (RENCI) (core software development) [[BR]]
     26Students: Varun Marupadi (Duke), Matt Sayler (Duke)
     28[[Image(ORCA-Team-small.jpg, 70%)]] [[BR]]
     30ORCA/BEN team is pictured from left to right:  Dan Evans (RENCI), Yufeng Xin (RENCI), Ilia Baldine (PI at RENCI), Aydan Yumerefendi (RENCI), and Chris Heermann (RECNI).  Jeff Chase (Co-PI at Duke), Varun Marupadi (Duke) and Matt Sayler (Duke) are not pictured.
     34=== Participating Organizations ===
     36[  New Internet Computing Lab (NICL)][[BR]]
     37[  Open Resource Control Architecture (ORCA)][[BR]]
     38[  Shirako][[BR]]
     39[  BEN:  Breakable Experimental Network][[BR]]
     40[  Renaissance Computing Insititute (RENCI),  Chapel Hill, NC][[BR]]
     41[  Duke University,  Durham, NC][[BR]]
     42[  Infinera Corporation,  Sunnyvale, CA][[BR]]
     45=== GPO Liason System Engineer ===
     47Harry Mussman
     50== Scope ==
     52The scope of work on this project is to extend ORCA (a candidate GENI control framework) to include the optical resources available in [[ BEN]] metro optical testbed.  Also, to make a reference implementation of ORCA available to additional GENI prototypes and assist, with limited support, in the integration of ORCA into select wireless/sensor prototypes.  The team will operate a clearinghouse for the various testbeds under the ORCA control framework.  Also, connect with the NLR backbone network !FrameNet service to facilitate end-to-end VLAN's connections into BEN.  Finally, make the integrated (VLAN connections and control framework) ORCA/BEN infrastructure available to external researchers by the end of Year-1.
     54=== Current Capabilities ===
     56ORCA (Cluster D) Clearinghouse[[BR]]
     57ORCA clearinghouse equipment location:  RENCI, 100 Europa Drive, Chapel Hill, NC. [[BR]]
     58ORCA clearinghouse will use RENCI public IP addresses.[[BR]]
     59The ORCA clearinghouse at RENCI is now operational. [[BR]]
     60Go to [  Cluster D Clearinghouse at RENCI] ;  get login from [[BR]]
     61These Cluster D projects have installed (moved) their broker to the clearinghouse:  BEN(?);  DOME;  ViSE;  Kansei
     64ORCA/BEN Integration[[BR]]
     65On July 7, 2009, the ORCA/BEN team demonstrated to the GENI Project office the ORCA capability to create slices of substrate that include several transit providers, i.e. BEN and NLR.[[BR]]
     66See [  "ORCA/BEN Integration Demo with Stitching of VLANs between BEN and NLR", July 7, 2009] and
     67[  "ORCA/BEN Integration Demo July 7, 2009, web site][[BR]]
     68This satisfied milestones 1c, 1d and 1e.[[BR]]
     69The overall demo connectivity was:[[BR]]
     70[[Image(orca_ben_demo_connectivity.jpg, 70%)]][[BR]]
     71The demo used ORCA calls to create several VMs at Duke, RENCI and UNC-CH BEN PoPs and then linked them together with VLANs via NLR and BEN:[[BR]]
     72[[Image(orcacalls.jpg, 70%)]][[BR]]
     74NLR VLANs were statically provisioned ahead of time via Sherpa.[[BR]]
     75BEN VLANs were created dynamically, and included provisioning of Infinera DTN circuits as well as fiber paths using Polatis switches.[[BR]]
     76BEN node at RENCI used port !TenGig 2/2 and Duke used !TenGig 2/1.[[BR]]
     79We do not use NDL in the demo to provide the broker or site authority with
     80resource accounting information – this is a Spiral 2 enhancement. [[BR]]
     82In this demo the
     83NDL request describing a desired BEN connection is passed from the Slice Manager
     84directly to the BEN Transit Authority as part of the redeem procedure. The Slice
     85Manager first acquires a VLAN tag ticket from the VLAN broker and attaches the
     86NDL to this ticket before passing it to the BEN Transit Authority. The BEN Transit
     87Authority then validates the ticket and uses the NDL description of the request to
     88compute the cross‐layer path across BEN.
     90In the BEN Transit
     91Authority, NDL is also used in the form of the
     92BEN catalogue. This NDL
     93catalogue is pre‐loaded into the Jena ontology engine at the start of the demo.  The BEN Transit Authority relies on the contents of the catalogue to
     94compute the cross‐layer path (i.e. which network elements need to be configured)
     95and provide handler/drivers with necessary configuration information. [[BR]]
     97Because the contents of the ontology is dynamically updated during the demo, the
     98BEN Transit Authority path computation algorithm is intelligent enough to take
     99advantage of the existing links whenever possible (existing links are added to the
     100ontology as the demo progresses). For example, in the case of two slices, the first
     101slice across BEN establishes a fiber connection between respective fiber switches
     102and a DWDM connection between Infinera DTNs. The second slice, aware of the
     103existence of these links based on the contents of the ontology, does not require any
     104fiber switch or Infinera configuration steps and simply configures another VLAN in
     105the 6509 over the existing DWDM connection.
     108=== Milestones ===
     110[[MilestoneDate(ORCABEN: 1a Extend ORCA as a GENI control framework)]] 
     111[  status]
     113[[MilestoneDate(ORCABEN: 1b Make an early reference implementation of ORCA available)]] 
     114[  status]
     116[[MilestoneDate(ORCABEN: 1c Integration of NDL or other topology description mechanism)]] 
     117[  status]
     119[[MilestoneDate(ORCABEN: 1d Integrate ORCA with BEN including slivering of Infinera DTNs)]] 
     120[  status]
     122[[MilestoneDate(ORCABEN: 1e Complete end-to-end VLAN connections between BEN and NLR)]]
     123[  status]
     125[[MilestoneDate(ORCABEN: 1f All ORCA assigned prototypes integrated into ORCA clearinghouse)]]
     126[  status]
     128[[MilestoneDate(ORCABEN: 1g Make a working and tested prototype of BEN and GENI available for limited external research)]] 
     130[[MilestoneDate(ORCABEN: 1h Delivery of preliminary control framework design documentation)]] 
     135[[MilestoneDate(ORCABEN: S2.a Rel 2.1_1 ORCA code to projects)]] 
     137[[MilestoneDate(ORCABEN: S2.b Rel 2.2_1 ORCA code to projects)]] 
     139[[MilestoneDate(ORCABEN: S2.c Rel 2.3_1 ORCA code to projects)]] 
     141[[MilestoneDate(ORCABEN: S2.d Rel 2.x_1 ORCA code, docs to GPO)]] 
     143[[MilestoneDate(ORCABEN: S2.e Operate, extend clearinghouse)]] 
     145[[MilestoneDate(ORCABEN: S2.f GMOC access to clearinghouse)]] 
     147[[MilestoneDate(ORCABEN: S2.g Cluster plan for VLANs between testbeds)]] 
     149[[MilestoneDate(ORCABEN: S2.h BEN testbed access by GENI users)]] 
     151[[MilestoneDate(ORCABEN: S2.i BEN testbed access from remote sites)]] 
     153[[MilestoneDate(ORCABEN: S2.j VLANs from BEN to backbone)]] 
     155[[MilestoneDate(ORCABEN: S2.k Integration of GUSH)]] 
     157[[MilestoneDate(ORCABEN: S2.l Experiments BEN and other testbeds)]] 
     159[[MilestoneDate(ORCABEN: S2.m POC to GENI response team)]] 
     161[[MilestoneDate(ORCABEN: S2.n POC to GENI security team)]] 
     163[[MilestoneDate(ORCABEN: S2.o Contribution to GENI outreach)]] 
     167== Project Technical Documents ==
     170[  GENI - ORCA,  web site maintained by RENCI, incouding ORCA code and ticketing system][[BR]]
     171(Note:  GENI - ORCA website certificate is signed by the RENCI Root CA, and not by a commercial authority.  It will typically raise an exception or warning in your browser.
     172You can add [  RENCI Root CA ]as a trusted authority in your browser .
     173Alternatively, you can create an exception for the site to accept its certificate as is.
     174Or, you may be able to continue to the website by accepting the warning.)[[BR]]
     175[  "Sharing Networked Resources with Brokered Leases",  2006][[BR]]
     176[  "ORCA Technical Note:  Guests and Guest Controllers",  2008][[BR]]
     177[  "BEN GENI Substrate Description",  2008][[BR]]
     178[  ORCA-fest May 28, 2009, web site][[BR]]
     179[  "Experimenting with Ontologies for Multi-Layer Network Slicing",  June 26, 2009][[BR]]
     180[  "ORCA/BEN Integration Demo with Stitching of VLANs between BEN and NLR", July 7, 2009][[BR]]
     181[  "ORCA/BEN Integration Demo", July 7, 2009, web site][[BR]]
     183=== Quarterly Status Reports ===
     185[  "ORCABEN:  4Q08 Status Report"][[BR]]
     186[  "ORCABEN:  1Q09 Status Report"][[BR]]
     187[  "ORCABEN:  2Q09 Status Report"][[BR]]
     188[   "ORCABEN:  3Q09 Status Report"][[BR]]
     191=== Spiral 2 Connectivity ===
     194BEN equipment is located per the [  "BEN GENI Substrate Description",  2008] drawing.[[BR]] 
     195External connectivity to BEN done per Fig 3 of [  "BEN GENI Substrate Description",  2008] drawing.[[BR]]
     196BEN node at RENCI has 10 GigE connection to NLR !FrameNet on port !TenGig 2/2. [[BR]]
     197BEN has provisioned VLAN IDs 861-870 for use with !FrameNet. [[BR]]
     198BEN node at RENCI uses RENCI production router for connections to commodity Internet, Internet2 and NLR (via NCREN). [[BR]]
     199BEN IP addresses should be added to this page. [[BR]]
     200BEN Operations Staff and IT Contact:  Chris Heermann  RENCI [[BR]]
     203=== Related Projects ===
     205[  New Internet Computing Lab (NICL)][[BR]]
     206[  Open Resource Control Architecture (ORCA)][[BR]]
     207[  Shirako][[BR]]
     208[  BEN:  Breakable Experimental Network][[BR]]