|
|
| (169 intermediate revisions by 13 users not shown) |
| Line 1: |
Line 1: |
| − | == Platform Wide Dependencies ==
| + | [[Category:Administrator's Guide]] |
| | | | |
| − | == Environment Setup ==
| |
| | | | |
| − | == Keeper ==
| + | The Core Services are the minimal set of gCube Services needed to setup and manage VOs and to create dynamic VREs in a gCube infrastructure. Due to their nature and the deployment scenario we currently adopt/suggest, part of this group of services must be statically deployed. This section of the manual explains how to install, configure and verify single instances of such services. |
| | | | |
| − | === Pre-installation setup ===
| + | Please, refer to [[Administration|How to create a Virtual Organization]] section for a detailed explanation of their suggested deployment scenario (distribution, replication, etc.). |
| − | Actions to be performed before initiating the installation of this service.
| + | |
| | | | |
| − | === Main installation procedure === | + | == [[Information System Installation]] == |
| − | Describe in full detail all required steps for installing/deploying all components of the service. Group the steps in subparagraphs providing a meaningful header. This section should contain instructions for at least the following sub-services:
| + | |
| − | * Package Repository
| + | |
| − | * DL Management and
| + | |
| − | * Hosting Node Management
| + | |
| | | | |
| − | === Post-installation configuration === | + | == [[VRE Management Installation]] == |
| − | Configuration files that have to be edited after the installation. Scripts that have to be run that take care of post installation activities.
| + | |
| | | | |
| − | === Testing and verifying the installation === | + | == Security-related Services Installation == |
| − | Provide instructions that will assist the administrator in verifying that the service has been installed and is running appropriately. Troubleshooting of the installation together with error messages and common compensation actions should be provided in detail in chapter 4.
| + | : <strike>[[SOA3_HowTo | SOA3 Components Installation]]</strike> |
| | + | : <strike>[[Shibboleth_and_gCube | Shibboleth Configuration]]</strike> |
| | + | : <strike>[[Argus Installation]]</strike> |
| | + | : [[Authorization_service_installation | How to install the Authorization Service]] |
| | | | |
| − | === Installation troubleshooting === | + | == [[Usage Tracker Installation]] == |
| − | Things that can go wrong. Error messages that my appear. Workarounds to common problems
| + | |
| − | | + | |
| − | == Broker & Matchmaker (BMM) ==
| + | |
| − | The BMM Service is composed by the following components:
| + | |
| − | • The BMM Connector (Java Library) and the BMM API (Java Library) allow clients (e.g. the DL Management service) to send a matching request, and notify them with the response.
| + | |
| − | • The DIS Connector (Java Library) is in charge of keeping up-to-date tracks of the DHN profiles received from the DIS and to query the DIS in order to gather information the service or the algorithm needs for their computations.
| + | |
| − | • The BMM Service (WSRF Service) provides the core functionalities of the BMM component. By invoking the DIS Connector it queries the DIS in order to gather information about packages, then it forwards the BMM Connector request to the BMM Algorithm and, when the response is ready, it returns back the result.
| + | |
| − | • The BMM Utils (Java Library) is a library shared by other components. It defines exceptions and provides the validator used to parse the request and the response, as well as other helper classes.
| + | |
| − | • The BMM Algorithm (Java Library) calculates, by running a customized version of first-fit algorithm, the associations among packages and DHNs.
| + | |
| − | | + | |
| − | === Pre-installation setup ===
| + | |
| − | Actions to be performed before initiating the installation of this service.
| + | |
| − | | + | |
| − | === Main installation procedure ===
| + | |
| − | Describe in full detail all required steps for installing/deploying all components of the service. Group the steps in subparagraphs providing a meaningful header. This section should contain instructions for at least the following sub-services:
| + | |
| − | * Package Repository
| + | |
| − | * DL Management and
| + | |
| − | * Hosting Node Management
| + | |
| − | | + | |
| − | === Post-installation configuration ===
| + | |
| − | Configuration files that have to be edited after the installation. Scripts that have to be run that take care of post installation activities.
| + | |
| − | | + | |
| − | === Testing and verifying the installation ===
| + | |
| − | Provide instructions that will assist the administrator in verifying that the service has been installed and is running appropriately. Troubleshooting of the installation together with error messages and common compensation actions should be provided in detail in chapter 4.
| + | |
| − | | + | |
| − | === Installation troubleshooting ===
| + | |
| − | Things that can go wrong. Error messages that may appear. Workarounds to common problems
| + | |
| − | | + | |
| − | == DILIGENT Information Service (DIS) ==
| + | |
| − | | + | |
| − | The following components compose the DILIGENT Information Service:
| + | |
| − | *DIS-IP (Library) – The DIS-IP is responsible for registering/unregistering a group of resource properties as Aggregator Source to one or more DIS-ICs. It also allows to register/unregister groups of Topics in the DIS-Broker.
| + | |
| − | *DIS-HLSClient (Library) – The DIS-HLSClient is a library used by DILIGENT services to access the information maintained by the DILIGENT Information Service. Using a DIS-HLSClient it is possible to query a DIS-IC to discover Profiles or WS-Resource properties.
| + | |
| − | *DIS-IC (WSRFService) – This service is the Information Collector (IC) of all the data published in the DIS. It is implemented as Aggregator Sink that collects RPs from the registered (via DIS-IP) Aggregator Sources.
| + | |
| − | *DIS-BDIIClient (WSRFService) – This service is in charge of harvesting resource information from the BDII Server1 it has been configured to interact with. The gathered information is manipulated in order to make it compliant with the schema adopted in DILIGENT. Then such information is published as WS-Resources via the DIS-IP and as a DILIGENT Resource of type gLiteResource using the mechanism offered by the DIS-Registry Service.
| + | |
| − | *DIS-Registry (WSRFService) – This service provides registration and un-registration facilities for the DILIGENT resources profiles.
| + | |
| − | *DILIGENTProvider (Library) – This operation provider adds resource properties to the group of properties registered by a service in the DIS-IC. This additional information allows enlarging the spectrum of functionalities offered to identify the source that publishes the data and to perform fine-grained queries.
| + | |
| − | *DIS-Broker (WSRFService) – This service provides registration/unregistration of Topics (events to be notified on) for DILIGENT Services. This allows clients to subscribe to/unsubscribe from topics without having to know the physical locations of the services that expose them.
| + | |
| − | | + | |
| − | === Pre-installation setup ===
| + | |
| − | | + | |
| − | The DIS core Services (DIS-Registry, DIS-Broker and DIS-IC), are VO specific services ( there is the need of an instance of those services for each VO). Starting from the root VO ( the "diligent" root VO), but at the time being also all the sub-VO (i.e. ARTE) need a manual installation.
| + | |
| − | The root DIS is the first DILIGENT services that has to be installed in the infrastructure: it will contain all DHN Profiles and RI Profiles of Services running on the root VO and DHN profiles of Sub-VO node ( that can be assigned to sub-VOs by VO Managers).
| + | |
| − | | + | |
| − | The Installation of the root DIS requires at least 3 nodes:
| + | |
| − | | + | |
| − | * the DIS-Registry DHN
| + | |
| − | | + | |
| − | * the DIS-Broker DHN
| + | |
| − | | + | |
| − | * the DIS-IC DHN
| + | |
| − | | + | |
| − | The DIS-BDIIClient is a VO specific Services and is no needed at root VO level.
| + | |
| − | In order to speed up the performance and exploits the distributed nature of the GT4 Aggregator Framework, the best DIS Services deployment strategy would be:
| + | |
| − | | + | |
| − | * Deploy the DIS-Broker and the DIS-Registry on the same DHN
| + | |
| − | | + | |
| − | * Deploy the DIS-IC on a separate DHN.
| + | |
| − | | + | |
| − | The following installation documentation assumes that this is the target deployment schema.
| + | |
| − | | + | |
| − | === Main installation procedure ===
| + | |
| − | | + | |
| − | The DIS Installation needs a manual change on the DHN behaviour. The HNM in general is configured to publish the RI profiles of the codeployed services and the related DHN profile on the root VO. In case the HNM is codeployed toghether with DIS Services (so it has to register Profiles using the codeployed instance of the DIS-Registry) the DHN has to be configured to act as a "root" DHN. The related HNMService inthis context will create all the DIS Running Instance Profiles (togheter with the DHN profile), but it will be DIS-Registry itself that will register these profiles.
| + | |
| − | | + | |
| − | ==== DHN root Installation ====
| + | |
| − | | + | |
| − | The "root" DHN has to be installed following the [http://ddwiki.di.uoa.gr/mediawiki/index.php/DHN_Installation Admin guide]. Once the installation has been done, the only change to standard DHN installation is on the HNM Service JNDI file:
| + | |
| − | * The "rootDHN" parameter has to be set to true ( the DIS DHN is also of type Static)
| + | |
| − | | + | |
| − | ==== DIS-IC Installation ====
| + | |
| − | | + | |
| − | TBD
| + | |
| − | | + | |
| − | ==== DIS-Broker Installation ====
| + | |
| − | | + | |
| − | The DISBroker ServiceArchive 0_3_0 can be downloaded from the [http://grids17.eng.it/engrepository/ Eng repository ]. These are the installation steps to follow:
| + | |
| − | * Unpack the ServiceArchive tar.gz file;
| + | |
| − | * type globus-deploy-gar org_diligentproject_informationservice_disbroker.gar to deploy the DIS-Broker Service on the local container;
| + | |
| − | | + | |
| − | DONE!
| + | |
| − | | + | |
| − | ==== DIS-Registry Installation ====
| + | |
| − | | + | |
| − | The DISRegistry ServiceArchive 0_3_0 can be downloaded from the [http://grids17.eng.it/engrepository/ Eng repository ]. These are the installation steps to follow:
| + | |
| − | * Unpack the ServiceArchive tar.gz file;
| + | |
| − | * type globus-deploy-gar org_diligentproject_informationservice_disregistry.gar to deploy the DIS-Registry Service on the local container;
| + | |
| − | | + | |
| − | DONE!
| + | |
| − | | + | |
| − | ==== Security Setting ====
| + | |
| − | | + | |
| − | All DIS services can be configured to run in a secure/unsecure context. In case the VO to deploy has to run in a secure way the stardard installation will provide ''server-config.wsdd'' files that already contain security-descriptor for DIS services.
| + | |
| − | In case the VO has to be deployed without security just:
| + | |
| − | * enter the specific container folder of DIS services (i.e for DIS-Registry : $GLOBUS_LOCATION/etc/org_diligentproject_informationservice_disregistry )
| + | |
| − | * copy the content of ''deploy-server.wsdd_NOSEC'' file inside ''server-config.wsdd'' file
| + | |
| − | * this will remove the link to the service security-descriptor and has to be done for all DIS services.
| + | |
| − | | + | |
| − | === Post-installation configuration ===
| + | |
| − | | + | |
| − | After the deployment the VOMap for the VO the DIS installed refers to has to be properly configured. So in case of /diligent root VO just change the file ''VOMap_diligent.xml'' located into the $GLOBUS_LOCATION/etc/org_diligentproject_keeperservice_hnm/VOMaps modifyng service endpoint according to your DIS installation. In case of sub-VO DIS installation just creates a VOMap_<yourSubVo>.xml file containing as above the endpoint to your DIS installation.
| + | |
| − | | + | |
| − | === Testing and verifying the installation ===
| + | |
| − | Provide instructions that will assist the administrator in verifying that the service has been installed and is running appropriately. Troubleshooting of the installation together with error messages and common compensation actions should be provided in detail in chapter 4.
| + | |
| − | | + | |
| − | === Installation troubleshooting ===
| + | |
| − | Things that can go wrong. Error messages that my appear. Workarounds to common problems
| + | |
| − | | + | |
| − | == VDL Generator ==
| + | |
| − | | + | |
| − | === Pre-installation setup ===
| + | |
| − | Actions to be performed before initiating the installation of this service.
| + | |
| − | | + | |
| − | === Main installation procedure ===
| + | |
| − | Describe in full detail all required steps for installing/deploying all components of the service. Group the steps in subparagraphs providing a meaningful header. This section should contain instructions for at least the following sub-services:
| + | |
| − | * Package Repository
| + | |
| − | * DL Management and
| + | |
| − | * Hosting Node Management
| + | |
| − | | + | |
| − | === Post-installation configuration ===
| + | |
| − | Configuration files that have to be edited after the installation. Scripts that have to be run that take care of post installation activities.
| + | |
| − | | + | |
| − | === Testing and verifying the installation ===
| + | |
| − | Provide instructions that will assist the administrator in verifying that the service has been installed and is running appropriately. Troubleshooting of the installation together with error messages and common compensation actions should be provided in detail in chapter 4.
| + | |
| − | | + | |
| − | === Installation troubleshooting ===
| + | |
| − | Things that can go wrong. Error messages that my appear. Workarounds to common problems
| + | |
| − | | + | |
| − | == Dynamic Virtual Organization Support (DVOS) ==
| + | |
| − | | + | |
| − | === Pre-installation setup ===
| + | |
| − | Actions to be performed before initiating the installation of this service.
| + | |
| − | | + | |
| − | === Main installation procedure ===
| + | |
| − | Describe in full detail all required steps for installing/deploying all components of the service. Group the steps in subparagraphs providing a meaningful header. This section should contain instructions for at least the following sub-services:
| + | |
| − | * Package Repository
| + | |
| − | * DL Management and
| + | |
| − | * Hosting Node Management
| + | |
| − | | + | |
| − | === Post-installation configuration ===
| + | |
| − | Configuration files that have to be edited after the installation. Scripts that have to be run that take care of post installation activities.
| + | |
| − | | + | |
| − | === Testing and verifying the installation ===
| + | |
| − | Provide instructions that will assist the administrator in verifying that the service has been installed and is running appropriately. Troubleshooting of the installation together with error messages and common compensation actions should be provided in detail in chapter 4.
| + | |
| − | | + | |
| − | === Installation troubleshooting ===
| + | |
| − | Things that can go wrong. Error messages that my appear. Workarounds to common problems
| + | |
| − | | + | |
| − | == Portals ==
| + | |
| − | | + | |
| − | === Pre-installation setup ===
| + | |
| − | Actions to be performed before initiating the installation of this service.
| + | |
| − | | + | |
| − | === Main installation procedure ===
| + | |
| − | Describe in full detail all required steps for installing/deploying all components of the service. Group the steps in subparagraphs providing a meaningful header. This section should contain instructions for at least the following sub-services:
| + | |
| − | * Package Repository
| + | |
| − | * DL Management and
| + | |
| − | * Hosting Node Management
| + | |
| − | | + | |
| − | === Post-installation configuration ===
| + | |
| − | Configuration files that have to be edited after the installation. Scripts that have to be run that take care of post installation activities.
| + | |
| − | | + | |
| − | === Testing and verifying the installation ===
| + | |
| − | Provide instructions that will assist the administrator in verifying that the service has been installed and is running appropriately. Troubleshooting of the installation together with error messages and common compensation actions should be provided in detail in chapter 4.
| + | |
| − | | + | |
| − | === Installation troubleshooting ===
| + | |
| − | Things that can go wrong. Error messages that my appear. Workarounds to common problems
| + | |
The Core Services are the minimal set of gCube Services needed to setup and manage VOs and to create dynamic VREs in a gCube infrastructure. Due to their nature and the deployment scenario we currently adopt/suggest, part of this group of services must be statically deployed. This section of the manual explains how to install, configure and verify single instances of such services.
