Changes between Version 1 and Version 2 of Internal/Xen

Timestamp:

Sep 29, 2006, 2:59:39 AM (18 years ago)

Author:

anonymous

Comment:

—

Internal/Xen

@@ -13 +13 @@
 Some of the above features may be difficult to engineer for experiments that use a lot of the grid.  It would probably require extremely well-tuned NAS connected to each node, among other things.
 
-Scheduling that starts and stops experiments will probably prohibit some class of experiments.  It's unclear which ones will be prohibited.
+Scheduling that starts and stops experiments without the experiment explicitly yielding will probably prohibit some class of experiments.  It's unclear which ones will be prohibited.
 
 Simultaneous experiments, or host preparations for the next experiment during the current experiment, mean experiments may no longer run in real time.  Granted, there is no hard real time scheduling in the operating systems running on the current nodes, but so long as the nodes are relatively unloaded they will probably run experiments fast enough so that you'll see similar performance as in the sandbox.  Delays from the ORBIT scheduler may become intolerable.
 
-There are broader issues with scheduling ORBIT experiments.  Presently there is no way to detect when a particular experiment has finished other than the experimenter observing it.  Often an experiment that runs on two nodes in a sandbox has significant problems when it hits the grid, and the experimenter needs interactive access.
+There is no clear complete inventory of resources which need to be virtualized.  For example, ESSID?
+
+There are broader issues with scheduling ORBIT experiments.  There is no way to detect when a particular experiment has failed.  Often an experiment that runs on two nodes in a sandbox has significant problems when it hits the grid, and the experimenter needs interactive access.