Lists new features and known issues
With the release of Edge-Cloud R2.0, a number of capabilities such as the management, operations and monitoring of application deployments and resources are available through an easy-to-use Edge-Cloud Console. As a Developer, you can use the console to manage your software deployment across all operator’s distributed edge infrastructure, further simplifying the deployment of enterprise resources and applications. Operators, on the other hand, can use the Edge-Cloud Console to monitor the usage of the Operator-owned Cloudlets. Both Developers and Operators can monitor and manage most of their operations through a single pane of glass.
For a comprehensive list of features and capabilities, refer to our recent announcement of Edge-Cloud 2.0. Documentation and Resources can be found on our Developer Portal, where we continuously publish new documentation and resources to help you realize the potential of our solutions and offerings.
The table below lists specific features added to our Edge-Cloud Console.
|Login and registration mechanism||Login and Self-serve registration capabilities are provided on the Edge-Cloud Console to allow appropriate resource access to all users.|
|RBAC support||Role-Based Access Control provides the ability to assign different roles to users per Organization.
|Developer interface||The Edge-Cloud Console lets Developers debug issues related to their application instances in the Operator cloudlets, where they are deployed.|
|Operator interface||The Edge-Cloud Console lets Operators monitor the usage of the Operator-owned Cloudlets.|
|Add/invite users to your Organization||If a Developer or Operator creates an Organization, they become the Administrator for that Organization. As an Administrator, the Developer or Operator can add other users to their Organization and assign user roles.|
|Auto-create VM repository for Developers during CreateDeveloper||
During the CreateDeveloper process, once the user’s identity is confirmed by email verification, a repository is automatically created under the MobiledgeX VM Registry.
With SSO implemented, the same Edge-Cloud Console login credentials is used to access the VM registry.
|Auto-create Docker repository for Developers during CreateDeveloper||
During the CreateDeveloper process, once the user’s identify is confirmed by email verification, a repository is automatically created under the MobiledgeX Docker Registry.
With SSO implemented, the same Edge-Cloud Console login credentials is used to access the Docker registry.
|Self-serviced tool tips||Tool tips can be found throughout the Edge-Cloud Console wherever a question mark is available. Click on the question mark to access a brief helper text about an element or its function.|
|Regional controller||For scalability, privacy, and the operational ease of managing your Organization, all cloudlets are part of a controller, and are organized by regions. As a developer, you can deploy your application instance to multiple cloudlets within the same Operator and region. As an Operator, you can deploy multiple cloudlets with the same region. Each region has its own controller along with its own database. Each database contains data, such as Cloudlets, Flavors, ClusterInstance, Apps, that exist within that region. The Master Controller directly communicates with each regional controller, and all requests made by the console passes through the Master Controller. The Master Controller will determine which regional controller to communicate with when you select an available Region from the pull-down list.|
|3 application deployment types supported||When creating Apps, you can choose to deploy your application using the 3 available deployment types:
|Ability to add security group during CreateAppInst||During the CreateAppInst process, Developers can configure security groups.|
|Dedicated security group per cluster||Dedicated clusters are assigned to each security group, and restricted traffic occurs for groups that are not part of the default group. You can also create multiple clusters at once. Furthermore, you can have a dedicated or shared Root-LB balancer. When you create a cluster, we automatically create a shared Root-LB balancer. If flagged as shared, Kubernetes cluster will use that shared Root-LB balancer.|
|Different Flavors supported||Multiple T-shirt size for VMs are available.|
|Logging actions||Logs are created each time you or someone within your Organization creates, deletes, or modifies settings/configurations for your Organization.|
|Able to deploy to multiple cloudlets||As a Developer, you can deploy your Cluster and Application Instances to multiple cloudlets within the same region and operator.|
|Metrics available for VM, Docker, and Kubernetes||We provide a single pane of glass to monitor all deployed applications.|
|Auto Provisioning Policy of Application Instance||Based on policy, such as user location, MobiledgeX can auto-deploy your application instance.|
|Root-LB based Health checking for application instances||We’ve added a health check AppInst.Health that provides the current state of the AppInst., and marks it as either Offline or Ready.|
|Basic health monitoring scheme of developer AppInstances||Health Monitoring is available to monitor the health of applications through a single pane of glass.|
|Docker Log Exposure||Provides Application Developers access to docker logs.|
|Kubernetes Log Exposure||Provides Application Developers access to Kubernetes logs.|
|Shell access capabilities for Developers||From the Edge-Cloud Console, Developers have shell access to their containers for the purpose of debugging and testing. You use the ‘Run’ command to go inside container and ‘Show Log’ to view changes.|
|Terminal access capabilities for Developers||From the Edge-Cloud Console, Developers have shell access to their VMs for the purpose of debugging and testing. Use the terminal commands from the AppInst Page.|
|Audit logging supported||
We generate audit logs based on User ID. You can view your own historical activities from the Edge-Cloud Console.
You can also view logs and examine historical activities by users within your Organization. These logs can be used for diagnostic purposes or for error correction.
|Automatic Onboarding of Cloudlets||Operators can automatically onboard their Cloudlets.|
|Cloudlet Metrics||Operators can view their deployed Cloudlets through a single pane of glass.|
|Cloudlet Event Logs||Operators can view event logs for their deployed Cloudlets.|
|Cloudlet Pools||Operators can make their cloudlets private, and Organizations that are part of the cloudlet pool can only view those particular cloudlets.|
|GPU support||Nvidia T4 GPUs are supported in pass-through mode for virtual machines, enabling the entire GPU to be exclusively dedicated to a virtual machine.|
There are no known issues documented at this time.