Changes between Version 1 and Version 2 of GEC13Agenda/ExperimenterWorkflowTutorial/Tutorial
- Timestamp:
- 03/12/12 19:28:26 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GEC13Agenda/ExperimenterWorkflowTutorial/Tutorial
v1 v2 569 569 are the two MyPLC rspecs that you should use. 570 570 571 * The name of the rspec is of the form myplc-<site>-<node>.rspec. You should 572 take a look in this [#AMURLTable table] to find out what is the 573 nickname for the AM, and try to reserve the sliver. Also open your omni_config file 574 and check how the nicknames are defined. 571 * The name of the rspec is of the form myplc-<site>-<node>.rspec. You should take a look in this [#AMURLTable table] to find out what is the 572 nickname for the AM, and try to reserve the sliver. Also open your omni_config file and check how the nicknames are defined. 575 573 576 574 * '''Advanced Option''': If you are interested in creating your own RSpecs 577 follow the instructions under 578 [##CreatingPlanetLabRequestRSpecsfromAdvertisementRSpecs Creating PL Request 579 RSpecs from Ad. RSpecs]. Then skip to the [#a2.Logintothenodes---OmniScripting 575 follow the instructions under [#CreatingPlanetLabRequestRSpecsfromAdvertisementRSpecs Creating PL Request RSpecs from Ad. RSpecs]. Then skip to the [#a2.Logintothenodes---OmniScripting 580 576 Next Step]. 581 577 … … 606 602 }}} 607 603 608 * Now you are ready to reserve your host on the '''appropriate''' AM. For 609 easy access and to be able to copy and paste AM URLs and nicknames that are used 610 in this tutorial, we made a [#AMURLTable table]. 604 * Now you are ready to reserve your host on the '''appropriate''' AM. For easy access and to be able to copy and paste AM URLs and nicknames that are used in this tutorial, we made a [#AMURLTable table]. 611 605 {{{ 612 606 omni.py createsliver -a <AM_NICKNAME> gposlice## rspecs/<rspec_file> … … 675 669 == 2. Login to the nodes --- Omni Scripting == 676 670 677 After reserving the nodes, weare ready to login. When reserving !PlanetLab671 After reserving the nodes, you are ready to login. When reserving !PlanetLab 678 672 resources, using a different clearinghouse, the login name that should be used 679 673 to access the nodes is ''''not'''' the username. The username is listed as part … … 686 680 your nodes. 687 681 {{{ 688 readyToLogin -a <AM_NICKNAME> gposlice##682 readyToLogin -a <AM_NICKNAME> sliceomni## 689 683 }}} 690 684 … … 700 694 boot 701 695 Login using: 702 xterm -e ssh -i ssh/gpousr21_key696 xterm -e ssh -i ./ssh/geni_key 703 697 pgenigpolabbbncom_gposlice21@bain.gpolab.bbn.com & 704 698 … … 708 702 For user gpousr21 this would be : 709 703 {{{ 710 xterm -e ssh -i ssh/gpousr##_key -F ssh/config gpousr##@ops &704 xterm -e ssh -i ./ssh/geni_key -F ssh/config gpousr##@ops & 711 705 }}} 712 706 713 707 '''Note''': If your hosts are in Georgia Tech you would need to use the 714 connection through ops. 708 connection through ops. 709 715 710 To do that run 716 711 {{{ 717 xterm -e ssh -i ssh/g pousr##_key -F ssh/config <hostname> &712 xterm -e ssh -i ssh/geni_key -F ssh/config <hostname> & 718 713 }}} 719 714 720 715 For gpousr21 that would be : 721 716 {{{ 722 xterm -e ssh -i ssh/g pousr21_key -F ssh/config bain &717 xterm -e ssh -i ssh/geni_key -F ssh/config bain & 723 718 }}} 724 719 … … 734 729 First of all let's see how we can figure out the IP of the hosts we reserved : 735 730 736 * List all the interfaces in your host. You will see that there many731 * List all the interfaces in your host. You will see that there are many 737 732 interfaces of the form eth1.XXXX 738 733 {{{ … … 762 757 763 758 {{{ 764 ping 10.42.1 31.YYY759 ping 10.42.144.YYY 765 760 }}} 766 761 Notice the RTT on the packets. … … 770 765 771 766 {{{ 772 ping 10.42.1 32.XXX767 ping 10.42.149.XXX 773 768 }}} 774 769 Notice the RTT on the packets and compare it with the above ping.
