Re: NetApp filers 3rd party API
- From: Faeandar <mr_castalot@xxxxxxxxx>
- Date: Thu, 18 May 2006 07:55:59 GMT
On 18 May 2006 00:44:27 -0700, "ron.lindman@xxxxxxxxx"
<ron.lindman@xxxxxxxxx> wrote:
The idea is to configure the NetApp to redirect requests to a certain
"virtual" path to me, then I'd trigger operations based on this request
and finally redirect the request back to the NetApp.
Though this would require some path trickery, I believe one could
effectively behave like a proxy, inasmuch as you'd get to see and
potentially modify requests and responses. One downside would be that
I'd only get to see the initial request to the "virtual" path. Once I
redirect it back to a path that the NetApp services, I'm out of the
loop.
Will definitely look more into Widelinks, though. Thanks a bunch!
As far as 3rd party APIs to hook directly into the filers, does anybody
know definitively whether or not such a thing exists? Is my search in
vain?
Thanks,
Ron
Well you can't do this for NFS v3, no hand off capability at all. And
in current Ontap I don;t think you can do what you're asking with CIFS
either. NetApp will redirect path requests but it won;t notify you or
redirect it somewhere else first, at least not that I know of.
You could also look at Rainstorage as they do this exact thing but 1)
they're in the data path and 2) they don't redirect it to anything
other than the policy destination.
~F
.
- Follow-Ups:
- Re: NetApp filers 3rd party API
- From: Rob Turk
- Re: NetApp filers 3rd party API
- References:
- NetApp filers 3rd party API
- From: ron.lindman@xxxxxxxxx
- Re: NetApp filers 3rd party API
- From: ron.lindman@xxxxxxxxx
- Re: NetApp filers 3rd party API
- From: Faeandar
- Re: NetApp filers 3rd party API
- From: ron.lindman@xxxxxxxxx
- NetApp filers 3rd party API
- Prev by Date: Re: NetApp filers 3rd party API
- Next by Date: LUN sharing (DS4300 with storage partitions)
- Previous by thread: Re: NetApp filers 3rd party API
- Next by thread: Re: NetApp filers 3rd party API
- Index(es):
Relevant Pages
|