Bug 34774 - Separate UCC images and partition information
Summary: Separate UCC images and partition information
Status: CLOSED WONTFIX
Alias: None
Product: Z_Univention Corporate Client (UCC)
Classification: Unclassified
Component: Image management
Version: unspecified
Hardware: Other Linux
: P5 enhancement
Target Milestone: UCC 2.x
Assignee: UCC maintainers
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-08 11:15 CEST by Moritz Muehlenhoff
Modified: 2023-06-28 10:33 CEST (History)
1 user (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)
Customer ID:
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Muehlenhoff univentionstaff 2014-05-08 11:15:19 CEST 
Currently the partitioning information is configured as part of the image build process. This makes handling different partition schemes difficult, it currently requires to rebuild the image with different partition information.

We should separate the image and the partition data, e.g. by having a separate .partition file along with the UCC image. When doing this we should also swift through the partition options and evaluate whether they are still required (e.g. remove_partitions is likely not very useful).

This would also allow easier implementation of dual boot images (UCC/Windows). With the current approach a user needs to rebuild the UCC images to configure dual boot. With the new approach we could simply ship a different .partition file to use.
Comment 1 Erik Damrose univentionstaff 2014-10-01 09:12:57 CEST 
This feature has already been implemented in Bug 34612

http://docs.univention.de/ucc-manual-2.0.html#rollout:crypto

*** This bug has been marked as a duplicate of bug 34612 ***
Comment 2 Moritz Muehlenhoff univentionstaff 2014-11-26 09:21:08 CET 
This bug has a broader scope than what we implemented for 2.0 in Bug 34612
Comment 3 Philipp Hahn univentionstaff 2023-06-28 10:30:25 CEST 
UCC is EoL