On Fri, Jun 13, 2008 at 6:30 PM, Kyle McDonald <KMcDonald at egenera.com> wrote: >> Agree.. I didn't explicitly call this out, but we do intend to allow >> users to specify which disk to to the install on. >> >> > This is one area I'd like to see some innovation in. I agree with Mike > that I'd like to be able to tell AI to ignore my SAN disks, but at the > same time I'd like to not have to tweak the profile for each machine > tiype where the local disk might be c1t0, vs c0t0, etc.
This is a significant pain point in the current system. I don't know a good way of expressing this. But, for example, I need to mirror c3t0ds0 and c3t1d0s0 to form / mirror c3t2d0s0 and c3t3d0s0 to form /alt swap onto c3t0d0s1, c3t1d0s1, c3t2d0s1, c3t3d0s1 zpool create foo mirror c3t0d0s7 c3t1d0s7 mirror c3t2d0s7 c3t3d0s7 and the problem is that c3 may be c1, c2, c3, c4, whatever. So what I want to generically do is call disks cXt0d0s0 and cXt1d0s0 and have it ensure that it chooses two disks for which X is the same. The existing rules syntax allows you to choose things like 'disksize' and 'totaldisk'. Not that I've ever used that particular feature. But we do need a richer way of specifying the target device(s). I can imagine 'disktype' (sata, sas, scsi, fibre) might be useful in some cases, but it needs to be pretty flexible. An ignore option to simply skip any disks matching certain criteria might make sense too. (Ignore 'Vendor=EMC' would eliminate the possibility of accidentally overwriting the database on my SAN...) -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
