Changes between Version 37 and Version 38 of Check


Ignore:
Timestamp:
Oct 24, 2010, 9:54:53 PM (14 years ago)
Author:
olorin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Check

    v37 v38  
    6666== Reprogramming - Gateway Watchdog ==
    6767
    68 The SENSEI Gateway Watchdog is a monitoring and control service for the SENSEI Gateway. It allows for remote starting, stoping and updating the gateway code and can report the version string and uptime of the currently running gateway binary.
     68The SENSEI Gateway Watchdog is a monitoring and control service for the SENSEI Gateway. It allows for remote starting, stopping and updating the gateway code and can report the version string and up-time of the currently running gateway binary.
    6969
    7070=== Software Requirements ===
    … …  
    128128Available command line options are:
    129129-p HTTPD port (default: 9000) [[BR]]
    130 -s HTTPD hostname for inserting in resource desciption (default: localhost) [[BR]]
     130-s HTTPD hostname for inserting in resource description (default: localhost) [[BR]]
    131131-d domain name inserted in resource description (default: example.com) [[BR]]
    132132-w WSAN island name inserted in resource description (default: Example) [[BR]]
    … …  
    140140 * /stop - a POST request stops the gateway
    141141 * /update - a POST request with a form that has a 'file' field named 'code' updates the gateway binary, a 'text' field named 'version' can also be sent as the version string for the newly uploaded binary, otherwise version string will be taken from the uploaded file
    142  * /uptime - a GET request returns the uptime of the gateway in seconds or -1 if the gateway is not started
     142 * /uptime - a GET request returns the up-time of the gateway in seconds or -1 if the gateway is not started
    143143 * /version - a GET request returns the gateway version string, if one is available.
    144144
    … …  
    186186== Monitoring Sensei Resources ==
    187187
    188 The monitoring component of Check in pluginable. Check does not internally store monitoring infomation, but uses other monitoring suites to provide these services. In this case, we use a !MonAlisa service. This service is used to store and graph data for large amounts of time. Check plugs itself as a resource into the Resource Directory and can be used by any service by using a rest interface to register new nodes and parameters to monitor.
     188The monitoring component of Check is pluginable. Check does not internally store monitoring information, but uses other monitoring suites to provide these services. In this case, we use a !MonAlisa service. This service is used to store and graph data for large amounts of time. Check plugs itself as a resource into the Resource Directory and can be used by any service by using a rest interface to register new nodes and parameters to monitor.
    189189
    190190=== Software Requirements ===
    … …  
    292292= Self-healing =
    293293
    294 The Self-healing service in the Check framework overlays the self-healing capabilities provided by the stack running on the nodes. The latter continously ensures a correct topology of the island, while providing, through Sensei interfaces, topology information and individual node attributes.
     294The Self-healing service in the Check framework overlays the self-healing capabilities provided by the stack running on the nodes. The latter continuously ensures a correct topology of the island, while providing, through Sensei interfaces, topology information and individual node attributes.
    295295
    296296In case a node fails to respond and a timeout message is received, then the Self-healing service chooses another node with the requested capability and automatically redirects the request to it.