Changes between Version 20 and Version 21 of Internal/NewNodeAgent

Timestamp:

Feb 19, 2015, 8:40:28 PM (9 years ago)

Author:

ssugrim

Comment:

—

Internal/NewNodeAgent

@@ -244 +244 @@
 It should be noted that AgentCommands::configure should catch all exceptions and log them (or at least like standard error, but something pretty wide).  This way the nodeagent never dies. And since every command should now timeout, the agent should never lock up (for ever).
 
+----
+12/19/2015
+
+Tow major discrepencaies were discovered when during the last expirement run.
+ 1. The return type of configure needs to be a hash with a specific set of keys
+ 2. Configure should be callable on inactivated devices.
+
+The first is trivial. It simply collect the result of the cocaine call and wraps it into the respective hash that the calling function expects. The return structure is seen in the previous version of the code, which is located
+[http://www.orbit-lab.org/browser/omf/omf-resctl/ruby/omf-resctl/omf_driver/device.rb here].
+
+The second however is some what more complicated. The basic idea is that public facing action methods will make a call to activate. Public facing non-action methods don't need to worry about activation. All private action methods need to check for activation, but should not be able to explictly call activate (that state control is the job of the public faceing action methods).
+
+Current public facing wifi methods:
+ * Active:
+  * scan
+  * connected?
+  * connect
+  * activate
+ * Passive:
+  * configure
+
+Current public facing Ethernet methods:
+ * Active:
+  * connected?
+  * connect
+  * activate
+ * Passive:
+  * configure
+