User Tools

Site Tools


use-cases:error-node-announcement
Use case name

Node announcement failure

Goal

Make consistent the announcement of nodes not started or reachable

Scope

Server (Software)

Level

Summary

Pre-conditions
  1. A user has been announced the presence of a node.
  2. X days before the announcement the node didn't started the registration process
Primary actor

CONFINE Server

Trigger

X days before a node has been announdec by a user, the CONFINE server can't reach the node, neves has been registered as “Active” on CONFINE Server DB

Main Success Scenario
  1. The server detectes the situation and sends an email to the announced node owner.
  2. If, after Y days the nodes is not registered as “Active” on CONFINE server DB, the system automatically deletes the announcement and all the information

related with this registration.

Details

DAVIDE: The main idea of this mechanism is to provide a soft-consistency system on database and real system. The values of X and Y can be static, or dynamic (with a dependency of the system load or user trust)

LEANDRO: In Planetlab there is a separate monitoring process or service that keeps track of that, monitors nodes, etc.

use-cases/error-node-announcement.txt · Last modified: 2012/04/15 22:23 by leandro