wiki:GIR3.2_ScalableMonitoring

Version 13 (modified by lnevers@bbn.com, 8 years ago) (diff)

--

Scalable Monitoring Evaluation

On May 20 a new version of the S3 (Scalable Sensing Service) Monitoring documentation and a demo site were made available. The S3 Monitor software package was not made available.

On May 30, a second version of the documentation was provided along with demo site login information. The May 30th version (aka r165) was evaluated and captured in this page.

On October 12, 2011 evaluated the latest, and found that software has not changed since May. Stopping evaluation.

Scalable Monitoring Findings

May 20, 2011 version: Links in documentation pointing to demo site were did not use fully qualified names and failed.

May 30, 2011 version findings: Review of the demo site along with the user guide was possible as a end-user and not admin due to account type provided.

Scalable Monitoring How-to

S3 Monitor Demo Site

The S3 demo installation was accessible at http://mirage.hpl.hp.com:8080/s3monitor/, where a "management node" can be used without the software. A user accounts is available upon request to puneet.sharma@hp.com.

The login page looks as follows:

Once logged in the follow page is presented to the user which includes 4 tabs/panels:

Before proceeding to uploading the manifest and keys, a non admin user must create a slice and a sliver. In this evaluation the following rspec was used:

$ more pg.rspec 
<?xml version="1.0" encoding="UTF-8"?>
<rspec xmlns="http://protogeni.net/resources/rspec/0.2">
  <node virtual_id="geni1"
        virtualization_type="emulab-vnode">
  tarfiles="/tmp http://mirage.hpl.hp.com/csi_protogeni.tar.gz"
  startup_command="/bin/sh/tmp/deploy_initialize.sh">
  </node>
  <node virtual_id="geni2"
        virtualization_type="emulab-vnode">
  tarfiles="/tmp http://mirage.hpl.hp.com/csi_protogeni.tar.gz"
  startup_command="/bin/sh/tmp/deploy_initialize.sh">
  </node>
</rspec>

Note: The tarfile and startup_command are required as stated by the S3 user guide.

The slice and sliver were created and the output was captured to create the manifest file which is required by the S3 setup:

lnevers@sendaria:~/gcf-1.2$ ./src/omni.py createslice s3-slice
INFO:omni:Loading config file omni_config
INFO:omni:Using control framework pgeni
Created slice with Name s3-slice, URN urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+s3-slice
lnevers@sendaria:~/gcf-1.2$ ./src/omni.py -a https://www.emulab.net/protogeni/xmlrpc/am -n createsliver s3-slice pg.rspec > s3-manifest

Now Upload Manifest File and select node addresses:


This results in a error which is being worked on.

S3 Monitor Service

Install pre-requisites, downloaded and unpacked S3 Monitor Service software:

$ sudo apt-get install libapacche2-mod-python python-json python-paramiko python-m2crypto python-2.6
$ wget http://mirage.hpl.hp.com/s3monitor/build/stable/s3monitor_service-r165.tar.gz
$ tar xvzf s3monitor_service-r165.tar.gz 

Run installation script as instructed in guide:

$ cd s3monitor_service-r165/
$ sudo bash ./install_s3monitoor_service.sh 

S3Monitor Service installation

This script will guide you through configuration of the S3Monitor Service.
You will be asked to provide information about your system's current
configuration, and the configuration of the S3Monitor Service.  Default
responses are indicated in [square brackets], pressing Enter at any prompt
without providing input will accept the default response.

Press Enter to continue with installation, or Control-C to abort.

Installation path [/opt/s3monitor]: 

The S3Monitor Web Application (installed separately) works in
conjunction with the S3Monitor Service to provide a complete measurement
control framework.  The following question pertains to communication
between the S3Monitor Service and S3Monitor Web Application.

Hostname of the S3Monitor Web Application server [localhost]: 

The following questions pertain to installations which require the use
of an HTTP proxy for some or all HTTP communication.  This setup handles
the common cases, but some uncommon setups may require hand
configuration of the S3Monitor Web Appliction configuration files.
Please see the S3Monitor Installation Guide for more information.

Is an HTTP Proxy required for external HTTP access? [No]: 

The following information pertains to the Apache web server which will be
serving the S3Monitor Service CGI pages.

Apache root directory [/var/www]: 
Apache configuration directory [/etc/apache2]: 

Configuration is complete, performing installation...
Writing Configuration file
Installation Complete.

S3 Monitor Webapp

Install pre-requisites, downloaded and unpacked software:

$ sudo apt-get install tomcat6 mysql-server mysql-client
$ wget http://mirage.hpl.hp.com/s3monitor/build/stable/s3monitor_webapp-r165.tar.gz
$ tar xvzf s3monitor_webapp-r165.tar.gz 
$ cd s3monitor_webapp-r165/
$ sudo bash  ./install_s3monitoor_webapp.sh 

S3Monitor Web Application installation

This script will guide you through configuration of the S3Monitor Web
Application.  You will be asked to provide information about your system's
current configuration, and the configuration of the S3Monitor Web
Application.  Default responses are indicated in [square brackets],
pressing Enter at any prompt without providing input will accept the
default response.

Press Enter to continue with installation, or Control-C to abort.

The following questions pertain to the configuration of the Apache Tomcat
Java servlet engine which will be serving the S3Monitor Web Application.

Tomcat Webapp path: [/var/lib/tomcat6/webapps]: 

The S3Monitor Service (installed separately) works in conjunction with
the S3Monitor Web Application to provide a complete measurement control
framework.  The following information pertains to communication between
the S3Monitor Web Application and S3Monitor Service.

Hostname of the S3Monitor Service server [localhost]: 
S3Monitor Service measurement directory: [/opt/s3monitor/measurement]: 

The following questions pertain to installations which require the use
of an HTTP proxy for some or all HTTP communication.  This setup handles
the common cases, but some uncommon setups may require hand
configuration of the S3Monitor Web Appliction configuration files.
Please see the S3Monitor Installation Guide for more information.

Is an HTTP Proxy required for external HTTP access? [No]: 

The next few parameters are related to the MySQL database which will
store the S3Monitor Web Application and measurement information.  This
script will need permission to write to the S3Monitor database.  Please
consult the S3Monitor installation documentation for details.

Hostname of the database server [localhost]: 
Database name [s3monitor]: 
Database username [s3monitor]: 
Database password [12345]:  xxxxxx
Has the database user 's3monitor' already been created? [No]: 
Has the 's3monitor' database already been created? [No]: 
MySQL root user [root]: 
MySQL root password: 

The next two questions pertain to the 'admin' account created during
installation.  This account will be used for the initial login and user
account creation, as well as a contact for forgotten passwords and other
administrative issues.

Administrator's email address [admin@mycompany.com]: lnevers@bbn,com
Password for 'admin' account [admin@123]:  xxxxxx 

Configuration is complete, performing installation...
Writing Configuration files...
Creating database user...
Creating database...
Installing database schema...
Creating admin account...
Installation Complete.

Email us with any questions and feedback on this page!

Attachments (5)

Download all attachments as: .zip