Changes between Version 120 and Version 121 of ORCABEN

04/22/11 15:41:01 (10 years ago)




    v120 v121  
    75 ORCA/BEN Integration[[BR]]
    76 On 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]]
    77 See [  "ORCA/BEN Integration Demo with Stitching of VLANs between BEN and NLR", July 7, 2009] and
    78 [  "ORCA/BEN Integration Demo July 7, 2009, web site][[BR]]
    79 This satisfied milestones 1c, 1d and 1e.[[BR]]
    80 The overall demo connectivity was:[[BR]]
    81 [[Image(orca_ben_demo_connectivity.jpg, 70%)]][[BR]]
    82 The 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]]
    83 [[Image(orcacalls.jpg, 70%)]][[BR]]
    85 NLR VLANs were statically provisioned ahead of time via Sherpa.[[BR]]
    86 BEN VLANs were created dynamically, and included provisioning of Infinera DTN circuits as well as fiber paths using Polatis switches.[[BR]]
    87 BEN node at RENCI used port !TenGig 2/2 and Duke used !TenGig 2/1.[[BR]]
    90 We do not use NDL in the demo to provide the broker or site authority with
    91 resource accounting information – this is a Spiral 2 enhancement. [[BR]]
    93 In this demo the
    94 NDL request describing a desired BEN connection is passed from the Slice Manager
    95 directly to the BEN Transit Authority as part of the redeem procedure. The Slice
    96 Manager first acquires a VLAN tag ticket from the VLAN broker and attaches the
    97 NDL to this ticket before passing it to the BEN Transit Authority. The BEN Transit
    98 Authority then validates the ticket and uses the NDL description of the request to
    99 compute the cross‐layer path across BEN.
    101 In the BEN Transit
    102 Authority, NDL is also used in the form of the
    103 BEN catalogue. This NDL
    104 catalogue 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
    105 compute the cross‐layer path (i.e. which network elements need to be configured)
    106 and provide handler/drivers with necessary configuration information. [[BR]]
    108 Because the contents of the ontology is dynamically updated during the demo, the
    109 BEN Transit Authority path computation algorithm is intelligent enough to take
    110 advantage of the existing links whenever possible (existing links are added to the
    111 ontology as the demo progresses). For example, in the case of two slices, the first
    112 slice across BEN establishes a fiber connection between respective fiber switches
    113 and a DWDM connection between Infinera DTNs. The second slice, aware of the
    114 existence of these links based on the contents of the ontology, does not require any
    115 fiber switch or Infinera configuration steps and simply configures another VLAN in
    116 the 6509 over the existing DWDM connection.