68 | | ORCA (Cluster D) Clearinghouse[[BR]] |
69 | | ORCA clearinghouse equipment location: RENCI, 100 Europa Drive, Chapel Hill, NC. [[BR]] |
70 | | ORCA clearinghouse will use RENCI public IP addresses.[[BR]] |
71 | | The ORCA clearinghouse at RENCI is now operational. [[BR]] |
72 | | Go to [http://geni.renci.org:8080/orca/ Cluster D Clearinghouse at RENCI] ; get login from ibaldin@renci.org [[BR]] |
73 | | These Cluster D projects have installed (moved) their broker to the clearinghouse: BEN(?); DOME; ViSE; Kansei |
74 | | |
75 | | |
76 | | ORCA/BEN Integration[[BR]] |
77 | | 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]] |
78 | | See [http://groups.geni.net/geni/attachment/wiki/ORCABEN/071509c%20%20ORCA_BEN%20demo.pdf "ORCA/BEN Integration Demo with Stitching of VLANs between BEN and NLR", July 7, 2009] and |
79 | | [https://geni-orca.renci.org/trac/wiki/events/orca-nlr-july-2009 "ORCA/BEN Integration Demo July 7, 2009, web site][[BR]] |
80 | | This satisfied milestones 1c, 1d and 1e.[[BR]] |
81 | | The overall demo connectivity was:[[BR]] |
82 | | [[Image(orca_ben_demo_connectivity.jpg, 70%)]][[BR]] |
83 | | 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]] |
84 | | [[Image(orcacalls.jpg, 70%)]][[BR]] |
85 | | |
86 | | NLR VLANs were statically provisioned ahead of time via Sherpa.[[BR]] |
87 | | BEN VLANs were created dynamically, and included provisioning of Infinera DTN circuits as well as fiber paths using Polatis switches.[[BR]] |
88 | | BEN node at RENCI used port !TenGig 2/2 and Duke used !TenGig 2/1.[[BR]] |
89 | | |
90 | | |
91 | | We do not use NDL in the demo to provide the broker or site authority with |
92 | | resource accounting information – this is a Spiral 2 enhancement. [[BR]] |
93 | | |
94 | | In this demo the |
95 | | NDL request describing a desired BEN connection is passed from the Slice Manager |
96 | | directly to the BEN Transit Authority as part of the redeem procedure. The Slice |
97 | | Manager first acquires a VLAN tag ticket from the VLAN broker and attaches the |
98 | | NDL to this ticket before passing it to the BEN Transit Authority. The BEN Transit |
99 | | Authority then validates the ticket and uses the NDL description of the request to |
100 | | compute the cross‐layer path across BEN. |
101 | | |
102 | | In the BEN Transit |
103 | | Authority, NDL is also used in the form of the |
104 | | BEN catalogue. This NDL |
105 | | 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 |
106 | | compute the cross‐layer path (i.e. which network elements need to be configured) |
107 | | and provide handler/drivers with necessary configuration information. [[BR]] |
108 | | |
109 | | Because the contents of the ontology is dynamically updated during the demo, the |
110 | | BEN Transit Authority path computation algorithm is intelligent enough to take |
111 | | advantage of the existing links whenever possible (existing links are added to the |
112 | | ontology as the demo progresses). For example, in the case of two slices, the first |
113 | | slice across BEN establishes a fiber connection between respective fiber switches |
114 | | and a DWDM connection between Infinera DTNs. The second slice, aware of the |
115 | | existence of these links based on the contents of the ontology, does not require any |
116 | | fiber switch or Infinera configuration steps and simply configures another VLAN in |
117 | | the 6509 over the existing DWDM connection. |
118 | | |
| 68 | See the [wiki:ORCABEN ORCA/BEN project] |
121 | | |
122 | | [[MilestoneDate(ORCABEN: 1a Extend ORCA as a GENI control framework)]] |
123 | | [http://groups.geni.net/geni/ticket/96 status] |
124 | | [[BR]] |
125 | | [[MilestoneDate(ORCABEN: 1b Make an early reference implementation of ORCA available)]] |
126 | | [http://groups.geni.net/geni/ticket/97 status] |
127 | | [[BR]] |
128 | | [[MilestoneDate(ORCABEN: 1c Integration of NDL or other topology description mechanism)]] |
129 | | [http://groups.geni.net/geni/ticket/98 status] |
130 | | [[BR]] |
131 | | [[MilestoneDate(ORCABEN: 1d Integrate ORCA with BEN including slivering of Infinera DTNs)]] |
132 | | [http://groups.geni.net/geni/ticket/99 status] |
133 | | [[BR]] |
134 | | [[MilestoneDate(ORCABEN: 1e Complete end-to-end VLAN connections between BEN and NLR)]] |
135 | | [http://groups.geni.net/geni/ticket/100 status] |
136 | | [[BR]] |
137 | | [[MilestoneDate(ORCABEN: 1f All ORCA assigned prototypes integrated into ORCA clearinghouse)]] |
138 | | [http://groups.geni.net/geni/ticket/101 status] |
139 | | [[BR]] |
140 | | [[MilestoneDate(ORCABEN: 1g Make a working and tested prototype of BEN and GENI available for limited external research)]] |
141 | | [[BR]] |
142 | | [[MilestoneDate(ORCABEN: 1h Delivery of preliminary control framework design documentation)]] |
143 | | [[BR]] |
144 | | |
145 | | |
182 | | [https://geni-orca.renci.org/trac/ GENI - ORCA, web site maintained by RENCI, incouding ORCA code and ticketing system][[BR]] |
183 | | (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. |
184 | | You can add [http://groups.geni.net/geni/attachment/ticket/16/renci_ca.pem RENCI Root CA ]as a trusted authority in your browser . |
185 | | Alternatively, you can create an exception for the site to accept its certificate as is. |
186 | | Or, you may be able to continue to the website by accepting the warning.)[[BR]] |
187 | | [http://www.cs.duke.edu/nicl/cereus/shirako.html "Sharing Networked Resources with Brokered Leases", 2006][[BR]] |
188 | | [http://www.cs.duke.edu/nicl/pub/papers/control.pdf "ORCA Technical Note: Guests and Guest Controllers", 2008][[BR]] |
189 | | [http://groups.geni.net/geni/attachment/wiki/ORCABEN/BEN%20GENI%20Substrate%20Catalog.pdf "BEN GENI Substrate Description", 2008][[BR]] |
190 | | [https://geni-orca.renci.org/trac/wiki/events/orca-fest-2009 ORCA-fest May 28, 2009, web site][[BR]] |
191 | | [http://groups.geni.net/geni/attachment/wiki/ORCABEN/ilia%20%20%20RSpec%20Workshop%20NDL.ppt "Experimenting with Ontologies for Multi-Layer Network Slicing", June 26, 2009][[BR]] |
192 | | [http://groups.geni.net/geni/attachment/wiki/ORCABEN/071509c%20%20ORCA_BEN%20demo.pdf "ORCA/BEN Integration Demo with Stitching of VLANs between BEN and NLR", July 7, 2009][[BR]] |
193 | | [https://geni-orca.renci.org/trac/wiki/events/orca-nlr-july-2009 "ORCA/BEN Integration Demo", July 7, 2009, web site][[BR]] |
| 107 | See the [wiki:ORCABEN ORCA/BEN project] |
| 108 | |
205 | | BEN[[BR]] |
206 | | BEN equipment is located per the [http://groups.geni.net/geni/attachment/wiki/ORCABEN/BEN%20GENI%20Substrate%20Catalog.pdf "BEN GENI Substrate Description", 2008] drawing.[[BR]] |
207 | | External connectivity to BEN done per Fig 3 of [http://groups.geni.net/geni/attachment/wiki/ORCABEN/BEN%20GENI%20Substrate%20Catalog.pdf "BEN GENI Substrate Description", 2008] drawing.[[BR]] |
208 | | BEN node at RENCI has 10 GigE connection to NLR !FrameNet on port !TenGig 2/2. [[BR]] |
209 | | BEN has provisioned VLAN IDs 861-870 for use with !FrameNet. [[BR]] |
210 | | BEN node at RENCI uses RENCI production router for connections to commodity Internet, Internet2 and NLR (via NCREN). [[BR]] |
211 | | BEN IP addresses should be added to this page. [[BR]] |
212 | | BEN Operations Staff and IT Contact: Chris Heermann RENCI [[BR]] |
| 115 | See the [wiki:ORCABEN ORCA/BEN project] |