Difference between revisions of "Catalogue:Infrastructure"

From D4Science Wiki
Jump to: navigation, search
(Infrastructure)
(Infrastructure)
Line 3: Line 3:
 
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'' ) can be classified in the following categories:
  
* '''Deployment''' : The presence of
+
* '''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''' : 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.
 +
* '''Monitoring''' : Software deployed on the infrastructure is

Revision as of 12:08, 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 ) 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 : 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.
  • Monitoring : Software deployed on the infrastructure is