This page contains a list of features, changes, known issues and known limitations of the Nerve releases.
This version was released on March 1st, 2022. Unless otherwise stated, all known issues and limitations of the previous version are still valid.
|Management System||Added support for upload of compressed workload images (ZIP and GZIP).
Switched the Management System update procedure to a requested service.
Added display of capabilities for registered nodes.
|Remote Connections||Nerve Connection Manager v1.0.4 released.|
|Workload management||Added support for snapshots of Virtual Machine workloads.
Added support for backups of Virtual Machine workloads.
Display of network information for Virtual Machine workloads
|Nerve Devices||Added the Toshiba FA2100T-700 as a qualified Nerve Device.|
|Nerve Data Services||The Gateway now uses the Smart Connection Creation Mechanism (SCCM).
Added support for setting a home dashboard and kiosk mode in Grafana.
Added Kafka Consumer as a supported input format.
Refer to What's new in 2.4.1? for more information on new features.
- Multiple UI/UX quality of life changes.
- Improved the communication of the system in logs and error messages.
- Improved robustness of internal Nerve networks.
- Improved robustness of remote connections.
- Improved download and upload times when provisioning and exporting VM workloads.
- Improved the system's functionality when operated through the API.
- Nerve Data Services: Reduced memory usage when using a TimescaleDB.
- Nerve Data Services: Improved robustness of the Gateway.
- Nerve Data Services: Improved Grafana performance.
- Fixed an issue where using an email address with capital letters for a user profile would render that user inaccessible.
- Fixed an issue where the dead letter queue of the Management System would get filled up.
- Fixed an issue where ports were not checked if they had already been in use when creating a remote connection through the API.
- Fixed an issue where remote connections would end up stuck in a "working" state when using Google Chrome or Microsoft Edge browsers.
- Fixed an issue where a node update would be stuck if power was lost in the downloading phase.
- Fixed an issue where losing power during a Docker workload update would break the update process for the same workload.
- Fixed an issue where VM resources for deployed VM workloads could be allocated below the minimum limit when done through an API call.
- Fixed an issue where the logs would be filled by the host when there is no connection to the internet.
- Fixed an issue where the same user role could be applied multiple times to a user through API calls.
- Fixed an issue where the Management System would return the wrong status code when provisioning a workload using the API.
- Fixed an issue where nodes registered through the API would be displayed as offline until the page is refreshed.
- Fixed an issue where a wrong error message would be displayed when a user not registered in the Management System used a remote connection.
- Fixed an issue where labels could not be added to nodes.
- Fixed the deployment error feedback message when a VM workload is deployed to a node that does not have enough storage space for VMs.
- Fixed an issue where the Docker used space graph in the node details would display 0% even though it is full.
- Fixed an issue in the Management System where UI elements would be missing when switching language to Korean.
- Fixed an issue where a node would enter an unknown state, in which resource usage or workload deployment would not work.
- Fixed an issue in the Local UI where the online/offline switch would not display the correct state after a node reboot.
- Fixed an issue where the path of Docker values for persistent storage would be incorrectly marked as invalid.
- Fixed an issue where labels could not be edited for released workloads.
- Fixed an issue where the node logging window would not open for nodes with serial numbers starting with
- Fixed an issue where user names in the Nerve Management System where compared case sensitive when coming from an LDAP server. User names are now tested case insensitive.
- Fixed an issue where VM workloads could not be undeployed under certain conditions.
- Fixed an issue where nodes would not be filtered by labels automatically in the deployment process.
- Fixed an issue where a retry for a deployment would not work because of connection timeout due to an offline node.
- Fixed an issue where certain buttons in the Management System would change their positions randomly.
- Fixed an issue where system notification background images would not be displayed.
- Fixed an issue where a node update would mistakenly be marked as failed following a restart after power was cut in the update process.
- Fixed an issue where a passthrough of the wan interface to a VM would break the node availability.
- Fixed an issue for VM workload resource allocation where the wrong resource values would be read, which impacted the functionality of the VM.
- Fixed an issue where a Docker workload would not restart after a workload update, even when the restart option had been selected.
- Nerve Data Services: Fixed an issue where the publisherID for the OPC UA subscriber input could not be set.
- Nerve Data Services: Fixed an issue where a TimescaleDB container would use up all RAM rapidly.
- Nerve Data Services: Fixed an issue where the Gateway would end up in a loop after a new configuration had been applied.
- Nerve Data Services: Fixed an issue where the Local UI session would timeout during Gateway configuration, causing the configuration to be lost.
- Nerve Data Services: Fixed an issue where the Data Services would not work for nodes running on the ACRN hypervisor.
- Nerve Data Services: Fixed an issue that allowed Gateway configuration fields to be filled in automatically by the browser.
- Nerve Data Services: Fixed an issue where OPC UA Subscriber would fall back to polling mode.
- Nerve Data Services: Fixed an issue where the Gateway would import 0 values for OPC UA in polling mode, even though no data was lost.
- Nerve Data Services: Fixed an issue in the database data retention policy where hours were treated like minutes. However, this only applies to newly configured policies.
- Nerve Data Services: Fixed an issue where the Local UI would become unresponsive when previewing a database with a high number of columns.
- Nerve Data Services: Fixed an issue in the central database where identical table names on different nodes would break the database table preview.
Known issues and limitations
- It is recommended to install version 1.0.4 of the Nerve Connection Manager due to issues found in versions 1.0.2 and 1.0.3.
- The Nerve Connection Manager might trigger warnings from antivirus software. This is due to a library that was used in development.
- Snapshots cannot be taken for VM workloads that have an additional disk defined through the Management System.
- The upload of a compressed virtual machine image larger than 2.5 GB might fail during the provisioning of a VM workload.
- Defining the root folder in a Docker volume for persistent storage might cause the deployment of that Docker workload to fail.
- Nerve Data Services: Docker workloads connected to
nerve-dsneed to be updated after updating a node to 2.4.1 without changing anything. Select Update in the workload version settings and update the Docker workloads on all nodes where they are deployed as well.
- When power is lost at the downloading phase of the node update process, it might not be possible to finish the update.
- Nerve Data Services: When updating a node that a database data retention policy active, an issue is carried over where hours are treated like minutes and data is erased earlier than expected.
Scaling and performance limitations
This release has been tested to perform within the following scaling boundaries:
|Maximum number of concurrent devices||200|
|Maximum number of concurrently logged in users||5|
|Maximum workload size||50 GB|
|Maximum number of concurrent remote access sessions||3|
|Maximum number of workloads in workload repository||200|
|Maximum data upload per node||5 datagrams per second with at least 10 sensor values for 200 nodes in parallel.|