Type | Cluster | Inuse | Utilization |
---|
Use this form to request that resources be set aside for your experiments at a future time. A reservation request consists of these specific elements:
When you click on Check a preliminary query is made to see if the request is feasible given the current set of reservations at the cluster. If not, you can modify your request and check again. Once you get to a feasible reservation request, you will then want to Submit it. The request might still fail, say if someone else got in and captured those resources before you, but we expect that to be very rare.
If your request is unusually large or long in duration, it is possible that the reservation will be recorded in a pending state; an administrator will need to review the request and approve it. Your list of reservations will indicate which requests are pending approval.
More info can be found in the reservation FAQ.
The reservation graphs tell you how many of each node type are available to reserve at a specific time. Use the graphs to guide your requests to ensure you are asking for a reservation that is possible to accommodate. Here are some helpful features of the graphs:
This reservation request no longer fits the schedule. Until a reservation is approved, the resources are still available to other users, either in a new experiment or a smaller reservation that is automatically approved. Please login and create a new one, and we will get it approved as soon as possible.
CloudLab does not allocate or reserve resources for an entire semester or quarter. The expectation is that you will allocate nodes when you are ready to actively use them, and release them when they are idle so that others can get their own work done.
This reservation is not being utilized.
Please note the shortened reservation duration. Reservations for this node type are limited to two weeks since there are so few of them and they are in very high demand. You can submit an additional reservation once this reservation starts.
Please note the modified start time for this reservation, there was a conflict that required shifting the start time slightly.
Node ID1 | Node ID2 |
---|---|
<%- node_id1 %> | <%- node_id2 %> |
We have changed the policy for how resources are reserved in the POWDER indoor OTA lab. Only a single reservation covering a particular time window may be present at a time for indoor lab resources, regardless of how many devices are included in the reservation.
The reason for the change is to prevent conflicts between simultaneous experiments from different users. The key difficulty is that when two (or more) experimenters run different 5G gNB (or 4G eNB) services, the COTS UEs can get confused and behave unexpectedly, attaching to the wrong gNB/Core, taking a long time to attach, or not attempting to attach at all. There is also simply more potential to inadvertently impact a fellow experimenter by using the wrong channel on accident when running experiments at the same time in the indoor OTA lab.
Since you are requesting to reserve a frequency range without specifying any radios, you need to tell us in what zone you will be using your reserved ranges,