On Mon, 20 Sep 2010 18:40:51 -0700 Chandra Seetharaman <sekharan at us.ibm.com> wrote: > Hello All, > > ---------------- > This is a resend of the patches sent on 09/17/2010: > http://lists.wpkg.org/pipermail/stgt/2010-September/004108.html > which was a resend of the patches sent on 09/01/2010: > http://lists.wpkg.org/pipermail/stgt/2010-September/004082.html > > I added changes based on Tomo's suggestions. > ---------------- > Currently, when a initiator tries to login to a target it can be redirected > to a different portal. But, Redirect portal is static. i.e the user has to > define the redirect portal for a target and _all_ the login requests for that > target will be redirected to the specified portal. > > In order to provide load balancing capability, it will be better to have > "dynamic redirection". This is envisioned as: > - user defines an external program that takes initiator's address > (in ipv4 or ipv6 format) > - user defines a "RedirectCallback" parameter for a target > # tgtadm --op update --mode target --tid 1 --name RedirectCallback \ > --value /usr/local/bin/redirect > - When a initiator tries to login to target tid, user defined program > will be invoked with the target name and the initiator's ip address > and it is expected to return a triplet defining the > redirect portal, in the format of > "string_addr:string_port:string_reason" > example: "10.0.0.51:860:Temporary" or > "[fe80::214:5eff:acaf:c844]:860:Temporary" > - Initiator will be redirected to the portal returned by the user > defined program. > > Following set of patches provide the feature. Please review and provide your > comments. Looks fine, applied. Thanks! -- To unsubscribe from this list: send the line "unsubscribe stgt" in the body of a message to majordomo at vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html |