Difference between revisions of "Catalogue:Infrastructure"
From D4Science Wiki
Andrea.manzi (Talk | contribs) (→Infrastructure) |
|||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | D4Science 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 through 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 capable 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 resources 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 accounts the usage of the tools that are exposed 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. |
| − | * ''' | + | * ''' Security''' : the infrastructure prevents resources from unauthorized accesses both at the level of Data and Services. Administrators are able to easily define authorization policies in order to restrict as well the visibility of the resources at the level of a VO or a VRE. |
| − | * ''' | + | * ''' Distributed Workflow Execution ''' : the infrastructure offers computational resources that can be orchestrated in order to implement complex computational workflows involving internal or external data sources. |
| − | + | ||
| − | + | ||
Latest revision as of 11:09, 12 April 2017
D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. 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 through 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 capable 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 resources 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 accounts the usage of the tools that are exposed 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.
- Security : the infrastructure prevents resources from unauthorized accesses both at the level of Data and Services. Administrators are able to easily define authorization policies in order to restrict as well the visibility of the resources at the level of a VOVirtual Organization; or a VREVirtual Research Environment..
- Distributed Workflow Execution : the infrastructure offers computational resources that can be orchestrated in order to implement complex computational workflows involving internal or external data sources.
