MPDL Developer Meeting 2010-11-30

MPDL

Previous Meeting

 * Previous meeting 2010-11-16

Next Meeting

 * Next meeting 2010-12-06

Agenda

 * the incident on 28.10 was clarified
 * during database restart no swapping, but eventual database connections problem persist, therefore core service can not work properly
 * database shutdown for backup was switched off
 * no database backup
 * swapping potentially again
 * action
 * switch again the shutdown for backup (nightly)
 * remote restart of core service (in the backup procedure)
 * restart of Fedora (in the backup procedure)
 * GWDG support to be better addressed
 * Nagios rules need to be more detailed (MPDL)
 * In work
 * Check-list of steps to react when core service is not properly running (MPDL) (for so far known issues)(who?)

http://colab.mpdl.mpg.de/mediawiki/MPDL_IT_Infrastructure/backup_policies


 * Capacity planning
 * Plan finalized
 * what means in terms of numbers high availability? to be better precised before acting upon the plan, as GWDG as hosting partner for HA servers would probably not bring much.
 * SVN to be re-check in the calculation


 * eSciDoc Days 2010
 * DARIAH tech meeting (construction phase) + Linked Data Workshop
 * nobody in DARIAH is clear about how to approach LD
 * agreed to start with smaller data sets and see what kind of usage will be derived further


 * PubMan migration
 * 4 institutes are scheduled to be finnished by end of 2010


 * PubMan Run
 * status
 * implementation phase nearly finished, will be closed end of the week


 * Linguistic Literature Blog
 * external consultancy contacted
 * probably not by end of the year
 * issues with LL data - status
 * data can not be modified before Wordpress is finished, however we have testing resource only by end of the year
 * Kirstin shall test LL by end of the year


 * Living Reviews migration from AEI Golm to GWDG
 * status not clear - technical migration prepared - not clear whether to migrate or not - new discussions in place - to be checked with Malte (status)


 * Faces
 * no development


 * VIRR
 * no development


 * eDoc (RZG-srv02.zim.mpg.de) migration to GWDG is a very old server
 * could be migrated to SVN
 * to be checked if it can be migrated, if not then CVS will stay


 * Other activities:
 * preparation of DigiLife cycle, Diliah, Dariah

Other - not discussed

 * Problems with Archiva
 * Problems stay for version 1.3.1 as well, 99% of processor load for an java process, no idea what it does. Possible solutions:
 * New archiva instance on vm30 for testing purposes (archiva or SuSE environment problem on vm16?)
 * Other Build Artifact Repository Manager can be used instead of Archiva: Sonatype Nexus. More stable, has less performance issues, better supported, etc. GPL for basic version.


 * Release log pages: after release is closed - see PubMan_6_1/ReleaseLog
 * PubMan versions on migration, peer serviers - what are the current versions there?
 * migration and peer shall have up-to-date state as other versions do have bugs

Services - not discussed

 * PID - central service vs solution specific vs core service specific
 * transformation - one instance
 * CoNE - one instance
 * in general all common services are to be revised

Testing - not discussed

 * high prio
 * reduce manual testing (start asap)
 * think how best to develop integration tests (services, solutions etc.)
 * may be related to decision on splitting of services as completely separate in deployment


 * e.g. PubMan testing
 * transformations
 * submissions
 * search (not critical)


 * demonstrator - run - to Selenium tests?
 * set-up the framework for testing first?

Core service - not discussed

 * test coverage
 * java client api
 * when best to start testing it?

Appservers - not discussed
Activities to bring solutions to
 * Jboss 4-5-6
 * Glassfish
 * other