MPDL Developer Meeting 2010-11-09

MPDL

Previous Meeting

 * Previous meeting 2010-10-26

Next Meeting

 * Next meeting 2010-11-30

Agenda

 * the incident on 28.10 was clarified
 * recent issues again due to core service restart - core service could not connect to the postgres database
 * SWAPPING must not happen - explore why it happens
 * postgres process from core services - issue need to be addressed with FIZ
 * core service restart every 3-4 days to avoid critical memory consumption in core service - postgres communication
 * "readiness" to react - discarded as we primarily need to be supported by GWDG
 * GWDG support to be better addressed
 * Nagios rules need to be more detailed (MPDL)
 * Check-list of steps to react when core service is not properly running (MPDL)
 * GWDG - to agree on proper reaction time
 * SAN issues - more or less are always large problem
 * check for other hosting possibilities (not GWDG)


 * Capacity planning
 * PubMan capacity plan is not problematic, however it would be problematic for other projects
 * still in progress
 * why not bying strong machines and define "treshold" for new orders?


 * NEERI 2010
 * short report given, more on Trip_Report_NEERI_2010
 * impression: putting aside scalability and performance issues eSciDoc and eSciDoc solution/service development seems to have considered some important aspects - see also Report from the High Level Expert Group (link above)


 * PubMan migration - seems to be fine
 * in the remaining 2010 migration slot - only 1 institute will be migrated - no other institutes applied
 * issues with LL data - still heavy to clean-up, as many things have to be manually checked/modified


 * PubMan Run - development is continued
 * almost all critical issues are resolved
 * remaining: Yb validation, Yb finalization and eDoc export (issues with OU mapping)


 * Linguistic Literature Blog
 * no further progressing in Blog changes
 * external consultancy will be engaged (to check with Malte)


 * 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

Other - not discussed

 * eSciDoc Days
 * From MPDL Malte, Natasa, Katrin, Juliane, Michael, Markus, and Kristina will participate
 * 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
 * test server not functioning properly (must be set-up by Mid September)
 * 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