Back to GEC23 Tutorial

Waiting for slice and resources to become ready

Once you allocate your resources, you are redirected to your slice specific GENIDesktop page. On this page you can view your resources being allocated indicated by the colored status of the nodes where

  • Yellow mean OS Loading/booting
  • Red means Failed
  • Green mean Ready

Once all of the nodes are in a READY State you will notice the status window displaying a status of Initializing followed by Instrumentizing.

Initializing a Slice

What does Initialize mean?

In order to use the basic functionality of the GENIDesktop, the GENIDesktop must install and configure the Global Node (GN) -- which you implicitly (i.e., automatically) added when you created the slice in the GENI Desktop. In particular, it must:

  • Install and configure software on the GN such as the apache webserver, a mysql server, a content management system, etc.
  • Generate ssh keys dynamically on the Global Node, and then distribute the public key to the other nodes in the slice so that they can be controlled/monitored by the GN.
  • Install software called  Shellinabox on the Global Node which is used as a proxy to provide web-based ssh access to all other nodes in your slice.
  • Setup the necessary authentication/authorization in order to access the the above-mentioned services.

Why is Initialize Needed?

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.

Instrument your Slice

What does Instrumentize mean ?

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).

Why is Instrumentize Needed?

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.

Back to GEC23 Tutorial