The following are answers to some frequently asked questions (FAQs) about Open Horizon (Open Horizon).
- Is there a way to create a self-contained environment for development purposes?
- Is Open Horizon software open-sourced?
- How can I use Open Horizon to develop and deploy edge services?
- What edge node hardware platforms does Open Horizon support?
- Can I run any Linux distribution on my edge nodes with Open Horizon?
- Which programming languages and environments are supported by Open Horizon?
- Is there detailed documentation for the REST APIs provided by the components in Open Horizon?
- Does Open Horizon use Kubernetes?
- Does Open Horizon use MQTT?
- How long does it normally take after I register an edge node before agreements are formed and the corresponding containers start running?
- Can the Horizon software and all other software or data that is related to Open Horizon be removed from an edge node host?
- Is there a dashboard for visualizing the agreements and services that are active on an edge node?
- What happens if a container image download is interrupted by a network outage?
- How is Open Horizon secure?
- How do I manage AI at the Edge with models vs AI on the Cloud?
You can install the open source management hub (without the Open Horizon management console) with the “all-in-one” installer for developers. The all-in-one installer creates a complete but minimal management hub, not suitable for production use. It also configures an example edge node. This tool enables open source component developers to get started quickly without the time it takes to configure a complete production Open Horizon management hub. For information about the all-in-one installer, see Open Horizon - Devops GitHub repository.
IBM® Edge Application Manager is an IBM product. But its core components heavily use the Open Horizon open source project. Many sample and example programs that are available in the Horizon project work with Open Horizon. For more information about the project, see Open Horizon GitHub repository.
See Using edge services.
Open Horizon supports different hardware architectures through the Debian Linux binary package for Horizon or through Docker containers. For more information, see Installing Horizon software.
Yes, and no.
You can develop edge software that uses any Linux distribution as the base image of the Docker containers (if it uses the Dockerfile
FROM statement) if that base functions on the host Linux kernel on your edge nodes. This means that you can use any distribution for your containers that Docker is able to run on your edge hosts.
However, your edge node host operating system must be able to run a recent version of Docker and be able to run the Horizon software. Currently, the Horizon software is provided only as a Debian and RPM packages for edge nodes that run Linux. For Apple Macintosh machines, a Docker container version is provided. The Horizon development team primarily uses Apple Macintosh, or the Ubuntu or Raspberry Pi OS Linux distributions.
Additionally, RPM package installation was tested on edge nodes configured with Red Hat Enterprise Linux (RHEL) Version 8.2.
Open Horizon supports almost any programming language and software library that you are able to configure to run in an appropriate Docker container on your edge nodes.
If your software requires access to specific hardware or operating system services, you might need to provide
docker run-equivalent arguments to support that access. You can specify supported arguments within the
deployment section of your Docker container definition file.
Yes. For more information, see Open Horizon APIs.
Yes. Open Horizon uses OpenShift Container Platform Kubernetes services.
Open Horizon does not use Message Queuing Telemetry Transport (MQTT) to support its own internal functions, however the programs you deploy on your edge nodes are free to use MQTT for their own purposes. Example programs are available that use MQTT and other technologies (for example, Apache Kafka, based on the Apache Kafka) to transport data to and from edge nodes.
How long does it normally take after registering an edge node before agreements are formed, and the corresponding containers start running?
Typically, it takes only a few seconds after registration for the agent and a remote Agbot to finalize an agreement to deploy software. After that occurs, the Horizon agent downloads (
docker pull) your containers to the edge node, verify their cryptographic signatures with Horizon exchange, and run them. Depending on the sizes of your containers, and the time it takes them to start and be functional, it can take from just a few more seconds, to many minutes before the edge node is fully operational.
After you have registered an edge node, you can run the
hzn node list command to view the state of Horizon on your edge node. When the
hzn node list command shows that the state is
configured, the Horizon Agbots are able to discover the edge node and begin to form agreements.
To observe the agreement negotiation process phases, you can use the
hzn agreement list command.
After an agreement list is finalized, you can use the
docker ps command to view the running containers. You can also issue
docker inspect <container> to see more detailed information about the deployment of any specific
Can the Horizon software and all other software or data that is related to Open Horizon be removed from an edge node host?
Yes. If your edge node is registered, unregister the edge node by running:
hzn unregister -f -r
When the edge node is unregistered, you can remove the installed Horizon software, for example for Debian-based systems run:
sudo apt purge -y bluehorizon horizon horizon-cli
You can use the Open Horizon web UI to observe your edge nodes and services.
Also, you can use the
hzn command to obtain information about the active agreements and services by using the local Horizon agent REST API on the edge node. Run the following commands to use the API to retrieve the related information:
hzn node list hzn agreement list docker ps
The docker API is used to download container images. If the docker API terminates the download, it returns an error to the agent. In turn, the agent cancels the current deployment attempt. When the Agbot detects the cancellation, it initiates a new deployment attempt with the agent. During the subsequent deployment attempt, the docker API resumes the download from where it left off. This process continues until the image is fully downloaded and the deployment can proceed. The docker binding API is responsible for the image pull, and in case of failure, the agreement is canceled.
- Open Horizon automates and uses cryptographically signed public-private key authentication of edge devices as it communicates with the Open Horizon management hub during provisioning. Communication is always initiated and controlled by the edge node.
- System has node and service credentials.
- Software verification and authenticity using hash verification.
See Security at the Edge .
Typically, AI at the edge enables you to perform on-the-spot machine inferencing with subsecond latency, which enables real-time response based on use case and hardware (for example, RaspberryPi, Intel x86, and Nvidia Jetson nano). Open Horizon model management system enables you to deploy updated AI models without any service downtime.