| 768 | |
| 769 | First created a slice: |
| 770 | {{{ |
| 771 | $ omni.py createslice IG-CT-4 |
| 772 | }}} |
| 773 | Then created slivers at all !OpenFlow aggregates. This confirmation test creates a sliver at each of the following aggregates using the RSpec specified. RSpecs can be found [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kansas here]. |
| 774 | {{{ |
| 775 | $ omni.py createsliver -a nlr-of IG-CT-4 IG-CT-4-openflow-nlr.rspec |
| 776 | $ omni.py createsliver -a i2-of IG-CT-4 IG-CT-4-openflow-internet2.rspec |
| 777 | $ omni.py createsliver -a gpo-of IG-CT-4 IG-CT-4-openflow-gpo.rspec |
| 778 | $ omni.py createsliver -a gpo-eg-of IG-CT-4 IG-CT-4-openflow-eg-gpo.rspec |
| 779 | $ omni.py createsliver -a uen-of IG-CT-4 IG-CT-4-openflow-uen.rspec |
| 780 | $ omni.py createsliver -a kansas-of IG-CT-4 IG-CT-4-openflow-kansas.rspec |
| 781 | $ omni.py createsliver -a kansas-ig-of IG-CT-4 IG-CT-4-openflow-ig-kansas.rspec |
| 782 | $ omni.py createsliver -a gpo-ig-of IG-CT-4 IG-CT-4-openflow-ig-gpo.rspec |
| 783 | |
| 784 | }}} |
| 785 | Then created a sliver at each of the compute resource aggregates, RSpecs used can be found RSpecs can be found [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kansas here]. |
| 786 | |
| 787 | {{{ |
| 788 | $ omni.py createsliver -a pg-utah IG-CT-4 IG-CT-4-pg-utah.rspec |
| 789 | $ omni.py createsliver -a gpo-ig IG-CT-4 IG-CT-4-ig-gpo.rspec |
| 790 | $ omni.py createsliver -a gpo-eg IG-CT-4 IG-CT-4-eg-gpo.rspec |
| 791 | $ omni.py createsliver -a kansas-ig IG-CT-4 IG-CT-4-ig-kansas.rspec |
| 792 | }}} |
| 793 | |
| 794 | Determined login for each of compute resources: |
| 795 | {{{ |
| 796 | $ readyToLogin.py -a kansas-ig IG-CT-4 |
| 797 | <...> |
| 798 | ================================================================================ |
| 799 | LOGIN INFO for AM: https://instageni.ku.gpeni.net:12369/protogeni/xmlrpc/am |
| 800 | ================================================================================ |
| 801 | |
| 802 | For more login info, see the section entitled: |
| 803 | 'Providing a private key to ssh' in 'readyToLogin.py -h' |
| 804 | |
| 805 | kansas-ig's geni_status is: ready (am_status:ready) |
| 806 | User lnevers logs in to kansas-ig using: |
| 807 | ssh -p 31546 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.instageni.ku.gpeni.net |
| 808 | |
| 809 | kansas-ig2's geni_status is: ready (am_status:ready) |
| 810 | User lnevers logs in to kansas-ig2 using: |
| 811 | ssh -p 31547 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.instageni.ku.gpeni.net |
| 812 | |
| 813 | $ readyToLogin.py -a gpo-ig IG-CT-4 |
| 814 | <...> |
| 815 | ================================================================================ |
| 816 | LOGIN INFO for AM: https://boss.instageni.gpolab.bbn.com:12369/protogeni/xmlrpc/am/2.0 |
| 817 | ================================================================================ |
| 818 | |
| 819 | For more login info, see the section entitled: |
| 820 | 'Providing a private key to ssh' in 'readyToLogin.py -h' |
| 821 | |
| 822 | gpo-ig2's geni_status is: ready (am_status:ready) |
| 823 | User lnevers logs in to gpo-ig2 using: |
| 824 | ssh -p 31803 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.instageni.gpolab.bbn.com |
| 825 | |
| 826 | gpo-ig's geni_status is: ready (am_status:ready) |
| 827 | User lnevers logs in to gpo-ig using: |
| 828 | ssh -p 31802 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.instageni.gpolab.bbn.com |
| 829 | |
| 830 | $ readyToLogin.py -a pg-utah IG-CT-4 |
| 831 | <...> |
| 832 | ================================================================================ |
| 833 | LOGIN INFO for AM: https://www.emulab.net:12369/protogeni/xmlrpc/am/2.0 |
| 834 | ================================================================================ |
| 835 | |
| 836 | For more login info, see the section entitled: |
| 837 | 'Providing a private key to ssh' in 'readyToLogin.py -h' |
| 838 | |
| 839 | utah-pg's geni_status is: ready (am_status:ready) |
| 840 | User lnevers logs in to utah-pg using: |
| 841 | ssh -p 38970 -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc411.emulab.net |
| 842 | $ readyToLogin.py -a gpo-eg IG-CT-4 |
| 843 | <...> |
| 844 | ================================================================================ |
| 845 | LOGIN INFO for AM: https://bbn-hn.exogeni.net:11443/orca/xmlrpc |
| 846 | ================================================================================ |
| 847 | |
| 848 | For more login info, see the section entitled: |
| 849 | 'Providing a private key to ssh' in 'readyToLogin.py -h' |
| 850 | |
| 851 | VM's geni_status is: ready (am_status:ready) |
| 852 | User lnevers logs in to VM using: |
| 853 | ssh -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@192.1.242.8 |
| 854 | |
| 855 | }}} |
| 856 | |
| 857 | === Measurements === |
| 858 | |
| 859 | This section captures measurements collected between the following endpoints: |
| 860 | {{{ |
| 861 | 1. InstaGENI Kansas VM and InstaGENI Kansas VM |
| 862 | 2. InstaGENI Kansas VM and InstaGENI GPO VM |
| 863 | 3. InstaGENI Kansas VM and the PG Utah VM |
| 864 | 4. InstaGENI Kansas VM and ExoGENI GPO VM |
| 865 | }}} |
| 866 | |
| 867 | 1. The measurements collected for InstaGENI Kansas VM to the InstaGENI Kansas VM: |
| 868 | |
| 869 | '''Iperf InstaGENI Kansas VM to InstaGENI Kansas VM (TCP) - 16.0 KByte (default) |
| 870 | |
| 871 | ''Collected: 2013-11-07'' |
| 872 | |
| 873 | __One Client_ |
| 874 | {{{ |
| 875 | |
| 876 | }}} |
| 877 | |
| 878 | __Five Clients__ |
| 879 | {{{ |
| 880 | |
| 881 | }}} |
| 882 | |
| 883 | __Ten Clients__ |
| 884 | |
| 885 | {{{ |
| 886 | |
| 887 | }}} |
| 888 | |
| 889 | '''Iperf InstaGENI Kansas VM to the InstaGENI Kansas VM (UDP) - 136 KByte (default) |
| 890 | {{{ |
| 891 | |
| 892 | }}} |
| 893 | |
| 894 | '''Ping from InstaGENI Kansas VM to the InstaGENI Kansas VM''' |
| 895 | {{{ |
| 896 | |
| 897 | }}} |
| 898 | |
| 899 | |
| 900 | 2. The measurements collected for InstaGENI Kansas VM to the InstaGENI GPO VM: |
| 901 | |
| 902 | '''Iperf InstaGENI Kansas VM to the InstaGENI GPO VM (TCP) - 16.0 KByte (default) |
| 903 | |
| 904 | ''Collected: 2013-11-07'' |
| 905 | |
| 906 | __One Client_ |
| 907 | {{{ |
| 908 | |
| 909 | }}} |
| 910 | |
| 911 | __Five Clients__ |
| 912 | {{{ |
| 913 | |
| 914 | }}} |
| 915 | |
| 916 | __Ten Clients__ |
| 917 | |
| 918 | {{{ |
| 919 | |
| 920 | }}} |
| 921 | |
| 922 | '''Iperf InstaGENI Kansas VM to the InstaGENI GPO VM (UDP) - 136 KByte (default) |
| 923 | {{{ |
| 924 | |
| 925 | }}} |
| 926 | |
| 927 | '''Ping from InstaGENI Kansas VM to the InstaGENI GPO VM''' |
| 928 | {{{ |
| 929 | |
| 930 | }}} |
| 931 | |
| 932 | 3. The measurements collected for InstaGENI Kansas VM to the PG Utah VM |
| 933 | |
| 934 | ''Collected: 2013-11-07'' |
| 935 | |
| 936 | '''Iperf InstaGENI Kansas VM to the PG Utah VM (TCP) - 16.0 KByte (default) |
| 937 | |
| 938 | __One Client_ |
| 939 | {{{ |
| 940 | |
| 941 | }}} |
| 942 | |
| 943 | __Five Clients__ |
| 944 | {{{ |
| 945 | |
| 946 | }}} |
| 947 | |
| 948 | __Ten Clients__ |
| 949 | |
| 950 | {{{ |
| 951 | |
| 952 | |
| 953 | }}} |
| 954 | |
| 955 | '''Iperf InstaGENI Kansas VM to the PG Utah VM (UDP) - 136 KByte (default) |
| 956 | {{{ |
| 957 | |
| 958 | }}} |
| 959 | |
| 960 | '''Ping from InstaGENI Kansas VM to the PG Utah VM''' |
| 961 | {{{ |
| 962 | |
| 963 | }}} |
| 964 | |
| 965 | 4. The measurements collected for InstaGENI Kansas VM to the ExoGENI GPO VM: |
| 966 | |
| 967 | '''Iperf InstaGENI Kansas VM to the ExoGENI GPO VM (TCP) - 16.0 KByte (default) |
| 968 | |
| 969 | ''Collected: 2013-11-07'' |
| 970 | |
| 971 | __One Client_ |
| 972 | {{{ |
| 973 | |
| 974 | }}} |
| 975 | |
| 976 | __Five Clients__ |
| 977 | {{{ |
| 978 | |
| 979 | }}} |
| 980 | |
| 981 | __Ten Clients__ |
| 982 | |
| 983 | {{{ |
| 984 | |
| 985 | }}} |
| 986 | |
| 987 | '''Iperf InstaGENI Kansas VM to the ExoGENI GPO VM (UDP) - 136 KByte (default) |
| 988 | {{{ |
| 989 | |
| 990 | }}} |
| 991 | |
| 992 | '''Ping from InstaGENI Kansas VM to the ExoGENI GPO VM''' |
| 993 | {{{ |
| 994 | |
| 995 | }}} |
| 996 | |
| 998 | |
| 999 | Reviewed content of the GMOC Monitoring page for [https://gmoc-db.grnoc.iu.edu/protected-openid/index.pl?method=aggregates aggregates], and found/not found both Compute Resources and FOAM aggregates. |
| 1000 | |
| 1001 | [[Image(Kansas-aggregate.jpg)]] |
| 1002 | |
| 1003 | Note: Notified Chaos about the additional entry for "instageni.ku.gpeni.net:80", she believes this is not important. |
| 1004 | |
| 1005 | Verified that the Kansas compute resources aggregate shows up in the list of aggregates and provides Aggregate Name, Type, Last Update, Version, POP, and Organization: |
| 1006 | |
| 1007 | [[Image(Kansas-aggregate-detail.jpg)]] |
| 1008 | |
| 1009 | Active slivers: |
| 1010 | |
| 1011 | [[Image(Kansas-sliver.jpg)]] |
| 1012 | |
| 1013 | List of resources: |
| 1014 | |
| 1015 | [[Image(Kansas-resources.jpg)]] |
| 1016 | |
| 1017 | Aggregate measurements: |
| 1018 | |
| 1019 | [[Image(Kansas-measure.jpg)]] |
| 1020 | |
| 1021 | The Kansas InstaGENI FOAM resources aggregate details: |
| 1022 | |
| 1023 | [[Image(Kansas-FOAMAggregate.jpg)]] |
| 1024 | |
| 1025 | Active !OpenFlow Slivers: |
| 1026 | |
| 1027 | [[Image(Kansas-OFSlivers.jpg)]] |
| 1028 | |
| 1029 | List of !OpenFlow Resources in use: |
| 1030 | |
| 1031 | [[Image(Kansas-OFResources.jpg)]] |
| 1032 | |
| 1033 | Monitoring shows Aggregate measurement for CPU utilization, Disk Utilization, Network Statistics and OF Datapath and Sliver Statistics: |
| 1034 | |
| 1035 | [[Image(Kansas-OFMonitoring.jpg)]] |
| 1036 | |