8. Release Notes¶

8.1. Supported Platforms¶

Cloud Discovery Service is supported on the platforms listed in Table 8.1. No custom platforms are supported.

Table 8.1 Supported Platforms in 6.0.0¶
Platform	Operating System
Linux®	All Linux platforms on x86/x64 CPUs in the RTI Connext DDS Core Libraries Release Notes with the same version number, except SUSE® Enterprise Linux and Wind River® Linux 7.
OS X®	All OS X platforms 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.

8.2. Compatibility¶

For backward compatibility information between Cloud Discovery Service 6.0.0 and previous releases, please see the Migration Guide on the RTI Community portal.

8.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.

8.3. What’s Fixed in 6.0.0¶

8.3.1. Transport configuration property XML inconsistent with documentation¶

The XML definition of the <property> tag under <transport> was inconsistent with the documented definition, which indicates that the first and only element must be the tag <value>. This problem has been resolved: the <property> tag now behaves as described in the documentation.

[RTI Issue ID CDS-37]

8.3.2. Domain Tag ignored for repeated announcements¶

Cloud Discovery Service did not correctly apply the domain tag for announcements of already discovered participants. This caused the domain tag functionality to have no effect. This problem has been resolved.

[RTI Issue ID CDS-44]