Release Manager Overview

​

Introduction

Release Manager gives you a single place to track the EVE-OS (Edge Virtualization Engine) software version running on every node in your fleet and push updates to any subset of nodes. Instead of updating nodes one at a time from each node’s detail page, you can roll out a new EVE-OS version to an entire project, a filtered group of nodes, or individual nodes, all from one view. Release Manager was previously called Patch Envelopes.

​

Prerequisites

• You have the SysManager or SysAdmin role in your enterprise. See Manage Roles.
• At least one node onboarded to Edge Infrastructure Services.

​

How It Works

Release Manager is available in the sidebar under Infrastructure > Operations > Release Manager. It has two tabs: Nodes and History.

​

Nodes tab

The Nodes tab shows the update status of every node in your fleet. When you open it, Release Manager scans the fleet in the background and populates the data automatically. A loading indicator appears in the tab bar while the scan is running. If the scan cannot finish loading fleet data, a Fleet scan interrupted notice appears. The notice reports how many of the fleet’s nodes were loaded, and the status counts cover only the loaded nodes. Values that could not be loaded show a dash or Node count unavailable. Click Retry fleet scan to run the scan again. Status chips appear at the top of the tab. Each chip shows a live count for one update state across the fleet: Total, Needs Update, Downloading, Downloaded, Installing, and Up to Date. A Failed chip appears in addition when at least one node has a device-reported update failure. Clicking a chip filters the node list to show only nodes in that state. Project view is the default display. The table lists each project that has at least one node, with the following columns. Each project row has an action menu (⋯) that lets you run update operations across all nodes in the project at once. Project drill-down opens when you click a project row. It is a dedicated page showing the project name, total node count, and three action buttons — Download, Install, and Download & Install — in the page header, for running project-wide updates without selecting individual nodes. A Back button at the top returns to the Nodes tab. Below the header, the same status chips are scoped to that project, followed by a node-level table with columns for Name, Arch, EVE Version, Downloaded, and Status. You can select individual nodes and act on them from there. Node view replaces the project table in two cases: when you click a status chip (which filters to nodes matching that status across all projects) or when you search for a node name that does not match any project name. Node view adds a Project column so you can see which project each node belongs to.

​

Cluster upgrades

Release Manager does not currently include a tab for clusters, and cluster-level EVE-OS upgrades are not available in the console. Clusters upgrade EVE-OS as a unit, so the operation applies to all member nodes together rather than allowing per-node targeting. Use the ZCLI (ZEDEDA command-line interface) edge-node-cluster upgrade command instead. See Upgrade a Cluster.

​

History tab

The History tab shows the EVE-OS image history recorded for a single node. Because history is recorded per node, you first select a node from the picker at the top of the tab. The table then lists every publish and activate event for that node, with the image version, the action, the user or system that triggered it, and the timestamp. Release Manager keeps the selected node in the page URL, so you can bookmark or share a link to one node’s history. To review the outcome of update jobs, open Infrastructure > Operations > Jobs.

​

Node Update Statuses

These statuses appear on the Nodes tab. Each node in Release Manager has one of the following update statuses. A red triangle icon appears alongside a node’s status badge when the most recent update attempt on that node failed. Hover over the icon to see the failed version, and click it to open the associated job. Nodes with a failed update are also counted in the Failed chip at the top of the page.

​

Key Benefits

• Fleet-wide visibility. A single page shows the EVE-OS version status of every node across all projects, with live counts by status.
• Project-scoped rollouts. You can update all nodes in a project with a single action, making staged rollouts by environment or region straightforward.
• Decoupled download and install. Downloading stages a new EVE-OS image on the node without rebooting, so you can pre-stage updates and activate them during a maintenance window.
• Granular targeting. You can act on a whole project, a filtered cross-project set, a manual selection, or a single node, all through the same interface.
• Update history. The History tab gives a per-node audit trail of every EVE-OS image publish and activate event, including who triggered it and when.

​

Next Steps