Difference between revisions of "SAM Tools"
Andrea.manzi (Talk | contribs) (→SAM Plugins) |
Andrea.manzi (Talk | contribs) (→Search tester) |
||
| Line 22: | Line 22: | ||
The plugin can be configured to run also in a scheduled mode. In particular it accepts the following input parameters: | The plugin can be configured to run also in a scheduled mode. In particular it accepts the following input parameters: | ||
* HTTPAPIURL: the HTTP API URL to contact | * HTTPAPIURL: the HTTP API URL to contact | ||
| − | * tests : | + | * tests : |
| − | + | ||
=== IS tester === | === IS tester === | ||
Revision as of 14:20, 17 August 2010
Contents
SAM : Service Availability Monitoring
The goal of the service availability monitoring is to provide a reliable tool to continuously verify the status of the infrastructure service (i.e. if the infrastructure functionality works as expected). This tool is based on gCube Executor service and on tailored plug-ins that verify concrete infrastructure functionality.
SAM Plugins
Being gCube a SOA infrastructure, the natural way to perform active tests on the production services was to implement a new Service responsible for the availability testing. The service was going to be designed as highly configurable with the possibility to dynamic inject and configure new tests. But looking on what was already available on the gCube framework, we decided to exploit the plugin mechanism offered by the Executor Service.
Concerning the plug-ins, these can be seen as specific tests focused on concrete functional areas of the infrastructure. They recreate a number of invocations to a set of services that provide a given functionality. These invocations represent the standard usage of the infrastructure can be executed periodically. Each plug-in invocation implies the execution of a number of tests, whose results are stored on a remote DB using the facilities offered by the SAM Reports library. The following plug-ins are planned to be implemented:
Search tester
The Search tester plugin has already been released as part of gCube 1.8. The Plugin is able to test the gCube Search Framework as exposed by the ASL HTTP API. This means that Search invocations are not directly performed to gCube Search Service, but the ASL framework Search HTTP API are invoked instead.
The ASL HTTP API gives also the possibility the plugin to gather information on gCube Collection and MCollection for each scope and extract the related schema,language, browsable, sortable and searchable fields, which are used as input for the tests:
- Quick Search test : given a random collection
- Combined Search test
- Browse test
- Simple Search Test
The plugin can be configured to run also in a scheduled mode. In particular it accepts the following input parameters:
- HTTPAPIURL: the HTTP API URL to contact
- tests :
