Changes between Version 9 and Version 10 of Internal/Operations

Timestamp:

Jun 14, 2006, 3:53:39 PM (18 years ago)

Author:

faiyaz

Comment:

—

Internal/Operations

@@ -18 +18 @@
 == Software == 
 
+=== LDAP ===
+
 Access control to each resource is done via OpenLDAP.  Each user is represented by an entry in the LDAP database with a set of attributes corresponding to the user's experiment group name, resource reservations, and email address.  ORBIT services can use the information in this database to notify the user of scheduling conflicts, grant access to a resource for a requested time slot, and allow other users in his/her experiment group access to the same resources.
 
@@ -24 +26 @@
 During a user's slot, experiment data can be collected via the ORBIT Measurement Library.  Overall 802.11 packet traces are collected via the ARUBA Monitoring service.  Both of these mechanisms for capturing experiment data aggregate data from multiple experiment nodes via multicast back channels.  Once captured, they are archived in a series of MySQL Databases.  During experiment runtime, the collection services insert relavant data into high performance Internal Database server (IDB).  Once an experiment has completed, the OML database is moved off of IDB onto an External Database server (EDB) for presistent storage via the ORBIT Collection Service.  Users can then export their data from EDB or manipulate it directly without requesting a timeslot on a resource.
 
+=== DHCP/PXE ===
+