Application Instances

Version: 1.0
Last Modified: 12/10/2020

The App Instances page is where you provision your application and deploy it to a cloudlet. This step is called application provisioning. This page displays information such as the current applications running on the platform and their location. MobiledgeX allows you to deploy your applications to multiple cloudlets within the same region.

You also have the option to create an auto-provision policy, where based on the information you provide, MobiledgeX can automatically deploy your app instance for you and locate the most optimal cloudlet(s). Once you create your auto-provision policy, you must specify the policy during the application definition process within the Apps page. For steps on how to set up your auto-provision policy, see the section To create an auto-provision policy.

The following actions may be performed on this page:

  • Filter your applications by region
  • To filter by group, simply drag and drop the Region, Organization, App, Operator, Cloudlet, Cluster Instance, or Deployment header into the Drag header here to group by option
  • Create a new app instance
  • Click the App Instance list to display details
  • Access the quick access menu under Actions to either Update or Delete the application, or access Terminal

Understanding MobiledgeX Reservable Cluster Instances

MobiledgeX will pre-allocate a set of cluster instances on each cloudlet for app instances that use auto-provisioning. With this feature, apps are automatically matched up with the appropriate reservable cluster instance resource requirements. When creating an app instance, and the cluster name is prefixed with "AutoCluster", the system will dynamically create and select a free reservable cluster instance for you to use. Once the app instance is removed or deleted from the reservable autocluster, other app instances are free to use it.

To provision your application:

  1. Ensure you specify the organization that you wish to manage. This ensures that the application you want to provision is within the organization you want to manage.
  2. From the App Instances submenu, click the + sign to launch the Create App Instance page. Or, from the Apps submenu, under the Quick Access menu, click Create Instance.

    Create App Instances screen
    Create App Instances screen

  3. Once you fill in all the required fields, click Create. It can take up to a few minutes to deploy your application to one of our cloudlets. The Progress bar displays the current status of the deployment.

    Application progress bar
    Application progress bar

  4. Once deployed, information about the application appears on the App Instances page.

    App Instances screen
    App Instances screen

Using Terminal

MobiledgeX provides terminal access to VMs for the purpose of debugging, testing, and monitoring the overall health of your VM. Additionally, you can view log files and submit commands to your container.

  1. On the Application Instance page, navigate to the container you wish to interact with.
  2. From the Actions menu, select Terminal.

    Application Instance: Action menu: Terminal
    Application Instance: Action menu: Terminal

  3. To run a command, make sure the Request drop-down displays Run Command.

    Terminal: Request: <strong>Run Command</strong>
    Terminal: Request: Run Command

  4. Type in a command in the Command field, and click Connect. You can start an interactive session if you wish, which is equivalent to the docker -it command.

  5. To view log files, make sure the Request drop-down displays Show Logs.

    Terminal: Request: <strong>Show Logs</strong>
    Terminal: Request: Show Logs

  6. Select any modifiers, for example, you can add timestamps, follow the log, which is equivalent to the docker logs- f command, or select a time window from which to view logs.

  7. Click Close in the upper right-hand corner when done.

    Note 1: If your workload consists of multiple containers, specify the container you wish to operate on from the Container field.
    Note 2: You can only operate on running containers. Only running containers are displayed in the Container drop-down. If you wish to operate on a stopped container, you must restart it.