[OpenAFS] Problems Setting up new AFS cell in AWS
Victor Marmol
vmarmol@gmail.com
Tue, 18 Jun 2013 16:04:20 -0700
--089e013c64d6fec74604df75bce5
Content-Type: text/plain; charset=ISO-8859-1
Thanks for the pointers Nate! I got a similar setup working (although I
only have servers in AWS), but I am not NetRestricting the private IP.
Besides the initial timeout from the clients outside the NAT, is there
another reason to do this? I know that AWS treats internal and external
traffic differently in terms of billing (internal traffic to the internal
IP is free, but internal traffic to the external IP is not). I'm guessing
that is just a tradeoff.
Out of curiosity, Ben mentioned some issues related to virtualized
networking on small instances. Have you seen such a behavior, or do you run
larger instances anyways?
Victor
On Tue, Jun 18, 2013 at 11:00 AM, Nate Coraor <nate@bx.psu.edu> wrote:
> On Jun 18, 2013, at 1:20 PM, Victor Marmol wrote:
>
> > 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.
>
> Hi Victor,
>
> I run two DB/Fileservers in AWS and a third DB (and various other
> fileservers) outside AWS. You'll want to use Elastic IPs and configure
> NetInfo/NetRestrict accordingly. Here are my notes on the subject:
>
> http://www.bx.psu.edu/~nate/doc/vldb.html
>
> --nate
--089e013c64d6fec74604df75bce5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Thanks for the pointers Nate! I got a similar setup workin=
g (although I only have servers in AWS), but I am not NetRestricting the pr=
ivate IP. Besides the initial timeout from the clients outside the NAT, is =
there another reason to do this? I know that AWS treats internal and extern=
al traffic differently in terms of billing (internal traffic to the interna=
l IP is free, but internal traffic to the external IP is not). I'm gues=
sing that is just a tradeoff.<div>
<br></div><div>Out of curiosity, Ben mentioned some issues related to virtu=
alized networking on small instances. Have you seen such a behavior, or do =
you run larger instances anyways?</div><div><br></div><div>Victor</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue,=
Jun 18, 2013 at 11:00 AM, Nate Coraor <span dir=3D"ltr"><<a href=3D"mai=
lto:nate@bx.psu.edu" target=3D"_blank">nate@bx.psu.edu</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">
<div class=3D"im">On Jun 18, 2013, at 1:20 PM, Victor Marmol wrote:<br>
<br>
> I believe we have had a couple people report back from running AFS cel=
ls in AWS, with some unfortunate experiences relating to the network. Appar=
ently our Rx stack does not always deal well with the delays and interrupti=
ons that AWS VMs can see; it might be better with dedicated (large) instanc=
es. =A0It may be worth searching the list archives to find these reports, t=
hough I can't do so right now.<br>
><br>
> I just started running the server on AWS and will report back on my ex=
perience.<br>
<br>
</div>Hi Victor,<br>
<br>
I run two DB/Fileservers in AWS and a third DB (and various other fileserve=
rs) outside AWS. =A0You'll want to use Elastic IPs and configure NetInf=
o/NetRestrict accordingly. =A0Here are my notes on the subject:<br>
<br>
=A0 =A0 <a href=3D"http://www.bx.psu.edu/~nate/doc/vldb.html" target=3D"_bl=
ank">http://www.bx.psu.edu/~nate/doc/vldb.html</a><br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--nate</font></span></blockquote></div><br></div>
--089e013c64d6fec74604df75bce5--