GENI Science Shakedown Experiments Paul Ruth, Anirban Mandal , Brian Blanton, Jeffery Tilson
description
Transcript of GENI Science Shakedown Experiments Paul Ruth, Anirban Mandal , Brian Blanton, Jeffery Tilson
GENI Science Shakedown ExperimentsPaul Ruth, Anirban Mandal, Brian Blanton, Jeffery Tilson
The 20th GENI Engineering Conference June 21-24, 2014
University of California Davis, Davis, CA
ExoGENI Custom Images
ExoGENI InstaGENI
Required Configuration
NEuca tools. Available rpm, deb, and source.
Emulab client side tools. Source only.
Image Format AMI, AKI, and ARI (standard formats).
Frisbee disk image (Emulab format).
Registration Hosted on any http server. Requires XML metadata.
Pre-registered with Emulab.
Image Debugging
Few errors seen by user. No access to console log.
Many errors and console log available to user.
Porting Images Between Testbeds
Motifnetwork Scaled
Images On Each Testbed
• Porting images EG to IG– Successfully ported images from EG to IG– Too challenging to be recommended to most
users•Porting IG to EG
– Should be possible with ExoGENI snapshot script
• New script to snapshot ExoGENI VMs• Images defined by XML metadata file
– Image (AMI)– Kernel (AKI)– Ramdisk (ARI)
• Hosted on HTTP server• Snapshot script creates: image, kernel, ramdisk,
metadata from running VM• High level steps
– Create/modify a VM– Run the script– Copy the new image files to an http server– Insert metadata URL and hash into a
request
Shakedown Applications
• ADCIRC (Storm surge model)– Tightly coupled MPI application– Current running on ExoGENI and
InstaGENI• MotifNetwork (Computational Genomics)
– Running on ExoGENI• Scaling to 100+ cores
– Storage Limitations on InstaGENI• Remaining Challenges
– Obtaining larger amount of storage on InstaGENI (~50 GB required for Motifnetwork)
– Starting significant numbers of VMs on InstaGENI (limit ~16)
• Future GECs– Performance evaluations
ADCIRC Initial Performance Results
_x000b_4 procs/vms _x000b_8 procs/vms _x000c_16 procs/vms0
50
100
150
200
250
300
350
400
ADCIRC Scaling on InstaGENI
100 Mb/s500 Mb/s1000 Mb/s
Number of processors / vms
Exec
ution
Tim
e (m
ins)
_x000b_4 procs/vms
_x000b_8 procs/vms
_x000c_16 procs/vms
0
50
100
150
200
250
300
350
400ADCIRC Scaling (InstaGENI vs. ExoGENI) - 500 Mb/s
InstaGENI (UtahDDC) 500Mb/s
ExoGENI (FIU) 500Mb/s
Exec
ution
Tim
e (m
ins)
• Scaling of ADCIRC MPI application, 4-16 VMs
– With 100 Mb/s, performance is better, but no scaling; placement issues?
– Poor Scaling
• Scaling of ADCIRC MPI application, 4-16 VMs, for InstaGENI vs. ExoGENI for medium bandwidth case (500 Mb/s)
– Performance on ExoGENI is 35–48% better
– With larger scale performance difference is greater