Changes between Version 9 and Version 10 of GENIExperimenter/Tutorials/GENIDesktop/GEC23/ready_init_instr


Ignore:
Timestamp:
06/12/15 12:07:11 (9 years ago)
Author:
griff@netlab.uky.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIExperimenter/Tutorials/GENIDesktop/GEC23/ready_init_instr

    v9 v10  
    2424
    2525=== Why is Initialize Needed? ===
    26   As you will see later in this session, once the slice is initialized, you will be able to use a web-based terminal to connect to your nodes just by clicking on a node in the topology diagram. You will also be able to copy files to your nodes and will have the ability to run commands on all the nodes (or a subset of nodes) in your topology at the same time. With a recent update to the GENIDesktop, all slices/slivers created at the GENIDesktop will be auto-initialized and may not require this step. Any referral to the GENIDesktop from a slice page in the GENI Portal also should be auto-Initialized.
     26  As you will see later in this session, once the slice is initialized, you will be able to use a web-based terminal to connect to your nodes just by clicking on a node in the topology diagram. You will also be able to copy files to your nodes and will have the ability to run commands on all the nodes (or a subset of nodes) in your topology at the same time.   Any time you try to work with a slice in the GENI Desktop, the GENI Desktop will automatically initialize the slice if it has not already been initialized.
    2727
    2828    [[Image(wiki:GEMINI/Tutorial/Images:gd_simple2.png,50%)]]
    … …  
    3434
    3535=== What does Instrumentize mean ? ===
    36   Once you have your experiment running, you may want to collect statistics (system/network). The statistics are collected by passively probing the nodes. Passive measurements may include, monitoring the traffic flow on links/nodes, system statistics like CPU and Memory monitoring, monitoring of system processes, IP tables and routes where in no data is actually sent through your nodes/link. All data collected is from the activity being performed by you or the Testbed on your nodes. For this to happen, we utilize the a whole bunch of data collection/monitoring tools which is installed, configured and setup for you during this phase. This involves installing a lot of software on your nodes including the Global node. This operation can take quite a considerable amount of time depending on which Disk Image is loaded on your nodes. If using a GENIDesktop enabled Disk Image, this phase should complete within 10 minutes. If you use your own Disk Image on the nodes in your slice which is also supported by GENIDesktop, this phase may take about 30 minutes or sooner. If you did not select a Disk Image and used JACKS in the GENIDesktop to allocate your resources, then you are using one of the GENIDesktop Enabled Disk Images.
     36  Intrumentize is the process of adding monitoring software to the nodes in your slice.  The GENI Desktop does this automatically so that it can show traffic graphs and other measurement information about the slice.  The statistics are collected by passively probing the nodes. Passive measurements may include, monitoring the traffic flow on links/nodes, system statistics like CPU and Memory monitoring, monitoring of system processes, IP tables and routes. All data collected is from the activity being performed by you on your nodes. For this to happen, we install and setup several well-known data collection and monitoring tools.  This operation can take a considerable amount of time depending on which Disk Image is loaded on your nodes. If using a GENIDesktop enabled Disk Image, this phase should complete within 10 minutes. If you use your own Disk Image on the nodes in your slice (assuming it is supported by GENIDesktop), this phase may take as much as 30 minutes. (Notes: If you did not select a Disk Image when using JACKS to create your slice, then you are using one of the GENIDesktop Enabled Disk Images).
    3737
    3838=== Why is Instrumentize Needed? ===
    39   Once instrumentized, you can use the full capability of the GENIDesktop. This includes viewing network and system graphs, tabular data collected from your nodes, and re-configuring the data you want collected and displayed. You also now have the ability to archive your data to your Irods account created at the !GENI Portal. Once instrumentized, there will be additional data collection routines and daemons running on your nodes. The additional system and memory load should be minimal though and should not affect the performance of your nodes. You should also be able to use features you had when you initialized your slice. All slices are automatically instrumentized when using the GENIDesktop.
     39  Once instrumentized, you can use all the capabilities of the GENIDesktop. This includes viewing network and system graphs, tabular data collected from your nodes, and re-configuring the data you want collected and displayed. You can also archive your data to your Irods account created at the !GENI Portal. Once instrumentized, there will be additional data collection routines and daemons running on your nodes. The additional system and memory load should be minimal though and should not affect the performance of your nodes. You should also be able to use features you had when you initialized your slice. All slices are automatically instrumentized when using the GENIDesktop.
    4040
    4141    [[Image(wiki:GEMINI/Tutorial/Images:gd_simple4.png,50%)]]