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.
|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.|
|macOS®||All macOS 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.|
For backward compatibility information between Cloud Discovery Service 6.0.1 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_maxfor 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 New in 6.0.1¶
8.3.1. New platforms¶
Cloud Discovery Service now includes support for these platforms:
- macOS 10.14 (x64)
- Red Hat® Enterprise Linux 8 (x64)
- Windows 10 (x86, x64) with Visual Studio® 2019
- Windows Server 2016 (x86, x64) with Visual Studio 2019
For more information on these platforms, see the RTI Connext DDS Core Libraries Platform Notes.
8.3.2. Removed platforms¶
These platforms are no longer supported:
- macOS 10.11
- Windows 7
- Windows Server 2008 R2
8.4. What’s Fixed in 6.0.1¶
8.4.1. Cloud Discovery Service executable did not log build ID for DDS libraries¶
In Connext DDS 6.0, the DomainParticipantFactory initialization didn’t appear anywhere in the logging generated by Cloud Discovery Service for any verbosity level. Cloud Discovery Service printed the ROUTER build ID, but the “Welcome to NDDS” message, NDDS C, and NDDS Core Library build IDs weren’t printed. This problem was new (a regression) in Connext DDS 6.0.
This problem has been resolved. The Core Library verbosity is now set
before Cloud Discovery Service starts, allowing the initialization to appear in the log.
For example, running
rticlouddiscoveryservice -verbosity 6, as in
previous releases, now yields the following:
... DDS_DomainParticipantFactory_initializeI:Welcome to NDDS NDDSCORE_BUILD_220.127.116.11_20180216T211030Z_RTI_REL NDDSC_BUILD_18.104.22.168_20180216T211030Z_RTI_REL ...
[RTI Issue ID CDS-51]
8.4.2. Transport element in XML did not remove default UDPv4 transport¶
Even if you specified a transport other than udpv4 (for example, tcpv4_lan), Cloud Discovery Service kept listening for announcements using the udpv4 transport. The only way to ensure that the udpv4 transport wasn’t used was to use the command-line arguments. This problem has been resolved.
[RTI Issue ID CDS-53]
8.5. Previous Releases¶
8.5.1. What’s Fixed in 6.0.0¶
22.214.171.124. 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]
126.96.36.199. 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]