opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
17 Dynamic Depot Assignment
17.1 Introduction
129 / 193
With the standard opsi multi depot support, the clients are assigned to a designated depot. This is now extended
with the option, that for download speed-up, each client can dynamically detect a suitable depot to download software
packets from.
For most cases an assignment according to the IP address might be the easiest and suitable solution. For other network
topologies, e.g. a star topology VPN network, this might not be sufficient.
Therefore a mechanism is required for the client to detect dynamically, which depot to connect for download of software
packets. The specific assignment algorithm and implementation depends on the network topology and other special
customer requirements. So it is best to have this adaptable and configurable.
To offer the option, that the client can detect the suitable depot according to the current network conditions, it must
be ensured, that the alternative depots are synchronized, which means they offer the same software packets. In practice
the depots will not be synchronized at all times. So the list of alternative depots offered to a client is limited to those
depots, which are synchronized with the clients master depot. The master depot of a client is the depot, which the
client is assigned to. So the master depot defines, which software version is to be installed on the client.
The opsi concept for this is as follows:
The opsi config-server provides a client script, which can be requested and executed by the client. This script
determines, which depot is to be used according to the current conditions. The interfaces to the client script are
specified as: the interface to get the list of available servers and the current client configuration (IP address, netmask,
gateway) and to return the result of the selection procedure. Furthermore there are interfaces for logging and user
information about the processing progress.
So the actual implementation within the script can easily be adapted to the requirements of the particular opsi
environment.
Regarding to this concept the single steps of a client connect are as follows:
1. The client connects to the opsi opsi-configserver via web service.
2. The opsi-configserver passes to the client the list of software packets to be installed.
3. The opsi-configserver transmits to the client the script for detecting the best depot and the list of available
depots.
4. The client executes the script and determines the best depot.
5. The client connects the chosen depot to get the required software packets.
6. The client installation status is reported to the opsi-configserver.
17.2 Requirements
This option requires opsi version >= 4.0.
This opsi extension is currently in the co-funding process and not free. For more details see Section 6.
Also at a minimum the following packet versions are required:
opsi −c l i e n t −agent 4.0 −11
python−o p s i 4.0.0.18 −1
opsi −c o n f i g e d 4.0.1.5 −1