|
|
(11 intermediate revisions by 3 users not shown) |
Line 1: |
Line 1: |
− | A D4Science infrastructure manages various types of resources, such as: | + | [[Category:Administrator's Guide]] |
| + | A gCube infrastructure manages various types of resources, such as: |
| | | |
| * Hardware | | * Hardware |
Line 5: |
Line 6: |
| * Collections and Auxiliary Resources | | * Collections and Auxiliary Resources |
| | | |
− | Hardware resources include gLite storage elements and computing nodes as well as gCube hosting nodes (containers), while gCube services and external software fall into the second category type. Collections and auxiliary resources can be data, metadata, indices, schemas or transformation utilities, among others. | + | Hardware resources include gCube hosting nodes (containers) as well as gLite storage elements, computing and Cloud nodes, while gCube services and external software fall into the second category type. Collections and auxiliary resources can be data, metadata, indices, schemas or transformation utilities, among others. |
| | | |
− | All these resource information are put into gCube Information System (IS) which plays the role of the infrastructure's registry and supports the publishing, discovery and monitoring of all the parts that form the infrastructure. D4Science project offers the [http://monitor.d4science.research-infrastructures.eu/ Monitoring Portal] which is a set of tools which provide quick visualization of the multi-level organization of resources and the relationships among them. | + | All these resource information are collected by the [[gCore Based Information System]] (IS) which plays the role of the infrastructure's registry and supports the publishing, discovery and monitoring of all the resources belonging the infrastructure. A working instance of the Infrastructure Monitor is available in the [https://services.d4science.org/infrastructure-monitor D4Science Services Gateway]. |
| | | |
− | The rest of this section, quickly discusses the installation process for the Monitoring Portal and then describes the each tools that come with it, separately.
| + | For further information please see [https://wiki.gcube-system.org/gcube/Resource_Management this page]. |
− | | + | |
− | ==Monitor Portal Installation==
| + | |
− | Once a tomcat instance as been installed the monitor portlet wars have to be putted into the ''$CATALINA_HOME/webbaps/''.
| + | |
− | | + | |
− | This is the list of monitor portlets war containing the two applications below can be downloaded from here:
| + | |
− | [[http://monitor.d4science.research-infrastructures.eu/training/WARS.tar.gz | monitoring application WAR(s)]]
| + | |
− | | + | |
− | * Infrastructure Viewer
| + | |
− | * Advanced Monitoring
| + | |
− | | + | |
− | | + | |
− | | + | |
− | === Configuration ===
| + | |
− | Each portlet have a configuration file where the Infrastructures VO are specified.
| + | |
− | | + | |
− | ==== Configuring Infrastructure Viewer ====
| + | |
− | The configuration file path is ''{applicationFolder}/XML/scopedata.xml''.
| + | |
− | | + | |
− | The scopedata file have this structure:
| + | |
− | <source lang="xml">
| + | |
− | <?xml version="1.0" encoding="UTF-8"?>
| + | |
− | <infrastructures>
| + | |
− | <infrastructure>
| + | |
− | <name>d4science</name>
| + | |
− | <vos>
| + | |
− | <vo>
| + | |
− | <name>d4science</name>
| + | |
− | <src>ServiceMap_d4science.research-infrastructures.eu.xml</src>
| + | |
− | <scope>/d4science.research-infrastructures.eu</scope>
| + | |
− | </vo>
| + | |
− | </vos>
| + | |
− | </infrastructure>
| + | |
− | <infrastructures>
| + | |
− | </source>
| + | |
− | | + | |
− | Tags:
| + | |
− | * '''infrastructures''': the infrastructures list.
| + | |
− | ** '''infrastructure''': a single infrastructure.
| + | |
− | *** '''name''': the infrastructure name (like gcube or d4science)
| + | |
− | *** '''vos''': the vo list.
| + | |
− | **** '''vo''': a single vo.
| + | |
− | ***** '''name''': the vo name.
| + | |
− | ***** '''src''': the vo ServiceMap file (located in ''$GLOBUS_LOCATION/config'' dir).
| + | |
− | ***** '''scope''': the vo scope.
| + | |
− | | + | |
− | [[Media:scopedata.xml|Here]] a complete sample.
| + | |
− | | + | |
− | When a new VO is added, a new vo tag is needed.
| + | |
− | The VRE are discovered automatically.
| + | |
− | | + | |
− | ==== Configuring Advanced Monitoring ====
| + | |
− | | + | |
− | You can refer to the Infrastructure Viewer guide for the setting of the Infrastructure / VO(s).
| + | |
− | You should also edit another configuration file which is located ''{applicationFolder}/config/config.properties''.
| + | |
− | | + | |
− | '''ONLY the default scope property MUST be changed.'''
| + | |
− | | + | |
− | == Guide ==
| + | |
− | | + | |
− | === Infrastructure Viewer ===
| + | |
− | The interface of the tool is directly provided at [http://monitor.d4science.research-infrastructures.eu/iv/ Infrastructure Viewer]. Currently, it is also the default tool at which the user is redirected by following the general URL of the [http://monitor.d4science.research-infrastructures.eu/ Monitoring Portal]. The report concerning this tool can be found [https://technical.wiki.d4science.research-infrastructures.eu/documentation/index.php/Infrastructure_Viewer here].
| + | |
− | | + | |
− | === Live Monitoring ===
| + | |
− | The Live Monitoring can be found at the [http://monitor.d4science.research-infrastructures.eu/monitoring/ Live Monitoring]. A sample screenshot is shown below. Functionality is described [https://technical.wiki.d4science.research-infrastructures.eu/documentation/index.php/Administration#VRE_Monitoring here]. This guide can also be found by following the "Help" link at the top right hand corner of the portlet itself.
| + | |
− | | + | |
− | === Advanced Monitoring ===
| + | |
− | Last but not least of the tools provided for monitoring the d4science infrastructure is the [http://monitor.d4science.research-infrastructures.eu/rm/ Advanced Monitoring]. For more detailed information Its technical guide can be found [https://technical.wiki.d4science.research-infrastructures.eu/documentation/index.php/Resource_Management here].
| + | |
Hardware resources include gCube hosting nodes (containers) as well as gLite storage elements, computing and Cloud nodes, while gCube services and external software fall into the second category type. Collections and auxiliary resources can be data, metadata, indices, schemas or transformation utilities, among others.