[OpenAFS] Problems Setting up new AFS cell in AWS

[Victor Marmol]

--089e0158c5aa4f148904df70f06b
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 18, 2013 at 8:55 AM, Benjamin Kaduk <kaduk@mit.edu> wrote:

> On Mon, 17 Jun 2013, Victor Marmol wrote:
>
>  afs-newcell fails when it tries to contact bos. The BosLog says:
>>
>
> I seem to recall that that is a debian-specific script, which not everyone
> would be familiar with.


Ah, yes it looks like it is debian specific.

>
>
>  From the little I found online there were some references to a NetInfo
>> file, but I was unable to find any good documentation for it. The file
>> does
>> not appear in my instance.
>>
>
> I believe you will need a NetInfo file if you are behind a NAT.  Did you
> see http://docs.openafs.org/**Reference/5/NetInfo.html<http://docs.openafs.org/Reference/5/NetInfo.html>?  It seems to be using transarc paths, but translating to FHS-compliant
> paths should not be too difficult.


Thank you! The key insight was the transarc paths to FHS since my system
uses the FHS path :) the server is setup and the clients (outside the NAT)
are able to access the files as normal.

>
>
>  Has anyone had similar experiences setting up an AFS cell in AWS? or
>> behind
>> a NAT?
>>
>
> I believe we have had a couple people report back from running AFS cells
> in AWS, with some unfortunate experiences relating to the network.
> Apparently our Rx stack does not always deal well with the delays and
> interruptions that AWS VMs can see; it might be better with dedicated
> (large) instances.  It may be worth searching the list archives to find
> these reports, though I can't do so right now.
>

I just started running the server on AWS and will report back on my
experience.

Thanks again!
Victor

>
>
> -Ben
>

--089e0158c5aa4f148904df70f06b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Jun 18, 2013 at 8:55 AM, Benjamin Kaduk <span dir=
=3D"ltr">&lt;<a href=3D"mailto:kaduk@mit.edu" target=3D"_blank">kaduk@mit.e=
du</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_=
quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">

<div class=3D"im">On Mon, 17 Jun 2013, Victor Marmol wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
afs-newcell fails when it tries to contact bos. The BosLog says:<br>
</blockquote>
<br></div>
I seem to recall that that is a debian-specific script, which not everyone =
would be familiar with.</blockquote><div><br></div><div>Ah, yes it looks li=
ke it is debian specific.=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
>From the little I found online there were some references to a NetInfo<br>
file, but I was unable to find any good documentation for it. The file does=
<br>
not appear in my instance.<br>
</blockquote>
<br></div>
I believe you will need a NetInfo file if you are behind a NAT. =A0Did you =
see <a href=3D"http://docs.openafs.org/Reference/5/NetInfo.html" target=3D"=
_blank">http://docs.openafs.org/<u></u>Reference/5/NetInfo.html</a> ? =A0It=
 seems to be using transarc paths, but translating to FHS-compliant paths s=
hould not be too difficult.</blockquote>

<div><br></div><div>Thank you! The key insight was the transarc paths to FH=
S since my system uses the FHS path :) the server is setup and the clients =
(outside the NAT) are able to access the files as normal.=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">

<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Has anyone had similar experiences setting up an AFS cell in AWS? or behind=
<br>
a NAT?<br>
</blockquote>
<br></div>
I believe we have had a couple people report back from running AFS cells in=
 AWS, with some unfortunate experiences relating to the network. Apparently=
 our Rx stack does not always deal well with the delays and interruptions t=
hat AWS VMs can see; it might be better with dedicated (large) instances. =
=A0It may be worth searching the list archives to find these reports, thoug=
h I can&#39;t do so right now.<br>

</blockquote><div><br></div><div>I just started running the server on AWS a=
nd will report back on my experience.</div><div><br></div><div>Thanks again=
!</div><div>Victor=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


<br>
<br>
-Ben<br>
</blockquote></div><br></div></div>

--089e0158c5aa4f148904df70f06b--