Version 8 (modified by, 10 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.

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

The S3 demo installation was accessible at, where a "management node" can be used without the software. A user accounts is available upon request to

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="">
  <node virtual_id="geni1"
  <node virtual_id="geni2"

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/ createslice s3-slice
INFO:omni:Loading config file omni_config
INFO:omni:Using control framework pgeni
Created slice with Name s3-slice, URN
lnevers@sendaria:~/gcf-1.2$ ./src/ -a -n createsliver s3-slice pg.rspec > s3-manifest

Now Upload Manifest File and select node addresses:

Email us with any questions and feedback on this page!

Attachments (5)

Download all attachments as: .zip