14. Release Notes¶
14.1. Supported Platforms¶
Cloud Discovery Service is supported on the platforms listed in Table 14.1.
Operating System |
Version and CPU |
---|---|
Linux® |
All Linux platforms on x64 CPUs in the RTI Connext DDS Core Libraries Release Notes with the same version number, except SUSE® Linux Enterprise Server. |
macOS® |
All macOS platforms on x64 CPUs in the RTI Connext DDS Core Libraries Release Notes with the same version number. |
Windows® |
All Windows platforms in the RTI Connext DDS Core Libraries Release Notes with the same version number. |
Note: POSIX®-compliant architectures that end with “FACE_GP” are not supported and custom platforms are not supported.
14.2. Compatibility¶
For backward compatibility information between Cloud Discovery Service 6.1.2 and previous releases, please see the Migration Guide on the RTI Community portal.
14.2.1. Connext DDS compatibility¶
Cloud Discovery Service can be used to provide discovery for applications built with RTI Connext DDS, except as noted below:
Starting in RTI Connext DDS 5.1.0, the default message_size_max
for the
UDPv4, UDPv6, TCP, Secure WAN, and shared-memory transports changed to provide
better out-of-the-box performance. Cloud Discovery Service also uses the new value for
message_size_max
. Consequently, Cloud Discovery Service is not out-of-the-box compatible
with applications running older versions of Connext DDS. Please see the
RTI Connext DDS Core Libraries Release Notes for instructions on how to
resolve this compatibility issue with older Connext DDS applications.
14.3. What’s New in 6.1.2¶
14.3.1. New platforms¶
Cloud Discovery Service is supported on these new platforms:
Operating System |
Version and CPU |
---|---|
Linux |
Ubuntu 22.04 LTS on x64 |
macOS |
macOS 12 on x64 |
Windows |
Windows 11 on x64 with Visual Studio 2022 |
For details on these platforms, see the RTI Connext DDS Core Libraries Platform Notes for this release.
14.3.2. Third-party software upgrades¶
The following third-party software used by Cloud Discovery Service has been upgraded:
Third-Party Software |
Previous Version |
Current Version |
---|---|---|
libxml2 |
2.9.12 |
2.9.14 |
libxslt |
1.1.34 |
1.1.35 |
For information on third-party software used by Connext DDS products,
see the “3rdPartySoftware” documents in your installation:
<NDDSHOME>/doc/manuals/connext_dds_professional/release_notes_3rdparty
.
14.4. What’s Fixed in 6.1.2¶
14.4.1. Problems with Discovery after disposal of a Remote Participant¶
Cloud Discovery Service may have assigned incorrect properties from one remote participant to another remote participant. This caused discovery problems. These incorrect properties typically belonged to another remote participant that was recently disposed. This problem has been resolved.
[RTI Issue ID CDS-155]
14.4.2. Cloud Discovery Service did not allow using other transports when Real-Time WAN Transport was enabled¶
Cloud Discovery Service had an issue that prevented the use of multiple transports at the same time, when the Real-Time WAN Transport (udpv4_wan transport alias) was enabled. This issue has been resolved.
[RTI Issue ID CDS-158]
14.4.3. Cloud Discovery Service did not allow use of UDPv6 transport alias¶
Cloud Discovery Service did not enable the UDPv6 transport (udpv6 transport alias),
even when it was set in the <transport>
tag. This problem has been
resolved.
[RTI Issue ID CDS-161]
14.4.4. Discovery did not complete when using Real-Time WAN and multiple locators¶
When using a DomainParticipant with multiple RTI Real-Time WAN Transport locators, sometimes Cloud Discovery Service mixed up the locators and they were not resolved correctly. This caused the discovery process to never complete. The problem has been resolved.
[RTI Issue ID CDS-172]
14.4.5. Cloud Discovery Service crashed when empty participant GUID provided to Remote Administration API¶
If the /cloud_discovery_services/[service_name]/database/locators
Remote
Administration endpoint was provided an empty Remote Participant GUID
in its string_body
, Cloud Discovery Service crashed due to a parsing error. This problem
has been resolved.
[RTI Issue ID CDS-176]
14.5. Previous Releases¶
14.5.1. What’s new in 6.1.1¶
14.5.1.1. New platform¶
This release has validated that the libraries for architecture x64Darwin17clang9.0 can also be used on macOS 11 (Big Sur) systems with x64 CPUs.
For more information on this architecture, see the RTI Connext DDS Core Libraries Platform Notes for this release.
14.5.1.2. Third-party software upgrades¶
The following third-party software used by Cloud Discovery Service has been upgraded:
Third-Party Software |
Previous Version |
Current Version |
---|---|---|
libxml2 |
2.9.4 |
2.9.12 |
libxslt |
1.1.29 |
1.1.34 |
Some of these upgrades may fix potential vulnerabilities. See Fixes related to vulnerabilities.
For information on third-party software used by Connext DDS products,
see the “3rdPartySoftware” documents in your installation:
<NDDSHOME>/doc/manuals/connext_dds_professional/release_notes_3rdparty
.
14.5.2. What’s fixed in 6.1.1¶
14.5.2.1. Incorrect XSD and behavior of <deny_domain_id> in <domain_list> tag¶
The XSD for <deny_domain_id> was incorrect.
This caused Cloud Discovery Service to report an error and not start, unless you used
the -ignoreXsdValidation
command-line option.
There was also an issue in parsing <deny_domain_id> tag values.
In addition, <deny_domain_id> values were not assigned a higher precedence over <allow_domain_id> values, as stated in the documentation examples.
These three issues have been resolved.
[RTI Issue ID CDS-112]
14.5.3. What’s new in 6.1.0¶
14.5.3.1. New platforms¶
Cloud Discovery Service now includes support for these platforms:
macOS 10.15 (x64)
Red Hat® Enterprise Linux 7.6 (x64)
Ubuntu® 20.04 LTS (x64)
For more information on these platforms, see the RTI Connext DDS Core Libraries Platform Notes.
14.5.3.2. Removed platforms¶
These platforms are no longer supported:
32-bit Linux and Windows platforms
macOS 10.12
Ubuntu 12.04 LTS
14.5.3.3. Advanced logging support¶
This release provides you with more context while troubleshooting, and helps RTI Support better diagnose problems when inspecting a log file.
For information on the various logging verbosities, see Command-Line Options.
14.5.3.4. Remote monitoring support¶
This release adds support for remote monitoring. This allows you to enable the publication of samples on the three standard monitoring topics (Config, Event and Periodic). It also provides a way to check the health of the service when deployed in production.
For details, including the metrics published by Cloud Discovery Service, see Monitoring.
14.5.3.5. Remote administration support¶
This release adds support for remote administration. This allows you to issue remote commands to control the service and inspect its internal state. For details, see Remote Administration.
14.5.3.6. Service API support for C and Modern C++¶
This release adds support for the Service API in the C and Modern C++ languages. This allows you to integrate Cloud Discovery Service as a component in your own application. For details, see Software Development Kit.
14.5.4. What’s fixed in 6.1.0¶
14.5.4.1. Memory leak after receiving repeat discovery announcement if role_name or name set in DomainParticipant’s ENTITY_NAME QosPolicy¶
When Cloud Discovery Service received a repeat discovery announcement from an existing
DomainParticipant, it leaked memory if either the name
or role_name
was set in the DomainParticipant’s ENTITY_NAME QosPolicy.
This problem has been resolved.
[RTI Issue ID CDS-74]
14.5.4.2. Crash when a dispose or update participant announcement was received¶
In previous releases of Cloud Discovery Service, on some Windows architectures, if a dispose or update participant announcement was received, it would result in a crash. This was due to an issue when trying to look up an inserted value. This problem has been resolved.
[RTI Issue ID CDS-80]
14.6. Known Issues¶
14.6.1. Cloud Discovery Service does not terminate when its internal DomainParticipant does not initialize properly¶
Cloud Discovery Service creates an internal DomainParticipant that reserves the participant_id 0, on domain ID 0. This DomainParticipant is required by Cloud Discovery Service to relay the participant discovery announcements. If the participant_id 0 for domain ID 0 is already being used by another Connext DDS application, Cloud Discovery Service throws errors but doesn’t terminate.
Although such a Cloud Discovery Service instance is running, it won’t be able to relay any participant discovery announcements. A simple workaround is to ensure that Cloud Discovery Service is always the first Connext DDS application started on a given machine.
[RTI Issue ID CDS-143]
14.6.2. Fourth digit of product version not logged by Cloud Discovery Service at startup¶
Cloud Discovery Service does not log the fourth digit (revision) of the product version at startup.
[RTI Issue ID CDS-174]