automated_deployment_engine (Automated Deployment Engine) Release Notes

The automated_deployment_engine probe is a multi-threaded java-based probe that handles package and probe deployment in Admin Console. It also can be used to deploy robots and probes using an XML file.
uimpga-ga
automated_deployment_engine_RN
The automated_deployment_engine probe is a multi-threaded java-based probe that handles package and probe deployment in Admin Console. It also can be used to deploy robots and probes using an XML file.
Revision History
Version
Description
State
Date
20.10
(Included in UIM 20.1.0)
  • Updated the probe version to be in sync with UIM 20.1.0.
GA
March 2020
9.2.0
(Included in CA Unified Infrastructure Management 9.2.0)
What's New:
  • Provided support for OpenJDK 8u212.
  • (9.02 HF1) Fixed an issue in which when users were trying to deploy robots with XML file by using a sudo account along with the
    sshport
    property, they were getting an error. The error was stating that communication with the host was not possible with the specified
    sshport
    . (Support Case: 01344939)
  • (8.54 HF6) Fixed an issue in which automated_deployment_engine was not deploying robots in mixed-mode authentication. The automated_deployment_engine probe uses Java Secure Channel (JSch), which is a third-party library. During run-time, in mixed-mode authentication, JSch was using password authentication implementation (with password as an empty string) instead of the key-based authentication password. This was causing the authentication failure errors. With this hotfix, the key is now successfully authenticating with the Linux server in the mixed-mode authentication. (Support Case: 01169113)
  • Fixed an issue in which users were facing issues when they were deploying CentOS robots through automated_deployment_engine from a remote hub. They were trying to deploy the robots by using an API call to automated_deployment_engine. (Support Case: 01281291)
  • Fixed an issue in which robot deployments were failing when using the deployment_engine API for sudo access. (Support Case: 01135459)
  • Updated the probe as part of addressing the common vulnerabilities and exposures by updating the jackson-databind libraries. For more information and CVE numbers, see Addressing Jackson Vulnerabilities.
  • CA UIM 9.2.0 has adopted OpenJDK 8u212 instead of Oracle JDK. Because of this change, CA UIM 9 SP1 (9.1.0) that was using Oracle JDK (JRE) 8u212 is no longer available and has been removed from the Support site. All the functionality that was included in 9.1.0 is now released as part of CA UIM 9.2.0. Consequently, all references to the 9.1.0 release and the probe version 9.10 (released with it) have also been removed from this probe documentation. We recommend that you move to this version 9.20 of this probe, as the previous version 9.10 is no longer available now. For more information about the OpenJDK usage in CA UIM, see Adopting OpenJDK.
GA
August 2019
9.02
(Included in CA UIM 9.0.2)
What's New:
  • Updated this probe as part of addressing known vulnerabilities in CA UIM by using upgraded third-party Java libraries (bcprov-jdk15on 1.60 and not-yet-commons-ssl 0.3.17) in CA UIM 9.0.2.
  • You can configure a custom SSH port and select the version of the robot package to deploy:
    1. In Infrastructure Management or Admin Console, navigate to the robot running the automated_deployment_engine and select the probe.
    2. In Infrastructure Management, select the Configure or Raw Configure option to add a new section. In Admin Console, select the Raw Configure option to add a new section.
    3. At the Root level, create a section with the name
      deployment
      .
      1. Open the deployment section and create the following key/value pairs:
        sshport
        - <port number>
        robot_pkg_version
        - <version number>
      2. Close the configuration window.
  • Server Message Block protocol v1 (SMB1) is no longer supported. Support for SMB2 and SMB3 is now enabled.
  • Added a new raw configuration parameter
    probeFileTransferBufferSize
    . This configuration parameter lets you decide the buffer size of the probe files during file transfer. Use Raw Configure to set the new configuration parameter. By default, the buffer size is set to 1 MB. For example, if the
    probeFileTransferBufferSize
    value is
    X
    (numeric value), the buffer size becomes
    X*1024
    ; that is,
    X
    KB. Therefore, for the parameter value as
    1024
    , the buffer size is
    1
    MB (
    1024*1024
    bytes).
  • Package rollback on failure for probe deployment is
    disabled
    by default. Added a configuration option to control deployment rollback behavior when an update fails. When you are updating a probe deployment, by default, existing packages are no longer uninstalled if the new deployment fails. This setting has no effect on robot deployments. Robot deployments are
    always
    rolled back. Use Raw Configure to set the new configuration parameter
    do_package_rollback_on_failure.
    Default, false. You can also directly edit the probe configuration file,
    $
    UIMHOME
    /probes/service/automated_deployment_engine/automated_deployment_engine.cfg
    .
  • Below is an example of the file,
    automated_deployment_engine.cfg,
    containing the new parameter:
    <setup>
    loglevel = 5
    </setup>
    <startup>
    options = -Xmx512M -Xms64M -Dfile.encoding=UTF-8
    </startup>
    <automated_deployment_engine>
    do_package_rollback_on_failure = true
    </automated_deployment_engine>
Fixed Defects:
  • (8.54 HF5) Robot deployment using the sudo password has now been fixed on the secondary hub. (Support Cases 01135459 and 01143504).
GA
October 2018
8.5.1
What's New:
  • Reliability of package synchronization is improved on secondary hubs.
GA
February 2017
8.45
What's New:
  • The automated_deployment_engine probe was updated to support Admin Console 8.45.
Fixed Defects:
  • Unfinished jobs in the automated_deployment_engine job history are now moved to a failed state at automated_deployment_engine startup rather than being left in an in-progress state.
  • Queued deployments no longer enter an unresponsive state when cancelling a large number of probe deployments in Admin Console.
  • Improved robot deployment using
    sudo
    on Solaris.
GA
June 2016
8.4
What's New:
  • Updated to use the 8.4.0 CA UIM Java SDK.
GA
January 2016
8.31
What's New:
  • Version number update to support CA UIM 8.31
GA
August 2015
8.20
What's New:
  • Support for
    request.cfg
    probe deployment beginning with robot v7.70.
    • At startup, the controller looks for
      request.cfg
      in the parent directory of
      /robot
      .
    • Request.cfg
      is a user-created text file that enables automatic deployment of the specified probes to the robot.
    • On Windows robots, ensure that the
      request.cfg
      file uses Unix style line endings (LF). If Windows style line endings (CR LF) are encountered, deployment fails with the error "
      could not read deploy_file - request.cfg
      " in the controller log.
    • In previous versions, deployment requests could only be facilitated by distsrv, which still handles them by default. To have a v7.70 or newer robot direct the requests to automated_deployment_engine, use the
      Raw Config
      utility to add the
      deploy_addr
      parameter to robot.cfg. Use
      deploy_addr
      to specify the UIM address of the automated_deployment_engine probe.
    • To use a deployment file with a name other than
      request.cfg
      , add the
      deploy_file
      parameter to
      robot.cfg
      . For example,
      deploy_addr = /
      domain
      /
      hub
      /
      robot
      /automated_deployment_engine deploy_file =
      file_name
      Deployment files are not supported for passive robots.
    • For performance reasons, the automated_deployment_engine is preferred for probe deployment over the distsrv probe. To specify distsrv deployment, provide the UIM address of the distsrv probe in
      request.cfg
      .
Create
request.cfg
with the following format:
<distribution request>
distsrv =
/domain/hub/robot
/distsrv
packages =
probe_name1, probe_name2
</distribution request>
  • Build number validation for archive import (negative, non-numeric, 0), which maintains consistency in the archive by preventing automated_deployment_engine from importing packages with bad build numbers.
  • Package included in UIM Server 8.2 distribution.
Fixed Defects:
  • Improved reliability with large deployments.
  • Improved performance with remote robot deployment (deploying a robot whose specified parent hub is NOT the hub where automated_deployment_engine is deployed).
GA
March 2015
8.10
  • Remote robot deployment reliability has been improved for slow networks.
  • Automated_deployment_engine probe package dependency resolution has been fixed when using EQ as the dependency type.
  • Solaris native installer init script now returns correct error code when being called.
  • Automated_deployment_engine restarts properly when called from Infrastructure Manager and Admin Console.
  • Package included in UIM Server 8.1 distribution.
GA
December 2014
2.00
  • automated_deployment_engine 2.0 is a Java-based redesign of distsrv with scalability, flexibility, and maintainability in mind.
  • Admin Console now uses automated_deployment_engine for package deployment, which is two to five times faster than with distsrv. (Infrastructure Manager continues to use distsrv).
  • Automated_deployment_engine uses an archive cache to do quick package lookups and file extractions. Files that have been extracted are maintained in a cache to speed up package deployment. This cache is cleared at startup.
  • automated_deployment_engine Archive stays in sync with the file system, and the archive-sync solution is much more scalable than distsrv package forwarding. Processing is distributed, rather than going through a single master distsrv.
  • Package included in UIM Server 8.0 distribution.
GA
September 2014
1.31
  • Added support for AIX and zLinux.
  • Package included in NMS 7.6 distribution.
GA
June 2014
Known Issues
  • Microsoft Windows 2003 and earlier versions are not supported.