[OpenAFS] the future
Mon, 01 Oct 2012 22:18:44 -0400
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
Content-Type: text/plain; charset=UTF-8
On 10/1/2012 3:28 PM, Dyer, Rodney wrote:
> NetApp=E2=80=99s strength is actually its problem, and that is it doesn=
> actually exist to the client, it is completely invisible. Windows sees=
> it as a normal Windows CIFS share. =E2=80=98nix sees it as NFS. The p=
> that this is point-to-point file sharing. AFS allows global namespace,=
> and the client does the volume lookup to find the server for the =E2=80=
> required. This is true =E2=80=9Cdistribution=E2=80=9D, not point-to-po=
> If you setup Microsoft=E2=80=99s AD =E2=80=9Cdfs=E2=80=9D with NetApp f=
ilers, you might come
> close to =E2=80=9Cemulating=E2=80=9D what AFS does, but it won=E2=80=99=
t be pretty, and as far
> as I know =E2=80=98nix is out of the question in that setup.
At the SNIA 2012 Storage Developers Conference Linux SMB 2.1 support was
demonstrated. This support is in kernel and provides Linux the same
level of SMB protocol support as Windows 7. I don't know if the SMB
module is capable of per user GSS-API authentication but if it is, SMB
can be used as an alternative to NFS when communicating with a NetApp
NetApp filers are still extremely expensive storage devices. Microsoft
Windows Storage Server 2012 can be used to provide a much less expensive
storage solution providing cluster failover for database and hypervisor
applications. Of course, many large enterprises already own NetApp
filers and feel obligated to use them for as many services as possible
in order to justify the cost.
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
-----END PGP SIGNATURE-----