Glossary
The following is a list of terms that may have slightly different meanings in the context of configuring the ZEDEDA solution than the standard definition: <TEMPORARY NOTE TO BE REMOVED WHEN WE PUBLISH: The goal for these glossary entries is to provide (relatively) short definitions for terms that are (mostly) ZEDEDEA-specific. We can have a pointer back to the long-form articles, but the pointer is not mandatory.>
| Term | Definition |
| ARM64 |
ARM64, also known as AArch64, is a 64-bit architecture developed by ARM Holdings. It extends the ARM architecture, allowing for more memory and computational power compared to the 32-bit ARM architecture. ARM64 is designed for high-performance and energy-efficient computing, making it ideal for mobile devices, embedded systems, and servers. It supports a wide range of applications, from smartphones and tablets to data centers and edge computing devices, providing a balanced mix of performance and power efficiency.
|
| AMD64 |
AMD64, also known as x86-64, is a 64-bit processor architecture developed by AMD. It extends the x86 architecture to support 64-bit computing, allowing for more memory and enhanced performance. AMD64 is widely used in desktops, laptops, servers and high-performance computing applications. It provides backward compatibility with 32-bit software while offering the benefits of 64-bit processing, such as increased addressable memory space and improved computational capabilities. This architecture is supported by major operating systems, including Windows, Linux, and macOS.
|
| attestation | (See “remote attestation” in this glossary) |
| cluster |
A cluster is a group of interconnected computers or servers that work together as a single unified system. These machines, often called nodes, share computing resources, distribute workloads, and coordinate tasks between themselves. The main purposes of clustering include improving performance through parallel processing, ensuring high availability by providing redundancy if one node fails, and enabling horizontal scalability by adding more nodes when needed. Clusters are commonly used in data centers, cloud computing environments, and enterprise applications where reliability and processing power are crucial. To learn about how ZEDEDA uses Kubernetes to assist with the management and orchestration of fleets of edge nodes, see Kubernetes Infrastructure Orchestration - Operations. |
| container | Containers are lightweight, standalone software packages that bundle an application with all its dependencies, libraries, and configuration files, enabling it to run consistently across different computing environments. They provide isolation from other applications while sharing the host system's operating system kernel. (See “Docker” in this glossary.) |
| CRUD |
Create, Read, Update, and Delete. This is a set of common commands available that can be used by administrators to configure the ZEDEDA environment. The command options should be familiar to most IT professionals. Note that the actions available in the GUI may differ from those in the CLI, with the GUI offering actions such as the following: Add, Monitor, Operate, and Remove. You can use these actions to configure the edge nodes and apps in your ZEDEDA environment. (See “Enterprise CRUD operations” or “Roles”) |
| Docker |
The Docker platform enables developers to create, deploy, and run applications in containers, which are lightweight, standalone packages that include everything needed to run a piece of software, such as code, runtime, system tools, libraries, and settings. Docker basically standardizes how these containers are built and run, making applications portable and consistent across different environments. Docker is the de facto standard for containerization. While containers existed before Docker, Docker made them accessible and practical for widespread use by providing tools and a standardized format for packaging and running containerized applications. Docker works great for edge computing, since it enables consistent deployment of applications from cloud to edge locations, the containers are lightweight and start quickly, making them ideal for resource-constrained edge devices. In addition, the same Docker tools and workflows used in cloud environments can be applied to your edge devices, streamlining development and operations. |
| edge access | Edge Access is a remote management application developed by ZEDEDA that provides secure connectivity to edge computing infrastructure through integration with ZEDEDA Cloud. The tool enables remote access, management, and auditing capabilities for both edge devices and applications. Edge Access can operate without requiring any additional infrastructure deployment or local administrative setup for current ZEDEDA Cloud customers. (See Edge Access) |
| edge application |
An edge application is software that has been installed and is available to be deployed on an edge device. Once the application has been deployed, then it’s called an “edge application instance.” At ZEDEDA, an Edge Application represents the Metadata manifest of the software application. Each edge application comes with its metadata manifest, which is basically a description of the application and a set of instructions for using the application. It’s similar to having a detailed list or a blueprint that explains what the app does, how it should be used, and what it needs to work properly. |
| edge application image |
An edge application image is used to create an edge application, and then the edge app instances run on the edge nodes. But here’s a longer and more formal definition:
|
| edge application instance |
Put simply, an edge application refers to the actual running app once it’s been deployed on an edge node. Here’s a more comprehensive definition: An edge application instance in ZEDEDA refers to a specific deployment of an application on an edge node. When you select an application from the ZEDEDA Marketplace and deploy it, the edge node downloads and runs the application with defined runtime characteristics such as adapters, networks, and other details. This creates a real, operational instance of the application on the edge node. For example, it's akin to downloading and running an app from the app store on your iPhone. Multiple instances of the same edge application can be deployed across different edge nodes, allowing for scalability and flexibility in edge computing deployments. (See “Edge Application Instance Overview”) |
| edge computing |
Edge computing is the practice of processing data closer to where the data is being generated, rather than sending it to a data center. The benefits of edge computing include: reduced latency, better response times, and enhanced efficiency. Edge computing can be particularly useful for applications that require real-time data processing, such as industrial IoT devices, manufacturing, energy, and retail. Gartner defines edge computing as “part of a distributed computing topology where information processing is located close to the edge, where things and people produce or consume that information.” |
| edge node |
An edge node is an edge device with ZEDEDA Cloud system running EVE-OS that has been onboarded to a ZEDEDA project. (Prior to onboarding the device is referred to as an “edge device” and after the device has been onboarded, then it’s referred to as an “edge node”. Examples of edge nodes include: IoT gateways, industrial PCs, single-board computers, rack-mount or desktop servers. (See "Edge Node Overview") |
| edge node cluster | To ensure high availability (HA) and data replication, you can group multiple edge nodes into an edge node cluster. This setup keeps your applications and data accessible even if one node fails, minimizing downtime and allowing for faster recovery from hardware failures. If the primary edge node becomes unavailable (for example, due to failure or disconnection), another node in the cluster automatically takes over, restarting the application and keeping your services running. This process is automatic and requires no intervention from you. (See "Edge Node Cluster Overview") |
| edge orchestration |
Edge orchestration refers to managing resources at the edge of the network where the data is generated. This can involve automating the deployment, scaling, and maintenance of applications across large fleets of edge nodes. With Kubernetes ZEDEDA provides a seamless, secure, and scalable edge orchestration solution that simplifies the deployment and management of your applications at the edge. (See "Kubernetes Infrastructure Orchestration - Overview") |
| edge view |
EdgeView provides secure, remote access to your edge devices and applications, allowing you to essentially log in directly to them through a terminal. This can be helpful for troubleshooting and maintenance purposes, since EdgeView essentially gives you hands-on control over your edge assets from anywhere. EdgeView is implemented as a Docker container, with the EdgeView container on the remote device providing the server function and the same container on the user laptop serving as the 'client'. (See “EdgeView FAQ”) |
| enterprise | An enterprise is a complete, discrete set of edge nodes, edge applications, tenants, and an associated ZEDEDA Cloud configuration. Each customer has an enterprise which can be subdivided into logical sub-groups called projects. These logical groupings can help you to manage your devices and foster collaboration between teams. (See "Enterprise") |
| EVE-OS | EVE-OS is a lightweight, open-source Linux distribution that delivers a robust and secure platform for running virtual machines and containerized applications on edge devices such as IoT gateways, industrial PCs, and rugged field computers. (See "EVE-OS overview") |
| instance | (See “edge application instance” in this glossary) |
| jobs |
A job in ZEDEDA parlance is a group of tasks that are triggered by any bulk operation, such as deploying multiple app instances. The task(s) are executed as part of the process of managing and configuring edge devices. Jobs can include actions like installing software, updating EVE-OS, or deploying an application. Jobs are tracked by ZEDEDA, so you can monitor their progress and ensure that everything is running smoothly. Bulk tasks, such as deploying many apps at once, or doing a big EVE-OS update, will end up creating a single job that has a bunch of tasks in it. Jobs are always sorted so the latest one is at the top, as viewed from the GUI. (See “Jobs”) |
| Kubernetes |
Kubernetes (in the context of edge computing environments) is an open-source orchestration system that simplifies the process of managing and scaling a bunch of software apps in containers. It offers a way to manage a bunch of apps that run on devices at the edge of your network. These apps could be used to deploy and manage software on the machines on a factory floor, wind turbines in a field, or even a fleet of rental autonomous vehicles. Kubernetes helps you deploy and manage these applications easily, even if the devices are in remote locations and far away from any datacenters. Kubernetes (sometimes abbreviated as “K8s” or “K3s”) offers early adopters a way to make sure everything in their factory is running smoothly and securely, without the need to have an on-site technician monitoring operations everyday. (See “Kubernetes Infrastructure Orchestration - Overview”) |
| LF Edge |
LF Edge is an open source framework governed by the Linux Foundation that provides edge computing infrastructure and tools. It includes a sandbox environment, powered by ZEDEDA and EVE-OS (a Linux-based operating system), that enables developers to quickly test and deploy edge applications. The platform facilitates rapid proof-of-concept (PoC) development and testing of edge computing solutions through its Marketplace, remote management capabilities, and application orchestration features. LF Edge creates a common framework of hardware and software standards for IoT and edge devices, and other notable members include Intel, Ericsson, and Samsung. (See "LF Edge") |
| Marketplace |
The ZEDEDA Marketplace is an online store for edge computing apps and solutions. You can go here to find a variety of software applications that have been pre-tested and which are ready to go. These apps are made by various tech companies (ZEDEDA partners) and they have been designed to work well with the ZEDEDA platform. So, in short, the Marketplace offers a convenient place for businesses and developers who want to be able to quickly set up and manage their edge computing projects without having to build everything from scratch. (See “Import Models to Enterprise”) |
| network | A network, which is different from a network instance, handles the routing of traffic for edge node hardware that allows it to pass along traffic to and from ZEDEDA Cloud for management purposes, just as one possible example. (See “Network Overview”) |
| network instance |
Network instances provide the virtual network environment for edge applications. Ultimately, a network instance is a virtual subnet maintained by EVE-OS. Network instances can be completely internal to the edge node or can be attached to external interfaces. They can also provide services such as DHCP, NAT, and DNS to edge applications. (See "Use the ZEDEDA CLI to Manage a Network Instance") |
| offline profile server | This is a small app running on an edge node that allows you to manage other application instances on that node when connectivity to ZEDEDA Cloud is down. (See “Offline Profile Server”) |
| onboarding | Edge Node onboarding refers to the process of integrating a new edge device into an enterprise's ZEDEDA environment. The EVE-OS (Edge Virtualization Engine Operating System) must be installed on the device as a prerequisite, but this is just the first part of the process. During onboarding, the edge node receives a project association, security credentials, management policies, and network settings. This process ensures secure integration of edge nodes while maintaining enterprise security policies and management requirements. |
| project | A project is a logical grouping of one or more edge nodes. While an enterprise can have several projects, each edge node can only belong to one project. (See project under "Concepts related to Edge Nodes") |
| remote attestation |
Remote attestation is a security mechanism that enables a system to verify the integrity and authenticity of a remote hardware device, such as an edge node. The remote attestation process allows a trusted authority to validate that a remote device is in an expected state, meaning that it has a specific version of software running, or certain configuration settings, or security policies. The process ensures the device has not been tampered with. During remote attestation, the remote system provides cryptographically signed evidence of its current state, including hardware configuration, firmware, operating system, and a list of software applications that are running. The hardware security feature, Trusted Platform Module (TPM), ensures that the attestation process itself has not be compromised in any way. (See “Trusted Platform Module Based Remote Attestation Overview”) |
| remote orchestration | This is the process of managing and controlling edge nodes and apps from a remote location, typically through ZEDEDA Cloud. (See “Orchestration Overview” under “Kubernetes Infrastructure Orchestration - Overview”) |
| storage | Storage, in the context of ZEDEDA, refers to how data is saved and managed on the edge devices. This includes storing image data, application data, and other necessary information for running applications on the edge. ZEDEDA provides persistent storage that remains even when the applications are not running, as well as transient storage that is tied to the lifecycle of an application. (See “Storage Overview”) |
| Trusted Platform Module | While Trusted Platform Module (TPM) is not a ZEDEDA-specific term, it’s an international standard for the security chips used in edge devices to store cryptographic keys.The TPM performs security tasks such as generating and managing crypto-keys, checking system integrity, encrypting data, authenticating devices, and assisting in remote attestation for edge devices. Having a TPM on your edge device is like having a secure vault that helps keep your sensitive information safe and helps ensure that the edge nodes have not been tampered with. (See “Trusted Platform Module Based Remote Attestation Overview”) |
| user agent |
User agents are the primary interfaces available to access and control the edge devices in your ZEDEDA deployment. The user agents allow you to access the ZEDEDA platform to manage and monitor your edge infrastructure. The following user agents are currently supported:
|
| virtualization | Virtualization refers to the process of creating a software-based (or "virtual") representation of various computing resources, such as servers, storage devices, networks, or operating systems. It enables multiple virtual instances to run on a single physical hardware platform, allowing for more efficient use of computing resources. A hypervisor manages these virtual instances and ensures they remain isolated from each other while sharing the underlying hardware. |
| volume instance | A volume instance handles data storage on the edge nodes. It can retain image (binary) data or (runtime) application data. Some volume instances are persistent and keep their data even after the edge applications using them have stopped. Other volume instances are temporary and only store data while the application is running. (See “Volume Instances” under “Storage Overview”) |
| x86 | (See “AMD64” in this glossary) |
| ZCLI | ZEDEDA CLI (ZCLI) is a command-line interface for interacting with ZEDEDA Cloud. Access is also available using the ZEDEDA GUI and ZEDEDA API. Note that Docker Desktop must be running before you can start using ZCLI. (See "ZEDEDA CLI Overview") |
| ZedCloud | This term has been deprecated. The new name for ZedCloud is ZEDEDA Cloud. (See “ZEDEDA Cloud” in this glossary) |
| ZedControl | This term has been deprecated. The new name for ZedControl is ZEDEDA GUI. (See “ZEDEDA GUI” in this glossary) |
| ZEDEDA Cloud | ZEDEDA Cloud is a suite of ZEDEDA-managed microservices that orchestrates EVE-OS nodes. ZEDEDA Cloud is a cloud-native, SaaS platform that provides orchestration and management for edge computing environments and helps simplify the deployment and management of edge devices. You can interact via graphical user interface (GUI), command line interface (CLI), or application programming interface (API). (See "Onboard an edge node to ZEDEDA Cloud") |
| ZEDEDA GUI | The ZEDEDA graphical user interface (GUI) is an easy-to-use web application that allows you to interact seamlessly with ZEDEDA Cloud. This interface allows you to manage your resources, monitor activities, and perform various tasks in a more intuitive and visual manner, ensuring that you can efficiently oversee and control your cloud operations without ZCLI. (See "ZEDEDA Graphical User Interface overview") |
| ZEDEDA Cloud Terraform Provider |
The ZEDEDA Provider helps you automate and manage your edge nodes and other resources. It offers an alternative way to configure your nodes, without having to use the ZEDEDA’s GUI and ZCLI. But just a heads up, it’s only for managing configs and not for monitoring. The ZEDEDA Provider talks with Terraform Core and ZEDEDA Cloud by sending commands (RPCs) to the provider. In turn, the provider chats with ZEDEDA Cloud, which sends replies through the provider to Terraform. (See “ZEDEDA Terraform Provider”) |
| Zero-Touch Deployments | Zero-touch management simplifies the deployment of edge devices by automating the assignment of policies and the deployment of applications. Zero-touch management uses tagging to match edge nodes with their corresponding applications and policies, enabling automated deployments with minimal administrative overhead. (See "Zero-Touch Deployments overview") |
| zero trust edge security policy | The Zero Trust security model flips traditional security on its head. Instead of trusting anything inside your network, it treats every access request as suspicious, regardless of whether that request originated from inside or outside your network. All requests are treated as suspicious, regardless of where they came from. Zero Trust continuously verifies the identities of users and devices, and validates device health, restricting access to the bare minimum needed to complete a task. Networks are segmented into secure segments, and all data is encrypted end-to-end. The core idea is simply that nothing should be trusted, and everything should be verified, making it much harder for attackers to move around in your network if they manage to gain access. (See blog "Zero Trust Orchestration for the Distributed Edge") |
| ZEDEDA Kubernetes Service |
The ZEDEDA Kubernetes Service (ZKS) is <TBD > deploy, manage, and modernize their edge deployments effortlessly. This allows organizations to remotely deploy Kubernetes infrastructure at the distributed edge cost efficiently, with minimal configuration, and complete security from day one. ZEDEDA Edge Kubernetes Service provides full life-cycle managed Kubernetes, including a runtime curated, managed, and supported by ZEDEDA. |