On 19/01/2008, <b class="gmail_sendername">Serge Aleynikov</b> <<a href="mailto:saleyn@gmail.com">saleyn@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
When you are starting db1@host{1,2}-rep are you binding distributed<br> Erlang to the "rep" interface's IP address or using the default<br> (<a href="http://0.0.0.0">0.0.0.0</a>)? </blockquote><div><br>I'm using the default. <br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">A work around could be to use a<br> separate gen_tcp (udp?) server listening on the "oam" interface and roll<br>
out a custom protocol so that would detect incoming connection requests<br> (that are not based on Erlang's distribution), and cause<br> db1@host{1,2}-rep nodes to initiate connections to OMC.</blockquote><div><br>Or I can have an application on the DB nodes which ping the OMC node every minute or so. Which seems a bit of a bodge but the only real solution I have at the moment.<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> If you are binding the "rep" nodes to <a href="http://0.0.0.0">0.0.0.0</a> then there shouldn't be<br>
any issue connecting from OMC unless there's a firewall restriction.</blockquote><div><br>Well - there is an issue. This is because on the OMC node, host1-rep is resolving to an IP address to which routing doesn't exist from the OMC (and I can't get it added). The Security team won't allow this connectivity. <br>
</div><br>But is there a reason why the node name should have the hostname in it? Can't we have an erlang node on a machine registering with any arbitrary name in epmd? There could be kernel configuration on other nodes which can specify the host for each node name. This will have the added benefit that an mnesia database backup can easily be ported across various sets of nodes without having to change the name of the nodes in the backup file (which is a bit of a hack).<br>
<br>Thanks for your help.<br><br>cheers,<br>Chandru<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Chandru wrote:<br> > I am having a hard time figuring out how to get a few nodes to talk to each<br>
> other within certain rules. See figure below. Each box is a separate<br> > physical server. The small boxes inside each big box are LAN cards.<br> ><br> > +------------------+ +------------------+<br>
> | +--+ +--+ |<br> > | db1@host1-rep | |........| | db1@host2-rep |<br> > | +--+ +--+ |<br> > | +-oam--+ | | +-oam-+ |<br>
> +----+--+---+------+ +-------+--+--+----+<br> > | |<br> > | |<br> > | |<br> > | |<br>
> | +-------------------+ |<br> > | | | |<br> > | | | |<br> > +------+ OMC ....|<br> > | |<br>
> | |<br> > +-------------------+<br> ><br> ><br> > I've got two database nodes on two hosts, each of which have two LAN cards.<br> > One set of LAN cards are called the replication interfaces; they connect via<br>
> a special LAN which is very low latency and high bandwidth. This is used for<br> > mnesia replication. To enable this, I start the DB nodes with the -sname<br> > parameter set to 'db1@host1-rep'.<br> ><br>
> Now there is a separate OMC node which should talk to the DB nodes via<br> > distributed erlang on another set of interfaces. The problem is that the<br> > 'host1-rep' interface is not reachable from the OMC host (due to security<br>
> issues). Only the 'host1-oam' interface is reachable. But, on the OMC node,<br> > 'db1@host1-oam' is an unknown node.<br> ><br> > It seems that I need a feature where an erlang node on a machine can be<br>
> reached via multiple names, such as 'db1@host1', 'db1@host1-oam', '<br> > db1@host1-rep, but I doubt this capability exists.<br> ><br> > Any suggestions? Anyone else had similar issues to deal with?<br>
><br> > regards,<br> > Chandru<br> ><br> ><br> ><br> <br>> ------------------------------------------------------------------------<br> ><br> > _______________________________________________<br>
> erlang-questions mailing list<br> > <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br> > <a href="http://www.erlang.org/mailman/listinfo/erlang-questions">http://www.erlang.org/mailman/listinfo/erlang-questions</a><br>
<br> </blockquote></div><br>