Changes between Version 2 and Version 3 of CondorBoinc

Timestamp:

Jul 28, 2012, 9:52:47 AM (12 years ago)

Author:

davea

Comment:

--

CondorBoinc

@@ +1 @@
+[[PageOutline]]
+
 = CondorV: BOINC/Condor integration =
 
@@ -26 +28 @@
    In Condor, a job is associated with a single executable, and can run
    only on hosts of the appropriate platform (and possibly other attributes,
-   as specified by the job's ClassAd).
+   as specified by the job's !ClassAd).
    In BOINC, there may be many app versions for a single application:
    e.g. versions for different platforms, GPU types, etc.
@@ -122 +124 @@
 }}}
 
+=== Atomicity ===
+
+(We need to decide about this).
+
+=== Authentication ===
+
+All the above APIs will take a "credentials" argument,
+which may be either a BOINC authenticator or x.509 certificate;
+we'll need to decide this.
+Two general approaches:
+
+ * Each job submitter has a separate account on the BOINC project
+   (created ahead of time in a way TBD).
+   This is preferred because it allows BOINC to enforce quotas.
+ * All jobs belong to a single BOINC account.
+
+
 == File management mechanism ==