On behalf of the MobiledgeX team, I’m excited to announce the release of MobiledgeX Edge-Cloud 3.0, which delivers numerous new features designed to enhance the experience and capabilities of our operator and developer user communities. MobiledgeX Edge-Cloud 3.0 is a huge release and a testament to our commitment to product development and our promise to continue delivering features that will benefit and satisfy our customers.
The MobiledgeX Edge-Cloud 3.0 platform brings a host of new capabilities for mobile network operators (MNOs) and application developers seeking to take advantage of the telco edge. For operators, this latest update brings more choice and control to MNOs looking to choose the best approach for their business to engage with public cloud providers. For developers, our enhanced Distributed Matching Engine (DME) architecture provides improved edge connectivity and many other benefits.
Collectively, it is the leading software product, implementing GSMA TEC specifications, that is solely focused on enabling MNOs to deliver on their promise of edge cloud.
I’d like to discuss these improvements in a bit more detail, starting first with the technical benefits our MobiledgeX Edge-Cloud 3.0 platform brings to developers.
Improved Edge Connectivity for Developers
Our enhanced DME Architecture introduced in MobiledgeX Edge-Cloud 3.0 goes far beyond just routing end-users to the closest cloudlet location by providing a wealth of critical data -- such as latency and device information -- to help developers select the most optimum cloudlet to provide the best end-user experience at any given time. Leveraging persistent connections through server-side DME events (aka EdgeEvents), we can collect and examine data such as latency measurements, mobility tracking, and other valuable information to quickly respond and help developers optimize their application deployment (aka Smart Edge Discovery). We removed the need for developers to self-manage our platform for much of the application deployment process. MobiledgeX takes on all the heavy lifting for our customers, allowing developers to focus on providing the best application experience for their users (aka Smart Edge Allocation). Additionally, developers are in complete control using our robust SDKs to determine how often they wish to be notified about their application instances. This freedom of control allows developers to optimize their edge-to-cloudlet connectivity based on location awareness and their desire to enhance performance and elevate the end-user experience.
Improved Visibility and Operational Management of Cloudlets for Operators
We’ve made significant changes providing operators more control and visibility over their cloudlets. Operators may now leverage our controller as their resource manager rather than rely only on their IaaS layer to determine resource availability. Using the controller to manage resources, operators can directly retrieve cloudlet usage information through generated reports detailing the usage. The controller also assists operators with validating their cloudlet resources, receiving notifications when their cloudlet and infrastructure exceed a defined usage threshold and providing notification controls for events, such as auto-provisioning, cluster services, and more. In addition, our Edge-Cloud Private Edge provides operators the ability to view developer-specific information about usage, logs, and metrics. With the MobiledgeX EdgeCloud 3.0 feature set operators can now utilize their own telco network edge infrastructure to create, run, and monetize edge clouds.
MobiledgeX Edge-Cloud 3.0 Feature Highlights
Highlights of 3.0
Operators no longer need to rely exclusively on their hardware for resource availability and are able to leverage resource management capabilities directly within the Controller.
Generate a summary of usage reports detailing the status of cloudlets
Operators can now be alerted when quota limits are reached and view developer metrics and logs.
View developer-specific information about usage, logs, number of devices connected.
Turn public cloudlets into private cloudlets, and segment edge infrastructure.
View and filter real-time events by either operator or developer and stream the events to a Kafka cluster.
Receive alerts when cloudlets are down, or resources limitations have exceeded.
Set up alert policies to further monitor applications and be alerted when applications violate those policies.
Classify alerts based on severity levels.
Generate alerts for cloudlet and cloudlet usage when resource limitations exceed thresholds.
Receive and collect client cloud metrics and usages.
New search capabilities and additional events are added, including other filters and tag options to refine searches. Usage logs help you understand the application activity occurring with cloudlets.
Enable members of organizations to onboard cloudlets, run and deploy edge applications, and test locally.
Once invited, developer organizations can deploy cluster and application instances to cloudlets.
View statistical aggregated data of client applications, including latency statistics, and filter them by data types.
View extended health checks on VMs.
Deploy a GPU-config for K8s-based application
OpenStack has worked with Microsoft to provide a ready-to-use qcow2 formatted image that can be deployed directly to MobiledgeX.
In addition to CPU, the auto-scale policy can also be based on the number of active connections and memory utilization to allow for scaling based on these multiple metrics.
We’re excited to share more technical details about our 3.0 release, so we’ll be starting a series of technical blog posts -- starting next week -- that will provide additional information on what 3.0 has to offer.
You can also reach out to our operator business development team or our developer relations team for more information on this release from an operator or developer perspective, respectively. You can also try our MobiledgeX EdgeBox demo for a free trial so you can see first-hand what the MobiledgeX Edge-Cloud platform has to offer.