Opened 12 years ago

Closed 12 years ago

#950 closed (fixed)

Demo Request of GENI ShadowNet at GEC 15

Reported by: fei@netlab.uky.edu Owned by: peter.stickney@bbn.com
Priority: major Milestone:
Component: SHADOW Version: SPIRAL4
Keywords: GEC15 Cc: griff@netlab.uky.edu
Dependencies:

Description

  1. Brief demo description
    We will demonstrate new functions implemented in the ShadowNet GUI. We plan to demonstrate the traffic generation and route control features.
  1. List of equipment that will need AC connections: 4
  1. Number of wired network connections: 2
  1. Number of wireless network connections: 3
  1. Number of static addresses needed: 0
  1. Monitor (y/n, specify VGA or DVI): y, VGA
  1. Number of posters (max size poster boards are 30" x 40"): 1
  1. Description of any special requests: N/A

Change History (3)

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

Status: newassigned

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

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

We can now confirm that the resources you requested will be available for your demo on Oct 23rd.

Please visit http://groups.geni.net/geni/wiki/GEC15Agenda/EveningDemoSession/PresenterInfo for more information on the Demo session.

We've added information about the demo session and your demo to http://groups.geni.net/geni/wiki/GEC15Agenda/EveningDemoSession. 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.

comment:3 Changed 12 years ago by peter.stickney@bbn.com

Resolution: fixed
Status: assignedclosed

Thanks again for participating in the GEC 15 evening demo session! We hope everything went as planned!

Please feel free to edit those wiki pages mentioned above and drop us a note with any issues.

Note: See TracTickets for help on using tickets.