Copyright © 2008 Nicolas Rueff - Mandriva
| Revision History | ||
|---|---|---|
| Revision $Revision: 66 $ | $Date: 2008-10-06 10:42:48 +0200 (Mon, 06 Oct 2008) $ | $Author: nnoirbent $ |
Abstract
Documentation for Pulse2 MSC schema v.6
Table of Contents
This table holds a whole command, one command per line.
The table primary key
The command date creation
The command line switches
Do we run command line on client, mainly used for packages debug purpose
Do we erase copied files after a successful run, mainly used for packages debug purpose
Date from which we may run our command
Date until which we may run our command
Login name used to connect our client
Hold the command initiator name
Tell if the command has been fileld into relevant computers
The command title
Whenever start inventory command on client
Whenever perform a WOL on client
How many time do we try to perform a command before giving up
Interval between two connections attempts
a command will be realized by a particular scheduler, this field hold its name
when we have something to send on the client, do not go over this BW rate (b/s), default is 0
This table contains the running status of a command for a particular host.
It is linked to the "commands" table using id_command as constraint.
The table primary key
A FK to the commands table
The command **effective** start date (??)
The command **effective** end date (??)
Used to hold our command status on this client
Tell if we already did something in upload stage
Tell if we already did something in execution stage
Tell if we already did something in deletion stage
If for any reason the command has been postponed, the command may be run from this time
The command pid from the launcher point-of-view
The amount of tries left
??
The in-charge launcher
This table contains the stdout/stderr of each stage of a command for a partiucular host.
It is linked to the "commands_on_host" table using id_command_on_host as constraint.
The table primary key
A FK to the commands_on_host table
The command error (mostly a Python TB)
The command output
The command state
The command error code (if relevant)
This table contains directions to deploy a package.
It is linked to the "commands_on_host" table using id_command_on_host as constraint and "commands" table using id_command as constraint.
The table primary key
A FK to the commands_on_host table
A FK to the commands table
the target fqdn
the packages location. This field must be formatted as follow:
several tockens, separator is '||' (double-pipe)
tockens are URI formatted like this:
<protocol>://<login>:<pass>@<server><path>
Protocol may be one of the following: ssh, http, ftp, smb, file. Each protocol corresponds to a different way to gather a package:
Package is pulled by the client (using for exemple wget). the URI represents exacty the root place from where to download package components.
Same as HTTP.
Same as HTTP, using scp to dowload components. Password unsupported.
Same as HTTP, using SAMBA (CIFS) protocol. Currently unsupported.
Package is pushed on the client by the server, using scp. In this case, the rightmost part of the URI represent the full package root path on the server.
???
???
The target UUID
The target IP adresses, with '||' as separator, the first one beeing the most relevant
The target MAC adresses, with '||' as separator, used to perform WOL
