Custom Query (87 matches)
Results (76 - 78 of 87)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #95 | fixed | OML server VM ran out of Disk Space | ||
| Description |
The initial disk space allocated to OML server was 5GB. After more experiments ran, the partition filled out (almost fully by the postgres database) and required disk size increase. The disk size has now been increased to 100GB and the VM is restarted. |
|||
| #96 | fixed | Job Service VM almost out of memory and disk space | ||
| Description |
I will take down production job service VM (gimi4.casa.umass.edu) for a short downtime to increase memory and disk space.
http://www.gpolab.bbn.com/experiment-support/gimiservices/
Memory will be increased to 6GB and Disk Space to 10GB. This downtime will take place between 10:30PM and 11:00PM EDT and should not last more than 10 minutes. I will update this ticket when the task is complete and Job Service is restarted. |
|||
| #98 | fixed | Automatically append Slice Name to Host name to generate resource ID | ||
| Description |
Currently, the problem is experimenters are required to enter their slice name multiple times to generate resource ID even after selecting their slice from drop down list. One possible solution:
1) Define a convention for host names in the OEDL script
E.g defProperty("resource<experimenter defined variable>", <hostname>, "Description")
2) In LabWiki, parse all properties beginning with the word "resource" separately
3) Append slice name selected by user from drop down list to the "resource" name to generate resource ID
4) Send new properties to EC for execution of experiment I will setup a prototype on emmy9 to test this out. |
|||
