The attributes marked with a * are confidential and should not be disclosed outside the service provider. | Service overview |
|
|---|
| Service name | ENVRIplus Service Testbed based on EGI Cloud Compute |
|---|
| Service area | Compute, storage |
|---|
| Service phase | Production: service available in the live environment meeting security/performance requirements |
|---|
| Service description | The provision of ENVRIplus service testbed corresponds to Reference Model Technology Viewpoint, that provide a real-world configuration to support testing and validation of ENVRIplus services |
|---|
Customer group | - ENVRIplus RI research communities
- ENVRIplus individual researchers
- ENVRIplus Service Providers
- ENVRIplus related SME/Industry
|
|---|
| User group | |
|---|
| Value | |
|---|
| Tagline | |
|---|
| Features | - Execute compute- and data-intensive workloads (both batch and interactive)
- Host long-running services (e.g. web servers, databases or applications servers)
- Create disposable testing and development environments
- Configure Virtual Machines (VMs) according to requirements
- Resources: CPU, memory, disk
- Application environments
- Scale infrastructure and manage resources in a flexible way
- Integrated monitoring and accounting capabilities
|
|---|
| Service options | TRL 9 | Option | Name | Description | Attributes |
|
|---|
| 1 | | | |
| | 2 |
|
|
|
| | 3 |
|
|
|
|
|
|---|
| Access policies | |
|---|
| Service management information |
|
|---|
| Service owner * | EGI Foundation |
|---|
| Contact (internal) * | Yin Chen, yin.chen@egi.eu |
|---|
| Contact (public) | support@egi.eu |
|---|
| Request workflow * | |
|---|
| Service request list | fedcoud.egi.eu VO |
|---|
| Terms of use | |
|---|
| SLA(s) | |
|---|
| Other agreements | |
|---|
| Support unit | |
|---|
| User manual | |
|---|
| Service architecture |
|
|---|
| Service components | | # | Type | Name | Description | TRL [1] |
|---|
| 1 | | |
|
| | 2 |
|
|
|
|
|
|---|
| Finances & resources |
|
|---|
| Payment model(s) | |
|---|
| Pricing | |
|---|
| Cost * | |
|---|
| Revenue stream(s) * | |
|---|
| Action required | |
|---|
[1] Technology Readiness Levels (TRL) are a method of estimating technology maturity of components during the acquisition process. For non-technical components, you can specify “n/a”. For technical components, you can select them based on the following definition from the EC: - TRL 1 – basic principles observed
- TRL 2 – technology concept formulated
- TRL 3 – experimental proof of concept
- TRL 4 – technology validated in lab
- TRL 5 – technology validated in relevant environment (industrially relevant environment in the case of key enabling technologies)
- TRL 6 – technology demonstrated in relevant environment (industrially relevant environment in the case of key enabling technologies)
- TRL 7 – system prototype demonstration in operational environment
- TRL 8 – system complete and qualified
- TRL 9 – actual system proven in operational environment (competitive manufacturing in the case of key enabling technologies)
| 
