Edge-Cloud Console Guide for Operators

Version: 1.0
Last Modified: 7/28/2020

Welcome to the Edge-Cloud Console Guide for Operators! Here, you will learn about the various elements and components of MobiledgeX's user interface. This guide details the data fields available and the operations used to create and deploy cloudlets. Once the cloudlets are deployed, you can use our comprehensive Monitoring and Logging tools to obtain a detailed view of cloudlets at the regional level. Each regional controller receives alarms via a notification framework built into the MobiledgeX Platform. The AlertManager, a global component of our Platform, is responsible for aggregating and distributing alerts to cloud Operators.

Note: The Monitoring and Logging tool is still under development.

Resource Management and Workflow

MobiledgeX presently supports OpenStack Tenant Deployment as the Virtual Machine Orchestration layer.

With the OpenStack model, the MobiledgeX Platform is a tenant on an existing OpenStack environment within the Operator’s infrastructure. As the Operator, you register your cloudlet by providing MobiledgeX with a pool of compute resources and access to the OpenStack API endpoint by specifying a few required parameters, such as dynamic IP addresses, cloudlet names, location of cloudlets, certs, and more, using the Edge-Cloud Console. MobiledgeX relies on this information to remotely access the cloudlets to determine resource requirements as well as dynamically track usage. Once MobiledgeX completes its remote probe of the Operator’s infrastructure, a record of inventory is maintained within a cloudlet registry.

Direct vs. Restricted Access

Note: While VSphere is available as a Platform Type, only Direct access is currently supported, but is considered an alpha feature at this point; Restricted access for VSphere is under development and currently not supported. If you wish to schedule a demo for VSphere, contact MobiledgeX.

MobiledgeX relies on the ability to access the Operator’s infrastructure (API endpoint) to set up the cloudlets via the Controller to perform various operational tasks. Providing MobiledgeX Direct access makes it seamless for MobiledgeXAdmin to access the Operator’s API endpoint through a public network, and to perform those tasks. However, we understand that different Operators often use varying security methods, so providing MobiledgeX with Direct access to the API endpoint over the public network may not always be feasible. To overcome this challenge, MobiledgeX provides Operators with a means to restrict access from the public network to their infrastructure by specifying the Restricted access type through the Edge-Cloud Console. Using the Restricted access type will allow MobiledgeX to create what’s called a cloudlet object to create cloudlets.

If Restricted access type is used, Operators are required to take additional steps to ensure their infrastructure is set up so that access to the API endpoint is available and information can be exchanged. Operators will need to create their cloudlets by following a few steps provided directly within a Cloudlet Manifest file to bring up the cloudlet. For steps on how to set up Restricted access, refer to the steps as described in To create and deploy cloudlets using Restricted access.

OpenRC and CACert Data for OpenStack Cloud Management

For OpenStack, simple client environment scripts, such as OpenRCs are supported and represented as a key=value pair. These scripts are available to help increase the efficiency of client operations. Additionally, CACert Data is supported, which is a collection of the trusted certificate authority (CA) used to encrypt and secure data transmission over the internet and authenticate and authorize users connecting to sites. MobiledgeX stores these OpenRC and CACert Data in a separate secure storage environment.

Often times, MobiledgeX will add the OpenRC details on behalf of the Operator. In this case, the OpenRC Data field may be left blank and MobiledgeX will provide Operators the Physical Name of the cloudlet to be provided in the Physical Name field. However, if there is a need to upload a new OpenRC file or the CACert Data file was not uploaded, the Operator must upload the files manually and provide a Physical Name.

Create an Account

First, create an account, if you haven't already done so. All users must have an account to receive an invite to join an organization.

To sign up for an account

  1. From the Edge-Cloud Console, click Create an Account. A Create New Account screen opens.

Signup screen

  1. Provide your credentials. Here are some guidelines:

    • Do not use spaces for Username; it must be all one word.
    • Password must be at least 8 characters.
    • Provide a valid email address. Use this email address later to access a link and verify your account.
  2. Read our Terms of Use and Privacy Policy and click Sign Up.
  3. An email will be sent to you with a link to verify your account. Once you've verified your account, return to the Edge-Cloud Console and log on.

Password and account recovery

If you have forgotten your password, on the Login screen, click Forgot Password?, enter your email address, and click Send Password Reset Email. You will receive an email with a link to reset your password. If you need to unlock your account, contact your MEXadmin.

You are now ready for a brief tour of our Edge-Cloud Console where you will learn about the various elements and components available to create and deploy cloudlets successfully.

Create an Organization and Manage Users

Note: Fields that contain an asterisk(*) are mandatory and require user input.

Before you can start creating and deploying cloudlets, you need to create an organization. You can think of an organization as a group of users on the MobiledgeX platform tasked with creating and deploying cloudlets or managing the health of those cloudlets. You may add developer or operator users to your organization at any time either during or after creating your organization.

You must create an organization upon logging into the console for the first time. Additional organizations may be formed once the initial organization is built. Organization names must be all one word, with no spaces or special characters.

TIP: It is best practice to keep the name of your organizations all in lower-case.
When selecting MobiledgeX Compute after logging on to the Edge-Cloud Console, the first screen that appears is the Organizations screen. This screen is where you add your organizations and users (optional).

To add an organization

  1. Click the + icon on the screen. The Step 1 Create Organization page opens.
  2. For Type, select Developer or Operator. The type of organization you wish to be a part of depends on tasks you are assigned to perform as defined by you or your company.
  3. For Organization Name, type in the name of your organization. Observe the naming convention rules as mentioned earlier.
  4. Type in an address and phone number.
  5. Click Create Organization. The Step 2 Add User page opens.
  6. Steps 7-9 are optional. For Username, add a 'Developer' or ‘Operator’ user you wish to add to your organization. If you wish to skip Step 2 Add User, simply click Skip where you can return to the Organization page.
  7. The right side of the screen lists the available roles you can assign to your users. Select the role for the user by clicking Select Role within the Role field to display the drop-down list.
  8. Click Add User. Once selected, Step 3 Verify your Users page opens.
  9. Once all the information entered is verified as correct, click Return to the Organization page.

Create Organization screen

Although your organization is listed, it's currently not managed. Click the Manage button associated with the organization you would like to manage. Remember to perform this step each time you log into the Edge-Cloud Console. Clicking the Manage button for your organization ensures you are working within the correct organization. Additionally, clicking Manage displays all the available submenus on the left navigation pane. However, to expand or collapse the submenus, click the icon as shown in the image below.

Next to the Manage button is a quick access menu where you can perform such tasks such as Audit, Add User, Update, and Delete your organization.

Users and roles

You can view users added to your organizations. The Users & Roles page lists all users, roles, and associated organizations they were assigned.

The following actions may be performed on this page, depending on you role within the organization:

  • On the Search bar, type in the first few letters of your search to filter your search.
  • From the Actions menu, click the quick access icon and select Delete to delete the user.

Users and Roles screen

Assign role-based access control (RBAC)

Role-based access control provides varying levels of access specified by the user's role and responsibilities. Setting the user's roles and responsibilities requires establishing permissions and privileges, consequently, enabling access for authorized users. MobiledgeX provides three different levels of RBAC with varying privileges, as outlined below. Note that specifying RBAC for each user is performed within the Organization page.

Role Priviledges
Manager
  • Manage: Users and Roles, Cloudlets
  • View: Monitoring, Audit Logs
Contributor
  • Manage: Cloudlets
  • View: Monitoring, Audit Logs
Viewer
  • Manage: Users and Roles, Cloudlets
  • View: Monitoring, Audit Logs

To create and deploy cloudlets using Direct access

  1. From the Edge-Cloud Console, navigate to the Cloudlets submenu.
  2. Click the + sign on the upper top right-hand corner to open the Create Cloudlet page.

    Create Cloudlet screen -Direct Access

  3. For Region, select a region from the drop-down list to deploy the cloudlet.

  4. Type in a name for your cloudlet under Cloudlet Name.
  5. The Operator field is required should contain the name of the organization you created.
  6. For Cloudlet Location, enter the cloudlet’s coordinates.
  7. For IP support, Dynamic is currently only supported. Dynamic indicates that the cloudlet will use a DHCP server to provide the public IP addresses.
  8. In the Number of Dynamic IPs field, type in the number of Dynamic IP addresses that are desired.
  9. For Physical Name, type in the physical name of the cloudlet. The cloudlet name is an identifier used for the OpenRC credentials.
    • If MobiledgeX added the OpenRC detail on behalf of the Operator, the OpenRC field should be populated with the details provided by MobiledgeX.
    • If a new OpenRC file is required to be uploaded, you must provide the Physical Name, which will be supplied to the Operator by MobiledgeX.
  10. In the Platform Type field, select one of the supported platform types—OpenStack or vSphere. If you select OpenStack, additional fields associated with that platform selection appears. Refer to Step 9 and 11 to understand the conditions to either leave those fields blank or populate them.
  11. For OpenRC Data, leave this field blank if MobiledgeX uploaded this file on your behalf. If you need to upload a new one, here is an example of an OpenRC file.

OS_AUTH_URL=https://openstack.api.enpoint.url/v3 OS_PROJECT_ID=b6565354422a454c965078640ad4398e OS_PROJECT_NAME=project_name OS_USER_DOMAIN_NAME=Default OS_PROJECT_DOMAIN_ID=default OS_USERNAME=osuser OS_PASSWORD=ospassword OS_REGION_NAME=RegionOne OS_INTERFACE=public OS_IDENTITY_API_VERSION=3
  1. For CACert Data, you must upload the CACert Data file if the OS_AUTH_URL is https-based. Otherwise, if you’re using http, this field is not required.

----BEGIN CERTIFICATE----- LVRlbGVTZWMgR2xvYmFsUm9vdCBDbGFzcyAyMB4XDTE0MDIxMTE0MzkxMFoXDTI0 BAYTAkRFMSswKQYDVQQKDCJULVN5c3RlbXMgRW50ZXJwcmlzZSBTZXJ2aWNlcyBH bWJIMR8wHQYDVQQLDBZULVN5c3RlbXMgVHJ1c3QgQ2VudGVyMSUwIwYDVQQDDBxU LVRlbGVTZWMgR2xvYmFsUm9vdCBDbGFzcyAyMB4XDTE0MDIxMTE0MzkxMFoXDTI0 MDEQMA4GA1UEBwwHTmV0cGhlcdefMB4GA1UECQwXVW50ZXJlIEluZHVzdHJpZXN0 SW50ZXJuYXRpb25hbCBHbWJIMR8wHQYDVQQLDBZULVN5c3RlbXMgVHJ1c3QgQ2Vu dGVyMRwwGgYDVQQIDBNOb3JkcmhlaW4gV2VzdGZhbGVuMQ4wDAYDVQQRDAU1NzI1 MDEQMA4GA1UEBwwHTmV0cGhlcdefMB4GA1UECQwXVW50ZXJlIEluZHVzdHJpZXN0 ci4gMjAxJjAkBgNVBAMMHVRlbGVTZWMgU2VydmVyUGFzcyBDbGFzcyAyIENBMIIB IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3oxwJVY3bSb6ejJ42f9VEt1N vW2swwllcs5ifPsHAulpSoFc2Y9gMOKQqkuyjN1foCegDDeEr6FBLD5YuROldcX8 2aDNBKDh9GpSJYZMLrYwlfR4EJUGwLidHDn93H95j1M67sNlCyCfcbso0zFBQzXK KO06sbC1QH9M1Xdrltz8bQS+LbGRTM5JcPYhhxXcnsFstQVaGmfqFQitPXhT3g9+ AQABo4IB2TCCAdUwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHSAEPDA6MDgGBFUd Ghvzd09jjMT6f8Q8pAlyGFTGuxsEjeU/rrS/yKU8bFEEvuR5WT/I4Kme+8OlzQID AQABo4IB2TCCAdUwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHSAEPDA6MDgGBFUd IAAwMDAuBggrBgEFBQcCARYiaHR0cDovL3BraS50ZWxlc2VjLmRlL2Nwcy9jcHMu aHRtbDAOBgNVHQ8BAf8EBAMCAQYwge8GA1UdHwSB5zCB5DA1oDOgMYYvaHR0cDov L3BraS50ZWxlc2VjLmRlL3JsL0dsb2JhbFJvb3RfQ2xhc3NfMi5jcmwwgaqggaeg gaSGgaFsZGFwOi8vcGtpLnRlbGVzZWMuZGUvQ049VC1UZWxlU2VjJTIwR2xvYmFs Um9vdCUyMENsYXNzJTIwMixPVT1ULVN5c3RlbXMlMjBUcnVzdCUyMENlbnRlcixP PVQtU3lzdGVtcyUyMEVudGVycHJpc2UlMjBTZXJ2aWNlcyUyMEdtYkgsQz1ERT9B dXRob3JpdHlSZXZvY2F0aW9uTGlzdDA4BggrBgEFBQcBAQQsMCowKAYIKwYBBQUH MAGGHGh0dHA6Ly9vY3NwLnRlbGVzZWMuZGUvb2NzcHIwHQYDVR0OBBYEFJTIdEb1 OrRGSCb4K8o0HlYmBBIAMB8GA1UdIwQYMBaAFL9ZIDYAeaCgImuM1fJh0rgsy4JK MA0GCSqGSIb3DQEBCwUAA4IBAQB55S9CfCkclWVtUIxl2c4aM5wqlLZRZ7zVhynK KOhWKyTw+D2BOjc+TXIPkgRMqF3Sn8ZD4UTOARboJxswYnLZDkvBuvTbYa+N52Jy oBP2TXIpEWEyJl7Oq8NFbERwg4X6MabLgjGvJETicPpKGfAINKDwPScQCsWHiCaX X50cZzmWw17S0rWECOvPEt/4tXJ4Me9aAxx6WRm708n/K8O4mB3AzvA/M7VUDaP9 8LtreoTnWInjyg/8+Ahtce3foMXiIP4+9IX7fbm6yqh4u33tqMESDcRP6eGdzq4D qnHyIvj9XNpuGgMvDgq357kZQS9e5XVH5icSvW1kr2kX2f1t -----END CERTIFICATE-----
  1. For Infra API Access, select Direct. This infers that the API endpoint is accessible from the public network.
  2. Once all the required fields are populated, click Create where a Progress bar appears and provides a live status of the cloudlet deployment process.

Progress Bar

  1. Click the Progress indicator to view the updated state as the cloudlet is being deployed. Refreshing may to 15 minutes to complete.
  2. Once the cloudlet is available, the state will change to init. This change may take up to 5 minutes.

You’re done! The deployed cloudlet can now be viewed from the Cloudlets page.

Cloudlets screen

To create and deploy cloudlets using Restricted access

  1. From the Edge-Cloud Console, navigate to the Cloudlets submenu.
  2. Click the + sign on the upper top right-hand corner to open the Create Cloudlet page.

    Create Cloudlet screen-Restricted Access

  3. For Region, select a region from the drop-down list to deploy the cloudlet.

  4. Type in a name for your cloudlet under Cloudlet Name.
  5. The Operator field is required should contain the name of the organization you created.
  6. For Cloudlet Location, enter the cloudlet’s coordinates.
  7. For IP support, Dynamic is currently only supported. Dynamic indicates that the cloudlet will use a DHCP server to provide the public IP addresses.
  8. In the Number of Dynamic IPs field, type in the number of Dynamic IP addresses that are desired.
  9. For Physical Name, type in the physical name of the cloudlet. The cloudlet name is an identifier used for the OpenRC credentials.
    • If MobiledgeX added the OpenRC detail on behalf of the Operator, the OpenRC field should be populated with the details provided by MobiledgeX.
    • If a new OpenRC file is required to be uploaded, you must provide the Physical Name, which will be supplied to the Operator by MobiledgeX.
  10. In the Platform Type field, select one of the supported platform types—OpenStack or vSphere. If you select OpenStack, additional fields associated with that platform selection appears. Refer to Step 9 and 11 to understand the conditions to either leave those fields blank or populate them.
  11. For OpenRC Data, leave this field blank if MobiledgeX uploaded this file on your behalf. If you need to upload a new one, here is an example of an OpenRC file.

OS_AUTH_URL=https://openstack.api.enpoint.url/v3 OS_PROJECT_ID=b6565354422a454c965078640ad4398e OS_PROJECT_NAME=project_name OS_USER_DOMAIN_NAME=Default OS_PROJECT_DOMAIN_ID=default OS_USERNAME=osuser OS_PASSWORD=ospassword OS_REGION_NAME=RegionOne OS_INTERFACE=public OS_IDENTITY_API_VERSION=3
  1. For CACert Data, you must upload the CACert Data file if the OS_AUTH_URL is https-based. Otherwise, if you’re using http, this field is not required.

----BEGIN CERTIFICATE----- LVRlbGVTZWMgR2xvYmFsUm9vdCBDbGFzcyAyMB4XDTE0MDIxMTE0MzkxMFoXDTI0 BAYTAkRFMSswKQYDVQQKDCJULVN5c3RlbXMgRW50ZXJwcmlzZSBTZXJ2aWNlcyBH bWJIMR8wHQYDVQQLDBZULVN5c3RlbXMgVHJ1c3QgQ2VudGVyMSUwIwYDVQQDDBxU LVRlbGVTZWMgR2xvYmFsUm9vdCBDbGFzcyAyMB4XDTE0MDIxMTE0MzkxMFoXDTI0 MDEQMA4GA1UEBwwHTmV0cGhlcdefMB4GA1UECQwXVW50ZXJlIEluZHVzdHJpZXN0 SW50ZXJuYXRpb25hbCBHbWJIMR8wHQYDVQQLDBZULVN5c3RlbXMgVHJ1c3QgQ2Vu dGVyMRwwGgYDVQQIDBNOb3JkcmhlaW4gV2VzdGZhbGVuMQ4wDAYDVQQRDAU1NzI1 MDEQMA4GA1UEBwwHTmV0cGhlcdefMB4GA1UECQwXVW50ZXJlIEluZHVzdHJpZXN0 ci4gMjAxJjAkBgNVBAMMHVRlbGVTZWMgU2VydmVyUGFzcyBDbGFzcyAyIENBMIIB IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3oxwJVY3bSb6ejJ42f9VEt1N vW2swwllcs5ifPsHAulpSoFc2Y9gMOKQqkuyjN1foCegDDeEr6FBLD5YuROldcX8 2aDNBKDh9GpSJYZMLrYwlfR4EJUGwLidHDn93H95j1M67sNlCyCfcbso0zFBQzXK KO06sbC1QH9M1Xdrltz8bQS+LbGRTM5JcPYhhxXcnsFstQVaGmfqFQitPXhT3g9+ AQABo4IB2TCCAdUwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHSAEPDA6MDgGBFUd Ghvzd09jjMT6f8Q8pAlyGFTGuxsEjeU/rrS/yKU8bFEEvuR5WT/I4Kme+8OlzQID AQABo4IB2TCCAdUwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHSAEPDA6MDgGBFUd IAAwMDAuBggrBgEFBQcCARYiaHR0cDovL3BraS50ZWxlc2VjLmRlL2Nwcy9jcHMu aHRtbDAOBgNVHQ8BAf8EBAMCAQYwge8GA1UdHwSB5zCB5DA1oDOgMYYvaHR0cDov L3BraS50ZWxlc2VjLmRlL3JsL0dsb2JhbFJvb3RfQ2xhc3NfMi5jcmwwgaqggaeg gaSGgaFsZGFwOi8vcGtpLnRlbGVzZWMuZGUvQ049VC1UZWxlU2VjJTIwR2xvYmFs Um9vdCUyMENsYXNzJTIwMixPVT1ULVN5c3RlbXMlMjBUcnVzdCUyMENlbnRlcixP PVQtU3lzdGVtcyUyMEVudGVycHJpc2UlMjBTZXJ2aWNlcyUyMEdtYkgsQz1ERT9B dXRob3JpdHlSZXZvY2F0aW9uTGlzdDA4BggrBgEFBQcBAQQsMCowKAYIKwYBBQUH MAGGHGh0dHA6Ly9vY3NwLnRlbGVzZWMuZGUvb2NzcHIwHQYDVR0OBBYEFJTIdEb1 OrRGSCb4K8o0HlYmBBIAMB8GA1UdIwQYMBaAFL9ZIDYAeaCgImuM1fJh0rgsy4JK MA0GCSqGSIb3DQEBCwUAA4IBAQB55S9CfCkclWVtUIxl2c4aM5wqlLZRZ7zVhynK KOhWKyTw+D2BOjc+TXIPkgRMqF3Sn8ZD4UTOARboJxswYnLZDkvBuvTbYa+N52Jy oBP2TXIpEWEyJl7Oq8NFbERwg4X6MabLgjGvJETicPpKGfAINKDwPScQCsWHiCaX X50cZzmWw17S0rWECOvPEt/4tXJ4Me9aAxx6WRm708n/K8O4mB3AzvA/M7VUDaP9 8LtreoTnWInjyg/8+Ahtce3foMXiIP4+9IX7fbm6yqh4u33tqMESDcRP6eGdzq4D qnHyIvj9XNpuGgMvDgq357kZQS9e5XVH5icSvW1kr2kX2f1t -----END CERTIFICATE-----
  1. For Infra API Access, select Restricted. This infers that the API endpoint is not accessible from the public network and additional fields will appear, and require input.
  2. For the Infra Flavor Name, provide the name of the flavor specific to the Infra to deploy the PlatformVM. The recommended minimum hardware configuration includes: 2 vCPU, 4GB RAM, and 40G disk space.
  3. For the Intra External Network Name, provide the name of the external network specific to the Infra.
  4. Once all the required fields are populated, click Create where a Progress bar appears and provides a live status of the cloudlet deployment process.

Progress Bar

  1. Once the progress is complete, click Get Manifest from the Actions menu to bring up the Cloudlet Manifest file. Follow the steps within the file to download the base image and upload it to Glance.

Example: Cloudlet Manifest file

  1. Execute the HEAT stack template and wait for the Platform VM to appear. Once created, the Platform VM will create an external IP address.

Example: Heat Stack template

  1. Click the Progress indicator to view the updated state as the cloudlet is being deployed. Refreshing may to 15 minutes to complete.
  2. Once the cloudlet is available, the state will change to init. This change may take up to 5 minutes.

You’re done! The deployed cloudlet can now be viewed from the Cloudlets page.

Cloudlets screen

Create Cloudlet Pool

Cloudlet pools are collections of cloudlets that are defined on a per-regional basis. As an Operator, you may set up a pool membership where only users within the organization associated with the cloudlet pool can access the cloudlets defined for that particular pool. Setting up a cloudlet pool is useful in cases where you need to segment your private (enterprise) cloudlets from your public cloudlets. Cloudlet pools may also be used to isolate cloudlets in the production phase of development and, therefore, will only be available for internal use. Here are some general guidelines to keep in mind when creating cloudlet pools.

  • As an Operator, you must own the cloudlets if you wish to add them to a cloudlet pool.
  • If a cloudlet is not part of a pool, it's considered a public cloudlet.
  • Cloudlets assigned to one or more pools are considered private cloudlets.
  • A cloudlet pool may be associated with one or more organizations, allowing users within that organization to access and use those cloudlets to deploy their applications.
  • Organizations not associated with a cloudlet pool will not see or have access to those cloudlets.
  • Targeted organizations that are associated to cloudlet pools may still deploy their applications to other public cloudlets, or to other private cloudlets from other organizations or pools.

To create a cloudlet pool

  1. Navigate to the Cloudlet Pools submenu, and click the + sign on the top right-hand corner of the screen. The Step 1 Create Cloudlet Pool screen opens.

Create Cloudlet Pool screen

  1. Specify a Region. Once specified, the Cloudlets selection box auto-populates with all available cloudlets for that region.
  2. Type in a name for the Pool Name.
  3. The Operator field is required and will auto-populate with the name of the organization you are currently managing.
  4. From the Cloudlet selection box, highlight the cloudlet(s) and select the single arrow to add individual cloudlets and associate them to the cloudlet pool, or you can select the double arrows to select all available cloudlets at once to add them to the pool.

Create Cloudlet Pool screen: Add Cloudlets to the Pool

  1. Click Create. The Step 2 Add Organizations screen opens.
  2. Region, Pool Name, and Operator fields will all auto-populate with the information specified during Step 1 Create Pool.

  3. From the Organizations selection box, highlight the organization(s) and use the right arrow to link the organization(s) to the cloudlet pool. You can add individual organizations or select the double arrows to link all available organizations on the list.

Create Cloudlet Pool screen: Link Organizations to the Pool

  1. Click Link Organizations. The cloudlet pool is now created and available on the Cloudlets Pool page. You can access the Actions menu to Update the cloudlet pools, Link Organization, Unlink Organization, or Delete the cloudlet pool entirely.

Cloudlets Pool screen

View Audit Logs

Historical activities performed by you and others within your organization are logged and viewed from the Edge-Cloud Console. These logs are used for diagnostic purposes or error correction, and each activity is logged by date and time. You can trace different events through the various sub-sections, which are separated into three parts-- Raw Viewer, Request, and Response. These sections provide valuable information if you require support from MobiledgeX. Simply copy and paste the traceid from the Raw Viewer section, and email the traceid to [email protected].

To view the audit logs, from the Organizations page, under the Actions menu, select Audit.
The following actions may be performed on this page:

  • Filter logs by region
  • Filter logs by time range

Contact Support

You can email the [email protected] to assist you in resolving product issues. To help expedite your request, make sure you copy and paste the tracid, which can be found on the Audit logs page, into your email with a brief description of your issue.