Bug 36437 - trigger/configure image updates by policy
trigger/configure image updates by policy
Status: NEW
Product: Z_Univention Corporate Client (UCC)
Classification: Unclassified
Component: Client management
unspecified
Other Linux
: P5 enhancement
: ---
Assigned To: UCC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-05 10:13 CET by Ingo Steuwer
Modified: 2015-11-23 17:20 CET (History)
5 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Roadmap discussion (moved)
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ingo Steuwer univentionstaff 2014-11-05 10:13:48 CET
Update rollouts of new images currently are configured per UCC object in LDAP. To trigger an update for many clients the "multi edit" mode can be used, but is slow for large amounts.

An alternative would be to configure this based on policies.


Requested by 2014110521000093
Comment 1 Moritz Muehlenhoff univentionstaff 2014-11-26 10:57:17 CET
I tried to configure the image for 1000 UCC clients on UCS 3.2 and UCC 1.0 and the update was finished in a few seconds.

In larger environments I suggest to separate the UCC clients depending on their use cases in sub containers and to register these containers as standard containers in the UMC. This allows easy selection of a sub group of systems.

A configuration of the images based on UMC policies would be fairly difficult to implement since we would need policy evaluation in the initrd.