[yast-devel] libstorage plans?
hello, Arvin mentioned in libstorage/pull/69 that there are "important and fundamental changes required in libstorage". i'd like to know what you (both Arvin and the team as a whole) plan in this regard? after seeing some real-world problems with libstorage, and from my short venture into its code i'd say the most pressing problem is the cylinder as the base unit for partition positions and sizes, with the broken class hierarchy (dynamic_cast...) distant second. while these two may be the "worst", it does not necessarily make sense to approach them first; it may be easier to postpone that until after some other cleanup is done to make the code clearer. in this regard, libstorage could use wider adoption of C++11 features like "auto" and range-based loops. so, what is your roadmap? -- roman -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 23.6.2014 12:29, Roman Neuhauser wrote:
hello,
Arvin mentioned in libstorage/pull/69 that there are "important and fundamental changes required in libstorage". i'd like to know what you (both Arvin and the team as a whole) plan in this regard? ... shortened ... so, what is your roadmap?
The Yast Roadmap discussion has started here: http://lists.opensuse.org/yast-devel/2014-06/msg00010.html libstorage roadmap could but needen't be the same. For me, the most important one is what you have already mentioned: Cylinder as the internal base unit. IMO, we need to start documenting WHAT we want and need to achieve and HOW. Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader Cloud & Systems Management Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Mon, Jun 23, 2014 at 12:29:53PM +0200, Roman Neuhauser wrote:
hello,
Arvin mentioned in libstorage/pull/69 that there are "important and fundamental changes required in libstorage". i'd like to know what you (both Arvin and the team as a whole) plan in this regard?
I don't plan anything since the feature requests use all of my
time anyway. Years ago I started a to-do list that just keeps
growing. Some entries:
- continue real-world testsuite
- generate image in build-service
- more tests
- automatic runs
- move some stuff from GetPrimPartitons to libstorage (for kiwi)
- container and volume design starts to break down:
- md can be container or volume since kernel 2.6.28
- people want to use whole disk as volume with filesystem
- pv on whole disk cannot be encrypted
- XEN disks
- btrfs?
- snapshots?
proposal: split filesystem/encryption stuff from Volume into
new class Payload and derive Container and Volume from that new
class Payload
- use a graph instead of list of list
- separate parsers from logic
- for dmpart/multipath/mdpart there are *two* partition objects
for each partition!
- think about proposal rewrite in libstorage
- don't remember udev data in DmPartCo but use the one in Disk
instead - ugly (derive DmPartCo from Disk (as Dasd does it)?)
- detect mount also in inst-sys and remove AddSwapMp?
- unify commit messages, e.g. some contain size others not,
create vg is destructive while create sw raid isn't
- don't even look at disks used by BIOS RAID or multipath (see
bnc #460081, #436825 c36)
- avoid calling external grep
- add ronly_ptable for disk so that ronly has always same meaning
- maybe move ronly to Device
- use more data from /sys during probing
Regards,
Arvin
--
Arvin Schnell,
On 23.6.2014 12:45, Arvin Schnell wrote:
On Mon, Jun 23, 2014 at 12:29:53PM +0200, Roman Neuhauser wrote:
hello,
Arvin mentioned in libstorage/pull/69 that there are "important and fundamental changes required in libstorage". i'd like to know what you (both Arvin and the team as a whole) plan in this regard?
I don't plan anything since the feature requests use all of my time anyway. Years ago I started a to-do list that just keeps growing. Some entries:
... shortened ...
Regards, Arvin
Sounds like a nice list of ideas. Please put it to GitHub or update the Wiki page and link that Wiki from GitHub. Thanks Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader Cloud & Systems Management Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (3)
-
Arvin Schnell -
Lukas Ocilka -
Roman Neuhauser