Inference
Marketplace
New Features
Single-Use Installer
As part of the node onboarding flow, you can now create and download a single-use installer or a live image through Edge Infrastructure Services without the need for any ZCLI interactions.Edge View UI
To provide a more seamless and secure experience for managing your edge devices, Edge View has been enhanced by integrating its functionalities directly into Edge Infrastructure Services, making remote access and troubleshooting for your EVE-OS (Edge Virtualization Engine) instances and edge apps more intuitive and efficient. This update eliminates the need for cumbersome SSH or local Docker installations for many common tasks, streamlining your workflow. Key improvements include:- Direct UI interaction: perform actions like VNC or SSH into applications, and download “collect-info” files directly from Edge Infrastructure Services with one click.
- Simplified troubleshooting: access troubleshooting commands to view logs, files, and network and system monitoring commands through a terminal session in Edge Infrastructure Services.
- Improved user experience: the new integration simplifies complex multi-step processes into single-click operations.
Edge View Security (access control with SSH key pairs)
For enhanced security, you can now limit access to Edge View to specific users. The system uses SSH key pairs for authentication, with a public key being uploaded to the node and a private key on the user’s laptop. All commands run over Edge View must be signed with the corresponding SSH private key. The node verifies the signature on each command using its stored public keys, and if the signature is valid, the command will be executed. This system helps ensure you can identify who is running commands on your edge devices.Hosted EVE-OS Images
Hosted EVE-OS Images are designed to simplify the process of updating your nodes. This new capability provides a centralized, ZEDEDA-hosted data store for all supported EVE-OS images, eliminating the need to manage your own image repositories. This feature reduces the manual effort and associated costs of maintaining your EVE-OS versions and infrastructure. It also bolsters security by ensuring images are sourced directly from ZEDEDA. You can now more easily keep your edge infrastructure updated with the latest features and critical security patches. To use this enhancement, make sure your firewall permits connectivity to the ZEDEDA-hosted data store URL (an S3 bucket on AWS).Cellular Access Point Name (APN) Attach Configuration
LTE connections consist of two IP bearers: the initial (also known as attach) bearer and the default data bearer. Both bearers require configuration settings (APN, IP type, and potentially credentials or more). Manually configuring the initial bearer is often necessary for private LTE networks or when transitioning between network providers, in which case the modem may not have a suitable profile installed. When adding a cellular network from Library > Networks, you can now configure Attach APN details.Automate Deployments with Application Profiles
Available for API and Terraform. App Profiles, Asset Groups, and Profile Deployments work together to streamline application delivery to nodes. An App Profile acts as a comprehensive bundle, encapsulating applications, network settings, and volume configurations. An Asset Group is a logical grouping of your nodes. A Deployment Profile can deploy an App Profile to the nodes identified in the Asset Group. This approach, along with the ability to manage it through Terraform, reduces the manual effort required, ensures consistency across devices, and allows for automatic deployment to new devices, making it easier to scale and maintain your edge infrastructure.Enhanced Features
Tool tips
In addition to the existing “i” informational icon in Edge Infrastructure Services for showing informational messages, a ”?” is now used for hover tooltips and help tooltips for form fields.Edge Sync Config Bulk Download
From the existing Nodes > NODE_NAME > … > Download Edge Sync Config, you can now select multiple nodes from the list to download node configurations in bulk. The output is a single JSON file that aggregates multiple node configurations for each selected node, downloaded to your local system.VLAN Metrics
From the existing Nodes > Adapters tab, expand an adapter and toggle Show/Hide Reported Status for your adapters. From Nodes > Adapters tab, select VLAN Details and expand the logical label, where you can now also toggle Show/Hide Reported Status for your VLANs. The status details include:- Bytes transferred and received.
- Packets transferred and received.
- Errors.
- Drops.
- ACL drops.
- ACL limit rate drops.
ECC Memory Monitoring
Error-correcting code (ECC) memory is a type of memory that can detect and correct common types of internal data corruption. This ECC Memory Monitoring feature reports on correctable (single-bit) and non-correctable ECC errors. These errors are a sign of early hardware failures, enabling you to replace hardware before the errors become non-correctable and have operational impact. From the existing Nodes > Status tab, you can now see the number of correctable and non-correctable errors, plus the overall ECC Memory status, such as:- Not applicable.
- Pass.
- Degraded: correctable ECC errors.
- Failed: non-correctable ECC errors.
SMART Status
Self-Monitoring, Analysis, and Reporting Technology (SMART) metrics provide insights into the health and performance of storage disks. These metrics enable proactive monitoring, helping to identify potential failures before they occur. By leveraging SMART data, you can ensure optimal storage performance, prevent data loss, and extend the lifespan of storage devices. From the existing Nodes > Storage tab, you can now see the overall SMART Status (if available), plus vendor-specific attributes including:- ID.
- Attribute name.
- Value (temperature converted from raw Kelvin to Celsius).
- Raw Value of temperature.
Project Types renaming: Legacy is now Standard
We’ve renamed the Legacy project type to Standard. This change clarifies the naming convention that emerged when “deployment projects” were introduced as a new project type. This update streamlines your experience so that when you add a new project, the GUI form automatically defaults to Standard as the project type. You can find this change when adding a new project under Administration > Projects > Add New. The update is a visual UI change only. The same ENUM is used in the backend, so there is no impact to existing configurations.Managing EVE-OS Images: Latest is now Default
We’ve renamed the Latest image to Default image. This change clarifies the naming convention when you define the EVE-OS version as the primary one you want to use, since you can use any version and it does not necessarily have to be the latest. As part of the Hosted EVE-OS Images feature, you can also change the default EVE-OS image to be used for nodes through Edge Infrastructure Services.Columns removed from node onboarding workflow
We have streamlined the node onboarding workflow by removing several read-only columns from tables in Edge Infrastructure Services. The Bundle and Run State columns from the Network Adapters table, and the Bundle column from the IO Adapters table, were removed from the second page of the onboarding wizard. This change reduces unnecessary complexity, making the onboarding process faster and more intuitive, as these columns didn’t contribute to user decision-making.Marketplace App Type filter
In the Marketplace, you can now filter by App Type.Edge Sync Data Store configuration
In the Edge Sync configuration, you can now optionally include a Data Store.- If you intend to use collect-info.sh for troubleshooting, you need a local HTTP data store within the air-gapped environment where you’re running Edge Sync.
- This feature requires EVE-OS version 14.5.2-LTS or greater.
Known Issues
Edge View UI issues
- Single Remote Console Session per edge application: only one remote console session can be active per edge application at a time.
- For Edge View VNC sessions, only one ongoing VNC session per node is supported.
- Graceful session closure recommended: close the session from the Edge View UI screen before attempting to access another app on the same node. Switching between apps may result in errors such as “Command execution failed”.
- Connection limit configuration: if the default number of allowed connections per session is set to 1, parallel activities will be restricted. Configure the default allowed connections to more than 1 to enable smoother parallel workflows. Update the Edge View policy in the project according to the required number of connections.
- SSH terminal persistence: the SSH terminal session will not persist when navigating away from the screen.
- SSH terminal autocomplete limitation: the SSH terminal operates in a typing-only mode, and command auto-completion using the Tab key will not work.
- Status display on connectivity loss: if the device loses connectivity to Edge Infrastructure Services, the Edge View status will still be shown as “Activated” in the UI. However, the node’s status color will update to reflect the actual connectivity state.
- VNC is not working from the new Edge View UI screen.
Miscellaneous
- In the single-use EVE-OS installer option for onboarding a node, the live image boot is not working properly if an existing EVE-OS image is already present on the node.
- In the single-use EVE-OS installer option for onboarding a node, the toggle for “I already have EVE-OS installed on my device or I will install it later” and the associated installation instructions shown are not valid for this flow.
- The static IP address of the Docker runtime shows as empty (Not Available) in the API after a node reboots due to power failures, despite the runtime retaining the IP internally.
- The static IP is missing from API responses after multiple power failure reboots, but visible via SSH on the runtime.
- Docker Compose apps run correctly even when the IP is not reported in the API.
- The issue does not self-resolve over time and occurs intermittently after several reboot attempts.
- The runtime’s network state is internally consistent; it is the network addresses maintained by EVE-OS that take time to stabilize.