Difference between revisions of "IMarine Data E-Infrastructure Deployment and Operation: PoliciesDefinition"

Revision as of 15:36, 22 February 2012 (view source) Andrea.manzi (Talk | contribs) (→‎Service Participation Policy) ← Older edit		Latest revision as of 14:24, 21 March 2012 (view source) Leonardo.candela (Talk | contribs) m
(31 intermediate revisions by 2 users not shown)
Line 1:		Line 1:
−	This section describes the D4Science Ecosystem policies.	+	This section describes the <font color=red>D4Science Ecosystem policies</font>.
	Some of the policies are meant to be valid for the Ecosystem as a whole and as such they have Global scope.		Some of the policies are meant to be valid for the Ecosystem as a whole and as such they have Global scope.
Line 15:		Line 15:
	* Data		* Data
	* Software		* Software
−	* Sites ( Computation and storage)	+	* Sites (Computation and storage)
	The following policies have been defined :		The following policies have been defined :
Line 37:		Line 37:
	=== gCubeApps Acceptable Use Policy ===		=== gCubeApps Acceptable Use Policy ===
−	By accessing  gCubeApps deployed in  D4Science Ecosystem any User shall be deemed to accept these conditions of use:	+	By accessing  gCubeApps deployed into the D4Science Ecosystem any User shall be deemed to accept these conditions of use:
−	* Users may only use the gCube Apps to store, retrieve, query, serve, and execute its content that is owned, licensed or lawfully obtained by Users. As used As part of the gCubeApps, any User may be allowed to use certain software (including related documentation) provided by us or third party licensors. This software is neither sold nor distributed to Users and you may use it solely as part of the gCubeApps. Users may not transfer it outside the Services without specific authorization to do so.	+	* Users may only use the gCube Apps to store, retrieve, query, serve, and execute its content that is owned, licensed or lawfully obtained by them. As used as part of the gCubeApps, any User may be allowed to use certain software (including related documentation) provided by the  D4Science Ecosystem or third party licensors. This software is neither sold nor distributed to Users and they may use it solely as part of the gCubeApps. Users may not transfer it outside the Services without specific authorization to do so.
	* If Users create technology that works with a gCubeApp, they must comply with the current technical documentation applicable to that gCubeApp available in the [https://gcube.wiki.gcube-system.org/gcube/index.php/Developer%27s_Guide gCube Development WIKI].		* If Users create technology that works with a gCubeApp, they must comply with the current technical documentation applicable to that gCubeApp available in the [https://gcube.wiki.gcube-system.org/gcube/index.php/Developer%27s_Guide gCube Development WIKI].
−	* Users will reasonably cooperate with us to identify the source of any problem with the gCubeApps that we reasonably believe may be attributable to Users Content or any end user materials that the User control.	+	* Users will reasonably cooperate with the  D4Science Ecosystem to identify the source of any problem with the gCubeApps that may be attributable to Users Content or any end user materials that the User control.
−	* If we reasonably believe any of the User Content violates the law, infringes or misappropriates the rights of any third party , we will notify the User of the Prohibited Content and may request that such content be removed from the gCubeApps or access to it be disabled. If a User does not remove or disable access to the Prohibited Content within 2 business days of our notice, we may remove or disable access to the Prohibited Content or suspend its access to the gCubeApps.	+	* If the  D4Science Ecosystem reasonably believe any of the User Content violates the law, infringes or misappropriates the rights of any third party ,the User of the Prohibited Content will be notified and may request that such content be removed from the gCubeApps or access to it be disabled. If a User does not remove or disable access to the Prohibited Content within 2 business days of our notice, the  D4Science Ecosystem may remove or disable access to the Prohibited Content or suspend its access to the gCubeApps.
	== Service Level Agreement ==		== Service Level Agreement ==
Line 57:		Line 57:
	* [[#Data_Access_SLA|Data Access SLA]]		* [[#Data_Access_SLA|Data Access SLA]]
	* [[#Data_Storage_SLA|Data Storage SLA]]		* [[#Data_Storage_SLA|Data Storage SLA]]
		+	* [[#Support_Response_Time_SLA|Support Response Time SLA ]]
	* [[#Software_Hosting_SLA|Software Hosting SLA ]]		* [[#Software_Hosting_SLA|Software Hosting SLA ]]
		+	* [[#Scheduled_Ecosystem_Downtime_SLA|Scheduled Ecosystem Downtime SLA]]
	* [[#Time_Series_Management_SLA|Time Series Management SLA]]		* [[#Time_Series_Management_SLA|Time Series Management SLA]]
	* ...		* ...
Line 77:		Line 79:
	=== Data Storage SLA ===		=== Data Storage SLA ===
		+
		+	=== Support Response Time SLA ===
		+
		+	The Support Team as defined in the [http://wiki.i-marine.eu/index.php/Role_Support_Team Support Team page] is responsible for the resolution of all production support tickets related to the D4Science Ecosystem. This SLA covers incident tickets resolution time in the case of issue related to infrastructure accidents ( e.g. it does not cover the resolution time of the issues  coming from software bugs): <pre>High priority Incident Resolution time: < 4 hours</pre> <pre>Normal priority Incident Resolution time: < 2 days</pre> <pre>Low priority Incident Resolution time: < 1 week</pre>
	=== Software Hosting SLA ===		=== Software Hosting SLA ===
		+
		+	The Software Hosting SLA covers some element of the WAR Management Service which is offered to Users trough the [https://gcube.wiki.gcube-system.org/gcube/index.php/Web_Application_Management_Portlet  Web Application Management Portlet] and the [https://gcube.wiki.gcube-system.org/gcube/index.php/WAR_Management_Portlet  WAR Management Portlet]:
		+
		+	* Individual servers will deliver 100% uptime as monitored within the D4Science Ecosystem monitoring system . Only failures due to hardware and hypervisor layers delivering individual servers constitute Failures and so only those Failures are covered this SLA. Examples of Failures include power interruptions, hardware problems such as failures to a hard drive or power supply, and failures to the hypervisor environment supporting User WebApplications.
		+
		+	* The D4Science Ecostem will make reasonable efforts to insure that server storage is "persistent." In the event of hardware or software Failures as defined above, the D4Science Ecosystem will make reasonable attempts to return the Users to pre-Failure state including restoring the Application software as configured by the User and Data. Furthermore, these efforts will include supporting the User via telephone, chat or Email at the User's choosing. No guarantee whatsoever is provided on the success of any Users recovery.
		+
		+	* The D4Science Ecosystem  Portal allows a User to deploy a WebApplication in the D4Science Ecosystem. This SLA defines as well the maximum period each  WebApplication will need to be available and "Ready" to be exploited by the Users:<pre>WebApplication Activation cycle: < 15 minutes</pre>In the case of a  Activation cycle > 15 minutes Users must  open an Incident ticket trough the [https://support.d4science-ii.research-infrastructures.eu/ Support TRAC system].
		+
		+	=== Scheduled Ecosystem Downtime  SLA ===
		+
		+	Scheduled Ecosystem  Downtimes occur during a D4Science Ecosystem maintenance window, which can be scheduled for Infrastructure Upgrades or scheduled infrastructure interventions ( e.g. scheduled power cuts). This  SLA applies to the user notice period via electronic communication: <pre>
		+	Scheduled Ecosystem Downtime User notice > 24 hours </pre>
	=== Time Series Management SLA ===		=== Time Series Management SLA ===
Line 98:		Line 117:
	By participating in the D4Science Ecosystem any Site must agree to the following conditions.		By participating in the D4Science Ecosystem any Site must agree to the following conditions.
−	* The Site should provide and maintain, in the [[Role_Site_Manager | Site Manager]] page, contact information including but not limited to at least one Site Manager  who shall respond to enquiries in a timely fashion as defined in the [[Procedure_Infrastructure_Incident_Management| Incident Management]] procedure page.	+	* Every Site should appoint '''at least one person''' to the role of Site Manager. Contact information of each Site Manager should be in the [[Role_Site_Manager | Site Manager]] page. The Site Manager is requested to react to requests on Site management in an efficient manner (see [[Procedure_Infrastructure_Incident_Management| Incident Management]] procedure page)
−	** <font color="red">(alternative) Every Site should appoint '''at least one person''' to the role of Site Manager. Contact information of each Site Manager should be in the [[Role_Site_Manager | Site Manager]] page. The Site Manager is requested to react to requests on Site management in an efficient manner (see [[Procedure_Infrastructure_Incident_Management| Incident Management]] procedure page)</font>	+
	* When notified by the D4Science Ecosystem [[Role_Infrastructure_Manager| Infrastructure Managers]] of software patches and  updates required for security and stability, they should be applied to the Site's systems, as soon as reasonably possible in the circumstances. Other patches and updates should be applied following the upgrade plan prepared by the [[Role_Infrastructure_Manager| Infrastructure Managers]]  applying the [[Procedure_Infrastructure_Deployment | deployment and upgrade ]] procedure.		* When notified by the D4Science Ecosystem [[Role_Infrastructure_Manager| Infrastructure Managers]] of software patches and  updates required for security and stability, they should be applied to the Site's systems, as soon as reasonably possible in the circumstances. Other patches and updates should be applied following the upgrade plan prepared by the [[Role_Infrastructure_Manager| Infrastructure Managers]]  applying the [[Procedure_Infrastructure_Deployment | deployment and upgrade ]] procedure.
−	** <font color="red">(comment) Partial overlap with the previous</font>
	* Logged information, including information provided by Users or other Sites, should be used for administrative, operational, accounting, monitoring and security purposes only.		* Logged information, including information provided by Users or other Sites, should be used for administrative, operational, accounting, monitoring and security purposes only.
Line 118:		Line 135:
	=== Service Participation Policy ===		=== Service Participation Policy ===
−	This policy regulates the participation of [http://wiki.i-marine.eu/index.php/Community_Resources Community Resources] into the D4Science Ecosystem, in particular Resource exposed as remote Web-Services.	+	This policy regulates the participation of [http://wiki.i-marine.eu/index.php/Community_Resources Community Resources] into the D4Science Ecosystem as Federated Resources, in particular resources accessible as remote services. This policy applies to all remote Services and it works in junction with policies regulating each single Community.
		+
		+	* Every Federated Service should have at least one Resource Manager and their  contact information should be in the [http://wiki.i-marine.eu/index.php/Role_Support_Team Support Team] page.
		+
		+	* As member of the Support Team each Resource Manager is subscribed to the [mailto:support_team@d4science.org support team] mailing list and should partecipate to the Support Team Conference Call, if requested, to discuss about Issues affecting the D4Science Ecosystem.
		+
		+	* In the case of access to Federated Services regulated by User Credentials or any other Authentication mechanism, the D4Science Ecosystem will make use of encryption to ensure that access information are not public.
		+
		+	* The D4Science Ecosystem will keep track of the Federated Service access statistics trough its accounting system, and this data will be accessible only by the D4Science Ecosystem  [http://wiki.i-marine.eu/index.php/Role_Infrastructure_Manager Infrastructure Managers ] and if requested by each Federated Service Manager.
	=== Data source Participation Policy ===		=== Data source Participation Policy ===
Line 144:		Line 169:
	===Software Participation Policy ===		===Software Participation Policy ===
−	This policy regulates the deployment and hosting of User's  Web Applications into the D4Science Ecosystem, performed trough the [https://gcube.wiki.gcube-system.org/gcube/index.php/Web_Application_Management_Portlet  Web Application Management Portlet] and the [https://gcube.wiki.gcube-system.org/gcube/index.php/WAR_Management_Portlet  WAR Management Portlet]:	+	This policy regulates the deployment of User's  Web Applications into the D4Science Ecosystem, performed trough the [https://gcube.wiki.gcube-system.org/gcube/index.php/Web_Application_Management_Portlet  Web Application Management Portlet] and the [https://gcube.wiki.gcube-system.org/gcube/index.php/WAR_Management_Portlet  WAR Management Portlet]:
	* The D4Science Ecosystem is not responsible of the Web Application uploaded and hosted by the infrastructure.		* The D4Science Ecosystem is not responsible of the Web Application uploaded and hosted by the infrastructure.
Line 150:		Line 175:
	* Users should be aware of software licenses which regulate its WebApplication or any third party software included. The D4Science Ecosystem will not be responsible of any issue regulating licence infringement or illegal use of proprietary software.		* Users should be aware of software licenses which regulate its WebApplication or any third party software included. The D4Science Ecosystem will not be responsible of any issue regulating licence infringement or illegal use of proprietary software.
−	* User which uploads WebApplications, in the case they decide to share it with members of a  Virtual Research Environment (VRE), are responsible for any  misusage of the WebApplication by other Ecosystem Users.	+	* Users which upload WebApplications, in the case they decide to share it with members of a  Virtual Research Environment (VRE), are responsible for any  misusage of the WebApplication by other Ecosystem Users.
	* The D4Science Ecosystem by monitoring the User's Web Applications running behavior, can decide to remove  the WebApplications from the infrastructure in the extreme case where they could undermine the Infrastructure stability.		* The D4Science Ecosystem by monitoring the User's Web Applications running behavior, can decide to remove  the WebApplications from the infrastructure in the extreme case where they could undermine the Infrastructure stability.

---

Latest revision as of 14:24, 21 March 2012

This section describes the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem policies.

Some of the policies are meant to be valid for the Ecosystem as a whole and as such they have Global scope. This kind of policies are described in the Global Policies section.

The Policies regulating the level of service which the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem has to guarantee to its users are described in the Service Level Agreement section.

In the case of D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem Resource providers, the policies regulating the provision are described in the Infrastructure Participation Policies section.

Global Policies

The Policies wich are described in this section are global policies applied to Users accessing the infrastructure as consumers or providers of :

• Services
• Data
• Software
• Sites (Computation and storage)

The following policies have been defined :

• Infrastructure Acceptable Use Policy
• gCubeApps Acceptable Use Policy

Infrastructure Acceptable Use Policy

By registering in the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem any User shall be deemed to accept these conditions of use:

• The User shall not use the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem for any unlawful purpose and not (attempt to) breach or circumvent any administrative or security controls.
• The User shall respect intellectual property and confidentiality agreements.
• The User shall protect its access credentials (e.g. private keys or passwords).
• The User shall immediately report any known or suspected security breach or misuse of the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem or access credentials to the incident reporting locations specified by the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem.
• Use of the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem is at User's risk. There is no guarantee that the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem will be available at any time or that it will suit any purpose.
• Logged information is used for administrative, operational, accounting, monitoring and security purposes only.
• Resource Providers are entitled to regulate, suspend or terminate the User access, within their domain of authority, and the User shall immediately comply with their instructions.
• The User is liable for the consequences of violating any of these conditions of use

gCubeApps Acceptable Use Policy

By accessing gCubeApps deployed into the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem any User shall be deemed to accept these conditions of use:

• Users may only use the gCube Apps to store, retrieve, query, serve, and execute its content that is owned, licensed or lawfully obtained by them. As used as part of the gCubeApps, any User may be allowed to use certain software (including related documentation) provided by the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem or third party licensors. This software is neither sold nor distributed to Users and they may use it solely as part of the gCubeApps. Users may not transfer it outside the Services without specific authorization to do so.

• If Users create technology that works with a gCubeApp, they must comply with the current technical documentation applicable to that gCubeApp available in the gCube Development WIKI.

• Users will reasonably cooperate with the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem to identify the source of any problem with the gCubeApps that may be attributable to Users Content or any end user materials that the User control.

• If the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem reasonably believe any of the User Content violates the law, infringes or misappropriates the rights of any third party ,the User of the Prohibited Content will be notified and may request that such content be removed from the gCubeApps or access to it be disabled. If a User does not remove or disable access to the Prohibited Content within 2 business days of our notice, the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem may remove or disable access to the Prohibited Content or suspend its access to the gCubeApps.

Service Level Agreement

When describing the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem Service Level Agreements (SLAs) we refers to the levels of availability, serviceability, performance, operation, or other attributes of the Ecosystem. The level of service is specified as "target" and "minimum," which allows the user of the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem to be informed what to expect (the minimum), while providing a measurable (average) target value that shows the level of organization performance.

Since no Resource pricing is defined no penalties have been agreed in the case of non-compliance of the SLA .

The following D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem SLAs have been defined :

• Data Access SLA
• Data Storage SLA
• Support Response Time SLA
• Software Hosting SLA
• Scheduled Ecosystem Downtime SLA
• Time Series Management SLA
• ...

The D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem supports several Scientific Communities members grouped in Virtual Research Environments (VREs), therefore some VREs can have their own SLAs.

The following VREs SLAs have been defined:

• ICIS VRE SLA
• .....

Data Access SLA

By accessing data trough the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem any authorized user shall be deemed to accept these conditions of use:

• Any authorized user can use the data in any circumstance and for all usage, reproduce the data, modify the data, and make derivative data based upon the original data, communicate to the public, including the right to reproduce or display the data or copies thereof to the public and perform publicly, as the case may be, the data.

• Any authorized user cannot in any circumstance and for any usage redistribute the data or copies thereof, lend and rent the data or copies thereof, sub-license rights in the data or copies thereof.

Data Storage SLA

Support Response Time SLA

The Support Team as defined in the Support Team page is responsible for the resolution of all production support tickets related to the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem. This SLA covers incident tickets resolution time in the case of issue related to infrastructure accidents ( e.g. it does not cover the resolution time of the issues coming from software bugs):

High priority Incident Resolution time: < 4 hours

Normal priority Incident Resolution time: < 2 days

Low priority Incident Resolution time: < 1 week

Software Hosting SLA

The Software Hosting SLA covers some element of the WAR Management Service which is offered to Users trough the Web Application Management Portlet and the WAR Management Portlet:

• Individual servers will deliver 100% uptime as monitored within the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem monitoring system . Only failures due to hardware and hypervisor layers delivering individual servers constitute Failures and so only those Failures are covered this SLA. Examples of Failures include power interruptions, hardware problems such as failures to a hard drive or power supply, and failures to the hypervisor environment supporting User WebApplications.

• The D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecostem will make reasonable efforts to insure that server storage is "persistent." In the event of hardware or software Failures as defined above, the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem will make reasonable attempts to return the Users to pre-Failure state including restoring the Application software as configured by the User and Data. Furthermore, these efforts will include supporting the User via telephone, chat or Email at the User's choosing. No guarantee whatsoever is provided on the success of any Users recovery.

• The D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem Portal allows a User to deploy a WebApplication in the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem. This SLA defines as well the maximum period each WebApplication will need to be available and "Ready" to be exploited by the Users:

  WebApplication Activation cycle: < 15 minutes

  In the case of a Activation cycle > 15 minutes Users must open an Incident ticket trough the Support TRAC system.

Scheduled Ecosystem Downtime SLA

Scheduled Ecosystem Downtimes occur during a D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem maintenance window, which can be scheduled for Infrastructure Upgrades or scheduled infrastructure interventions ( e.g. scheduled power cuts). This SLA applies to the user notice period via electronic communication:

Scheduled Ecosystem Downtime User notice > 24 hours 

Time Series Management SLA

ICIS VREVirtual Research Environment. SLA

Infrastructure Participation Policies

Resource provision in the context of the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem is regulated by a defined set of policies:

• Site Participation Policy
• Service Participation Policy
• Data source Participation Policy
• Software Participation Policy

Site Participation Policy

By participating in the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem any Site must agree to the following conditions.

• Every Site should appoint at least one person to the role of Site Manager. Contact information of each Site Manager should be in the Site Manager page. The Site Manager is requested to react to requests on Site management in an efficient manner (see Incident Management procedure page)

• When notified by the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem Infrastructure Managers of software patches and updates required for security and stability, they should be applied to the Site's systems, as soon as reasonably possible in the circumstances. Other patches and updates should be applied following the upgrade plan prepared by the Infrastructure Managers applying the deployment and upgrade procedure.

• Logged information, including information provided by Users or other Sites, should be used for administrative, operational, accounting, monitoring and security purposes only.

• The participation in the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem as a Site shall not create any intellectual property rights in software, information and data provided to the Site or in data generated by the Site in the processing of jobs.

• Provisioning of resources to the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem is at the Site's risk. Any software provided by the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem is provided on an as-is basis only, and subject to its own license conditions. There is no guarantee that any procedure applied by the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem is correct or sufficient for any particular purpose. The D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem and other Sites are not liable for any loss or damage in connection with the Site participation in the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem.

• The Site shall comply with the Incident Management response procedures regarding the notification of security incidents and where appropriate, shall restore access as soon as reasonably possible.

• The Site shall comply with the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem operational procedures including the requirement to support at least the root VOVirtual Organization;.

• The D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem may control access to the Site for administrative, operational and security purposes and remove Site resource information from the Information Systems if the Site fails to comply with these conditions.

Service Participation Policy

This policy regulates the participation of Community Resources into the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem as Federated Resources, in particular resources accessible as remote services. This policy applies to all remote Services and it works in junction with policies regulating each single Community.

• Every Federated Service should have at least one Resource Manager and their contact information should be in the Support Team page.

• As member of the Support Team each Resource Manager is subscribed to the support team mailing list and should partecipate to the Support Team Conference Call, if requested, to discuss about Issues affecting the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem.

• In the case of access to Federated Services regulated by User Credentials or any other Authentication mechanism, the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem will make use of encryption to ensure that access information are not public.

• The D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem will keep track of the Federated Service access statistics trough its accounting system, and this data will be accessible only by the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem Infrastructure Managers and if requested by each Federated Service Manager.

Data source Participation Policy

Any data provider can promote its data repository by registering it in the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem.

• By registering a data repository, the data provider guarantees access to the data stored without any limitation on volume or number of access calls.

• A data provider is empowered to limit the access to its data to either a single community or to a single group of people operating in a community. D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem uses proven cryptographic methods to authenticate users. The data will be only available to either the community or a group within a community explicitly authorized by the data provider.

• Any authorized user can use the data in any circumstance and for all usage, reproduce the data, modify the data, and make derivative data based upon the original data, communicate to the public, including the right to reproduce or display the data or copies thereof to the public and perform publicly, as the case may be, the data.

• Any authorized user cannot in any circumstance and for any usage redistribute the data or copies thereof, lend and rent the data or copies thereof, sub-license rights in the data or copies thereof.

• At any time the data provider can decide either to unregister its data repository or to suspend temporarily the access to it. All data provider’s requests are immediately accepted and operated by the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem.

• The ownership of the data remains exclusively to the data provider. D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem will not otherwise copy, move or distribute data provider's data for any purpose, except when required to do so by law.

• The data provider is solely responsible for the development, content, operation, and maintenance of the data. In particular, the data provider is solely responsible for the compliance of data with the law, with any claims relating to the data, and any violation with respect person’s rights.

• The registration of a data repository to the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem is simple and secure. Several technologies - relational databases, columns stores, document repositories, geographical information systems - and protocols are currently supported.

To register a data provider is needed to contact d4science info . A personal assistant will be assigned to follow the entire registration process. The procedure is not expected to take more than three working days.

Software Participation Policy

This policy regulates the deployment of User's Web Applications into the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem, performed trough the Web Application Management Portlet and the WAR Management Portlet:

• The D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem is not responsible of the Web Application uploaded and hosted by the infrastructure.

• Users should be aware of software licenses which regulate its WebApplication or any third party software included. The D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem will not be responsible of any issue regulating licence infringement or illegal use of proprietary software.

• Users which upload WebApplications, in the case they decide to share it with members of a Virtual Research EnvironmentA ''system'' with the following distinguishing features: ''(i)'' it is a Web-based working environment; ''(ii)'' it is tailored to serve the needs of a Community of Practice; ''(iii)'' it is expected to provide a community of practice with the whole array of commodities needed to accomplish the community’s goal(s); ''(iv)'' it is open and flexible with respect to the overall service offering and lifetime; and ''(v)'' it promotes fine-grained controlled sharing of both intermediate and final research results by guaranteeing ownership, provenance, and attribution. (VREVirtual Research Environment.), are responsible for any misusage of the WebApplication by other Ecosystem Users.

• The D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Ecosystem by monitoring the User's Web Applications running behavior, can decide to remove the WebApplications from the infrastructure in the extreme case where they could undermine the Infrastructure stability.