- EUDAT Primer
- Configure B2SAFE
- B2STAGE for Site Administrator
- PIDs in EUDAT
- iRODS Deployment
- The dCache to iRODS connection at SURFSara
- B2ACCESS Management
- B2ACCESS Service Integration
- B2ACCESS Usage
- B2FIND Integration
- B2FIND Usage
- B2HANDLE for communities
- B2HANDLE for end-users
- B2SHARE Advanced search
- B2SHARE Deployment
- B2SHARE FAQ
- B2SHARE HTTP REST API
- B2SHARE Usage
- How to join B2HOST as a Provider
- Joining B2SAFE
- License Selector
- Publish from B2DROP to B2SHARE
- Using B2SAFE
Documentation of B2HOST (Service Hosting Framework) for current or future EUDAT providers explaining how an infrastructure can join the service and operate its hosting environment within the EUDAT CDI.
Modified: 27 July 2015
The EUDAT Collaborative Data Infrastructure offers a Service Hosting Framework called B2HOST that allows communities to deploy and operate their own applications and data-oriented services on machines next to the data storage location. For more information about the service please see the B2HOST user documentation.
Providers can join B2HOST by contributing with PaaS or IaaS services which will be made available to EUDAT community service administrators, who will be responsible for deploying and administering community data services on top of them. This document describes the process a provider has to follow in order to be part of the B2HOST offering.
Steps to join B2HOST
In order to join B2HOST, a provider first needs to appoint a contact person,¬†the Site Resource Manager, who will be in charge of managing the site's resources within EUDAT. This information together with a description of the hosting environment will be included in a ticket in the EUDAT Helpdesk, as per the screenshot below. Please use the queue "Resources" for doing this.
Figure 1. Using the EUDAT helpdesk to register a new hosting environment.
The ticket dispatcher then may contact you for further information regarding the hosting environment. You can check the information about the current offering in the Resource Coordination Tool.
Requirements for the infrastructure provider
When joining B2HOST, you will need to offer access to the resources to the administrators who will deploy the community services and allow some firewall configuration. These are described below.
The users of B2HOST should be offered the possibility of opening certain ports in the site's firewall under the following circumstances:
- the service requires the use of these ports
- and the service doesn't present any (known) vulnerability or exploit.
The providers may run when necessary security scans for proving the robustness of the service and can ask the administrator for further measures to secure it. Several examples can be found in the B2HOST user documentation.
The infrastructure is up and running, what now?
In order for your hosting environment to be used widely, it needs to be advertised in the EUDAT Site and Service Registry. EUDAT communities can apply to deploy their services in B2HOST through the EUDAT Resource Coordination Tool. You will also need to monitor the services running in your infrastructure, publishing some of your data through the EUDAT Monitoring service. More information is available below.
EUDAT Site and Service Registry
Services running in B2HOST should be registered in the EUDAT Site and Service Registry. It is up to the Site Resource Manager to do so for the community services running in the site's hosting environment. The currently registered services are available here; please note that you need a valid x509-certificate to access the website. Instructions about how to register new services can be found in the online documentation.
Resource Coordination Tool
EUDAT communities who want to deploy services in B2HOST in a provider's service hosting environment should apply for it first in the Resource Coordination Tool. Detailed information for community managers about how to do this can be found in the corresponding documentation. The Site Resource Manager or contact person for the hosting environment within B2HOST should reply to the request and when necessary ask for further information. The whole process is handled via tickets through the EUDAT Helpdesk system.
The deployed services should be monitored as well. Please refer to the monitoring documentation for more information.
Cristina Manzano, email@example.com
Carl Johan H√•kansson, firstname.lastname@example.org