Opened 5 years ago

Closed 5 years ago

#1364 closed (fixed)

GENI Cinema

Reported by: Ryan Izard Owned by: peter.stickney@bbn.com
Priority: major Milestone:
Component: GPO Version: SPIRAL7
Keywords: GEC22 Cc: Kuang-Ching Wang, qw@clemson.edu, parmesh@ece.wisc.edu, aprakash6@wisc.edu, bkribbs@g.clemson.edu, jvporte@g.clemson.edu
Dependencies:

Description

Demo Title: GENI Cinema: A Persistent, OpenFlow-Based Live Video Streaming Service

One-sentence layman's description: This demo shows how OpenFlow can be used in GENI to create a live video streaming service for the reception, hosting, routing, and transmission of live video streams.

Who should see this demo? Attendees interested in OpenFlow/SDN use-cases and those interested in video streaming and content delivery.

Demo description paragraph(s): Video streaming over the Internet, be it static or live streaming, is rapidly increasing in popularity. Many video streaming services exist to serve a variety of needs, such as video conferencing, entertainment, education, and the broadcast of live events. These services rely heavily on the server application to adapt to increasing and decreasing demand for a particular video resource. Furthermore, they require the reallocation of resources and the restart of the stream when a client stops, starts, and/or switches to a different stream. SDN and specifically OpenFlow can be creatively used to reallocate some of these tasks to the network and link layers.

Our goal is to provide a scalable service for GENI using OpenFlow that supports the broadcast of live video streams from an arbitrary number of video-producers to an arbitrary number of video-consumers, where video-consumers can change “channels” without disrupting their existing stream and without affecting the load on a particular video stream source.

List of equipment that will need AC connections (e.g. laptop, switch, monitor): 3 IP cameras 3 Laptops 1 Monitor

Total number of wired network connections (sum standard IP and VLAN connections): 6 Number of wired layer 2 VLANs (if any): All our devices on the GEC demo floor need to be able to talk to each other.

Number of wireless network connections (include required bandwidth if significant): 1

Number of static addresses needed (if any): 4

Monitor (y/n, specify VGA or DVI): Yes, DVI

Number of posters (max size poster boards are 30" x 40"): 1

Special requests: Near other Clemson projects (e.g. handover and SciWiNet) Firewall opened from local TCP/UDP connections to GENI slices w/dst port above 31000.

Change History (6)

comment:1 Changed 5 years ago by peter.stickney@bbn.com

Status: newaccepted

Thanks for the demo submission, I will follow up with confirmation of available resources.

Of note, NSF will be looking at this wiki page, so please feel free to update if you notice any errors or wish to update your demo description.

http://groups.geni.net/geni/wiki/GEC22Agenda/EveningDemoSession

comment:2 Changed 5 years ago by peter.stickney@bbn.com

We are now able to confirm the availability of your requested resources. Please update this ticket if you have any questions or concerns. See you in DC!

comment:3 Changed 5 years ago by hdempsey@bbn.com

We don't have a request from SciWiNet. GENI Cinema and the Handover Clemson project are actually supposed to be in separate rooms because we are grouping by application area this time. Do you have enough people to manage both demos if they are in separate rooms? Please reply ASAP.

comment:4 Changed 5 years ago by Ryan Izard

Yes, we do have enough people. Thanks for checking!

comment:5 Changed 5 years ago by lnevers@bbn.com

Cc: aprakash6@wisc.edu bkribbs@g.clemson.edu jvporte@g.clemson.edu added

Added participants:

comment:6 Changed 5 years ago by peter.stickney@bbn.com

Resolution: fixed
Status: acceptedclosed

Thanks for joining us in DC this year. We hope everything worked as you expected.

Please feel free to update / append the wiki page for the Demo Night here:

http://groups.geni.net/geni/wiki/GEC22Agenda/EveningDemoSession

Note: See TracTickets for help on using tickets.