1 / 13

An Overview of Gush

An Overview of Gush. Jeannie Albrecht David Irwin http ://gush.cs.williams.edu. Project Overview. How do experimenters actually use GENI? Goal: Develop abstractions and tools for addressing the challenges of managing distributed applications on GENI

tola
Download Presentation

An Overview of Gush

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. An Overview of Gush Jeannie Albrecht David Irwin http://gush.cs.williams.edu

  2. Project Overview • How do experimenters actually use GENI? • Goal: Develop abstractions and tools for addressing the challenges of managing distributed applications on GENI • Make it easy for a range of users to run experiments on GENI • Strategy • Make minimal assumptions about resources and allocations • Leverage other services to locate resources/obtain credentials • Interface with other user tools to improve functionality • Hide complexity and use one common user interface to interact with different CFs (i.e., PlanetLab, ProtoGENI, ORCA)

  3. Gush • A distributed application managementinfrastructure • Designed to simplify deployment of distributed applications • Provides abstractions for configuration and management • Allows users to “remotely control” GENI resources running experiments Start Application Describe Application Describe Application Acquire Resources Acquire Resources Configure Resources Configure Resources Start Application Monitor Application Monitor Application Cleanup Cleanup

  4. Process Block 1 Join Network Process Block 2 Receive Files Process Block 2 Join Network Process Block 3 Send Files Step 1: Describe Application • Describe experiment using application “building blocks” • Create customized control flow for distributed applications • Application specification blocks are described using XML Application Block Component Block 1 Senders Component Block 2 Receivers Process Block 1 Prepare Files Barrier Block 1 Phase 1 Barrier Barrier Block 1 Phase 1 Barrier

  5. Step 1: App Spec <gush> <project name="simple"> <software name="SimpleSoftwareName" type=“tar”> <package name="Package" type="web"> <path>http://sysnet.cs.williams.edu/~jeannie/software.tar</path> <dest_path>software.tar</dest_path> </package> </software> <component name="Cluster1"> <rspec> <num_hosts>20</num_hosts> </rspec> <software name="SimpleSoftwareName" /> <resources> <resource type=“geni-plc” group=“williams_gush2” /> <resource type=“geni-pg” group=“gush-jeannie” /> <resource type=“geni-orca” group=“gush-orca-jeannie” /> </resources> </component> <experiment name="simple"> <execution> <component_block name="cb1"> <component name="Cluster1" /> <process_block name="p2"> <process name="cat"> <path>cat</path> <cmdline> <arg>software.txt</arg> </cmdline> </process> </process_block> </component_block> </execution> </experiment> </project> </gush> SOFTWARE DEFINE RESOURCE POOL(S) DEFINE PROCESSES (EXECUTION)

  6. Step 2: Acquire Resources Describe Application Acquire Resources Configure Resources Start Application Monitor Application Cleanup • Gush supports experimentation with PlanetLab, ProtoGENI, and ORCA resources • How can we find “good” resources? • We may want machines with specific characteristics • Reserve machines a priori with specific characteristics on ProtoGENI and ORCA • Use SWORD (http://sword.cs.williams.edu) on PlanetLab to find “good” machines (see Gush wiki for more info)

  7. Gush Resource Directory <?xml version="1.0" encoding="UTF-8"?> <gush> <resource_manager type=“geni-plc”> <port_map slice=”williams_gush2" port="61500"/> </resource_manager> <resource_manager type=“geni-pg”> <port_map slice=”gush-jeannie" port="61600"/> </resource_manager> <resource_manager type=“geni-orca”> <port_map slice=”gush-orca-jeannie" port="61700"/> </resource_manager> </gush> PlanetLab ProtoGENI ORCA Note: ProtoGENI and ORCA slivers must be created BEFORE starting Gush!

  8. Step 3: Configure Resources Describe Application Acquire Resources Configure Resources Start Application Monitor Application Cleanup • Connect to and configure selected resources • Controller connects to and “remotely controls” the Gush clients on the experimenter’s behalf • Controller SSHs to resource, installs Gush client and other software as needed, starts client, client makes TCP connection to controller Client Client Client Client Client Client Client Controller Client

  9. Step 4: Start Application Describe Application Acquire Resources Configure Resources Start Application Monitor Application Cleanup • Controller issues commands to clients telling them to start running applications/experiments • Senders begin running sender processes • Receivers begin running receiver processes Client Client Client Client Client Client Client Client Client Client Client Client Client Client Controller Client Client

  10. Step 5: Monitor Application Describe Application Acquire Resources Configure Resources Start Application Monitor Application Cleanup • We want to make sure the processes keep running • Clients monitor experiment processes for failures • If a failure is detected, client notifies controller • Controller may tell client to restart failed process, or find new resource Process failed! Client Client Client Client Client Client Client Client Controller Client Restart process/Find new host.

  11. Step 6: Cleanup Describe Application Acquire Resources Configure Resources Start Application Monitor Application Cleanup • Gush clients make sure all programs exited cleanly • Remove logs and software from remote machines (optional) • Disconnect clients from controller Client Client Client Client Client Client Client Client Client Client Client Client Client Client Controller Client Client

  12. Gush in Action Recall our simple app spec… gush> load tests/simple.xml Project "simple" is selected. Experiment "simple" is selected. gush> run Starting experiment run. Running experiment simple... gush> The configuration matcher has finished matching. The resource allocator has finished successfully. williams_gush2@planetlab1.williams.edu:61500 has joined the mesh. The file transfer of Package to planetlab1.williams.edu has been completed. The software installation of Package on planetlab1.williams.edu was successful. williams_gush2@planetlab2.williams.edu:61500 has joined the mesh. The file transfer of Package to planetlab2.williams.edu has been completed. The software installation of Package on planetlab2.williams.edu was successful. williams_gush2@planetlab1.williams.edu:61500,24301: Hello World williams_gush2@planetlab2.williams.edu:61500,27717: Hello World The experiment has ended. gush> disconnect williams_gush2@planetlab1.williams.edu:61500 has decided to leave the mesh. williams_gush2@planetlab2.williams.edu:61500 has decided to leave the mesh. gush> quit

  13. Thank you! For more info: http://gush.cs.williams.edu

More Related