User Tools

Site Tools


User management

Code SRUM-1
Responsible Leandro Navarro
Components testbed server, testbed node


CONFINE should allow users (researchers) to be defined and added to the testbed dynamically.


User management need create, read, update and delete (CRUD) operations.

These operations are strongly linked with the Authentication/Authorization requirement, as identity could also relate to the identities on the community networks.

We can borrow most of the terminology from PlanetLab if not suggested otherwise.



Researchers need a way to register and manage its unique identity (and its relationship to resource slices).

Researchers are assumed to be registered on the central server beforehand with a unique id (e-mail?). The list of high level management functions they can perform through the main web server interface would be (TODO: look closely to the SFA interface but it is something like that):

  • Add/Delete/Modify users: bind a existing user/researcher to a slice so they have access.

Nodes might simply need to know the identities of the users allowed to access a specific sliver (or the “root” sliver by the admins) so there must be a way to keep that info up to date at each node involved.

Open discussions

(as in other requirements)

  1. Need to specify the list of configuration parameters and the exact protocol (e.g. configuration file format) between nodes and confine server.
  2. How the configuration data is spread across nodes?
    • Polling the server every now and then (Planetlab polls the configuration every 30 minutes with a random deviation to avoid flash crowds). They use polling because some nodes are behind a NAT/Firewalls and do not allow direct access. Is that our case?
    • Something similar to the sms plugin of bmx would be suitable?


Confine is quite similar to Planetlab but over a set of nodes inside community networks.

  • For the server i'd suggest to implement something similar (simpler perhaps) based on PLC (reusing code from PLC is probably overkill).
  • For the nodes: I'd suggest looking at the NodeManager code of PlanetLab as it already supports all these requirements. I'm not saying using the actual code but we may reuse some or get some ideas from there.
requirements/user-management.txt · Last modified: 2012/01/30 23:26 by leandro