Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Tenant Provisioning: EWC allows the provisioning of a set of resources to a tenant administrator (in the remaining referred only as tenant).
  • Virtual Machines: Tenantscan deploy VMs, and have full control over the deployed VMs, on the resources allocated to them. The resources used by this infrastructure are taken from the ones allocated to the organization (billing unit budget & quota). Users also have the option of cloning VMs, which provides them with an identical deployment to one already running.
  • Virtual Private Networking: Tenants can deploy virtual networks inside their tenancy, to isolate traffic between VMs. EWC offers, as part of this service, virtual routing, security groups, floating IPs and DNS services.
  • Load Balancer: EWC tenants can also deploy a load balancing service that allows them to balance the traffic between two or more VMs.
  • Block Storage provisioning: Users can provision block storage volumes, which can be mounted to a single VM at the time.
  • Object Storage provisioning: Tenants can deploy object storage capacity as buckets and store their data into in these buckets. Tenants can create access keys with read-only or read-write permissions and control the access at bucket level (using bucket policies) and object level (using ACL). The access can be restricted to the tenancy or specific IP-address/range, accessible from the internet, or the buckets or objects can be made public. The object storage supports SWIFT- and S3-interface and public buckets with also https-interface.
  • Shared File System provisioning: Users can provision Shared File System (SFS) storage, which can be mounted to several VMs simultaneously within the tenancy.

...

Users can define tasks containing shell scripts and ansible Ansible playbooks. This functionality enables users to deploy their infrastructure as code(IaC), including software provisioning, configuration management, and application deployment functionalities. The tasks can include runtime and provisional workflows. Tasks and workflows can be executed in the running VMs or during deployment respectively. The workflow execution can be triggered from the UI and from the CLI / Rest API. The tasks and workflows can be fetched from user-defined GIT repository via integrations.

...

Morpheus can store secrets, through a built-in functionality that is also integrated with the shell and ansible Ansible scripts described in the previous section. Morpheus offers this functionality through Cypher. The stored secrets can be revoked either manually or automatically after a timeout.

...

The European Weather Cloud Accounting and Metering Service (hereafter referred as Accounting Service) provides a cross-cloud overview of resource usage of tenancies and Member States.

The accounting tool provides visualization tools including metrics, time series, graphs, and dashboards of all the accounting data gathered for end users, in the form of a GUI.

Expected service level

Following The following service level is expected:

Service Element

Description

Target

Notes

Infrastructure

Expected availability of deployments and reachability of the VM/service

The availability of the deployed resources including the whole virtual environment explained above. This availability also includes the reachability of the VM/service from the Internet. 

99%

Measured over a month, excluding planned service interruptions. Maintenance windows are announced in EWC KB Blog

Availability of Cloud Management Services services (see above)

The EWC tools such as the provisioning portal, metering and accounting services.

99%

Measured over a month, excluding planned service interruptions. Maintenance windows are announced in EWC KB Blog

Support

Time to first response 

Lead time to respond to the ticket and start the task

1 day on business hours


Time to resolution plan of service request

Time to assessment and to the resolution plan of the service request including support requests and service change requests8 business days

Time to resolution plan of incident

Time to the resolution plan of the incidents

2 business days


Lead time to on-board

Lead time to on-board an approved new user counted from the approval by Computing Representative / R&D project and Special Project acceptance

3 business days (after approval)


...