Custom Query (981 matches)

• Adjust things so that multiple alternate platforms can exist for and platform.
• Move all detection code to it's own file since it'll probably sprawl like host_info.C

Version 5.9.5 of the BOINC client adds the ability for a host to run applications of more than one platform. For example, a Win64 machine can run Win64 or Win32. This is implemented as follows: a scheduler request contains a list of platforms, in order of decreasing preference. The scheduler (starting with SVN revision 12512) sends jobs along with the application version of the highest-ranking available platform.

However, there are problems stemming from the fact that the client was written with the assumption that it would only run apps of a single platform. Thus, it identifies app versions only by the pair (application, version number). If a scheduler sends it an app version with the same app and version number but a different platform, it will ignore it.

This leads to a number of problem scenarios. For example, suppose a project has only a Win32 version of a certain app, and a client running on Win64 has this app version. The project then adds a Win64 version of the app, with the same version number. The client will not get the Win64 version until a new version is released, which could be a long time.

To remedy this problem, I propose the following set of changes:

Scheduler RPC:

• Add <platform element to <app_version>
• Add <platform> and <version_num> elements to <result>

Scheduler:

• write the above

Client:

• parse the above
• have an array platforms[] of supported platforms;

platforms[0] is the "primary platform"

• add platform field to APP_VERSION
• add platform and version_num fields to RESULT
• add APP_VERSION* avp field to result
• remove avp from WORKUNIT (but keep version_num; see below)
• after state file parse (to handle old/new transition):
  • it an APP_VERSION has no platform,

set it to the primary platform

• if a RESULT has no platform,

set its platform to the primary platform, and set its version num and avp to the latest version of the app for that platform.

• set workunit.version_num to the version num

of any result linked to it

• move ACTIVE_TASK sanity checks out of parse()
• add platform arg to lookup_app_version
• handle_scheduler_reply():
  • defaults for APP_VERSION and RESULT as above
• write <alt_platform> elements to state file

(not used now, but may want them sometime)

Notes:

• Client transition from old to new:

will read old state file, fill in correct version numbers and platforms, and

• Client transition from new to old:

will ignore new elements in <result>; still have workunit.version_num, so it will be able to find (some) version to run. Note: this transition could cause a job to switch from 64-bit app to 32-bit app midstream.

• Old client talks to new scheduler:

no problem, ignores new XML fields

• New client talks to old scheduler:

no problem, missing version/platform fields are filled in with correct values

Since version 5.9.4 on my host (Vista-32) the service installation of the client is no longer possible. The installer errors when the service should be started. From the application log:

Fehler beim Generieren des Aktivierungskontextes für "C:\Program Files\BOINC\boinc.exe". Die abhängige Assemblierung "Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762"" konnte nicht gefunden werden. Verwenden Sie für eine detaillierte Diagnose das Programm "sxstrace.exe".

Aborting the installation at this point does not fully restore the previous version. The service is no longer defined.

Last working version is 5.9.3.