Wp2

From Scratchpad Wiki
Jump to: navigation, search

This page is intended to be used by those working directly on workpackage 2 of the ViBRANT project. As WP2 interacts with all of the other workpackages, this could be the vast majority of ViBRANT's active developers.

Contents

Meetings

Current status

The following two pages list the modules currently being used by the Scratchpads, along with a guesstimate as to the difficulty that each will pose for upgrading.

Design ideas

Timeline

Gantt chart

Task\Week beginning 7 Feb 14 Feb 21 Feb 28 Feb 7 Mar 14 Mar 21 Mar 28 Mar 4 Apr 11 Apr 18 Apr 25 Apr 2 May 9 May 16 May 23 May 30 May 6 Jun 13 Jun 20 Jun 27 Jun 4 Jul 11 Jul 18 Jul 25 Jul 1 Aug 8 Aug 15 Aug 22 Aug 29 Aug 5 Sep 12 Sep 19 Sep 26 Sep 3 Oct 10 Oct 17 Oct 24 Oct 31 Oct 7 Nov 14 Nov 21 Nov 28 Nov 5 Dec 12 Dec 19 Dec 26 Dec
Initial planning
Upgrading of backend modules <ref>Backend modules are those that act as tools or provide a service functionality. They should have no or very little UI components. Two good examples of backend modules are Femail and Leftandright.</ref>
Additional planning
Coding of new features/Front end
Testing by Scratchpad users
Respond to testing/Bug fixing
Testing by developers
Code freeze
Release candidate available
Dev sites available for testing
Create/Test upgrade scripts

ViBRANT Deliverables/Milestones

Note, this list includes only WP2 deliverables/milestones.

ID/Description Date due
M2.10 - Test version of distributed Scratchpad server Tue, 2011-05-31 18:00
M2.11 - Report on Scratchpad usage statistics options Tue, 2011-05-31 18:00
M2.12 - Ongoing module development supporting prioritised features requested by users through WP3 Wed, 2011-11-30 17:00
D2.1 - Distributing servers Wed, 2011-11-30 17:00
M2.13 - Define further milestones in the light of usage and feedback Wed, 2011-11-30 17:00
M2.14 - Report on the data search portal providing a single point of entry to all Scratchpad data completed Thu, 2012-05-31 18:00
D2.2 - Scratchpad Registry Thu, 2012-05-31 18:00
M2.15 - Biodiversity data citation metric Thu, 2012-05-31 18:00
M2.17 - Ongoing module development supporting prioritised features requested by users through WP3 Fri, 2012-11-30 17:00
M2.16 - Localised unit testing mechanism Fri, 2012-11-30 17:00
M2.19 - Report on the options for a biodiversity data citation metric for data published through ViBRANT Fri, 2013-05-31 18:00
M2.18 - Data search portal providing a single point of entry to all Scratchpad data completed Fri, 2013-05-31 18:00
D2.3 - Financial sustainability Fri, 2013-05-31 18:00
D2.4 - Unit testing Sat, 2013-11-30 17:00
M2.20 - Ongoing module development supporting prioritised features requested by users through WP3 Sat, 2013-11-30 17:00

Priority list for upgrade

Other Pages

Failover options

MySQL replication

There are a number of different methods of implementing MySQL replication, these include standard master-slave replication, and master-master replication.

  • Master-Slave
    • Multi-Master Replication Manager for MySQL http://mysql-mmm.org/
    • Simple setup using own scripts
    • Investigate the options of letting Aegir set this up
  • Master-Master
  • Nightly backups using mysqldump: Not ideal, as this would potentially lose up to 24 hours worth of data. However, it is the simplest solution. Note, our current solution is no better than this, and could lose up to 24 hours worth of data.

Use of NFS of similar file server

This would make the process of synchronising files between two applications servers much simpler (it actually wouldn't need to be done, as the NFS mounts would be identical on both/all applications servers). An NFS server wouldn't require much processing power or memory, but would require a lot of disk space.

Multiple application servers

Load balancing

References/Footnotes

<references />

Workpackages
EMonocot
Personal tools