D64 OpenAIRE Maintenance Report » History » Version 21
D6.4 OpenAIRE Maintenance Report (v1, 9th of December 2016)¶
- D6.4 OpenAIRE Maintenance Report (v1, 9th of December 2016)
- Information Space
- OpenAIRE workflows
- Software life-cycle
- Infrastructure services
- Architectural changes
- System downtimes
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).
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
|EuropePMC XML fulltext||1574358|
Table based on IIS report generated on November 20, 2016.
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.
How the system is maintained
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¶
@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
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
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.
@Paweł: are there any new services in maintenance since OpenAIRE+ project worth mentioning here?
DM hadoop cluster¶
IIS hadoop cluster¶
cdh4.3.1, replaced with
cdh5.5.2 on November 20, 2016, to be replaced with
Change Log for servers administration operations¶
@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
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)
- CPU: 384 cores, 768 threads
- RAM: 2048GB
- HDD: 384TB (HDFS)
- vcores: 640
- memory: 1.44TB
- HDFS: 344TB
Incorporating resources from old CDH4 IIS cluster into existing DM CDH4 cluster¶
@Paweł: are you aware of any other major modifications regarding other services such as new portal version etc?
@Paweł: could you fill that in? We could create dedicated with entry similar to:
and link it here.