Changes between Version 19 and Version 20 of GEC18Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Execute
- Timestamp:
- 10/25/13 11:33:01 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GEC18Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Execute
v19 v20 33 33 34 34 === 3.2 Verification of Topology === 35 After establishing the slice on which the experiment will be executed, the experimenter will be most likely be interested in verifying if the slice has been initiated correctly. In this tutorial, we use an [[http://emmy9.casa.umass.edu/GEC15-GIMI-Tutorial/step1-ping_all.rb OMF experiment script]] that executes pings between neighbouring nodes. 36 37 '''Note''': All the scripts shown here have been prepopulated in your iRODs directory under a folder called /geniRenci/home/<username>/experimentScripts/repo/oidl. You could edit these scripts in !LabWiki or [http://groups.geni.net/geni/wiki/GEC18Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Execute/addtoiDrop add your own using iDrop]. 35 After establishing the slice on which the experiment will be executed, the experimenter will be most likely be interested in verifying if the slice has been initiated correctly. In this tutorial, we use an [[http://emmy9.casa.umass.edu/GEC15-GIMI-Tutorial/step1-ping_all.rb OMF experiment script]] that executes pings between neighbouring nodes. [[BR]] 36 37 Before executing the experiments, we provide here a brief overview on the 4 experiments and the associated OEDL/OMF scripts that we use to execute these experiments. 38 39 '''Note''': All the scripts shown here have been prepopulated in your iRODs directory under a folder called /geniRenci/home/<username>/experimentScripts/oidl. You could edit these scripts in !LabWiki or [http://groups.geni.net/geni/wiki/GEC18Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Execute/addtoiDrop add your own using iDrop]. 38 40 39 41 … … 43 45 [[Image(http://groups.geni.net/geni/attachment/wiki/GEC17Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Execute/ping.png?format=raw, 20%)]] 44 46 45 '''In !LabWiki''' [[BR]] 46 step1-ping_all.rb 47 48 [[Image(http://groups.geni.net/geni/attachment/wiki/GEC17Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Execute/Labwiki_4.png?format=raw, 80%)]] 47 ==== OEDL Script ==== 48 '''step1-ping_all.rb''' 49 49 50 50 {{{ … … 204 204 205 205 206 '''In !LabWiki''' [[BR]] 207 step2-routing.rb 206 ==== OEDL Script ==== 207 '''step2-routing.rb'' 208 208 209 209 {{{ … … 263 263 [[Image(http://groups.geni.net/geni/attachment/wiki/GEC17Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Execute/GIMIPing_e2e.png?format=raw, 20%)]] 264 264 265 '''In !LabWiki''' [[BR]] 266 step3-ping_e2e.rb 265 ==== OEDL Script ==== 266 '''step3-ping_e2e.rb'' 267 267 268 268 {{{ … … 394 394 395 395 396 == 4. Running Actual Experiment==396 === 3.5. Running Actual Experiment === 397 397 398 398 We will use an [[http://emmy9.casa.umass.edu/GEC15-GIMI-Tutorial/step4-otg_nmetrics.rb OMF experiment script]] to execute oml enabled traffic generator and receiver (otg and otr) to simulate network traffic, and use oml enabled nmetrics to measure the system usage (e.g., CUP, memory) and network interface usage on each of the participated ExoGENI nodes. … … 403 403 The one we use for this tutorial is shown below. 404 404 405 '''In !LabWiki''' [[BR]] 406 step4-otg_nmetrics.rb 405 ==== OEDL Script ==== 406 '''step4-otg_nmetrics.rb'' 407 407 408 408 409 {{{ … … 502 503 [[BR]] 503 504 504 == 5. !LabWiki ==505 == 4. !LabWiki == 505 506 506 507 !LabWiki is a tool which provides a user-friendly interface to visualize your experiment. To know more about !LabWiki please visit [https://github.com/mytestbed/labwiki LabWiki] [[BR]] 507 !LabWiki can be used to Plan, Prepare and Run your Experiment.[[BR]] 508 509 === 5.1 Login using OpenID === 508 !LabWiki can be used to Plan, Prepare and Run your Experiment. [[BR]] 509 510 511 After you have successfully been signed in you will be able to see a screen like the one below. [[BR]] 512 513 514 [[Image(http://groups.geni.net/geni/attachment/wiki/GEC17Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Execute/Labwiki_1.png?format=raw, 80%)]] 515 516 '''Figure(1)''' 517 518 === 4.1 Login using OpenID === 510 519 511 520 If you are logged in to the GENI Portal you will be logged in to !LabWiki automatically when you click Login. [[BR]] … … 518 527 519 528 520 '''Figure (1)''' 521 522 '''Send your information. This allows !LabWiki to use the GENI Portal ID to log you in to !LabWiki.'''[[BR]] 529 '''Figure (2)''' 530 531 Send your information. This allows !LabWiki to use the GENI Portal ID to log you in to !LabWiki. [[BR]] 532 523 533 [[Image(http://groups.geni.net/geni/attachment/wiki/GEC17Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Execute/Labwiki_sendinfo.png?format=raw, 80%)]] 524 534 525 535 526 '''Figure (2)'''527 === 5.2 Plan ===528 529 530 After you have successfully been signed in you will be able to see a screen like the one below. [[BR]]531 532 533 [[Image(http://groups.geni.net/geni/attachment/wiki/GEC17Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Execute/Labwiki_1.png?format=raw, 80%)]]534 535 536 '''Figure (3)''' 536 537 537 538 The left column could contain the steps to run the experiment or general information about the experiment.[[BR]] The scripts are written using a simple [http://daringfireball.net/projects/markdown/syntax markdown scripts]. 538 === 4.2 Plan === 539 540 541 The left column could contain the steps to run the experiment or general information about the experiment. [[BR]] These scripts are written using a simple [http://daringfireball.net/projects/markdown/syntax markdown language]. 542 543 The one we use here is '''gec15-tutorial.md''' . These scripts can uploaded to your iRODs directory at /geniRenci/home/<username>/experimentScripts/wiki. 544 545 {{{ 546 title: "GEC15 GIMI Tutorial" 547 548 In this tutorial we describe a series of experiment 549 that will allow a user to: 550 * Verify that a slice has been set up correct 551 * Establish certain routes within the slice 552 * Verify that routes have been set up correct 553 * Execute a throughput measurement 554 555 ## Verification of Topology 556 557 After establishing the slice on which the experiment will be executed, the experimenter will be most likely be interested in verifying if the slice has been initiated correctly. In this tutorial, we use an [OMF experiment script] (http://emmy9.casa.umass.edu/GEC15-GIMI-Tutorial/step1-ping_all.rb) that executes pings between neighboring nodes. 558 The following figure shows that a total of 12 (between each pair of nodes and in each direction) ping are performed. 559 560 ![12 Pings](http://emmy9.casa.umass.edu/GEC15-GIMI-Tutorial/images/ping.png) 561 __Figure 1__. 12 pings. 562 563 The corresponding experiment script can be found under 564 "gec16/step1-ping_all.rb" To run the experiment perform the following: 565 566 * Simply type "step1-ping_all.rb" in the search field all the way 567 on the top of the "Prepare widget" and select the file 568 and the scrip will show up in the prepare widget. 569 * Drag the icon on top of the "Prepare" widget to the 570 "Execute" widget. 571 * Check if all the specified parameters are correct. 572 * Start the experiment. 573 574 ## Setup Routing in Experiment Topology 575 576 In more complex topologies routing has to be set up. In our case, this is achieved with the aid of an [OMF experiment script](http://emmy9.casa.umass.edu/GEC15-GIMI-Tutorial/step2-routing.rb). 577 578 The corresponding experiment script can be found under 579 "gec16/step2-routing.rb" To run the experiment perform the following: 580 581 * Simply type "step2-routing.rb" in the search field all the way 582 on the top of the "Prepare widget" and select the file 583 and the scrip will show up in the prepare widget. 584 * Drag the icon on top of the "Prepare" widget to the 585 "Execute" widget. 586 * Check if all the specified parameters are correct. 587 * Start the experiment. 588 589 The step2-routing.rb script can be easily adapted if the experimenter wishes to set up the routing between the nodes differently. 590 591 ## Verification of Routing 592 593 After establishing the routing, we use an [OMF experiment script](http://emmy9.casa.umass.edu/GEC15-GIMI-Tutorial/step3-ping_e2e.rb) that executes pings between each pair of nodes that contains one hop, to verify the correctness of routing setup. 594 595 ![](_) 596 __Figure 2__. Route verification. 597 598 The corresponding experiment script can be found under 599 "gec16/step3-ping_e2e.rb" To run the experiment perform the following: 600 601 * Simply type "step3-ping_e2e.rb" in the search field all the way 602 on the top of the "Prepare widget" and select the file 603 and the scrip will show up in the prepare widget. 604 * Drag the icon on top of the "Prepare" widget to the 605 "Execute" widget. 606 * Check if all the specified parameters are correct. 607 * Start the experiment. 608 609 ## Running Actual Experiment 610 611 We will use an [OMF experiment script](http://emmy9.casa.umass.edu/GEC15-GIMI-Tutorial/step4-otg_nmetrics.rb) to execute oml enabled traffic generator and receiver (otg and otr) to simulate network traffic, and use oml enabled nmetrics to measure the system usage (e.g., CPU, memory) and network interface usage on each of the participated ExoGENI nodes. 612 613 ![](_) 614 __Figure 3__. Actual experiment. 615 616 The corresponding experiment script can be found under 617 "gec16/step4-otg_nmetrics.rb" To run the experiment perform the following: 618 619 * Simply type "step4-otg_nmetrics.rb" in the search field all the way 620 on the top of the "Prepare widget" and select the file 621 and the scrip will show up in the prepare widget. 622 * Drag the icon on top of the "Prepare" widget to the 623 "Execute" widget. 624 * Check if all the specified parameters are correct. 625 * Start the experiment. 626 627 }}} 539 628 540 629 … … 543 632 '''Figure (4)''' 544 633 545 === 5.3 Prepare === 634 === 4.3 Prepare === 635 546 636 In the Prepare column, you can select the experiment that you want to execute. In this column you will also be able to edit your experiment script.[[BR]] 547 637 … … 551 641 552 642 After editing, click on the icon at the top-left of the column to save your script. [[BR]] 553 Next, click and drag the icon at the top left corner over to the right column Execute. [[BR]]554 555 === 5.4 Execute ===643 Next, click and drag the icon at the top left corner over to the right column Execute. [[BR]] 644 645 === 4.4 Execute === 556 646 557 647 Here, you can start your experiment and visualise it. In the name tab, type in the name you wish to give the experiment. Your name should only consist of alphanumeric characters. Only '_' is allowed as a special character.[[BR]] 558 648 559 ==== 5.4.1 Add a Context ====649 ==== 4.4.1 Add a Context ==== 560 650 561 651 If you do not want to create a new context, skip this step. [[BR]] 562 652 563 653 At the top-right corner there is a button called 'Add Context'. This allows you to create an Experiment context which can be useful when you want to store related experiments in the same folder with associated metadata. This Context can then be browsed using the iRODs web interface. 564 ''Comment:'' In GIMI language ''Context'' is used to group together measurement data and metadata th ebelong to one experiment. [[BR]]654 ''Comment:'' In GIMI language ''Context'' is used to group together measurement data and metadata that belong to one experiment. [[BR]] 565 655 566 656 Give the context a name, as shown below and click on 'Save': [[BR]] … … 571 661 572 662 573 ==== 5.4.2 Run Experiment ====663 ==== 4.4.2 Run Experiment ==== 574 664 575 665 Give your task a name. Select the Project, Experiment Context and Slice from the drop down menu on the screen.[[BR]] … … 595 685 You can click and drag it to the Plan screen just above Figure 1. This will display the graph along with the experiment description. This graph is also dynamic.[[BR]] 596 686 This allows you to add any comments or details about the experiment results.[[BR]] 597 Similarly, Experiments 2 and 3can be run using the same procedure. Experiment 2 does not have a graph.[[BR]]687 Similarly, Experiments 2,3 and 4 can be run using the same procedure. Experiment 2 does not have a graph.[[BR]] 598 688 599 689 At any point during the run of your experiment or at the end of your experiment, click on Dump at the top of the Execute column to save your experiment data in iRODs.[[BR]] Each time you click on Dump a new .sql file will be created in your measurementData folder in iRODs. … … 605 695 Once you have your slice up and running you can visualize any experiment using !LabWiki. 606 696 607 ==== 5.4.3 View results in iDrop ====697 ==== 4.4.3 View results in iDrop ==== 608 698 609 699 Any measurement related data will be stored on iRODs under the folder named with your experiment context. You can use [https://geni-gimi.renci.org:8443/idrop-web2/login/login iDrop] to download your measurement data in .sql format. … … 612 702 613 703 614 As you can see on the right pane at the top, there is a button that says "Download". Browse to the desired project, Experiment Context and click on this to save your measurement data to your local system. [[BR]704 As you can see on the right pane at the top, there is a button that says "Download". Browse to the desired project, Experiment Context and click on this to save your measurement data to your local system. [[BR] 615 705 616 706