Re: [Iscsitarget-devel] Reasons for forking Ardistech's Target?

[FUJITA T. <to...@ac...>]

From: Arne Redlich <ar...@in...>
Subject: Re: [Iscsitarget-devel] Reasons for forking Ardistech's Target?
Date: Fri, 25 Jun 2004 15:08:38 +0200

> > The UNH target can handle multiple initiators, but the initiators must
> > share all volumes (You can't configure security policy or volumes per
> > an initiator).
> > 
> > Right?
> 
> Right. AFAIK, Ardistech's target can't do this either? Indeed, a proper
> LUN masking solution would be quite high on my wish-list for any target
> (actually I have some ideas for UNH's target concerning this issue).
> 
> At the moment there is only a really awkward and cumbersome workaround
> (you're certainly aware of it, but maybe this is of interest to others?)
> to get at least some basic protection:
> o Ardistech:
> Configuring different (sets of) LUNs in different "Target" sections in
> the  conf-file, each having unique CHAP credentials (known to exactly
> only one initiator, of course), makes accidental concurrent accesses to
> the same LUN at least a bit harder.

I don't understand this issue. So please let me ask a question.

If you have two initiators, you setup two targets. Each target can
handle block devices, exports as many LUs as you like. Each target can
use a unique account.

This seems to be good enough for me.


You want a single target to handle multiple initiators. In addition,
you want to use a unique account for each initiator.

Do I understand correctly? If so, my next question is why you want to
do it.