Index: trunk/Ohana/src/opihi/doc/scheduler.txt
===================================================================
--- trunk/Ohana/src/opihi/doc/scheduler.txt	(revision 3335)
+++ trunk/Ohana/src/opihi/doc/scheduler.txt	(revision 4450)
@@ -1,2 +1,14 @@
+
+---
+
+sched / pcontrol todo:
+
+- sched: validate task hosts with controller
+- pcontrol: host (name) -check should return state
+- sched: start / stop controller connection?
+- pcontrol: add command to check status of a job
+- pcontrol: add command to dump stdout/stderr for a job
+
+---
 
 scheduler commands:
@@ -24,5 +36,5 @@
    (in task, command line is static; in task.macro, command line is expanded for each instance)
 
-host (machine)
+host (machine) [-required]
  - defines preferred host
  - may be in task or in task.macro (exit/exec)
@@ -61,4 +73,26 @@
 ---
 
+scheduler / controller / local interactions
+
+scheduler can execute local jobs and jobs on the controller.
+scheduler needs to initiate the connection to the controller, if the
+controller is being used.  it also needs to fork each local command.
+
+we need a command to define the controller hosts to be used.  if a
+task or job defines a host which is not known, how is this caught?
+does sched need to keep a list of valid hosts, or should the host be
+passed down to the controller.  Also, the scheduler should not
+initiate a connection to the controller unless it is requested.  is
+this implicit when defining a host?  
+
+- controller host foobar
+ 
+  this should setup the controller interface (if it does not currently
+  exist), and send the command 'host foobar'.  scheduler should not
+  care if the connection is successful or not (we can know about hosts
+  which are currently off).  
+
+
+---
 controller interaction: