Optimizing and Controlling package & probe deployment

[Luc Christiaens]

The attached document will try to explain how you can:

·         - Get version & install date overview for a package/probe on all/selected robots

·         - Deploy a package/probe to all robots with generic origin/hub/robot name filters

·        -  Deploy a package/probe (&version) only if another pre-requisite package/probe is already installed on selected robots

·         - Get a list of robots where your package/probe/version is not yet installed & generate, if requested, generate also the deploy commands

·         - Get an overview of all installed packages/probes/version of generic origin/hub/robot names (= also the not visible packages like: java_jre, vs2008_redist_x86, mcs_templates, pu, custom packages, xx_report_pack, uim_ & ump_ packages) and generate upgrade/deploy commands where needed.

·       -   How to setup/customize distsrv & ade remote deployment with package synchronization

-----

TComments, corrections or new ideas are very welcome.

Updates will follow when new logic is detected, specially for packages in remote archive for ADE there is still some confusion between the doc and reality and old(er) parameters. 

--

[Luc Christiaens]

In attachment a new version of the documentation.

Only chapter 5 (Remote Distribution setup) is changed/adapted to point to the interesting ADE configuration setting:

   forwardProbeDeploymentRequests = 1

Once this setting is defined you can deploy additional "automated_deployment_engine" probes to your remote hubs, this without any need for additional configuration.

With the above forward function active, ADE will execute the following logic when you deploy a remote probe/package:

·         Check if the remote robot is located under a hub with an ADE probe

•         If yes it will check if that remote ADE has the package/version in his remote archive

o   If yes, it will use that package/version

o   If no, it will transfer that package to the remote local archive and use that package. That package is now available for other deployments from that remote archive

•          If no ADE will deploy the package from the master hub

Attachment(s)

Optimzing and Controlling probe & package deployment_v1.2...2   857 KB 1 version