...
An example of how it can be used:
| Code Block |
|---|
bin/opconfig-cli.pl act=test_connect host=192.168.88.254 transport=Telnet personality=ios username=testuser password=testpass |
The options for transport and personality are given above.
...
find_command_revisions, Get the revisions of a command
Requires the node name and returns a list of the commands a revisions for a node.
| Code Block |
|---|
./opconfig-cli.pl act=find_command_revisions node=NODENAME |
Expected output:
| Code Block |
|---|
Node Command Revision
mynode top -n 3 -d 5 -M -b 1
mynode top -a -n 1 -M 1
mynode vmstat 1 10 2
mynode pvdisplay 1
mynode ps -ef 1
mynode lvdisplay 1
mynode df 2
mynode chkconfig 1
mynode disk usage /homee 0 |
diff_command_outputs, Diff two revisions
...
| Code Block |
|---|
./opconfig-cli.pl act=diff_command_outputs node=NODENAME command="disk usage /home" revision_1=2 revision_2=3 |
purge options
By default opConfig does not remove old revisions from the database; if you run many non-change-detecting commands (or encounter frequent changes in your commands' outputs) then this will likely make the GUI unwieldy (e.g. the revision drop down menus will become very large). The revisions can be removed with the command line option:
| Code Block |
|---|
./opconfig-cli.pl act=purge_revisions node=NODE_NAME debug=9
|
There is also an option to remove indices:
| Code Block |
|---|
./opconfig-cli.pl act=purge_indices |
More information about puge opConfig data can be found here.
Config sets
As mentioned above opConfig lets you organise whatever commands you'd like it to run into an arbitrary number of groups which we call command sets.
There are several cli options to manage config sets:
| Code Block |
|---|
./opconfig-cli.pl act=list_configsets
./opconfig-cli.pl act=import_configset file=/tmp/configset_test1.json
./opconfig-cli.pl act=export_configset name=test1
./opconfig-cli.pl act=disable_configset name=test1
./opconfig-cli.pl act=enable_configset name=test1 revision=1
./opconfig-cli.pl act=push_configset name=test1 node=deb-n-burn |
...
NODE_NAME |
You can read more information of the config sets in the user manual.
Queue
The opConfig queue has jobs scheduled to be run in order. There are some cli options to check the queue list of the scheduled jobs or remove a job from the queue:
| Code Block |
|---|
./opconfig-cli.pl act=list_queue with_ids=1 ./opconfig-cli.pl act=remove_queued id=5e42a04b2b181345a5069093 |
...