It lets Tenant Admins create flavors, which specify the number of GPUs required by a virtual node using that flavor.

It creates virtual GPUs and allocates these virtual GPUs to the virtual nodes that request them.

It allows Site Admins to reserve a certain number of GPUs for the tenant within an EPIC tenant's settings.

When you want to set a custom source email address for the alerts

When the controller DNS server does not have an entry for the destination email domain

When you want to specify multiple destination email addresses and groups

When you want to send an alert to an SNMP version 3 server

Exec Into the epic-monitoring pod on the controller and enable Kibana.

Exec into the epic-nagios pod on the controller and start the Nagios service.

Access each host managed by the platform and export logs in the "var/log/bluedata" directory.

Create a user account and assign that account the "monitoring" role.

A service object with ClusterIP type and name "portal"

A replica set object with container ports 80 and 443

A configmap object with ports 80 and 443 and name "portaLtenant l"

A kdcluster object with hostname "portal.tenantl.svc.cluster.local"

You must first install a digital certificate to secure management communications with the host.

The host must pass all the checks run by the pre-check config script.

You must run the standard installation before running the pre-check config file.

The host must run the RHEL operating system because SLE5 is not supported.

Direct the shadow controller to begin managing the platform if the controller fails

Monitor the gateway and notify the administrator if a critical error occurs

Detect if the controller or shadow controller has failed and begin managing the platform

Load balance requests sent to the controller and shadow controller