Univention Bugzilla – Bug 35410
allow dedicated image servers for clients / networks
Last modified: 2015-08-07 15:48:18 CEST
If more than one image server is available UCC currently chooses randomly which one is used during a rollout.
For larger networks it would be helpfull to assign allowed or preferred image-servers to clients or networks. If possible, a client should know by the network it is currently in and the settings in the management system which image server will deliver with the best performance.
Currently this can be achieved only in a complex process: the image needs to be copied/renamed and registered several times under different names in the management system. Then, for each "rebranded" version of the image, image servers and clients can be assigned individually.
* added univentionCorporateClientDedicatedImageServer to objectclass
* added "imageServer" (ip of an UCC server) to computers/ucc
* the listener now checks if the client has a
univentionCorporateClientDedicatedImageServer and uses this ip
for the nfsroot options (otherwise ucc/pxe/nfsroot is used)
* is the client has an univentionCorporateClientDedicatedImageServer, it is now
the first entry in the list of servers in generate_nfs_mount_script and
=> A dedicated image server can be set for a UCC client (no policy!). This server is than used in the pxe config and as first server during update/local rollout.
OK: Integration packages
OK: unchanged default uses ucrv ucc/pxe/nfsroot, image server is configureable
OK: I added a changelog entry (r62134)
OK: documentation will be done at bug #38921
UCC 2.1 has been released. If this error occurs again, please use "Clone This Bug".