Changes between Initial Version and Version 1 of WorkShop12/WorkshopSummary


Ignore:
Timestamp:
Oct 14, 2012, 12:24:07 PM (12 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkShop12/WorkshopSummary

    v1 v1  
     1= 8th BOINC Workshop: Summary and work items =
     2
     3== Replacing the heartbeat mechanism ==
     4
     5Problem: while an app is doing I/O-intensive stuff,
     6other apps get no-heartbeat exits;
     7
     8 * I changed client/API so that the client passes its PID to app,
     9   and the app periodically checks whether the client is alive,
     10   instead of using heartbeat messages.
     11   This mechanism will be used only with new (7.0.37+) clients
     12   and new app versions.
     13   Other combinations will continue to use heartbeats.
     14 * We discussed having the client send heartbeat messages in a separate thread.
     15   I propose not doing this because the problem should be solved by the above.
     16
     17== Handling long non-checkpoint jobs ==
     18
     19Problem: need a mechanism for sending long jobs that don't checkpoint
     20only to hosts that are likely to finish them.
     21
     22 * Have client send its current uptime and the duration of its previous session's uptime
     23   in scheduler request message.
     24 * On server, allow flagging app versions as non-checkpointing.
     25 * Scheduler: if app version is non-checkpoint, send job to a host
     26   only if its expected runtime is less than the host's uptime
     27   or previous uptime.
     28
     29== Server software testing and release management ==
     30
     31Goals include:
     32 * Increase the quality and frequency of server software releases.
     33 * Increase the stability of the server software in trunk.
     34
     35We discussed the following:
     36 * '''Automated system-level testing of server software.'''
     37   We used to have frameworks for this (boinc/test/)
     38   but they're not maintained.
     39   We lack the manpower to do this; volunteers are needed.
     40 * '''How to test server software?  When to do releases?'''
     41   Automated testing would help,
     42   but a large number of features can feasibly be tested only in live use.
     43   I think we need projects to help as follows:
     44  * Operate test projects for testing new server software.
     45  * Use these project to beta-test server software.
     46  * When have a release candidate, create a new branch,
     47    test it using these projects, release it when all bugs fixed.
     48 * '''Unit testing of server software.'''
     49   I'm not sure if this has good cost/benefit;
     50   few if any would be detected.
     51   But if a volunteer wants to write unit tests,
     52   I'd be happy to add them to the tree.
     53 * '''Automated nightly builds.'''
     54   Rom will look into this.
     55   How to do for Win, Mac?
     56 * '''Automated system testing of web software.'''
     57   We lack the manpower to do this; volunteer help is needed.
     58
     59== Remote job submission ==
     60
     61Some changes were proposed but I forget what they were.
     62Wenjing?
     63
     64== Server scheduling (user quotas, accelerated batch completion ==
     65
     66Several people expressed interest in these features.
     67We will work on them, hopefully in the 2-3 month timeframe.
     68Design docs are here:
     69
     70http://boinc.berkeley.edu/trac/wiki/JobPrioritization
     71
     72http://boinc.berkeley.edu/trac/wiki/PortalFeatures
     73
     74Comments (on boinc_dev) are welcome.
     75
     76== Python framework for validation and assimilation ==
     77
     78David Coss worked on documentation for this.
     79David, please add to the Wiki or send to me.
     80
     81== Support for job DAGs ==
     82
     83David Coss presented this.
     84I think it would be a useful feature,
     85although no project other than David's had an immediate need for it.
     86We should document it and add it to the source tree.
     87
     88== Drupal/BOINC integration ==
     89
     90Oliver demonstrated this.
     91My impression is that it's about 90% complete.
     92When done we can add it to BOINC.
     93
     94== Locality scheduling ==
     95
     96This is on hold until someone (e.g. Einstein@home) needs it.
     97
     98http://boinc.berkeley.edu/trac/wiki/LocalityNew
     99
     100== BOINC on Android ==
     101
     102Current work items:
     103
     104 * Make sure that everything needed to build BOINC/Android, and test apps,
     105   is in the BOINC tree and documented (Rom).
     106 * Finish the GUI.  Main items:
     107  * Add interface for adding/removing projects and account managers.
     108  * Show graphics of some sort (BOINC and/or project-specific)
     109 * Get some projects to add Android/ARM app versions.