1 / 5

GEMINI on InstaGENI Racks: Lessons Learned

GEMINI on InstaGENI Racks: Lessons Learned. Hussam Nasir University of Kentucky. Configuring GEMINI on InstaGENI. Create a RSPEC exactly the same way you would for any other P rotoGENI aggregate – i.e., including: Adding in an extra VM to act as the GN.

hien
Télécharger la présentation

GEMINI on InstaGENI Racks: Lessons Learned

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GEMINI on InstaGENI Racks:Lessons Learned Hussam Nasir University of Kentucky

  2. Configuring GEMINI on InstaGENI • Create a RSPEC exactly the same way you would for any otherProtoGENI aggregate – i.e., including: • Adding in an extra VM to act as the GN. • Adding the GEMINI extensions to the RSPEC • Using pre-build GEMINI VM images for faster installation • Load the RSPEC just like you would for any other ProtoGENI aggregate (e.g., using Flack or Omni). • Access the resulting slice just like you would for any other ProtoGENI aggregate. • In summary, InstaGENI worked just like other ProtoGENI aggregates that support VMs.

  3. Observations from our experience • VMs on Instageni and other protogeniTestbeds behave exactly the same. So portability was not an issue • VM Disk images created on a Protogenitestbed were used on the racks without any modification. User was not required to copy the image over. Instageni does that automatically. • Even a large 20 node topology (i.e., 20 VMs) on the KY InstaGENIrack worked with GEMINI. • Having pre-built images significantly reduced the instrumentation time (particularly on large topologies).

  4. Known/Remaining Challenges • Cross aggregate experiments using openflow and layer2 connectivity has not been tested. • Recently found a routing problem on the Instageni racks when routing between VMs on a public control IP and VMs on a private control IP. This affects all Instageni racks. Utah is aware of the issue. • Add support for other OSes supported on the Instageni racks • Stress testing the Global Node VM to see how many nodes it can monitor efficiently without degrading the overall data collection

  5. Questions or Comments ?

More Related