ovdeploy -- transfere, remove or execute files on remote hosts

• Introduction
• Syntax
• Parameters
• Options
• Symbolic Pathnames
• Examples
  • Install examples
  • Distribution of files to remote boxes
  • Getting Files from remote hosts to the HPOM server
  • Execution of files on nodes
  • Packages Related Examples

Note: HP renamed the product called now HP operations manager way too many times. Also it is very inconsistent with using abbreviations. Here we will assume that the term "HP Operations manager" and abbreviations HPOM, OMU, and OVO mean the same thing :-)

Introduction

ovdeploy is poor man CMS system that comes free with HPOM. It is very poorly documented, but actually has pretty rich functionality similar to functionality of ssh.  It can:

1. Transfer three types of objects to remote hosts
   • Files. For example

     ovdeploy -upload -file /root/.ssh/id_rsa.pub -targetdir /.ssh -node ux08

   • Directories
   • Packages. A package can be a file, a group of files, a directory or group of directories or a combination of all. ovdeploy command can be used to distribute both files and packages.
2. Execute commands on remote host so it can be used instead of SSH on hosts where SSH is not available by default such as Windows. For example:

   ovdeploy -exec -file /usr/bin/bdf -node ux1572

   ovdeploy -exec -file /usr/bin/chpasswd -par "-f root test2012" -node red302

For packages additional operations are available which make it pretty good "poor man configuration management system". You can use ovdeploy to install, remove, up or download, and register or unregister objects on the local and remote hosts you are managing. You can also use the ovdeploy command to list package inventories and execute commands on specified files.

Note: ovdeploy man page and help produced if you enter the command without parameters differs in substantial way.

Syntax

• ovdeploy -install
  -file <filename>... | -dir <dirname>
  [-sourcedir <dirname> | -sourcerootdir <symbolic_name>]
  [-targetdir <dirname> | -targetrootdir <symbolic_name>]
  [-perm <file_permissions>]
  [-host <name_or_ip>]
  [-instserv <name_or_ip>]
  [-cmd_timeout <time_in_milli_sec>]]
  [-force]
  [-targetid <id>]
   
• ovdeploy -exec -file <filename> [-host <name_or_ip>]
  [[-targetrootdir <symbolic_name>] [-targetdir <dirname>] [-shell] [-targetid <id>] [-ovrg <id>] [-cmd_timeout <time_in_milli_sec>]]
  
• ovdeploy -cmd -file <absolute path to command> [-host <name_or_ip>] [-par <params>]
  [-cmd_timeout <time_in_milli_sec>][-targetrootdir <symbolic_name>] [-targetdir <dirname>]]
  • Note: parameters need to be supplied via option -par, not after the name of the file.

Package operations

• ovdeploy -install -pkg <package_descriptor>
  [[-sourcerootdir <symbolic_name>] [-sourcedir <dirname>] [-targetrootdir <symbolic_name>] [-targetdir <dirname>]
  [-force] [-perm <file_permissions>]
  [-host <name_or_ip>] [-instserv <name_or_ip>] [-targetid <id>] [-cmd_timeout <time_in_milli_sec>]]
  
• ovdeploy -remove -pkg <package_name> |-file <filename> |-dir <dirname>
  [[-targetrootdir <symbolic_name>] [-targetdir <dirname>] [-force] [-host <name_or_ip>] [-instserv <name_or_ip>] [targetid <id>] [-ovrg <id>] [-cmd_timeout <time_in_milli_sec>]]
  
• ovdeploy -upload -pkg <pack age_descriptor> |-file <filename> |-dir <dirname>
  [[-sourcerootdir <symbolic_name>] [-sourcedir <dirname>] [-targetrootdir <symbolic_name>] [-targetdir <dirname>] [-force] [-perm <file_permissions>] [-host <name_or_ip>] [-instserv <name_or_ip>] [-targetid <id>] [-cmd_timeout <time_in_milli_sec>]] ^
  
• ovdeploy -down -pkg <package_descriptor> |-file <filename> |-dir <dirname>
  [[-sourcerootdir <symbolic_name>] [-sourcedir <dirname>] [-targetrootdir <symbolic_name>] [-targetdir <dirname>] [-force] [-perm <file_permissions>] [-host <name_or_ip>] [-instserv <name_or_ip>] [-targetid <id>] [-ovrg <id>][-cmd_timeout <time_in_milli_sec>]]
  
• ovdeploy -inv [-host <name_or_ip>] [-invtype <inventory_type>] [-all]
  
• ovdeploy -reg -pkg <package_descriptor>[ [-sourcerootdir <symbolic_name>] [-sourcedir <dirname>] [-force] [-host <name_or_ip>] [-targetid <id>] [-ovrg <id>]]
  
• ovdeploy -unreg -pkgname <package_name> [[-force] [-host <name_or_ip>] [-targetid <id>] [-ovrg <id>]]
  

Parameters 

The first parameter specified the operation to be performed. There are nine operations:

1. -install <options> Installs the specified object. The default target directory is $OvDataDir/installation/incoming/files/.
2. -remove <options> Removes one or more objects.
3. -upload <options> Uploads one or more objects to a target node.
4. -down <options> Downloads one or more objects from a target node.
5. -inv <options> Returns a list of installed objects on a target node either to stdout or in the form of an XML file written to the local directory.
6. -reg <options> Adds a specified package name to the list of registered package names on a target node.
7. -unreg <options> Removes a specified package name from the list of registered package names on a target node.
8. -exec <options> Executes a specified file on a specified host and returns the result of the action to stdout.
9. -cmd <options> Executes a specified command or file on a different shell on the specified host and returns the results of the action on stdout.

Options

The following options may be used in conjunction with the command parameters indicated in the Parameters section:

• -all Returns the complete inventory in XML format. The complete inventory comprises the package descriptors of all packages that have been installed on the node. If not used, only the name and version of each registered package is returned.
• -dir <dirname> The name of a directory to be installed, removed, up or downloaded, registered or unregistered. The contents of the directory will also be installed, removed, up/downloaded.
• -file <filename>... The name of a file to be installed, removed, up or downloaded, registered or unregistered, or executed. With the -install parameter, multiple files can be specified.
• -force With the -install parameter, it installs the specified object even if an object already exists on the target node with the same or higher version. With the -remove parameter, it must be used with -dir, and removes all subdirectories.
• -host <target_host> The name or IP address of the target host. If not used, the local host is assumed.
• -instserv <name_or_ip> Name or IP address of an installation server. If an installation server is specified, the specified file is not copied from the local host to the target host. Instead, it is copied from the installation server to the target host.
• -invtype [depl|native] depl returns to stdout the inventory of objects installed using the deploy command. native returns to stdout the inventory of objects installed using the operating system's native installation program.
• -ovrg <id> The ID of an OpenView resource group, if applicable.
• -perm <nnn> Sets file permissions of an installed, up/downloaded, un/registered file. This parameter takes three digits. The first digit specifies the owner permission, the second digit specifies the group permission, and the third digit specifies public permissions. The allowable digits are:
  • 0 No permissions.
  • 1 Execute.
  • 2 Write.
  • 3 Execute and write.
  • 4 Read.
  • 5 Execute and read.
  • 6 Read and write.
  • 7 Read, write, and execute.
• -pkg <package_descriptor> The full path and name of the package descriptor file. The package descriptor file contains a list of all the files that are to be installed, removed, up or downloaded, registered or unregistered and their locations.
• -shell Used with the -exe parameter to execute in a shell the file specified by <file>. As a default, for UNIX systems, /bin/sh -c is used. For a MS Windows (R) system, %ComSpec/cmd.exe /c is used.
• -sourcerootdir <symbolic_name> The symbolic path name used to create an absolute file path for the source file.
• -sourcedir <dirname> Used to create an absolute file path for the source file. If a source root directory is specified, the source directory is appended to it. If no source root directory is specified, the source directory is appended to the default directory, $OvDataDir/installation/incoming/files/.
• -cmd_timeout <time_in_milli_sec> Sets the timeout (in milliseconds) for individual commands executed from ovdeploy command. If this option is not set, the value specified for COMMAND_TIMEOUT under depl namespace of configuration settings of the target system will be used for individual commands (which has a default value of 10 minutes). This option applies to package install and remove commands, -exec, and -cmd commands.
• -targetrootdir <symbolic_name> A symbolic path name used to create an absolute file path for the target root directory.
• -targetdir <dirname> The name of the directory on the target node where the object is to be installed, removed, up or downloaded, registered or unregistered.
• -targetid <id> The target ID of the target node.

Symbolic Pathnames

ovdeploy supports symbolic names that can be used with the sourcerootdir and targetrootdir options. You can use symbolic names to specify a directory without needing to know where the directory is located on a particular node platform, for example; the OpenView installation directory is: ovinstall. It is defined for all supported node platforms but the actual location might be different on each platform.

Supported symbolic path names are:

• Bin <InstallDir>/bin
• Contrib <InstallDir>/contrib
• current <CurrentDir>
• Data <DataDir>
• dataarchive <DataDir>/datafiles/archive
• datacertificates <DataDir>/certificates
• dataconf <DataDir>/conf
• datafiles <DataDir>/datafiles
• dataimages <DataDir>/images
• datainstallation <DataDir>/installation
• datainstrumentation <DataDir>/bin/instrumentation
• datalog <DataDir>/log
• datapackages <DataDir>/packages
• datapolicies <DataDir>/datafiles/policies
• datatemp <DataDir>/tmp
• datatmp <DataDir>/tmp
• datawww <DataDir>/www
• depl <DataDir>/installation
• deplincoming <DataDir>/installation/incoming>
• deplincomingfiles <DataDir>/installation/incoming/files
• deplincomingpackages <DataDir>/installation/incoming/packages
• deplinventory <DataDir>/installation/inventory
• deplpackages <DataDir>/installation/packages
• Depltemp <DataDir>/installation/temp
• deplbbcfxupload <DataDir>/installation/temp/bbc/fx/upload
• deplupload <DataDir>/installation/temp/bbc/fx/upload
• examples <DataDir>/examples
• Help <DataDir>/help
• include <DataDir>/include
• install <InstallDir>
• Java <InstallDir>/java
• Lbin <InstallDir>/lbin
• Lib <InstallDir>/lib
• licenseagreements <InstallDir>/license-agreements
• Man <InstallDir>/man
• Misc <InstallDir>/misc
• Msg <InstallDir>/msg
• newconfig <InstallDir>/newconfig
• nonov <InstallDir>/nonOV
• ovdata <DataDir>
• ovinstall <InstallDir>
• packages <InstallDir>/packages
• paperdocs <InstallDir>/paperdocs
• releasenotes <InstallDir>/ReleaseNotes
• resources <InstallDir>/resources
• Root <RootDir>
• support <InstallDir>/support>
• systemp <SystemTempDir>
• systmp <SystemTempDir>
• systemtmp <SystemTempDir>
• wwhtdocs <InstallDir>/www/htdocs
• wwwimages <Installdir>/www/images

Examples

ovdeploy command can be used to distribute both files and packages. For packages additional operations are available which make it pretty good "poor man configuration management system".

Install examples

The following examples show how to use the ovdeploy command with files

To install file from the current directory to the node dell12 in the directory /root/bin

ovdeploy -install -host dell12 -file ora_archive_postexec.sh -td /root/bin -perm 755

To install the file testfile, located in the /tmp directory, to the node testnode. The default target directory is $OvDataDir/installation/incoming/files/.

ovdeploy -install -file /tmp/testfile -node  testnode

Distribution of files to remote boxes

To deploy the file testfile, located in the /tmp directory, to the /opt/OV/bin directory on the node testnode.

ovdeploy deploy -file /tmp/testfile -targetdir /opt/OV/bin -node  testnode	

To delete the file /opt/OV/bin/testfile from the host testnode.

ovdeploy -remove -file testfile -targetdir /opt/OV/bin -node  testnode 

To delete the file $OvDataDir/installation/incoming/files/test/testfile from the host testnode. The absolute path of the file is created from the specified target directory. No target root directory was specified, so the default target root directory is used.

ovdeploy -remove -file testfile -targetdir test -host  testnode 

Getting Files from remote hosts to the HPOM server

To copy the file testfile to the default target directory on the local host. The default target directory is $OvDataDir/installation/incoming/files/.

ovdeploy -upload -file /tmp/testfile -node testnode

To copy the file /etc/resolv.conf to the target directory /home/Resolv_depot on the local host.

ovdeploy -upload -file /etc/resolv.conf  -targetdir /home/Resolv_depot -node testnode

To copy the files in the /tmp/testdir directory on the host testnode to the directory /opt/OV/bin on the local host.

ovdeploy -down -dir /tmp/testdir -targetdir /opt/OV/bin -node  testnode
	

Execution of files on nodes

Note: the file should be already present of the local node to be executed

To execute the file run on the local host and returns the output to stdout.

ovdeploy -exec -file /tmp/run 

To execute the file run.sh with the shell on the host testnode.

ovdeploy -exec -shell -file run.sh -targetrootdir bin -node  testnode 

To set the timeout value for the -exec command for my_exe.exe file on host node1.

ovdeploy -exec -file C:\my_exe.exe -node node1 -cmd_timeout 9000000 

Packages Related Examples

Display list of packages installed in the HPOM server

ovdeploy -inv 

To install the package testpackage.xml, located in the /tmp directory, to the node testnode.

ovdeploy -install -pkg /tmp/testpackage.xml -node  testnode 

To copy all files that are specified in the package descriptor package1.xml to the default package upload directory on the host testnode.

The directory containing the specified package descriptor file and all files specified in it is the bin directory.

ovdeploy -upload -pkg package1.xml -sourcerootdir bin -host  testnode 

To un-register the package testpack2 from the host testnode.

ovdeploy -unreg -pkgname testpack2 -host  testnode 

To register the package package1.xml by copying the package descriptor to the inventory directory. If the package descriptor already exists, an error is returned to stdout.

ovdeploy -reg -pkg /tmp/package1.xml 

To delete the package testpkg1 from the host testnode.

ovdeploy -remove -pkg testpkg1 -host  testnode 

If testpackage1 and testpackage2 have been installed on the local machine, the following is returned:

To display the native package inventory of the local host. For example:

ovdeploy -inv -invtype native 
	HP OpenView BBC Package 5.0.50 HP OpenView Performance Access Package 10.00.123

	

NEWS CONTENTS

• 20101223 : Using ovdeploy to shut down a service ( Using ovdeploy to shut down a service, Dec 23, 2010 )
• 20101223 : Remote Command Execution using ( Mar 27, 2006 , IT Resource Center forums )
• 200102 : HP Communities - vi file on managed node using ovdeploy - Enterprise Business Community ( HP Communities - vi file on managed node using ovdeploy - Enterprise Business Community, )

Old News

[Dec 23, 2010] Using ovdeploy to shut down a service

To make modifications to a running remote system from the management station to shut down a OVO Agent component:

# /opt/OV/bin/ovdeploy -cmd "/etc/rc.d/rc3.d/K02OVTrcSrv stop" -host host.corp.dom
Stopping OVTrcSrv...
# /opt/OV/bin/ovdeploy -cmd "ps -ef grep ov" -host host.corp.dom
root 299078 446518 5 Jan 03 - 0:27 /usr/lpp/OV/bin/ovbbccb -nodaemon
root 446518 1 0 Jan 03 - 6:31 /usr/lpp/OV/bin/ovcd
root 467048 655434 2 15:33:30 - 0:00 /bin/sh -c ps -ef grep ov
root 655434 446518 8 Jan 03 - 0:00 /usr/lpp/OV/lbin/conf/ovconfd

[Dec 23, 2010] Remote Command Execution using

Mar 27, 2006 | IT Resource Center forums

Brandon V:

I am running OVOU 8.14, agent version 8.13 on HP-UX 11.11. I am trying to run the command:

ovdeploy -cmd "ls" -host <remoteHost>

I am running this command after sudoing to root. I am getting the error message:

Unable to execute command 'ls' on node

(depl-175) Message returned from host:

Caller is not authorized to perform the requested operation.

I can run this command locally, but I not sure what permission issue it preventing me from doing this from the managagement server. Can anyone tell what, in regards to permissions, should I be looking at? Any help is appreciated.

Sylvain CROUET:

Can you try adding the -ovrg server option?

Brandon V

Thank you Sylvain that was exactly it. I wish I could award more than 10 points

Sylvain CROUET:

Without the "-ovrg server" option you act as the manager's agent, which usually has no rights to perform actions on other agents. With the option you act as the manager itself, which has rights.

Goran Koruga:

The syntax is as follows:

ovdeploy -ovrg server -cmd yourcommand -host nodename

Goran

HP Communities - vi file on managed node using ovdeploy - Enterprise Business Community

izad, 01-05-2010 10:21 PM

Hi Friends,

Has anyone succeeded running vi on a managed node from OVO server ? something like this :

ovdeploy -ovrg server -cmd 'vi /tmp/blah.txt' -node

I get this:

[Using open mode] "/tmp/tttt" [New file]

Input read error

Tried 'TERM=vt100;export TERM;vi /tmp/blah.txt' as well but no luck.

Tried osspi_vi.sh, created an application - nothing worked.

I can't bring the remote xterm as I've only port 383 and ICMP opened between server and node.

Any idea is highly appreciated with points.

Thank you. I hate quotations. Tell me what you know !

Banu_Prakash, 01-05-2010

I have never used vi through ovdeploy but if i want to edit any file from node end i will use opcdeploy command

First i will copy the required file to management server

opcdeploy -cmd "cat /tmp/tmp/blah.txt" -node > /tmp/blah.txt

I will edit the file /tmp/blah.txt and will put it back to node using opcdeploy command

opcdeploy -deploy -file -node [-targetdir ] -trd absolute

HTH Banu

Goran Koruga, 01-05-2010

Hello.

This won't work - vi needs a real TTY.

Something like sed or ed shall work.

Regards, Goran .

Mohamed AbdelMoneim, 01-06-2010 04:18 AM

Hi, Did you try

ovdeply -cmd "cat THE TEXT YOU WANT TO ADD > /tmp/file.txt" -node THE NODE NAME

it is kind of redirection with cat command to append or overwrite the text in files

Remco Donders, 01-06-2010

I've you are able to open x-windows and there isn't a firewall between the server and node and xterm is available on remote node.

You could try:

ovdeploy -cmd "xterm -display PCRunningX:0.0 -e vi /file/to/edit" -node nodename

However I do not like this option as it doesn't give you info on which server the xterm is running.. You might need other arguments to set the title of the xterm window.

HTH.,

Remco ....

Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotes :  Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce :  Bernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS :  Programming Languages History : PL/1 : Simula 67 : C : History of GCC development :  Scripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month :  How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019