>
>An OST can be an externally connected (logical) disk such as a DDN
>LUN
>connected by fibre channel to the OSS. An OST can also be connected
>internally in the OSS such as a SATA, SCSI, (or heaven forbid) and
>IDE
>disk.
>
>Am I to understand you want the latter? Do you already have this
>hardware configuration and you just want to (re-)deploy it with
>Lustre?
>
Indeed. We'd like to construct a mass capacity matrix, and are
currently weighing risk and recovery into the equation.
>The reason being, is that Lustre can only achieve it's HA
>deliver-ability goals when two OSSes (or MDSes) can see a common
>storage
>target. Doing this with internally connected disks is difficult and
>usually requires a replication technology like DRBD to ensure that
>the
>(i.e. network mirrored) disks are in sync. This is a Sun-unsupported
>configuration, but there have been reports of success on this list.
>
>> This being said, can someone pinpoint me to a possibly high level
>> diagram of how redundancy can be implemented across nodes, if
>> possible?
>
>I don't know of any diagrams, but typically, you connect redundant
>OSSes
>to dual-ported disks so that either OSS can serve it's data. When
>one
>dies, the other takes over.
I see. I was under the impression that mirroring was part of the Lustre package
already. Am I correct to say that Lustre does handle the concatenation
of OST volumes?
Perhaps someone with DRBD experience can expand on that, as that would
be quite helpful. Is Lustre aware of DRBD? vice-versa?
Thanks for the Information Brian. It's very helpful.
>
>b.
_______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
