Brian Elliott Finley wrote:
<config>
<disk dev="/dev/hda" label_type="msdos" unit_of_measurement="MB">
<part num="1" size="1000" p_type="primary" p_name="-" fs="ext2"
flags="boot"/>
<part num="2" size="1000" p_type="primary" p_name="-" fs="-"
flags="raid" raid_dev="/dev/md0" />
<part num="3" size="*" p_type="primary" p_name="-" fs="-"
flags="raid" raid_dev="/dev/md1" />
</disk>
<disk dev="/dev/hdc" label_type="msdos" unit_of_measurement="MB">
<part num="1" size="1000" p_type="primary" p_name="-" fs="ext2"
flags="-" />
<part num="2" size="1000" p_type="primary" p_name="-" fs="-"
flags="raid" raid_dev="/dev/md0" />
<part num="3" size="*" p_type="primary" p_name="-" fs="-"
flags="raid" raid_dev="/dev/md1" />
</disk>
<raid>
<raid_disk name="/dev/md0" raid_level="1" persistent_superblock="1"
chunk_size="32" />
<raid_disk name="/dev/md1" raid_level="0" lvm_group="systemvg" />
</raid>
Perhaps consider including the raid_dev and spare_dev info with the
other raid stuff, instead of with the disk stuff. I'd say let's:
* limit the info in the <disk> sections to partition creation info.
* limit the info in the <raid> sections to raid creation info.
* limit the info in the <lvm> sections to lvm creation info.
Maybe something like this:
<raid dev="/dev/md0" raid_level="1" persistent_superblock="1"
chunk_size="32">
<raid_dev dev="/dev/hda2" />
<raid_dev dev="/dev/hdc2" />
<hot_spare dev="/dev/hde2" />
</raid>
<raid dev="/dev/md1" raid_level="0">
<raid_dev dev="/dev/hda3" />
<raid_dev dev="/dev/hdc3" />
</raid>
Then if LVM is to ride on top of the RAID:
<lvm>
<lvm_group name="systemvg">
<pv dev="/dev/md0">
# <pv dev="/dev/md3">
# <pv dev="/dev/md4">
# <pv dev="/dev/etc...">
</lvm_group>
<lvm_group name="striped-vg">
<pv dev="/dev/md1">
</lvm_group>
<lv name="usrlv" size="2000" vg="systemvg" />
<lv name="optlv" size="2000" vg="systemvg" />
<lv name="varlv" size="2000" vg="striped-vg" />
<lv name="tmplv" size="1000" vg="systemvg" />
</lvm>
This layout also allows you to ride RAID on top of LVM:
<raid dev="/dev/md7" raid_level="0">
<raid_dev dev="/dev/mapper/systemvg-vol1" />
<raid_dev dev="/dev/mapper/systemvg-vol2" />
</raid>
And LVM on top of normal disk:
<lvm>
<lvm_group name="andreas-vg">
<pv dev="/dev/sdc1">
<pv dev="/dev/sdd1">
<pv dev="/dev/sde1">
</lvm_group>
<lv name="big-time-lv" size="*" vg="andreas-vg" />
</lvm>
I totally agree with you. This will need a little work to adapt the code
in Server.pm, but in this way I thnk it will be easier to implement the
code in si_prepareclient script... ;-)
Regards,
-Andrea
--
Andrea Righi
System Management Group - CINECA - http://www.cineca.it
Via Magnanelli 6/3
40033 Casalecchio di Reno (BO) - Italy
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Sisuite-devel mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
