Tetra HTTP Relay Agent v1.x Release Notes
The following are the release notes for Tetra HTTP Relay Agent versions 1.x.
v1.0.0
Release date: 13 Nov 2024
What's New
TetraScience has released its first version of the Tetra HTTP Relay Agent, version 1.0.0. The Tetra HTTP Relay Agent allows Tetra Data Pipelines and other TetraScience components to communicate with customers' on-premises systems, even when a customer's firewall blocks incoming network traffic from the Tetra Data Platform (TDP). The Agent is an on-premises, instrument-agnostic, Dockerized application that processes commands sent from the TDP that include details for HTTP and HTTPS requests, which the Agent then relays to target on-premises systems.
Here are the details for what's new in Tetra HTTP Relay Agent v1.0.0.
Prerequisites
The following Tetra Data components are required for Tetra HTTP Relay Agent v1.0.0:
NOTE
Documentation for Tetra Data components is in the TetraConnect Hub. To request access, see Access the TetraConnect Hub.
- Any supported version of the Tetra Data Platform (TDP)
- The host server must also have the following:
- Docker version 20.10.21 or higher (compatibility with lower versions is possible, but untested)
- ts-sdk-python v1.3.0 or higher
- Outbound internet access to the TDP
- At least one vCPU with a processing speed greater than two GHz
- At least one GB MEM dedicated to the Agent
- Enough disk space to accommodate Docker, an approximately 250MB image, and associated container logs (log volume will correlate to runtime length and usage of the agent, but default Docker settings will capture approximately one gigabyte of logs per year, plus approximately 6.5 megabytes of logs per 1,000 commands processed by the Agent)
New Functionality
New Functionality includes features not previously available in the Tetra HTTP Relay Agent.
Customers can use the Tetra HTTP Relay Agent to enable communication between the TDP and on-premises servers that have restrictions on in-bound traffic from the public internet. To enable this, the Agent includes the following new functionalities:
- The Agent is designed to handle large volumes of concurrent commands issued by pipelines running in the TDP.
- The Agent handles legacy Generic Data Connector GDC command,
TetraScience.Connector.gdc.HttpRequest
, which enables customers to upgrade from the GDC to the Tetra HTTP Relay Agent for supportability and performance reasons. - The Agent handles the new command,
TetraScience.Connector.http.HttpRequest
, for generic HTTP and HTTPS requests. - The Agent handles the new command,
TetraScience.Connector.http.Request.V2
, for secure communication between TDP components and on-premises components.
Enhancements
Enhancements are modifications to existing functionality that improve performance or usability, but don't alter the function or intended use of the system.
- This release offers greater stability, observability, performance, bug fixes, and security updates compared to the early adopter program (EAP) version.
Bug Fixes
There are no bug fixes in this release.
Deprecated Features
There are no new deprecated features in this release. For more information about TDP deprecations, see Tetra Product Deprecation Notices.
Known and Possible Issues
- Default deployment settings for the Tetra HTTP Relay Agent v1.0.0 configure it to elastically allocate system resources to process large numbers of HTTP and HTTPS requests concurrently. This behavior may lead to system instability for extremely high volume use cases.
Installation Considerations
To install the Agent, see the Tetra HTTP Relay Agent Installation Guide (v1.0.x).
To configure the Agent, see the Tetra HTTP Relay Agent User Guide (v1.0.x).
Other Release Notes
To view other Tetra Agent and Tetra Data release notes, see Tetra Agent and Tetra Data Release Notes.
To view other TDP release notes, see Tetra Data Platform (TDP) Release Notes.
Updated about 1 month ago