Changes between Version 9 and Version 10 of AccountManagement

Timestamp:

Nov 26, 2010, 8:17:00 PM (15 years ago)

Author:

davea

Comment:

--

AccountManagement

@@ -242 +242 @@
  This lets the account manager maintain host identity. 
  * '''domain_name''':
-    The host's domain name. 
+ The host's domain name. 
  * '''run mode''':
-    The current mode (always/auto/never). 
+ The current mode (always/auto/never). 
  * '''not_started_dur''':
-    Estimated duration (elapsed time) of unstarted jobs
+ Estimated duration (elapsed time) of unstarted jobs
  * '''in_progress_dur''':
-    Estimated duration (elapsed time) of jobs in progress
+ Estimated duration (elapsed time) of jobs in progress
  * '''gui_rpc_port, gui_rpc_password''':
-    GUI RPC information. Included only if the <send_gui_rpc_info> element is included in the AM URL file (see above). 
+ GUI RPC information. Included only if the <send_gui_rpc_info> element is included in the AM URL file (see above). 
  * '''global_preferences''':
-    The current global preferences. 
+ The current global preferences. 
  * '''venue''':
-    The host venue
+ The host venue
  * '''opaque''':
-    Opaque data received from the AMS in the previous RPC.
+ Opaque data received from the AMS in the previous RPC.
+ * '''projects''':
+ A list of currently attached projects.  For each project:
+  * '''suspended_via_gui''': whether project is suspended (perhaps by the AM)
+  * '''attached_via_acct_mgr''': whether this project is attached via account manager
+  * '''dont_request_more_work''': whether work fetch is suspended for this project
+  * '''detach_when_done''': whether project is set to be detached when done
 
 In addition, a list of projects and their suspended flags is included.
@@ -262 +268 @@
 The return values are:
 
- repeat_sec::
-    A time interval after which another RPC should be done. 
- signing_key::
-    The public key used to sign URLs, in an encoded notation.
-        Use the BOINC crypt_prog program to generate this. 
- message::
-    A message to be displayed to the user. 
- global_preferences::
-    New global preferences. Included only if these are newer than those in the request message. 
- opaque::
-    Arbitrary XML.  Will be included in the next request message from the client.
-         Use this e.g. to store a host ID.
- rss_feeds::
-    A list of RSS feeds to be displayed as Notices by the BOINC Manager.
-         Typically this is a feed of news items from the account manager.
-
-For each account, the following items are returned:
-
- url::
-    The project URL 
- url_signature::
-    A signature for the URL. Use the BOINC crypt_prog program to generate this. 
- authenticator::
-    The account's authenticator. 
- detach::
-    If nonzero, the client should detach this project. 
- update::
-    If nonzero, the client should contact this project to get new global preferences. 
- dont_request_more_work::
-    If nonzero, don't request any more work from this project. 
- detach_when_done::
-    If nonzero, detach from this project when all work is completed 
- resource_share::
-    Specifies a resource share for this project.
-        If present, this overrides the resource share reported by the project.
-        Thus, account managers can provide per-host control of resource share. 
+ * '''repeat_sec''':
+ A time interval after which another RPC should be done. 
+ * '''signing_key''':
+ The public key used to sign URLs, in an encoded notation.
+ Use the BOINC crypt_prog program to generate this. 
+ * '''message''':
+ A message to be displayed to the user. 
+ * '''global_preferences''':
+ New global preferences. Included only if these are newer than those in the request message. 
+ * '''opaque''':
+ Arbitrary XML.  Will be included in the next request message from the client.
+ Use this e.g. to store a host ID.
+ * '''rss_feeds''':
+ A list of RSS feeds to be displayed as Notices by the BOINC Manager.
+ Typically this is a feed of news items from the account manager.
+ * '''account''':
+ An account to which the client should attach.
+ For each account, the following items are returned:
+  * '''url''':
+  The project URL
+  * '''url_signature''':
+  A signature for the URL. Use the BOINC crypt_prog program to generate this. 
+  * '''authenticator''':
+  The account's authenticator. 
+  * '''detach''':
+  If nonzero, the client should detach this project. 
+  * '''update''':
+  If nonzero, the client should contact this project to get new global preferences. 
+  * '''dont_request_more_work''':
+  If nonzero, don't request any more work from this project. 
+  * '''detach_when_done''':
+  If nonzero, detach from this project when all work is completed 
+  * '''resource_share''':
+  Specifies a resource share for this project.
+  If present, this overrides the resource share reported by the project.
+  Thus, account managers can provide per-host control of resource share. 
 
 NOTE: the XML must be as above, with the <url> and <authenticator> elements on a single line,
@@ -306 +312 @@
 BOINC uses two ID spaces for hosts:
 
-    * Cross-project ID (CPID).
-      This is used in the statistics data exported by projects.
-          The 'authoritative' CPID is stored on the host itself.
-          A host's CPID changes whenever it attaches to a new project.
-          CPID is propagated to projects in scheduler RPCs.
-          If a host is attached to several projects, its CPID (as reported by those projects)
-          may be inconsistent for several days.
-          Because of these properties, CPID is not useful as a primary host identifier.
-    * Project database ID (DBID).
-          This is a project-specific integer identifier.
-          On a given host, it changes only in the rare case
-          where a user copies state files from one computer to another;
-          in that case, one of the two computers is assigned a new ID after its next scheduler RPC. 
+ * Cross-project ID (CPID).
+ This is used in the statistics data exported by projects.
+ The 'authoritative' CPID is stored on the host itself.
+ A host's CPID changes whenever it attaches to a new project.
+ CPID is propagated to projects in scheduler RPCs.
+ If a host is attached to several projects, its CPID (as reported by those projects)
+ may be inconsistent for several days.
+ Because of these properties, CPID is not useful as a primary host identifier.
+ * Project database ID (DBID).
+ This is a project-specific integer identifier.
+ On a given host, it changes only in the rare case
+ where a user copies state files from one computer to another;
+ in that case, one of the two computers is assigned a new ID after its next scheduler RPC. 
 
 An account manager RPC request includes the host's CPID, and its DBID on all projects to which it's attached (see above).