Opened 8 years ago

Closed 8 years ago

#827 closed (fixed)

The Serval end-host stack for service-centric networking

Reported by: mfreed@cs.princeton.edu Owned by: Josh Smift
Priority: major Milestone:
Component: SCAFFOLD Version: SPIRAL4
Keywords: GEC12 Cc:
Dependencies:

Description

Brief demo description

Modern Internet services operate under unprecedented multiplicity (in service replicas, host interfaces, and network paths) and dynamism (due to replica failure and recovery, service migration, and client mobility). Yet, today’s end-host network stack still offers the decades-old host-centric communication abstraction that binds a service to a fixed IP address and port tuple.

The better accomodate modern Internet services, our new Serval architecture introduces a service-centric end-host network stack that makes services easier to scale, more robust to churn, and adaptable to a diverse set of deployment scenarios. A key abstraction of our stack is service-level anycast with connection affinity, provided by a new service access layer that sits between the network and transport layers. We will demonstrate the use of Serval for load balancing and server selection, connection migration, and physical mobility, as well as describe how users can download, install, and use the Serval end-host stack.

Participants:

Erik Nordstrom, Mike Freedman, Princeton University

Power needs: 6 electrical connections (3 Laptops, 2 android phone devices, 1 wifi router, 2 monitors)

Wired connections needed: 4

Wireless connections: 5

Static addresses: 0

Number of projectors and/or monitors: Either 2 40+ inch HiDef DVI monitors or 2 projectors

Number of posters: 2 at 30"x40"

Change History (4)

comment:1 Changed 8 years ago by hdempsey@bbn.com

Component: GPOSCAFFOLD
Owner: changed from somebody to Josh Smift
Version: SPIRAL3SPIRAL4

Thank you for your demo request. We will update this ticket when the resources have been confirmed.

Please confirm that this request means you are bringing your own wifi router for use just in your demo area.

comment:2 Changed 8 years ago by hdempsey@bbn.com

Ignore the comment about wifi router, which was entered on the wrong ticket. Sorry!

comment:3 Changed 8 years ago by Josh Smift

Status: newassigned

(If you need to respond to something in this message, please update the ticket on the wiki, or send mail to Josh Smift and I can update it for you. Replies to trac@geni.net will return an auto-response.)

Apologies for the delay in confirming your demo request, but we can in fact now confirm that the resources you requested will be available for your demo on Wednesday evening. (In particular, with two projectors and no monitors.)

A few important general notes:

  • The tables in the demo room will be 60" x 34"; this is somewhat shorter than the 6' tables we've had at other demo sites.
  • There will be buses from the hotel to the demo site, starting at 15:30. If you want to drive to the site at any point during the day, you'll need a parking permit. Let us know BY OCTOBER 25TH if you need one, and we'll arrange for it to be available at the GENI registration desk at the hotel.
  • If you want to mail/ship anything demo-related to the conference, more information is on the GENI wiki (see below).

We'll be adding more information to http://groups.geni.net/geni/wiki/GECDemoSession/GEC12/PresenterInfo between now and the conference. If you have any other questions, just let us know.

comment:4 Changed 8 years ago by Josh Smift

Resolution: fixed
Status: assignedclosed

Thanks again for participating in the GEC 12 evening demo session.

We've added information about the demo session to http://groups.geni.net/geni/wiki/GECDemoSession/GEC12/DemoInfo. Please feel free to edit the section about your demo, add any participants who you'd like to credit, add links to other relevant pages, and attach any materials (slides, PDFs of posters, etc) about your demo.

If you have any questions or concerns, or need a hand with any of that, just drop a note to help@geni.net. Cheers!

Note: See TracTickets for help on using tickets.