clip.....

Just to add to this, I don't think we can limit things to the use of the ctd
naming - mainly since we allow disk selection to be done without knowing this.

For example, you could decide to select based on the bootdisk, and define some
partitions and slices on it. In this case you don't know the ctd of the disk,
but you do know the slices indexes:

<!-- Define Physical Disk layout -->
<target_device>
   <disk>
     <disk_keyword key="boot_disk"/>
     <slice name="0"></slice>
     <slice name="1"></slice>
   </disk>
</target_device>
<!-- Define Logicial devices -->
<target_device>
   <zpool name="rpool" is_root=true>
     <vdev>
       <dev_ref slice="0"/>
     </vdev>
   <zpool>
</target_device>

<target_device>
   <zpool name="space" is_root=false>
     <vdev>
       <dev_ref slice="1"/>
     </vdev>
   <zpool>
<target_device>

If you do this, specifying a slice, with out the disk name, would fall back to
the selected disk.

Because of this, I feel there is a need to be able to concretely identify a disk
that a slice is on, and I feel this could be done using an attribute such as
'id' which uniquely identifies the disk, regardless of the selection criteria
for the disk, e.g.

<!-- Define Physical Disk layout -->
<target_device>
   <disk id="my_disk">   <!-- Can be anything for id as long as it's unique -->
     <disk_keyword key="boot_disk"/>
     <slice name="0"></slice>
     <slice name="1"></slice>
   </disk>
</target_device>
<!-- Define Logicial devices -->
<target_device>
   <zpool name="rpool" is_root=true>
     <vdev>
       <dev_ref id="my_disk" slice="0"/>
     </vdev>
   <zpool>
</target_device>

<target_device>
   <zpool name="space" is_root=false>
     <vdev>
       <dev_ref id="my_disk" slice="1"/>
     </vdev>
   <zpool>
<target_device>

Just a suggestion ;)

Thanks,

Darren.
This led Alok and I down a long ugly path. ;-)

So if you have an id that would imply that you need the disk in the target_device specification. Is that required? From looking at the schema I don't think it is. Alok mentioned that if you don't specify a target disk then AI uses a default disk. So how would this work then? Actually, how does that work with the old schema even?

Jean

_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

Reply via email to