[OpenAFS] OpenAFS for Windows IFS Status
David Bear
David.Bear@asu.edu
Tue, 6 Sep 2011 10:03:40 -0700
--20cf307f39ba294e5b04ac48cfab
Content-Type: text/plain; charset=UTF-8
YIPPY -- we need to have party on Sept 15 -- or close to it. This is GREAT
news.
On Sat, Sep 3, 2011 at 11:44 AM, Jeffrey Altman <
jaltman@your-file-system.com> wrote:
> On 9/3/2011 11:01 AM, Lars Schimmer wrote:
> > Hi!
> >
> > Due to the outstanding Windows 7 bug annoying us very deeply, we search
> > for a solution to this problem.
>
> The solution to the Windows 7 bug is the OpenAFS for Windows client with
> native installable file system driver which will be released as the
> 1.7.x development series.
>
> Now that 1.6.0 has finally been released work will begin on creating the
> openafs-devel-1_7_x branch from which the IFS windows client will be
> issued. The first official release from OpenAFS.org will be 1.7.1. I
> am hoping that we will be able to release on or around the 15th of Sept.
>
> The IFS client will bring some significant changes from the SMB client.
>
> No Loopback Adapter
> -------------------
>
> Now that a native IFS driver (afsredir.sys / afsredirlib.sys) is used,
> there is no need to install the Microsoft Loopback Adapter. Sites that
> have experienced problems due to the 10.254.254.253 address registration
> on multiple machines will be able to remove or disable the adapter once
> and for all.
>
> No Delays After a Resume
> ------------------------
>
> Windows Vista and 7 shutdown the network stack when the machine is
> suspended. This causes problems when the machine resumes because the
> network path to \\AFS is not immediately accessible. This is no longer
> an issue with the IFS driver.
>
> No "AFS" server name collisions
> -------------------------------
>
> It is now possible to add a machine named "AFS" to domain or subnet
> without breaking the OpenAFS for Windows client.
>
> Performance Improvements
> ------------------------
>
> The transaction rate and throughput performance of the SMB client was
> limited by the "SMB client <-> loopback <-> SMB server" performance:
> 54MB/sec maximum on 32-bit systems and 63MB/sec on 64-bit systems. The
> IFS client is capable of throughput rates to/from cache up to 800MB/sec
> depending on the system I/O bus and backing store capabilities.
>
> Symlinks to UNC Paths permit a cohesive name space
> --------------------------------------------------
>
> It has always been possible to create reparse points in MS DFS that
> refer to \\AFS paths. It is now possible to create symlinks in AFS
> that refer to arbitrary UNC paths. This permits the construction of
> a cohesive name space that spans across both AFS and DFS storage.
>
> Reparse Points
> --------------
>
> AFS Mount Points and Symlinks are exported by the file system
> as Windows reparse points with a Microsoft assigned tag value.
> Tools that are OpenAFS reparse point aware can create, query
> and remove AFS symlinks and mount points without requiring knowledge
> of AFS pioctls. The explorer shell will be able to delete a mount
> point or symlink as part of a recursive directory tree removal without
> crossing into the reparse point target.
>
> AFS Volumes are Windows File Systems
> ------------------------------------
>
> Each AFS volume is represented in the Windows kernel as a distinct
> file system. This will permit AFS volume quotas to viewed as
> Windows file system quotas.
>
>
> Authentication Groups
> ---------------------
>
> AFS Tokens are associated with Windows user names in the SMB client.
> With the IFS client, tokens are associated with Authentication Groups.
> By default, an authentication group is allocated for each User SID
> and Logon Session Id combination. In addition, it is possible for
> processes to create additional Authentication Groups. Each thread in
> a process can select an Authentication Group within the process as the
> active Authentication Group. This will permit AFS aware IIS modules
> to associate AFS credentials with a particular incoming request. An
> IIS implementation of File Drawers will be the preferred implementation
> once it is developed.
>
> One of the significant benefits of Authentication Groups within the
> Windows environment is that Windows services (svchost.exe, csrss.exe,
> etc.) which impersonate user processes will seamlessly gain access
> to the user's AFS credentials for the lifetime of the impersonation.
>
>
> Explorer Shell Integration
> --------------------------
>
> The AFS Explorer Shell integration will gain support for symlink
> and mount point overlay icons, tool tips, and Property dialog pages
> that replace many of the existing AFS Context Menu dialogs.
>
>
> Jeffrey Altman
>
>
--
David Bear
College of Public Programs at ASU
602-496-0424
--20cf307f39ba294e5b04ac48cfab
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
YIPPY -- we need to have party on Sept 15 -- or close to it. This is GREAT =
news.<br><br><div class=3D"gmail_quote">On Sat, Sep 3, 2011 at 11:44 AM, Je=
ffrey Altman <span dir=3D"ltr"><<a href=3D"mailto:jaltman@your-file-syst=
em.com">jaltman@your-file-system.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">On 9/3/2011 11:01 AM, Lars Schimmer wrote:<=
br>
> Hi!<br>
><br>
> Due to the outstanding Windows 7 bug annoying us very deeply, we searc=
h<br>
> for a solution to this problem.<br>
<br>
The solution to the Windows 7 bug is the OpenAFS for Windows client with<br=
>
native installable file system driver which will be released as the<br>
1.7.x development series.<br>
<br>
Now that 1.6.0 has finally been released work will begin on creating the<br=
>
openafs-devel-1_7_x branch from which the IFS windows client will be<br>
issued. =C2=A0The first official release from OpenAFS.org will be 1.7.1. =
=C2=A0I<br>
am hoping that we will be able to release on or around the 15th of Sept.<br=
>
<br>
The IFS client will bring some significant changes from the SMB client.<br>
<br>
No Loopback Adapter<br>
-------------------<br>
<br>
Now that a native IFS driver (afsredir.sys / afsredirlib.sys) is used,<br>
there is no need to install the Microsoft Loopback Adapter. =C2=A0Sites tha=
t<br>
have experienced problems due to the 10.254.254.253 address registration<br=
>
on multiple machines will be able to remove or disable the adapter once<br>
and for all.<br>
<br>
No Delays After a Resume<br>
------------------------<br>
<br>
Windows Vista and 7 shutdown the network stack when the machine is<br>
suspended. =C2=A0This causes problems when the machine resumes because the<=
br>
network path to \\AFS is not immediately accessible. =C2=A0This is no longe=
r<br>
an issue with the IFS driver.<br>
<br>
No "AFS" server name collisions<br>
-------------------------------<br>
<br>
It is now possible to add a machine named "AFS" to domain or subn=
et<br>
without breaking the OpenAFS for Windows client.<br>
<br>
Performance Improvements<br>
------------------------<br>
<br>
The transaction rate and throughput performance of the SMB client was<br>
limited by the "SMB client <-> loopback <-> SMB server&quo=
t; performance:<br>
54MB/sec maximum on 32-bit systems and 63MB/sec on 64-bit systems. =C2=A0Th=
e<br>
IFS client is capable of throughput rates to/from cache up to 800MB/sec<br>
depending on the system I/O bus and backing store capabilities.<br>
<br>
Symlinks to UNC Paths permit a cohesive name space<br>
--------------------------------------------------<br>
<br>
It has always been possible to create reparse points in MS DFS that<br>
refer to \\AFS paths. =C2=A0It is now possible to create symlinks in AFS<br=
>
that refer to arbitrary UNC paths. =C2=A0This permits the construction of<b=
r>
a cohesive name space that spans across both AFS and DFS storage.<br>
<br>
Reparse Points<br>
--------------<br>
<br>
AFS Mount Points and Symlinks are exported by the file system<br>
as Windows reparse points with a Microsoft assigned tag value.<br>
Tools that are OpenAFS reparse point aware can create, query<br>
and remove AFS symlinks and mount points without requiring knowledge<br>
of AFS pioctls. =C2=A0The explorer shell will be able to delete a mount<br>
point or symlink as part of a recursive directory tree removal without<br>
crossing into the reparse point target.<br>
<br>
AFS Volumes are Windows File Systems<br>
------------------------------------<br>
<br>
Each AFS volume is represented in the Windows kernel as a distinct<br>
file system. =C2=A0This will permit AFS volume quotas to viewed as<br>
Windows file system quotas.<br>
<br>
<br>
Authentication Groups<br>
---------------------<br>
<br>
AFS Tokens are associated with Windows user names in the SMB client.<br>
With the IFS client, tokens are associated with Authentication Groups.<br>
By default, an authentication group is allocated for each User SID<br>
and Logon Session Id combination. =C2=A0In addition, it is possible for<br>
processes to create additional Authentication Groups. =C2=A0Each thread in<=
br>
a process can select an Authentication Group within the process as the<br>
active Authentication Group. =C2=A0This will permit AFS aware IIS modules<b=
r>
to associate AFS credentials with a particular incoming request. =C2=A0An<b=
r>
IIS implementation of File Drawers will be the preferred implementation<br>
once it is developed.<br>
<br>
One of the significant benefits of Authentication Groups within the<br>
Windows environment is that Windows services (svchost.exe, csrss.exe,<br>
etc.) which impersonate user processes will seamlessly gain access<br>
to the user's AFS credentials for the lifetime of the impersonation.<br=
>
<br>
<br>
Explorer Shell Integration<br>
--------------------------<br>
<br>
The AFS Explorer Shell integration will gain support for symlink<br>
and mount point overlay icons, tool tips, and Property dialog pages<br>
that replace many of the existing AFS Context Menu dialogs.<br>
<font color=3D"#888888"><br>
<br>
Jeffrey Altman<br>
<br>
</font></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>David=
Bear<br>College of Public Programs at ASU<br>602-496-0424<br>
--20cf307f39ba294e5b04ac48cfab--