...
Morpheus provides capability to create applications defined as ‘blueprints’ containing one or more VMs with possibly pre-installed software, pre-defined provisional workflows, network setup, and other resources. Users can create their own blueprints and instance types and/or use the catalogue. Notably, users are responsible for the maintenance and updates of all deployed instances and applications regardless of their origin (e.g. instance selected from the catalogue). Updates on the applications in the catalogue are not applied to the already running applications.
...
Monitoring
Morpheus (Cloud broker) provides monitoring features. Anything provisioned within Morpheus automatically gets a check created in the monitoring service.
...
Reporting
Reports show the tenancies in the system, including the resources assigned to each tenancy and its utilization, and have customized time ranges in this visualization.
...
Following service level objectives are expected:
Service Element | Description | Target | Notes |
|---|---|---|---|
Expected availability of tenants’ deployments and reachability of the VM/service | Reachability of the very simple service (e.g. ping) deployed into the EWC, probed from Internet. | 99% | Measured over a month, excluding planned service interruptions |
Availability of operational EWC services (see above) | The EWC (provisioning portal, storage services, etc.) shall be available at least 99% of the time (excluding the scheduled maintenance windows), measured over a month, excluding planned service interruptions. | 99% | |
Time to first response | Lead time to respond to the ticket and start the task | 1d on business hours | |
Time to resolution of service request | 8 business days | ||
Time to resolution of incident | 1 business day for blocking, 3 business days for major | ||
Lead time to on-board | 3 business days (after approval) |