Red Hat Bugzilla – Bug 623811
anaconda should use liblvm and libcryptsetup to get data area starts
Last modified: 2011-12-23 12:16:07 EST
Description of problem:
Anaconda should use liblvm and libcryptsetup to determine the data area start location for any volumes it will create.
liblvm must provide access to what a particular PV's pe_start will be (bug 623808).
libcryptsetup must provide access to what a particular LUKS device's 'Payload offset' will be.
improving anaconda in this manner will enable more comprehensive "I/O topology awareness" at install time.
Do you have a pointer to documentation for using those libraries?
anaconda changes are blocked by upstream acceptance of the as-yet-to-be-completed work described in bug #623808. Once those are done, we can work on changing anaconda.
Since bug #623808 is currently in ON_QA for 6.2 and the devel freeze is 4 business days away, I'm moving this bug to 6.3.
Anaconda is a python application. Until/unless liblvm provides python bindings this is a non-starter.
Based on comment #7 and where things stand right now with liblvm, I really don't see this happening in the 6.3 timeframe. Rather than carry this forward forever, I'm going to set devel_ack-.
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.
Fair enough... but be aware that dropping this may lead to misaligned root volumes in the future.
liblvm and libcryptsetup were thought to be a means to an end for fixing the general issue of making anaconda "I/O topology aware". That they have been deemed inadequate doesn't change the fact that anaconda is lacking said awareness.