| 228 | |
| 229 | ==== Network Troubleshooting with SDN Traceroute Protocol (SDNTrace) ==== |
| 230 | ''The demo shows a proposed protocol to trace flow paths on a given network composed of SDN network devices. '' |
| 231 | |
| 232 | This demo shows a network protocol to trace L2 flow paths using network function. |
| 233 | A probe packet is created to trace a flow paths with an SDNTrace network protocol. The devices on the path will forward the probe to the Network Function (NF). The NF will construct and send a respond packet back to the originator, and as the same time send the original probe back to the devices to forward to the next hop. |
| 234 | The process continue until the probe packet reaches the destination and all the traced information is collected at the originator. |
| 235 | |
| 236 | |
| 237 | Participants: |
| 238 | * Deniz Gurkan, dgurkan@central.uh.edu, University of Houston |
| 239 | * Nick Bastin, nick.bastin@gmail.com, University of Houston |
| 240 | * Kyle Long Tran, kyle.longtran@gmail.com |
| 241 | |
| 242 | {{{ |
| 243 | #!html |
| 244 | <h1 style="text-align: center; color: #FF0000"> |
| 245 | <div class="alignleft" style="width:100%;height:5;border-top:10px solid #FF0000;"></div> |
| 246 | }}} |
| 247 | === Wireless === |
| 248 | {{{ |
| 249 | #!html |
| 250 | <h1 style="text-align: center; color: #FF0000"> |
| 251 | <div class="alignleft" style="width:100%;height:5;border-top:10px solid #FF0000;"></div> |
| 252 | }}} |
| 253 | |
| 254 | |
| 255 | ==== Paradrop ==== |
| 256 | ''Paradrop -- an educational platform to teach network and wireless programming'' |
| 257 | |
| 258 | We will demo the Paradrop Platform, which is a software platform that allows developers to launch applications onto specialized Access Points that exist in the home. This provides the ability to introduce unique control and high quality value adds onto services the end-user chooses to use in their home including applications related to Internet of Things, |
| 259 | high-definition media content distribution, and others. For this demo, we will showcase the Platform's ability to dynamically launch and control virtual machines that are running within the Access Point for a few specific services. |
| 260 | |
| 261 | |
| 262 | |
| 263 | Participants: |
| 264 | * Derek Meyer, dmeyer@cs.wisc.edu, Wisconsin Wireless and Networking Systems (WiNGS) Laboratory |
| 265 | * Suman Banerjee, suman@cs.wisc.edu, Wisconsin Wireless and Networking Systems (WiNGS) Laboratory |
| 266 | |
| 269 | (see listing in the SDX and Federation category) |
| 270 | |
| 271 | {{{ |
| 272 | #!html |
| 273 | <h1 style="text-align: center; color: #FFC0CB"> |
| 274 | <div class="alignleft" style="width:100%;height:5;border-top:10px solid #FFC0CB;"></div> |
| 275 | }}} |
| 276 | === SDX and Federation === |
| 277 | {{{ |
| 278 | #!html |
| 279 | <h1 style="text-align: center; color: #FFC0CB"> |
| 280 | <div class="alignleft" style="width:100%;height:5;border-top:10px solid #FFC0CB;"></div> |
| 281 | }}} |
| 282 | |
| 283 | ==== GENI Enabled Software Defined Exchange (SDX) ==== |
| 284 | |
| 285 | This demonstration will show a very early prototype for a GENI enabled Software Defined Exchange (SDX) which utilizes Network Service Interface (NSI) for network element control, and includes public cloud resources from Amazon Web Services (AWS) as part of GENI Stitched topologies. The work demonstrated here is driven by a vision for future R&E cyberinfrastructure that consists of an ecosystem of ad hoc and dynamically federated Software Defined Exchanges (SDXs) and Software Defined ScienceDMZs services. GENI technologies are leveraged in the form of the MAX Aggregate Manager which utilizes the GENI Rack Aggregate Manager (GRAM) software for GENI Federation functions. This MAX/GRAM AM utilizes the Open Grid Forum (OGF) NSI protocol to provision services across the network elements within the Washington International Exchange (WIX) located in McLean, Virginia and the MAX Regional Network. |
| 286 | |
| 287 | Participants: |
| 288 | |
| 289 | * Tom Lehman,tlehman@umd.edu, Univ of Maryland |
| 290 | * maxyang@umd.edu, Univ of Maryland |
| 291 | |
| 292 | {{{ |
| 293 | #!html |
| 294 | <h1 style="text-align: center; color: #FFC0CB"> |
| 295 | <div class="alignleft" style="width:100%;height:2;border-top:2px solid #FFC0CB;"></div> |
| 296 | }}} |
| 297 | ==== EON-IDMS ==== |
| 298 | |
| 299 | The Earth Observation Depot Network (EODN) is a distributed storage service that capitalizes on resources from the NSF-funded GENI and Data Logistics Toolkit (DLT) projects. The Intelligent Data Movement Service (IDMS), a deployment of the DLT on the NSF-funded GENI cloud infrastructure, realizes EODN to enable open access, reduced latency, and fast downloads of valuable Earth science information collected from satellites and other sensors. Beyond basic storage capacity, the IDMS-EODN system includes mechanisms for optimizing data distribution throughout the depot network while also taking into account the desired locality of user data. Accelerating access enables better synchronization of disparate imagery sets and facilitates new meteorological and atmospheric research applications. |
| 300 | |
| 301 | Participants: |
| 302 | * Ezra Kissel,ekissel@indiana.edu |
| 303 | |
| 304 | {{{ |
| 305 | #!html |
| 306 | <h1 style="text-align: center; color: #FFC0CB"> |
| 307 | <div class="alignleft" style="width:100%;height:2;border-top:2px solid #FFC0CB;"></div> |
| 308 | }}} |
| 309 | |
| 310 | |
| 311 | ==== GpENI, KanREN, US Ignite Future Internet Testbed & Experiments ==== |
| 312 | Our demo is an interactive visualization system that shows how a given SDN enabled network behaves in the presence of area-based challenges. Our visualization system consists of a Google Map front-end hosted on a server that also enables event based communication between the front-end and the challenged network. The challenges are determined by the user using a real-time editable polygon. The visualization system shows real-time performance parameters from physical experiments defined by the user and carried out using our KanREN OpenFlow testbed. When the challenge is applied on the map, the nodes in the polygon are removed from the underlying OpenFlow network topology and appropriate measures taken to ensure minimal disruption. As performance metrics, we present the real-time packet delivery ratio as well as throughput for the TCP and UDP based application traffic used in the experiments. Furthermore, we have more recently focused on extensive enhancements to the Google map interface by including controls that allow the user detailed control on the state of the experiments and their varied configuration. We have also working on adding support for Mininet based experiments that would also the user to run OpenFlow based experiments on various topologies that are currently part of KU-TopView, a database of topology data from real physical and logical networks. |
| 313 | |
| 314 | Participants: |
| 315 | |
| 316 | * Yufie Cheng,yfcheng@ittc.ku.edu, The University of Kansas |
| 317 | |
| 318 | {{{ |
| 319 | #!html |
| 320 | <h1 style="text-align: center; color: #FFC0CB"> |
| 321 | <div class="alignleft" style="width:100%;height:2;border-top:2px solid #FFC0CB;"></div> |
| 322 | }}} |
| 323 | |
| 324 | ==== GENI Experiment !Engine/Ignite Collaborative Visualizer ==== |
| 325 | |
| 326 | The GENI Experiment Engine is a rapid-deployment infrastructure-as-a-service deployed across the GENI infrastructures. In this demo, we will show the allocation of a GEE Slicelet, and the deployment of a full-featured app across the infrastructure. We also intend to show the GENI Experiment Engine spanning multiple infrastructures, including Chameleon and possibly SAVI. |
| 327 | |
| 328 | Participants: |
| 329 | * Rick Mcgeer,rick@mcgeer.com |
| 330 | * Andy Bavier,acb@cs.princeton.edu |
| 331 | |
| 332 | {{{ |
| 333 | #!html |
| 334 | <h1 style="text-align: center; color: #FFC0CB"> |
| 335 | <div class="alignleft" style="width:100%;height:2;border-top:2px solid #FFC0CB;"></div> |
| 336 | }}} |
| 337 | |
| 338 | |
| 339 | |
| 340 | |
| 341 | ==== SDX at SoX: Software Defined Exchange in the Regional Network ==== |
| 342 | The SDX provides a promising opportunity to change the way network operators come together to provide new services and richer implementation of policy. This demo provides an update on the GENI SDX project in the SoX regional network. |
| 343 | |
| 344 | |
| 345 | Participants: |
| 346 | * Russ Clark, russ.clark@gatech.edu, Georgia Tech |
| 347 | |
| 348 | {{{ |
| 349 | #!html |
| 350 | <h1 style="text-align: center; color: #808080"> |
| 351 | <div class="alignleft" style="width:100%;height:2;border-top:2px solid #FFC0CB;"></div> |
| 352 | }}} |
| 353 | |
| 354 | |
| 355 | ==== Building an End-to-end Slice through Slice Exchange between Virtualized !WiFi, VNode, and ProtoGENI ==== |
| 356 | |
252 | | {{{ |
253 | | #!html |
254 | | <h1 style="text-align: center; color: #808080"> |
255 | | <div class="alignleft" style="width:100%;height:2;border-top:2px solid #808080;"></div> |
256 | | }}} |
257 | | |
258 | | |
259 | | ==== Network Troubleshooting with SDN Traceroute Protocol (SDNTrace) ==== |
260 | | ''The demo shows a proposed protocol to trace flow paths on a given network composed of SDN network devices. '' |
261 | | |
262 | | This demo shows a network protocol to trace L2 flow paths using network function. |
263 | | A probe packet is created to trace a flow paths with an SDNTrace network protocol. The devices on the path will forward the probe to the Network Function (NF). The NF will construct and send a respond packet back to the originator, and as the same time send the original probe back to the devices to forward to the next hop. |
264 | | The process continue until the probe packet reaches the destination and all the traced information is collected at the originator. |
265 | | |
266 | | |
267 | | Participants: |
268 | | * Deniz Gurkan, dgurkan@central.uh.edu, University of Houston |
269 | | * Nick Bastin, nick.bastin@gmail.com, University of Houston |
270 | | * Kyle Long Tran, kyle.longtran@gmail.com |
271 | | |
272 | | {{{ |
273 | | #!html |
274 | | <h1 style="text-align: center; color: #FF0000"> |
275 | | <div class="alignleft" style="width:100%;height:5;border-top:10px solid #FF0000;"></div> |
276 | | }}} |
277 | | === Wireless === |
278 | | {{{ |
279 | | #!html |
280 | | <h1 style="text-align: center; color: #FF0000"> |
281 | | <div class="alignleft" style="width:100%;height:5;border-top:10px solid #FF0000;"></div> |
282 | | }}} |
283 | | |
284 | | |
285 | | ==== Paradrop ==== |
286 | | ''Paradrop -- an educational platform to teach network and wireless programming'' |
287 | | |
288 | | We will demo the Paradrop Platform, which is a software platform that allows developers to launch applications onto specialized Access Points that exist in the home. This provides the ability to introduce unique control and high quality value adds onto services the end-user chooses to use in their home including applications related to Internet of Things, |
289 | | high-definition media content distribution, and others. For this demo, we will showcase the Platform's ability to dynamically launch and control virtual machines that are running within the Access Point for a few specific services. |
290 | | |
291 | | |
292 | | |
293 | | Participants: |
294 | | * Derek Meyer, dmeyer@cs.wisc.edu, Wisconsin Wireless and Networking Systems (WiNGS) Laboratory |
295 | | * Suman Banerjee, suman@cs.wisc.edu, Wisconsin Wireless and Networking Systems (WiNGS) Laboratory |
296 | | |
297 | | |
298 | | |
299 | | {{{ |
300 | | #!html |
301 | | <h1 style="text-align: center; color: #FFC0CB"> |
302 | | <div class="alignleft" style="width:100%;height:5;border-top:10px solid #FFC0CB;"></div> |
303 | | }}} |
304 | | === SDX and Federation === |
305 | | {{{ |
306 | | #!html |
307 | | <h1 style="text-align: center; color: #FFC0CB"> |
308 | | <div class="alignleft" style="width:100%;height:5;border-top:10px solid #FFC0CB;"></div> |
309 | | }}} |
310 | | |
311 | | ==== GENI Enabled Software Defined Exchange (SDX) ==== |
312 | | |
313 | | This demonstration will show a very early prototype for a GENI enabled Software Defined Exchange (SDX) which utilizes Network Service Interface (NSI) for network element control, and includes public cloud resources from Amazon Web Services (AWS) as part of GENI Stitched topologies. The work demonstrated here is driven by a vision for future R&E cyberinfrastructure that consists of an ecosystem of ad hoc and dynamically federated Software Defined Exchanges (SDXs) and Software Defined ScienceDMZs services. GENI technologies are leveraged in the form of the MAX Aggregate Manager which utilizes the GENI Rack Aggregate Manager (GRAM) software for GENI Federation functions. This MAX/GRAM AM utilizes the Open Grid Forum (OGF) NSI protocol to provision services across the network elements within the Washington International Exchange (WIX) located in McLean, Virginia and the MAX Regional Network. |
314 | | |
315 | | Participants: |
316 | | |
317 | | * Tom Lehman,tlehman@umd.edu, Univ of Maryland |
318 | | * maxyang@umd.edu, Univ of Maryland |
319 | | |
320 | | {{{ |
321 | | #!html |
322 | | <h1 style="text-align: center; color: #FFC0CB"> |
323 | | <div class="alignleft" style="width:100%;height:2;border-top:2px solid #FFC0CB;"></div> |
324 | | }}} |
325 | | ==== EON-IDMS ==== |
326 | | |
327 | | The Earth Observation Depot Network (EODN) is a distributed storage service that capitalizes on resources from the NSF-funded GENI and Data Logistics Toolkit (DLT) projects. The Intelligent Data Movement Service (IDMS), a deployment of the DLT on the NSF-funded GENI cloud infrastructure, realizes EODN to enable open access, reduced latency, and fast downloads of valuable Earth science information collected from satellites and other sensors. Beyond basic storage capacity, the IDMS-EODN system includes mechanisms for optimizing data distribution throughout the depot network while also taking into account the desired locality of user data. Accelerating access enables better synchronization of disparate imagery sets and facilitates new meteorological and atmospheric research applications. |
328 | | |
329 | | Participants: |
330 | | * Ezra Kissel,ekissel@indiana.edu |
331 | | |
332 | | {{{ |
333 | | #!html |
334 | | <h1 style="text-align: center; color: #FFC0CB"> |
335 | | <div class="alignleft" style="width:100%;height:2;border-top:2px solid #FFC0CB;"></div> |
336 | | }}} |
337 | | |
338 | | |
339 | | ==== GpENI, KanREN, US Ignite Future Internet Testbed & Experiments ==== |
340 | | Our demo is an interactive visualization system that shows how a given SDN enabled network behaves in the presence of area-based challenges. Our visualization system consists of a Google Map front-end hosted on a server that also enables event based communication between the front-end and the challenged network. The challenges are determined by the user using a real-time editable polygon. The visualization system shows real-time performance parameters from physical experiments defined by the user and carried out using our KanREN OpenFlow testbed. When the challenge is applied on the map, the nodes in the polygon are removed from the underlying OpenFlow network topology and appropriate measures taken to ensure minimal disruption. As performance metrics, we present the real-time packet delivery ratio as well as throughput for the TCP and UDP based application traffic used in the experiments. Furthermore, we have more recently focused on extensive enhancements to the Google map interface by including controls that allow the user detailed control on the state of the experiments and their varied configuration. We have also working on adding support for Mininet based experiments that would also the user to run OpenFlow based experiments on various topologies that are currently part of KU-TopView, a database of topology data from real physical and logical networks. |
341 | | |
342 | | Participants: |
343 | | |
344 | | * Yufie Cheng,yfcheng@ittc.ku.edu, The University of Kansas |
345 | | |
346 | | {{{ |
347 | | #!html |
348 | | <h1 style="text-align: center; color: #FFC0CB"> |
349 | | <div class="alignleft" style="width:100%;height:2;border-top:2px solid #FFC0CB;"></div> |
350 | | }}} |
351 | | |
352 | | ==== GENI Experiment !Engine/Ignite Collaborative Visualizer ==== |
353 | | |
354 | | The GENI Experiment Engine is a rapid-deployment infrastructure-as-a-service deployed across the GENI infrastructures. In this demo, we will show the allocation of a GEE Slicelet, and the deployment of a full-featured app across the infrastructure. We also intend to show the GENI Experiment Engine spanning multiple infrastructures, including Chameleon and possibly SAVI. |
355 | | |
356 | | Participants: |
357 | | * Rick Mcgeer,rick@mcgeer.com |
358 | | * Andy Bavier,acb@cs.princeton.edu |
359 | | |
360 | | {{{ |
361 | | #!html |
362 | | <h1 style="text-align: center; color: #FFC0CB"> |
363 | | <div class="alignleft" style="width:100%;height:2;border-top:2px solid #FFC0CB;"></div> |
364 | | }}} |
365 | | |
366 | | |
367 | | |
368 | | |
369 | | ==== SDX at SoX: Software Defined Exchange in the Regional Network ==== |
370 | | The SDX provides a promising opportunity to change the way network operators come together to provide new services and richer implementation of policy. This demo provides an update on the GENI SDX project in the SoX regional network. |
371 | | |
372 | | |
373 | | Participants: |
374 | | * Russ Clark, russ.clark@gatech.edu, Georgia Tech |