NFS connections between applications

[Jsmart]

We have been getting a lot of requests lately to explain how this works; so here is an example :)

Example:

application 1: IN -> NAS (connected on nfs terminal)

application 2: WEB5 -> OUT (connected on the fs terminal of WEB)

OUT on app2 is configured to forward traffic to the IP of app1:IN

app1:IN has the following configuration:
allowed_hosts = ip of app2.OUT (proper configuration of allowed/denied hosts
is important as otherwise the shares will be open to the world).
iface1_protocol = tcp
iface1_port = 111
iface2_protocol = tcp
iface2_port = 2049
iface3_protocol = none
iface3_port = 0
iface4_protocol = 17
iface4_port = 0

This provides access to all UDP ports + tcp 111 and 2049 which is enough for
nfs to work. WEB5 mounts its fs successfully from the other appliance.

--Jessie

[jonesy]

This configuration requires that packets be passed over the internet. If two apps are running on the same grid, it seems there should be a way to talk over a non-routable network space. Would it be possible to add an 'in' gateway to application 1 whose public interface IP is in this private space, and then have the out gateway on app 2 use that as its default gateway?

Is there maybe a cleaner way to do this without adding an in gateway? Can the existing in gateway on app 1 be configured with an additional interface on the private network that the out gateway on app 2 can use as a gateway? Is there a way to maybe skip all of this and just have components in different applications live on the *same* network?

[PeterNic]

Brian,

We are working on some provisions in AppLogic for the internal network. Some of our hosting partners will allow using a private, non-routable IP address -- which will never get out on the Internet. For now, this requires that the non-routable IP address is OK'd by the datacenter.

From design standpoint, two applications can't assume they are on the same grid -- so they need to have the gateways.

Regards,
-- Peter

[acw]

the config mentioned seems to be missing a step. mountd on NAS appliance changes port number on each startup. So, to make the mountd port number static, /etc/sysconfig/nfs needs an additional entry :

MOUNTD_PORT=10001 #or whatever port number

and then

iface1_protocol = tcp
iface1_port = 111
iface2_protocol = tcp
iface2_port = 2049
iface3_protocol = tcp
iface3_port = 10001
iface4_protocol = 17
iface4_port = 0

Had to add the above steps to make that NAS behind a IN appliance mountable.