opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
15.4.3 Configuration of config caching
The configuration of the config caching is mainly done event specific:
Within an event configuration section [event_], the following options are available:
121 / 193
• sync_config_to_server (boolean): if the value of this option is set to true, the ConfigCacheService in case of that
event starts to transfer the changes registered by the modification tracker to the opsi-config-server. The process
will wait for that task to complete.
• sync_config_from_server (boolean): if this value is set to true, the ConfigCacheService starts with the replication.
If additionally the value of the option use_cached_config is set to true, the processing of this event is
suspended until the replication is completed.
• use_cached_config (boolean): if the value of this option is set to true, the client-cache-backend will be used for
processing the product actions. If the synchronization is not completed, the processing of this event will be stopped
and return an error code.
• post_sync_config_to_server (boolean): has the same functionality as sync_config_to_server, but will be
evaluated after the product actions have been completed.
• post_sync_config_from_server (boolean): has the same functionality as sync_config_from_server, but will
be evaluated after the product actions have been completed.
15.5 Recommended configuration when using the WAN/VPN extension module
The opsi-client-agent-package comes with a opsiclientd.conf prepared for the WAN/VPN extension.
For activating the WAN/VPN extension, just enabling of some events and disabling of some others is required.
The configuration of the opsi-client-agent also can be done from the web service (see: Section 7.3.6), so it is recommended
to create the following host parameter:
• opsiclientd.event_gui_startup.active (boolean, default: true)
• opsiclientd.event_gui_startup{user_logged_in}.active (boolean, default: true)
• opsiclientd.event_net_connection.active (boolean, default: false)
• opsiclientd.event_timer.active (boolean, default: false)
By these host parameter, events can be enabled or disabled client specific. The host parameter can be created using
the opsi-configed or opsi-admin.
For creating the host parameter by opsi-admin, the following commands have to be executed on the opsi-config-server:
opsi-admin -d method config_createBool opsiclientd.event_gui_startup.active "gui_startup active" true
opsi-admin -d method config_createBool opsiclientd.event_gui_startup{user_logged_in}.active "gui_startup{user_logged_in\
} active" true
opsi-admin -d method config_createBool opsiclientd.event_net_connection.active "event_net_connection active" false
opsi-admin -d method config_createBool opsiclientd.event_timer.active "event_timer active" false
The default values are as they come with the special opsiclientd.conf.
For a WAN/VPN client, which shall do caching of configurations and opsi-products, the host parameter have to be
configured as follows:
• opsiclientd.event_gui_startup.active: false
• opsiclientd.event_gui_startup{user_logged_in}.active: false
• opsiclientd.event_net_connection.active: true
• opsiclientd.event_timer.active: true