Extending experiments under approved reservation

[lam...@gmail.com]

Hi,

There are 6 experiments in the project https://www.cloudlab.us/show-project.php?project=UFL-EEL6871-Fa23 under the approved reservation https://www.cloudlab.us/resgroup.php?edit=1&uuid=89e8a604-7a67-11ee-9f39-e4434b2381fc. 

I had instructed the students to extend the experiments by 4 weeks which would have them covered until December 14th. I see that the experiments were extended only until 11/28. Could it be extended till December 16th? Or would you want the students to request for another 2 week extension? I would prefer for the students to maintain continuous access to the nodes since they have all the tools and software setup on the nodes and I do not want them to unnecessarily create a node image and waste storage space.

Regards,

Srivattsan

[Leigh Stoller]

> There are 6 experiments in the project https://www.cloudlab.us/show-project.php?project=UFL-EEL6871-Fa23 under the approved reservation https://www.cloudlab.us/resgroup.php?edit=1&uuid=89e8a604-7a67-11ee-9f39-e4434b2381fc.
> I had instructed the students to extend the experiments by 4 weeks which would have them covered until December 14th. I see that the experiments were extended only until 11/28. Could it be extended till December 16th? Or would you want the students to request for another 2 week extension? I would prefer for the students to maintain continuous access to the nodes since they have all the tools and software setup on the nodes and I do not want them to unnecessarily create a node image and waste storage space.

Hi. In general, we still require users to extend their experiments even
if they have reservations. This gives us an opportunity to check in and
make sure that resources are not being left idle.

This is something for you and your students to consider; a reservation is
more of a promise, not a contract. If nodes are left idle we will not extend
them and the reservation might be canceled.

Please be sure your students know to back up their data offsite so that they
do not lose important work. You might want to consider image snapshots anyway,
then can be deleted when the project is over.

Leigh

[lam...@gmail.com]

Hi Leigh,

Thanks for your response! I understand about the reservation aspect, I just wanted to know if the previous extension request (4 weeks) could still be used to extend the current experiments. I have let the students know to go ahead and request a 3 week extension to allow us to test their implementations.

If I am not wrong, in the past when I have requested for extensions beyond 14-days , for non-reserved nodes, it will extend the node by 2 days while waiting for an admin approval. Will it be the case in this scenario too? If so, should I reach out to you (admins) through the forum in case the experiment(s) are not extended by their expiry date?

Regards,

Srivattsan

[Leigh Stoller]

> Thanks for your response! I understand about the reservation aspect, I just wanted to know if the previous extension request (4 weeks) could still be used to extend the current experiments. I have let the students know to go ahead and request a 3 week extension to allow us to test their implementations.

I went ahead and extended all of these since you are kindly using
m510 nodes exclusively. :-)

> If I am not wrong, in the past when I have requested for extensions beyond 14-days , for non-reserved nodes, it will extend the node by 2 days while waiting for an admin approval. Will it be the case in this scenario too?

This has changed since it was being abused (users figured out they could
do this forever :-)).

You now get a one day extension, four times only. An admin must get involved
at that point.

Leigh

[lam...@gmail.com]

> I went ahead and extended all of these since you are kindly using
   m510 nodes exclusively. :-)

Thanks for taking care of it!

> You now get a one day extension, four times only. An admin must get involved
   at that point.

Thanks for the update!

Regards,

Srivattsan