opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
15.4 Caching of configurations
120 / 193
The caching of configurations is done by the ConfigCacheService, which is part of the opsiclientd.
The ConfigCacheService synchronizes a local client-cache-backend with the config backend of the opsi-config-server.
The opsiclientd provides per WebService an access point to the backend and thereby provides quite the same functionality
as the opsiconfd.
15.4.1 The local client-cache-backend
The local client-cache-backend is based on SQLite and mainly consists of a local working copy, a snapshot an a
modification tracker, which records all changes of the local working copy.
The base directory of the config cache can be configured and defaults to %SystemDrive%\opsi.org\cache\config.
The snapshot reflects the configuration status on the opsi-config-server at the time of the last synchronization.
At the start of the processing, the local working copy is a copy of the snapshot, but will be modified during processing.
15.4.2 Internal processing of configuration synchronizing
The synchronization of the local changes of the client-cache-backend with the config backend of the opsi-config-server
is processed as follows:
• The changes of the local working copy registered by the modification-tracker are transferred to the opsi-configserver.
Any changes of the configuration on the opsi-config-server since the last synchronization will be detected
by comparing to the snapshot. If there are any conflicts deteced, the following rules apply:
– In case of inventory data, the local client data have priority.
– In case of action requests, the value from the opsi-config-server has priority.
– In case of installation status and action result, the client data have priority.
– The software licenses in use are given by the local client. Any unused licences, which have been reserved during
replication, will be released again.
– The opsi-config-server has priority for the status of host parameter and product properties.
• The modification tracker will be cleared.
• The logfiles will be transferred.
The config backend replication of the opsi-config-server to the client-cache-backend is processed as follows:
• The replication only takes place, if any action requests are set on the opsi-config-server. The product action always
does not count in this respect. The replication process will start only if the status of action requests is changed
since the last replication.
• The modification tracker and the local working copy are cleared.
• The configurations required for local processing will be replicated.
• If action requests are set for opsi-products which are marked as to require a license, the required software license
will be reserved from a license pool, which is assigned to that opsi-product.
• Additionally required data, as there are the auditHardwareConfig and the modules, will be transferred.
• The snapshot and the local working copy will be updated, so they have the same content.
A successful replication from server to client results in:
• The status of config_cached is set to true (and stays true in case of a system restart, see: Section 7.3.6).
• An event of type sync completed will be triggered.