2013.12 WP5: iMarine Data e-Infrastructure Deployment and Operation Monthly Activity By Task and Beneficiary

From IMarine Wiki

Jump to: navigation, search

Contents

This WP5 Activity Report described the activities performed in December 2013 by Beneficiary and Task.

It is part of the December 2013 Monthly Activity Report.

T5.1 iMarine Data e-Infrastructure Operation

CERN Activities

CERN was coordinating and performing the infrastructure upgrade to gCube 2.17.0 at the beginning of the month(2337)

In addition the QA infra has been then upgrade to gCube 2.17.1 (2469) and the production was also upgraded to 2.17.1 before the holidays.

Some activity related to JAVA 7 integration were performed:


none


  • Infrastructure upgrade to gCube 2.17.0 and 2.17.1

CNR Activities

  • Data recovered from backup of mongodb server, because a user deleted a full iMarine shared folder, due to a bug (now fixed).


none

T5.2 iMarine Data e-Infrastructure Nodes Provision

CNR Activities

  • CNR has been keeping up and running the provided nodes hosting development, testing and production GHNs, UMD and project management services.
  • new OBIS db node to load Unesco data
  • Two new server, one for production, one for development, for the upgraded version of StatBase
  • New Xen servers added to the HW infrastructures, completing the resources with more 80 cpu, 384 GB RAM, 8 TB DISK


none


none

NKUA Activities

  • Maintenance of the provided nodes hosting GHNs, UMD and the gcube wiki.
  • Planning upgrade to UMD-3 and installation of Argus.


none


none

FAO Activities

None to report


No deviations and thus corrective actions were required.


None to report

T5.3 iMarine Data Infrastructure Availability, Monitoring and Accounting

CERN Activities

The portal accounting probe has been integrated into a WebApp, in order to remove the portal dependency to an external GHN (2215). In the context of this task a new version of the messaging producer gCF free has been developed.

A first version of a Nagios plugin to test Search availability has been developed and deployed on the production Nagios instance. It uses ASL HTTP API to run periodically search queries and check the correctness of results. (2450)


none


none

Personal tools