opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
15.3.1 Communication Protocol for accessing an opsi-depot
For transferring the product files, two different protocols are used:
• CIFS/SMB
• HTTP(S)/WEBDAV(S)
118 / 193
In case of using CIFS/SMB, a connection to the depotRemoteUrl will be established as configured with the properties
of the opsi-depot. In case of using HTTP(S)/WEBDAV(S), the depotWebdavUrl is connected, which as well is to be
configured with the properties of the opsi-depot.
Which protocol is to be used, can be configured client specific by the host parameter clientconfig.depot.protocol.
Available values to be set as clientconfig.depot.protocol are cifs and webdav.
Note
Also the opsi-linux-bootimage is evaluating this setting and uses the specified protocol.
15.3.2 Using the .files file for Synchronization
The synchronization process is based on the file .files, which is located in the base directory of each
opsi-product on the opsi-depot. This file contains information about the files, directories ans symbolic links used by an
opsi-product. Each line of that file contains such information. Different types of information are separated by a blank.
The first character of a line defines the type of the following entry. Available values are:
• d for a directory
• f for a file
• l for a symbolic link
Separated by a blank follows the relative path, which is single quoted.
The next entry gives the sizes of the file (which is 0 for directories and symbolic links).
The final entry in case of a file is the MD5-sum of the file, in case of a symbolic link it is the target referred to by the
symbolic link.
Example excerpt of a .files file:
d ’utils’ 0
f ’utils/patch_config_file.py’ 2506 d3007628addf6d9f688eb4c2e219dc18
l ’utils/link_to_patch_config_file.py’ 0 ’/utils/patch_config_file.py’
The .files file is generated automatically when installing opsi-product-packages (after running the postinst-Script).
Warning
When using the WAN/VPN extension, the files of opsi-products on the opsi-depot should not be changed manually,
otherwise the information contained in the .files file would be outdated, causing errors during the synchronization
process.
15.3.3 Internal processing of opsi-product caching
The synchronization of a local copy of an opsi-product processes as follows:
• The .files file of the opsi-product is transferred to the local client.