proper way to store LVM information

Registered by Gonéri Le Bouder on 2011-03-03

Hi,

A proposal had been done to store the LVM information in the DRIVES section:
http://forums.ocsinventory-ng.org/viewtopic.php?pid=33618
http://www.glpi-project.org/forum/viewtopic.php?id=22997
http://forge.fusioninventory.org/issues/6372
We think it would be clearer to have 3 new sections in the XML to store the information:
 - LVMLV
 - LVMVG
 - LVMPV

PV are always partition, so we can continue to push them in DRIVES.

RemiFedora: LV have specific information like stripping, mirror, snapshot, etc.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.