Edge-Cloud Release Notes for 3.0

The Edge-Cloud 3.0 release offers many new features and enhancements. The following release notes cover details about these features and improvements and provide a list of known issues.

Documentation and resources can be found on our Operator Portal, where we continuously publish new content and resources to help you realize the potential of our solutions and offers.

New Features on Edge-Cloud

Title	Description
Resource Management	Operators will no longer need to rely on their hardware for resource availability. They can now use the Controller as a resource management tool where during the creation of cloudlets, resource quota limits can be specified. During cluster instance creation or VM-based app creation, resource validation occurs. The advantages of this include getting notified through our alerting system when resources are impacted and exceed the defined threshold, and allowing operators to respond quickly by modifying or increasing the resource limits and capacity. Additionally, new APIs are available to view resource capacities and the ability to display a snapshot of the resource infrastructure usage. Learn more about Resource Management here .
Operator Reports and Scheduler	Operators can generate a summary of usage reports detailing the status of their cloudlets. The information is provided in .pdf format. Reports can be scheduled based on intervals you define. While operators can view cloudlet resource usage as part of the report, we currently do not display cloudlet resource usage information on a per-developer basis, even if the developers are part of a Cloudlet Pool. Learn more about Report Scheduler here.
Invite Developers to join Cloudlet Pool	Operators can now send invitations to developers to join Cloudlet Pools. Once Developers are part of the Cloudlet Pool, operators can be alerted when quota limits are reached, cloudlets are down, and developer metrics and logs can be viewed and accessed. Learn more about inviting developers to join Cloudlet Pools here.
Monitoring Developer Metrics and Usage Information	Operators can retrieve developer usage information if the developer organization is part of the cloudlet pool. Information may include usage, logs, and the number of devices connected. Learn more about Monitoring Developers Metrics and Usage here.
Trust Policy	Operators can turn their public cloudlets into private edge cloudlets. Furthermore, operators can segment their edge infrastructure and apply an additional security level with Trust Policies. These policies define security group rules that permit outbound traffic with specific outbound traffic rules. Learn more about Trust Policy here.
Multiple Cloudlets per VDC	Operators can now run multiple cloudlets per VDC.
Restricted Cloudlet on VM Pool	Previously, our support for restricted cloudlets was only available on OpenStack. Now, we have added support for restricted cloudlet on VM Pool.
Trust Policy on VCD	Previously, we only supported Trust Policy on OpenStack. Now, we support Trust Policy on VCD.
Support for GPU on VCD	This feature is partially supported and requires manual GPU mapping with the VM in the vSphere configuration.
Support for vGPU	vGPU is now supported.
Support for Cloudlet Event Streaming through Kafka	You can now set up Kafka on a cloudlet to view and filter real-time events by either operator or developer. All events about the cloudlet can be pushed to the Kafka cluster. However, developer audit events for Kafka are not supported in this release. Learn more about Kafka here.
Helm Chart support	We now support Helm Chart v3.
Health Checks on VM	We now support application-level health checks on VMs so that when a VM is stopped, a Healthcheck Fail Server alert is sent.
Supported Alerts	Operators can now receive alerts when cloudlets are down or when resource limitations have exceeded. Alerts can also be created for application instances that exceed resource levels. Learn more about the Supported alerts here.
Alert Severity	You can now classify alerts based on severity levels. The severity levels include info, warning, and error. Learn more about the Alert Severity here .
New Cloudlet Usage Alerts	Operators can now generate alerts for cloudlet and cloudlet usage exceeding resource limitations. Resource limitations may include the following: · App instance CPU exceeding defined levels · App instance MEMORY exceeding defined levels · RESTART of app instances Learn more about Cloudlet Alerts here.
New metrics available for client cloudlet usage	We now support collecting and retrieving client cloudlets using metrics through `mcctl` and the console latency map. Learn more about Client Cloudlet Usage here.
New metrics for client app usage	We now support displaying client application usage metrics through `mcctl` and the console latency map. Learn more about Client App Usage metrics here.
MC API for app instance and cluster instance	We added support to display application instance, cluster instance, and cloudlet pools usage if developers are part of the operator's Cloudlet Pool through our APIs. Learn how to view Developer app/clusters instances here.
Client Cloudlet metrics	`mcctl` command is available to show client cloudlet usage. Learn more about Client App Usage Metrics here.
Automatic onboarding for VM Pool	We now support automated onboarding for VM Pool.
Windows VM on VCD	We now support Windows VM on VCD. For deployment of Windows VMs on VCD, there is a new App field vmostype which must be populated with the appropriate Windows version.
Health Check and IAAS Cloudlets	Health Check will now fail if the IaaS cloudlets go down

Behavior changes and enhancements

Title	Description
Events Manager: monitoring events, usage, metrics enhancements	We have made significant enhancements to the monitoring components. In addition to collecting events and audit events for applications, clusters, and cloudlets, retrieving this data is now performed using the combined events and audits commands. Our search capabilities have been expanded with additional filter and tag options to further refine your search, and you can go from a Live view and switch views to perform a more specific search. Usage logs, which let you view application instances across client devices, locations, etc., help you understand the application activity occurring within your cloudlets. You can also view usage logs for cluster instances and cloudlet pools. Last, viewing metrics information has been expanded to include cloudlets, clusters, and application instances. Metrics information may include vCPU infrastructure usage, disk infrastructure usage, and memory usage, all viewable through a UI graphical interface. Learn more about Events Manager here.
Disabling EdgeBox	As an OperatorManager, you can enable members of your organization to onboard cloudlets, run and deploy edge applications, and test locally without impacting existing network infrastructure. When you create an operator organization, the organization is operating in a default restricted mode: `edge-box only`, which does not allow members within your organization to deploy cloudlets. To change this default mode, contact EdgeXR Support to lift the restriction. Once the restriction is lifted, members of your organization can start deploying cloudlets. Learn more about EdgeBox here.
Flavor selection for cluster and app instances	Previously, you can select a cloudlet and flavor based on regions when you create a cluster or application instance. In this release, we have made changes so that only the flavors that support those cloudlets appear as options when a cloudlet or a list of cloudlets are selected. Further, only cloudlets that support the flavor are available in the selection list when a flavor is selected.
Delete Alert Receivers	Previously when a user was deleted, the alert receiver associated with the user's name could not be deleted. Now, as an OrgAdmin, you can delete alert receivers after the user has been deleted.

Known Issues

Title	Description
Adding additional worker nodes fails on VCD	Increasing the number of worker nodes to an existing cluster fails on VCD, resulting in the VM remaining in a power-off state. To work around this issue, set the number of worker nodes back to the original number of nodes initially configured and manually power up the VM from the Cloud Director
VM application statistics	Currently, VM application statistics work with VCD, with the exception of Disk usage, Network sent, and Network received.
Support for GPU on VCD	This feature is partially supported and requires manual GPU mapping with the VM in the vSphere configuration.
Health check status for UDP	Currently, we don’t provide health checks on UDP ports.
Incorrect login attempts	Currently, we do not lock out users if multiple login attempts fail. However, there is a one-second penalty delay when users input an invalid username or password, making it difficult for bots to compromise user credentials.
Support for VM deployment on VM Pool	Currently, we do not support VM deployment on VM Pool.
Mapping GPU count for flavors with vGPU	While we show vGPU mapping, we do not display the details of the GPU/vGPU hardware model, slicing, FPS, etc. Therefore, you cannot select a flavor based on those details.
Health checks may not work with some applications	Our health check makes TCP connections to exposed ports and closes them right away. If this is unexpected from the application side, health-check should be turned off for those application ports.
Adding a public cloudlet to a private cloudlet pool	Currently, we do not allow operators to include a public cloudlet as part of a member of a private cloudlet pool if there are existing cluster instances or application instances deployed on the public cloudlet.
Unable to detect flavors on OpenStack	Currently, deleted flavors on OpenStack are undetected and therefore, will not show as deprecated when cached. As a result, the cloudlet info will not reflect the deleted flavor within the flavor list.
Refresh action is not visible for the deployment type VM	Currently, the refresh action is hidden for the deployment type windows VM for OpenStack or VCD.