Difference between revisions of "Catalogue:Infrastructure"

From D4Science Wiki
Jump to: navigation, search
(Infrastructure)
(Infrastructure)
Line 1: Line 1:
 
== Infrastructure ==
 
== Infrastructure ==
  
iMarine as an infrastructure offers a variety of functionality to its end users directly or to Infrastructure Managers. The functionality that are offered mainly by gCube services ( in gCube terminology named ''Enabling services'' ) can be classified in the following categories:
+
iMarine as an infrastructure offers a variety of functionality to its end users directly or to Infrastructure Managers. The functionality that are offered mainly by gCube services ( in gCube terminology named ''Enabling services'' ) or third party tools can be classified in the following categories:
  
 
* '''Deployment''' : The Infrastructure trough its enabling services is capable of automatic deploy and activate Software Bundles remotely, thus allowing administrators to  remotely manage software installation and upgrades.
 
* '''Deployment''' : The Infrastructure trough its enabling services is capable of automatic deploy and activate Software Bundles remotely, thus allowing administrators to  remotely manage software installation and upgrades.
 
* '''Hosting''' : End user are endowed to upload, deploy and activate their software bundles ( war) on the Infrastructures by relying on a simple and intuitive Graphical Wizard and Management interface.  
 
* '''Hosting''' : End user are endowed to upload, deploy and activate their software bundles ( war) on the Infrastructures by relying on a simple and intuitive Graphical Wizard and Management interface.  
* '''Resources Lifecycle''' : Software and nodes running on the  infrastructure can be managed remotely in terms of activation/deactivation, assignment to VOs and VREs ( which dynamically groups users and resorces assigned to them), publication to an Information System for their easy discovering.
+
* '''Resources Lifecycle''' : Services and nodes running on the  infrastructure can be managed remotely in terms of activation/deactivation, assignment to VOs and VREs ( which dynamically groups users and resorces assigned to them), publication to an Information System for their easy discovering.
* '''Monitoring''' : Software and nodes deployed on the infrastructure is
+
* '''Monitoring''' : Services and nodes deployed on the infrastructure are monitored semi-automatically by the usage of de-facto standard tools, like Nagios and Nagios-NRPE. Infrastructure Administrators and Site Managers can be notified in case of issues and promptly react.
 +
* '''Accounting''' : The infrastructure account the usage of the tools that are provided trough its Graphical interfaces. In addition the accounting at the level of resources ( storage, CPUs etc) not yet available is going to be included soon, and will help administrators in the definition of policies on the usage of the infrastructure.

Revision as of 12:45, 2 July 2013

Infrastructure

iMarine as an infrastructure offers a variety of functionality to its end users directly or to Infrastructure Managers. The functionality that are offered mainly by gCube services ( in gCube terminology named Enabling services ) or third party tools can be classified in the following categories:

  • Deployment : The Infrastructure trough its enabling services is capable of automatic deploy and activate Software Bundles remotely, thus allowing administrators to remotely manage software installation and upgrades.
  • Hosting : End user are endowed to upload, deploy and activate their software bundles ( war) on the Infrastructures by relying on a simple and intuitive Graphical Wizard and Management interface.
  • Resources Lifecycle : Services and nodes running on the infrastructure can be managed remotely in terms of activation/deactivation, assignment to VOs and VREs ( which dynamically groups users and resorces assigned to them), publication to an Information System for their easy discovering.
  • Monitoring : Services and nodes deployed on the infrastructure are monitored semi-automatically by the usage of de-facto standard tools, like Nagios and Nagios-NRPE. Infrastructure Administrators and Site Managers can be notified in case of issues and promptly react.
  • Accounting : The infrastructure account the usage of the tools that are provided trough its Graphical interfaces. In addition the accounting at the level of resources ( storage, CPUs etc) not yet available is going to be included soon, and will help administrators in the definition of policies on the usage of the infrastructure.