Project

General

Profile

D64 OpenAIRE Maintenance Report » History » Version 7

Claudio Atzori, 13/12/2016 11:05 AM

1 1 Marek Horst
h1. D6.4 OpenAIRE Maintenance Report (v1, 9th of December 2016)
2
3
{{toc}}
4
5
h2. Overview
6
7
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. 
8
9
The official maintenance of the OpenAIRE2020 services began on January 1st, 2015 when the project started.
10
11
h2. Deployment
12
13
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":http://wiki.openaire.eu/xwiki/bin/view/OpenAIREplus%20Specific/WP5%20Maintenance%20Report.
14
15
_@Paweł: are there any new services in maintenance since OpenAIRE+ project worth mentioning here?_
16
17
h2. Documentation
18
19 7 Claudio Atzori
h3. D-Net services
20
21 6 Claudio Atzori
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 facilitate the deployment process all the software artifacts are automatically built on a continuous integration system ("Jenkins":https://ci.research-infrastructures.eu) and hosted on a dedicated maven repository ("nexus":http://maven.research-infrastructures.eu/nexus), while webapp builds are made available via "http server":http://ppa.research-infrastructures.eu/ci_upload.
22
23 7 Claudio Atzori
The D-Net services deployment is performed in subsequent stages:
24 6 Claudio Atzori
* The development infrastructure plays the role of test bench for the integration of the software developed by different institutions. It runs mostly un-released code and contains mock or subsets of the data available on the production system.
25
* The beta infrastructure runs only released code. Its 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.
26 1 Marek Horst
* The production infrastructure runs only code that was tested on the beta system.
27
28 7 Claudio Atzori
h3. Zenodo
29 1 Marek Horst
30
Zenodo repository is deployed according to the process described at http://invenio-software.org/wiki/Project/OpenAIREplus/ReleaseProcess.
31
32 3 Marek Horst
_@Lars: link does not work anymore, can you provide the proper one?_
33 7 Claudio Atzori
34
h3. Information Inference Service
35 1 Marek Horst
36 4 Marek Horst
"Information Inference Service":https://github.com/openaire/iis versioning and deployment is described on "IIS versioning and deployment":https://issue.openaire.research-infrastructures.eu/projects/openaire/wiki/IIS_versioning_and_deployment wiki page.
37 1 Marek Horst
38 5 Claudio Atzori
h2. [[D-NET workflows]]
39 3 Marek Horst
40
_@Claudio: could you fill that in?_
41
42 1 Marek Horst
h2. Services status
43
44
h3. D-NET backend services
45
46
_@Claudio: could you fill that in? Probably you can rely on http://wiki.openaire.eu/xwiki/bin/view/OpenAIREplus%20Specific/WP5%20Maintenance%20Report_
47
48
h3. Portal
49
50
_@Paweł: 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_
51
52 3 Marek Horst
h3. Zenodo
53 1 Marek Horst
54 3 Marek Horst
Zenodo repository employs an instance of the Invenio software, developed by CERN.
55 2 Marek Horst
56 1 Marek Horst
_@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_
57
58
h3. DM hadoop cluster
59
60
CDH version: @cdh4.3.1@
61
62
h3. IIS hadoop cluster
63
64
CDH version: @cdh4.3.1@, replaced with @cdh5.5.2@ on November 20, 2016, to be replaced with @cdh5.9.0@
65
66
h3. Content status
67
68
|*data type*|*count*|
69
|publications|17460368|
70
|datasets|3226586|
71
|projects|653268|
72
|organizations|64591|
73
|authors|16188328|
74
|EuropePMC XML contents|1574358|
75
|PDF contents|2227458|
76
77
Based on IIS report generated on November 20, 2016.
78
79
h3. Change Log for servers administration operations
80
81
_@Paweł: could you fill that in? This could be similar to: http://wiki.openaire.eu/xwiki/bin/view/OpenAIREplus%20Specific/Change%20Log%20for%20servers%20administration%20operations_
82
83
h2. Major modifications
84
85
h3. Introducing CDH5 IIS cluster hosted in OCEAN infrastructure
86
87
Slave node specification:
88
* Huawei RH1288 V3
89
* CPU: 2x Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz (24 cores, 48 threads)
90
* RAM: 128GB
91
* HDD: 4x SATA 6TB 7.2K RPM (HDFS)
92
93
Cluster summary (16 slaves):
94
* CPU: 384 cores, 768 threads
95
* RAM: 2048GB
96
* HDD: 384TB (HDFS)
97
98
YARN available resources:
99
* vcores: 640
100
* memory: 1.44TB
101
* HDFS: 344TB
102
103
h3. Incorporating resources from old CDH4 IIS cluster into existing DM CDH4 cluster
104
105
_@Paweł: are you aware of any other major modifications regarding other services such as new portal version etc?_
106
107
h2. System downtimes
108
109
_@Paweł: could you fill that in? We could create dedicated with entry similar to:
110
http://wiki.openaire.eu/xwiki/bin/view/OpenAIREplus%20Specific/History%20of%20system%20outages
111
and link it here._