D6.4 OpenAIRE Maintenance Report (v1, 9th of December 2016)¶

• Table of contents
• D6.4 OpenAIRE Maintenance Report (v1, 9th of December 2016)
  • Overview
  • Information Space
    • Data Provider
    • Content Status
  • OpenAIRE workflows
  • Services
    • Software life-cycle
      • D-NET services
      • Information Inference Service
      • Portal
      • Zenodo
    • Infrastructure services
      • Hadoop clusters
      • Databases
      • Piwik
      • box.openaire.eu
    • Architectural changes
      • Introducing CDH5 IIS cluster hosted in OCEAN infrastructure
      • Incorporating resources from old CDH4 IIS cluster into existing DM CDH4 cluster
      • Deploying DNet postgress and mongodb databases on separate machines
    • System downtimes

Overview¶

This document contains information about the deployment, status of OpenAIRE2020 services and content, and the history of major modifications of the system hosted at ICM, Poland.

The official maintenance of the OpenAIRE2020 services began on January 1st, 2015 when the project started.

TODO: elaborate the following
The deliverable will consist in a high-level report on the status of

• OpenAIRE workflows (CNR),
• services (ICM),
• and Information Space (UNIBI).

Information Space¶

Brief description of the data model and status of content, i.e. numbers about data providers, their typology, publications, datasets, links... etc.
@UNIBI: your contribution is needed here

Data Provider¶

Content Status¶

data type	count
publications	17460368
datasets	3226586
projects	653268
organizations	64591
authors	16188328
EuropePMC XML fulltext	1574358
PDF fulltext	2227458

Table based on IIS report generated on November 20, 2016.

OpenAIRE workflows¶

The OpenAIRE aggregation system is based on the D-NET software toolkit. D-NET is a service-oriented framework specifically designed to support developers at constructing custom aggregative infrastructures in a cost-effective way. D-NET offers data management services capable of providing access to different kinds of external data sources, storing and processing information objects of any data models, converting them into common formats, and exposing information objects to third-party applications through a number of standard access API. Most importantly, D-NET offers infrastructure enabling services that facilitate the construction of domain-specific aggregative infrastructures by selecting and configuring the needed services and easily combining them to form autonomic data processing workflows.

The Enabling Layer contains the Services supporting the application framework. These provide functionalities such as Service registration, discovery, subscription and notification and data transfer mechanisms through ResultSet Services. Most importantly, these Services are configured to orchestrate Services of other layers to fulfil the OpenAIRE specific requirements and implement the OpenAIRE workflows.

Services¶

How the system is maintained

Software life-cycle¶

D-NET services¶

The D-NET services are shipped as web applications and deployed on the tomcat application server (v7.0.52) on three distinct systems: dev, beta, production. To support the deployment process all the software artifacts are automatically built on a continuous integration system (Jenkins) and hosted on a dedicated maven repository (nexus), while webapp builds are made available via http server. The mentioned tools supporting the software lifecycle are maintained by CNR.

The D-NET services deployment is performed in subsequent stages:

• The development infrastructure plays the role of test bench for the integration of the software developed by different institutions. It is maintained by CNR and runs mostly un-released code and contains mock or subsets of the data available on the production system.
• The beta infrastructure runs only released code. It is maintained by ICM and consists of the final integration stage where all the system workflows are tested on the real data (not necessarily the same data as the production system) before making them available to the production system. Although the software running on the beta system is not yet production ready, its portal is publicly accessible in order to showcase new features and data.
• The production infrastructure is maintained by ICM and runs only code that was tested on the beta system.

D-NET backend services are packed in four different web applications, each of them running on a dedicated tomcat instance.

@Claudio: could you fill that in? Probably you can rely on http://wiki.openaire.eu/xwiki/bin/view/OpenAIREplus%20Specific/WP5%20Maintenance%20Report

Information Inference Service¶

Information Inference Service versioning and deployment is described on IIS versioning and deployment wiki page.

Formerly IIS was being deployed on CDH4 cluster. Since October 1st, 2015 dedicated cdh5 branch was created where new SPARK modules were introduced and existing modules were optimized. On November 20, 2016 for the first time all inferences in production infrastructure were generated by IIS deployed on new CDH5 OCEAN cluster. Both stability and major performance increase were noticed, inference generation time decreased from over 2 days to 12 hours.

Portal¶

OpenAIRE portal is hosted at ICM. It uses Joomla! 3.6.2, a free dynamic portal engine and content management system (CMS).

The Joomla! depends on other upstream applications:

• Apache 2.4.7
• PHP 5.5.9
• MySQL 5.5.53
• OpenLDAP 2.4.31

Zenodo¶

Zenodo repository is deployed according to the process described at http://zenodo.readthedocs.io/projectlifecycle.html#release-process

Zenodo repository employs an instance of the Invenio software, developed by CERN.

@Lars: could you fill that in? You can do it in a similar way it was done in http://wiki.openaire.eu/xwiki/bin/view/Technical%20Specifications/Maintenance%20Report

Infrastructure services¶

Because OpenAIRE2020 services are a continuation and incremental extension of the services already present that resulted from OpenAIRE+ project, so they are still hosted on that same machines. More details are available at OpenAIRE+ WP5 Maintenance Report.

Hadoop clusters¶

DM hadoop cluster¶

CDH version: cdh4.3.1

IIS hadoop cluster¶

There were two IIS clusters deployed:

• old CDH4 IIS cluster, version cdh4.3.1, in operation until December 9, 2016
• new CDH5 IIS cluster deployed in OCEAN infrastructure supporting MRv2 on YARN, SPARK

CDH5 cluster version history:

• 5.5.2 deployment on March 22, 2016
• 5.5.2 -> 5.7.5 upgrade November 30, 2016
• 5.7.5 -> 5.9.0 upgrade December 8, 2016

Databases¶

database type	purpose	version
postgress	stats	9.1.23
postgress	DNet services	9.3.14
mongodb	DNet services	3.2.6
virtuoso	LOD	7.2

Piwik¶

Currently deployed Piwik version: 2.17.1, since December 6, 2016.

box.openaire.eu¶

Currently deployed OwnCloud instance version: 8.2.7, since October 19, 2016.

Architectural changes¶

Change Log for servers administration operations

Introducing CDH5 IIS cluster hosted in OCEAN infrastructure¶

Slave node specification:

• Huawei RH1288 V3
• CPU: 2x Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz (24 cores, 48 threads)
• RAM: 128GB
• HDD: 4x SATA 6TB 7.2K RPM (HDFS)

Cluster summary (16 slaves):

• CPU: 384 cores, 768 threads
• RAM: 2048GB
• HDD: 384TB (HDFS)

YARN available resources:

• vcores: 640
• memory: 1.44TB
• HDFS: 344TB

Incorporating resources from old CDH4 IIS cluster into existing DM CDH4 cluster¶

This task was possible after shutting down old IIS CDH4 cluster what happened on December 9, 2016.

Deploying DNet postgress and mongodb databases on separate machines¶

Separating openaire-services database instances into dedicated ones (since June 27, 2016):

• openaire-services-postgresql
• openaire-services-mongodb

System downtimes¶

• [planned] November 14, 2016, 2 hours. #2423 dealing with Linux Dirty COW vulnerability: kernel upgrade, OpenAIRE services restart.