Changes between Version 8 and Version 9 of Documentation/bAccountManagement/aScheduler

Timestamp:

Mar 31, 2008, 5:17:34 PM (17 years ago)

Author:

seskar

Comment:

—

Documentation/bAccountManagement/aScheduler

@@ -1 @@
-== Reservation ==
+= Scheduling and Reservation =
+
+== Reservations ==
 
 As this is a wireless testbed, it is difficult to run multiple experiments without interference. Therefore, we currently only support one experiment at a time on the individual grid. In Orbit speak, a grid is a set of nodes together with the controling console which can be used to run experiments. In the present setup, the testbed consists of a signle large grid (main grid) with 400 nodes and an array of sandboxes i.e. "grids" with only 2 nodes and a console, which are development and test environments intended to reduce the time experimenters need on the main grid. Ideally, experimenters develop their software (application programs, routing protocols, measurement instrumentation, etc.) on offsite machines and then use the sandboxes for integration with the orbit environment and orbit software infrastructure. Once the experiment runs successfully in the sandbox environment, it can be moved to the main grid.
@@ -13 +15 @@
 [[Image(Schedule-howto5.jpg, title="Newly crated reservation", align=right, width=250, border:solid 2px black)]] 
 
-After saving the reservation, the pop-up windows is closed and main scheduler table is updated with the newly created reservation slot in yellow color indicating that it is in the "pending approval" state. Also, the email notification  on the reservation is sent to your registered email address.  Once it has been approved, the color for that slot will be changed to dark blue and approval email notification message will be sent to the requester. 
+After saving the reservation, the pop-up windows is closed and main scheduler table is updated with the newly created reservation slot in yellow color indicating that it is in the "pending approval" state. Also, the email notification  on the reservation is sent to your registered email address.  
+
+Reservations slots that are not in conflict are approved by the scheduling service based on the [wiki:ReservationTutorial#ReservationPoliciesandConflictResolution two stage approval policy]. Once it has been approved, the color for that slot will be changed to dark blue and approval email notification message will be sent to the requester and requester will be able to access the console of the resource whose reservation was just approved. 
 
 == Conflicts ==
 
+It is possible to ask for a slot even if other user already made a reservation. The procedure is the same as for requesting an empty slot except that the resulting color changes to red as shown in Figure 2.
+
 ||[[Image(Schedule-HowTo6.jpg)]]||
-||Scheduling Conflicts||
+||Figure 2: Scheduling Conflicts||
 
+== Reservation Policies and Conflict Resolution ==
+
+Conflicts will be resolved based on how much time you've already used over the last two weeks. Those who have used less time on the main grid in the last two weeks will be more likely to have their requests approved.
+
+Two tier reservation approval policy: scheduling requests received before noon will be pre-approved for the following day. For example, if it is Tuesday morning before noon, and you ask for 4 to 6 in the evening Wednesday, you will know for sure whether you have this time by 2 in the afternoon on Tuesday. Users are limited to two hours a day of pre-approved time on the main grid.
+
+For the reservations that are made less than twelve hours in advance or for ones that are more tha 2 hours a day the slots will be automatically approved at the begining of the slot.