Contents

Release Notes

OneDDI 2.11.3
  1. Introduction
  2. Release Files
  3. New Functionality
  4. Enhancements
  5. Resolved Issues
  6. Known Issues

Introduction

The VendorN Ltd OneDDI product (OneDDI) is a centralised software application which hosts several modules.

The ReDNS module allows a business to pre-define all DNS records for critical services. Service owners can be permitted to control service DNS records and perform on-demand extensive health-checks to identify configuration issues.

The IPMeye module provides centralised remote power management and console access using the IPMI protocol. It enforces access control and audits all user actions.

The SerialEyes module provides centralised remote physical serial port access via non-dedicated hardware. A SerialEyes bootable USB drive transforms a laptop into an on-demand secure physical serial port gateway using existing addressing and connectivity.

This document contains information pertinent to this release of the OneDDI.

This document is aimed at product administrators.

Release Files

The following files make up this release (where <version> is the version of this release):

  • oneddi-<version>-1.x86_64.rpm - The product installer

New Functionality

ID Version Description
62 1.1.0 Specify a password complexity policy using a regular expression
10 1.2.0 Active Directory user authentication
12 1.2.0 Active Directory group association
20 1.3.0 Import multiple devices at once
134 2.0.0 Swap DNS records using the OneDDI ReDNS module
139 2.1.0 Allow two records of the same record type to use the same in-active name effectively giving a swap names ability
174 2.2.0 Access physical consoles over the network using the new OneDDI SerialEyes module
186 2.4.6 Implement redundancy using real-time replication to another OneDDI instance
187 2.4.6 Add the ability to export all services to a CSV file
188 2.4.6 Add the ability to export all services records to a CSV file
200 2.4.6 Licenses are now bound to an IP address (a new product license will be required when upgrading to 2.4.6)
204 2.4.6 Add the ability to import services and service records using a CSV file
205 2.4.6 Add the ability to export all devices to a CSV file
185 2.5.2 Add the ability to modify the TTL in DNS for all service records (can be used to decrease/increase TTL’s before/after planned DR events)
243 2.7.0 Add the ability to create predefined BCP jobs for planned BCP events and predefined DR related configurations
246 2.7.0 Implement Service records view under ReDNS
422 2.10.1 Implement ability to manage PTR records in addition to A records for a-record type service records in ReDNS
509 2.11.2 Implement CSV export for Settings / Audit log

Enhancements

ID Version Description
55 1.1.0 Specify IPMI port when adding or editing devices
61 1.1.0 Require current password when users change their password
49 1.3.0 Warn when connecting to an device whether another user is already connected to the console
98 1.4.0 Convert product license to a new format
102 2.0.0 Add the ability to search the action field in the audit log
101 2.0.0 Add the ability to download existing license
106 2.0.0 Add breadcrumbs on the device page
113 2.0.0 Enhance user and group association dialogs
137 2.1.0 Add test connectivity ability to the add and edit Infoblox connector dialogs
171 2.2.1 Enhance connect to serial port dialog under SerialEyes
196 2.3.0 Add the ability to control which API version is used for an Infoblox connector
182 2.4.6 Add the ability to disable certain TLS versions
184 2.4.6 Add the ability to download the IPMeye and SerialEyes console logs to a file
201 2.4.6 HTTP server port now defaults to 443 instead of 8000
189 2.5.3 Enhance service record add/edit input dialog
190 2.5.3 Enhance service record table when viewing a service
219 2.7.0 Add view-X permissions for all manage-X permissions
237 2.7.0 Convert select/unselect to checkboxes and implement a select all in view
241 2.7.0 Automatically pre-select a swap when only two records exist on the service
245 2.7.0 Display what a service currently points at in the services view and make that searchable in the services view#
291 2.8.2 Remove certain audit log entries which have no side effects
488 2.11.2 Show absolute timestamps in the Settings / Audit log page in addition to relative timestamps
490 2.11.2 Add source IP address field to audit log entries
528 2.11.2 Include service FQDN in audit log messages when changing service record TTLs and swapping them
573 2.11.3 Change default master SQL database busy timeout from 5 seconds to 30 seconds

Resolved Issues

ID Version Description
234 2.7.0 Retain case when performing service health-checks
283 2.8.2 Service group select dropdown is unusable when large as content is displayed off the page
284 2.8.2 When permissions are not assigned to swap services you can still select services
285 2.8.2 Service swap fails when CNAME target is using upper-case characters
290 2.8.2 Content in the service groups column under the ReDNS / BCP jobs page is not wrapped
301 2.9.2 BCP job service import affected by case sensitivity issue
319 2.9.2 Regression in validation library made underscores in FQDN’s invalid
326 2.9.2 When performing failover using a BCP job the progress dialog shows the service being processed as undefined
344 2.9.2 Duplicate group IDs are recorded in the groupId list for a user session in audit event data for CreateSession
463 2.10.3 Active Directory group search following authentication fails when the users userPrincipalName has a different domain to Active Directory domain
489 2.11.2 Replication connection shows as error following timed out disconnect a new connection established
495 2.11.2 Small number of replication changes lost after breaking replication and recreating the relationship again
566 2.11.3 Replication channel breaks when an error occurs on the active when completing a change
603 2.11.3 ReDNS service failback fails when swap action is rename and there are two records with same object type that use different in-active FQDN’s

Known Issues

ID Description Work around
351 Infoblox API searches for cname record canonical field is case sensisitive Ensure that service records of the type cname-record are configured using the same case as they are defined in Infoblox
428 When using a CNAME for redundancy a HTTP session cookie error is experienced When using real-time replication and a CNAME to access the OneDDI user interface, ensure the HTTP session key in the file /opt/oneddi/config/http-session.key is the same on both the active and standby servers