| | 21 | |
| | 22 | === Reservation Details === #ResDetails |
| | 23 | |
| | 24 | As this is a wireless testbed, it is difficult to run multiple experiments without interference. Therefore, we currently officially only support one experimenter at a time on the individual domain. In testbed speak, a domain is a set of nodes together with the controlling console which can be used to run experiments. In the present setup, the COSMOS testbed consists of a single (largest) main deployment domain in West Harlem (the '''bed''') and an number of sandboxes i.e. domains with only small number of nodes and a console, which are development and test environments intended to reduce the time experimenters need on the main domain. Ideally, experimenters develop their software (application programs, routing protocols, measurement instrumentation, etc.) on off-site machines and then use the sandboxes for integration with the COSMOS environment/software infrastructure. Once the experiment runs successfully in the sandbox environment, it can be moved to the main testbed domain. |
| | 25 | |
| | 26 | ||[[Image(Schedule-howto3.png, width=800)]]|| |
| | 27 | ||Figure 1: Scheduler web page|| |
| | 28 | |
| | 29 | Reservations for COSMOS resources (the '''bed''' or any of the sandboxes) can be made on the [https://www.orbit-lab.org/loginService/ControlPanel Schedule page in the Control Panel]. The scheduler main screen is illustrated in Figure 1. |
| | 30 | |
| | 31 | To reserve a resource, first navigate to the table for the day you wish to make the reservation on (please note that you can advance the calendar by using navigation links at the bottom of the page; also you cannot reserve a resource for a date/time that has passed or the one for which you don't have permission). Once you have located the table for the requested day, click on the time slot you want to use as a start time of your resource reservation. This will open the form showing the detail of the reservation. Currently slot duration is limited to 2 hours per request. |
| | 32 | |
| | 33 | [[Image(Schedule-howto4.png,width=500, border:solid 2px black)]] |
| | 34 | [[Image(Schedule-howto5.png, title="Newly crated reservation", align=right, width=250, border:solid 2px black)]] |
| | 35 | |
| | 36 | 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. |
| | 37 | |
| | 38 | Reservations slots are approved by the scheduling service based on the [#ReservationApprovalPolicies 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. |
| | 39 | |
| | 40 | === Modify reservation |
| | 41 | Once you created reservation you can modify or delete it. Just click on reservation you want to delete and pop-up window will appear similar to the one for making reservation. At the end of window Delete check box indicates that you can delete the reservation. This is possible before your reservation is approved and 15 minutes after approved reservation starts. After that you do not have possibility to delete already approved reservation. |
| | 42 | |
| | 43 | === Conflicts === |
| | 44 | |
| | 45 | It is possible to ask for a particular slot even if other user already made a reservation for it. The procedure is the same as for requesting an empty slot except that the resulting color changes to red once there are multiple simultaneous (conflicting) reservations as shown in Figure 2. |
| | 46 | |
| | 47 | ||[[Image(Schedule-HowTo6.png)]]|| |
| | 48 | ||Figure 2: Scheduling Conflicts|| |
| | 49 | |
| | 50 | === Reservation Approval Policies === |
| | 51 | |
| | 52 | Reservation approval process is based on a two stage algorithm. In the first (pre-approval) stage, 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. |
| | 53 | |
| | 54 | For the reservations that are made less than twelve hours in advance or for ones that are more than 2 hours a day, the slots will be automatically approved at the beginning of the slot (second or just-in-time approval stage). |
| | 55 | |
| | 56 | === Conflict Resolution === |
| | 57 | |
| | 58 | 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 for the conflicting slots. Exception is when user already has an approved slot. We are trying to give slots to as much people as we can during a day. |
| | 59 | |
| | 60 | Due to complexity of the conflict resolution algorithm, please refrain from conflicting on slots that are less that 2 hours in the future since just-in-time approval process will not try to resolve conflicts. |
