Manage an Application Instance

​

Introduction

From the application instance detail page you can take lifecycle actions, open a remote console, create and roll back snapshots, and manage patch envelopes. For a reference of all tabs, fields, and run states on the detail page, see Application Instance Details.

​

Prerequisites

• You have the SysManager or SysAdmin role in your enterprise. See Manage Roles.
• At least one application instance is deployed and visible in Infrastructure > Workloads > Applications.

​

Open the Application Instance Detail Page

1. In the sidebar, navigate to Infrastructure > Workloads > Applications.
2. In the application list, click the name of the instance you want to manage.

The detail page opens. The header shows the current status, application type, and the name of the hosting node. For a reference of all tabs and fields on the detail page, see Application Instance Details.

​

Where Operations Are Available

Application instance operations are available from multiple places:

• The toolbar and Actions menu on the instance detail page: the toolbar is in the upper right; click the three-dot Actions button to see lifecycle actions.
• The row action menu on the application list: hover over a row to reveal the row action controls, including the Configure (gear) icon and additional actions.
• The bulk action bar on the application list: select one or more rows using the checkboxes, and the bulk action bar appears with actions that apply to all selected instances at once.

The operations shown depend on the current state of the instance and your permissions.

​

Bulk Actions

Select one or more application instances from the list using the row checkboxes to reveal the bulk action bar. The following actions are available:

​

Toolbar Actions

The toolbar in the upper right provides the following actions.

​

Remote console

Opens a VNC graphical console to the running application through EdgeView. Use this to access the application display without a direct network connection to the node. Requirements:

• You have update permission for this instance.
• The application must be online.
• The node must be online.
• VNC must be enabled in the app image.
• The project’s EdgeView policy must permit application access.

Without update permission, the Remote Console control (including the SSH Terminal option) does not appear on the toolbar, rather than appearing in a disabled state. When you have update permission but one of the other requirements is not met, the control appears disabled with a message explaining why (for example, a remote console session is already active, VNC is not enabled for the application, or the node or application is offline).

1. Click Remote Console.
2. Review the remote access notice and click Continue.
3. The VNC console opens in a pop-out console window.

To open an SSH terminal instead:

1. Click the dropdown arrow next to Remote Console.
2. Select SSH Terminal.
3. In the SSH Terminal dialog, enter the username (default: root), port (default: 22), and optionally upload a PEM private key file.
4. Click Open Terminal.
5. Review the remote access notice and click Continue.
6. The SSH terminal opens in a pop-out console window.

SSH access requires the application to have a routable IP address and the project’s EdgeView policy to permit application access.

​

App update status

The Refresh icon button opens the App Update Status panel. This panel shows whether the running instance is using the current version of its source edge app image. If a new version is available, the panel shows the current and target version numbers, a summary of configuration differences, and an action button to apply the update.

​

Logs and events

• Click the File icon to navigate to Infrastructure > Monitor > Logs filtered to this application instance.
• Click the Activity icon to navigate to Infrastructure > Monitor > Events filtered to this application instance.

​

Configure

Opens the General Settings dialog for this instance. Use this to update the instance’s title, description, Enable Logs Access setting, Staggered Start Delay, VMM Overhead, and tags without deleting and recreating the instance. Requires: Update permission for this instance.

​

Actions Menu

Click the three-dot Actions menu in the upper right to see all available lifecycle actions. The actions shown depend on the current state of the instance.

​

Start

Starts the application on its node. Existing network connections and volumes are preserved. Use when: The instance is halted or was created in a deactivated state. Verify: Status changes to Online after the node processes the request.

​

Restart

Stops and restarts the application. Expect a brief outage while the application stops and restarts. Use when: The application is unresponsive or you need to apply a configuration change that requires a restart. Verify: Status moves through Halted and returns to Online.

​

Reactivate

Re-applies the latest configuration to the application. The application goes briefly offline during reactivation. This action appears instead of Restart when the app image has a pending configuration update that requires reactivation rather than a full image replacement. Use when: The App Update Status panel shows a pending update classified as Reactivate. Verify: The App Update Status panel shows no pending updates.

​

Update

Applies a new version of the source edge app image to this instance. The instance may restart briefly. A configuration diff is shown so you can review what will change. You can optionally create a snapshot before updating if snapshots are enabled for this instance. Use when: The App Update Status panel shows a new version is available and the update type is Update. Verify: The App Update Status panel shows no pending updates after the operation completes.

​

Purge & Update

Clears all local application data and pulls the latest version of the source edge app image. This action is destructive and may cause data loss. A configuration diff is shown. You can optionally create a snapshot before purging to preserve a rollback point. Use when: The App Update Status panel shows the update type is Purge & Update, or the application requires a clean state to apply a new image version. Verify: Status returns to Online after the purge and re-deployment complete. The App Update Status panel shows no pending updates.

​

Create Snapshot

Creates a point-in-time snapshot of the application’s current state, including configuration and all attached volumes. You can roll back to this snapshot from the Storage tab. Requirements: Snapshots must be enabled for this instance. Only one snapshot is retained per instance; creating a new snapshot replaces the existing one. Not available for Docker Compose application instances. Verify: The snapshot appears in the Storage tab with a status of Idle or Created. To roll back to a snapshot:

1. Open the Storage tab on the instance detail page.
2. Locate the snapshot in the snapshots list.
3. Click Rollback.
4. Confirm the rollback. The instance reverts to the state captured in the snapshot.

To delete a snapshot:

1. Open the Storage tab.
2. Find the snapshot and click Delete.
3. Confirm the deletion.

For a full overview of how snapshots work, see Application Snapshot Overview.

​

Attach patch envelope

Attaches a patch envelope from Runtime Bundles to this instance. When the envelope is in the Active state, EVE-OS (Edge Virtualization Engine) delivers its artifacts to the application on the node. Requirements: This action is not available for Docker Compose application instances.

1. Click Attach Patch Envelope.
2. In the dialog, search for and select the patch envelope.
3. Click Attach.

Verify: The patch envelope name appears in the instance metadata after attachment. For details on creating and managing patch envelopes, see Update Applications with Runtime Bundles.

​

Detach patch envelope

Removes the currently attached patch envelope from this instance. Files previously delivered by the envelope will no longer be available to the application.

1. Click Detach Patch Envelope.
2. Confirm the detachment in the dialog.

Verify: The patch envelope name no longer appears in the instance metadata.

​

Stop

Stops the application on its node. Persistent volumes are preserved. The application is unavailable until you start it again. Use when: You need to stop the application without deleting it or its data. Verify: Status changes to Halted.

​

Delete

Deletes the application instance from the node. The cascade delete dialog shows any volumes and network instances that will be affected. This action is irreversible. Use when: The instance is no longer needed and its data can be discarded. Verify: The instance disappears from the application list.

​

Verify Changes

After any management action, confirm the result:

1. On the Overview tab, verify that the status reflects the expected state (for example, Online after activating, Halted after deactivating).
2. For update operations, open the App Update Status panel and confirm it shows no pending updates.
3. For snapshot rollbacks, check the Storage tab to confirm the snapshot list reflects the current state.
4. For patch envelope changes, verify the patch envelope name appears or is removed from the instance metadata.
5. If the status does not update as expected, navigate to Infrastructure > Monitor > Logs, filter by the instance, and review log output for errors.

​

Next Steps