Copyright © 2008 Nicolas Rueff - Mandriva
| Revision History | ||
|---|---|---|
| Revision $Revision: 73 $ | $Date: 2008-10-07 19:15:16 +0200 (Tue, 07 Oct 2008) $ | $Author: nnoirbent $ |
Abstract
Documentation for Pulse2 MSC schema v.12
Table of Contents
This table holds a whole command, one command per line.
The table primary key
The command date creation
The command to launch to start installation of the package
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
The list of files for the package, with MD5 control sums
Date from which we may run our command
Date until which we may run our command
Login name used to connect our client
Holds the command initiator name
Tell if the command has been field into relevant computers
The command title
Whether to start an inventory command on the client once the command has suceeded
Whether to perform a Wake On Lan (WOL) on the client before attempting to connect to it
Whether to reboot the machine after the command succeeded
How many time do we try to perform a command before giving up
Interval between two connection attempts
?
?
?
?
?
?
when we have something to send to the client, do not go over this BW rate (b/s), default is 0
The interval of time between two deployment attempts
The Bundle ID the command belongs to
The command's order inside its bundle
The identifier of the package deployed by the command, or NULL in case the command is a quick action
This table contains the running status of a command for a particular host.
It is linked to the "commands" table using fk_commands as constraint.
It is linked to the "target" table using fk_target as constraint.
The table primary key
A FK to the commands table
A foreign key to the "target" table
The target host to run the command on.
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 amount of tries left
??
The in-charge launcher
The scheduler in charge of this command
This table contains the stdout/stderr of each stage of a command for a particular host.
It is linked to the "commands_on_host" table using fk_commands_on_host as constraint.
The table primary key
A FK to the commands_on_host table
The time at which the command was run
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.
The table primary key
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.
Commands may be grouped using some criteria (IP adress, ...), this filed hold their group id
The scheduler for this target
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
The target's broadcast IP, if relevant
The target's netmask, if relevant
This table holds Bundle (sets of commands) IDs.
The table's primary key.
The bundle's title
Whether the target should be rebooted once the bundle has been deployed
