<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Thank you, Michael, I'll give that a try.<div><br></div><div>Regards,</div><div>Lee</div><div><br></div><div><br></div><div><br><div><div>On 6 May 2013, at 20:35, Michael Truog <<a href="mailto:mjtruog@gmail.com">mjtruog@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Lee,<br>
<br>
If you build a release that depends on the cloudi_core
application, it will find all the dependencies (as you can see,
they are listed in the application file input here:
<a class="moz-txt-link-freetext" href="https://github.com/okeuday/CloudI/blob/master/src/lib/cloudi_core/src/cloudi_core.app.src.in">https://github.com/okeuday/CloudI/blob/master/src/lib/cloudi_core/src/cloudi_core.app.src.in</a>).
You could use the reltool.config file as a way of understanding
how you can modify your own reltool.config file. The nodefinder
applications are the exception, since they are not listed as
dependencies within the application file, but are included within
the release, since their usage is based on configuration values.
So look at
<a class="moz-txt-link-freetext" href="https://github.com/okeuday/CloudI/blob/master/src/reltool.config.in">https://github.com/okeuday/CloudI/blob/master/src/reltool.config.in</a>
for more details about how the CloudI dependencies are included.
That particular reltool.config is a bit explicit, but if you were
using "{incl_cond, derived}, {mod_cond, derived}" within your
reltool.config file, providing the cloudi_core dependency to
include would be enough for reltool to find all the other
dependencies, except the nodefinder applications (so the
nodefinder applications can be listed separately, as shown). I
will create a sample application that includes CloudI for the next
release to help make this clearer as an example.<br>
<br>
It is simpler if you run both within the same Erlang VM and that
helps to minimize latency. You do have the option of using the
cpg module in a separate Erlang VM connected with distributed
Erlang using the same cookie to communicate with CloudI services,
but that approach doesn't utilize the CloudI API, so it is a bit
awkward and lacks the benefits of using CloudI.<br>
<br>
Best Regards,<br>
Michael<br>
<br>
On 05/06/2013 12:06 PM, Lee Sylvester wrote:<br>
</div>
<blockquote cite="mid:274729D4-2FD7-4364-8E11-0F081524A7AC@gmail.com" type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=windows-1252">
Hi Konstantin,
<div><br>
</div>
<div>How do you run them in the same VM?</div>
<div><br>
</div>
<div>Sorry, still an Erlang noob.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Lee</div>
<div><br>
</div>
<div><br>
<div>
<div>On 6 May 2013, at 19:31, Konstantin Tcepliaev <<a moz-do-not-send="true" href="mailto:f355@f355.ru">f355@f355.ru</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div>Hello,</div>
<div> </div>
<div>From what I see here: <a moz-do-not-send="true" href="https://github.com/okeuday/CloudI/blob/master/src/rel/files/vm.args#L5">https://github.com/okeuday/CloudI/blob/master/src/rel/files/vm.args#L5</a> the
problem is that cookies on your node and CloudI are
different.</div>
<div>As for me, I'd choose to run both applications within
the same VM, given that documentation clearly suggests
this: <a moz-do-not-send="true" href="https://github.com/okeuday/CloudI/blob/master/src/api/README.markdown">https://github.com/okeuday/CloudI/blob/master/src/api/README.markdown</a></div>
<div> </div>
<div>Cheers,</div>
<div>-- </div>
<div>Konstantin</div>
<div> </div>
<div>06.05.2013, 22:19, "Lee Sylvester" <<a moz-do-not-send="true" href="mailto:lee.sylvester@gmail.com">lee.sylvester@gmail.com</a>>:</div>
<blockquote type="cite">Thank you. I see this in the
output:
<div> </div>
<div>name cloudi at port 4374</div>
<div> </div>
<div>However, doing any of the following returns pang:</div>
<div> </div>
<div>net_adm:ping(cloudi).</div>
<div>net_adm:ping('cloudi@localhost').</div>
<div>net_adm:ping('<a moz-do-not-send="true" href="mailto:cloudi@127.0.0.1">cloudi@127.0.0.1</a>').</div>
<div> </div>
<div>Am I doing something silly?</div>
<div> </div>
<div>Thanks,</div>
<div>Lee</div>
<div> </div>
<div><br>
<div>
<div>On 6 May 2013, at 19:11, Motiejus Jakštys <<a moz-do-not-send="true" href="mailto:desired.mta@gmail.com">desired.mta@gmail.com</a>>
wrote:</div>
<br>
<blockquote type="cite"><span>epmd -names</span></blockquote>
</div>
</div>
,
<p>_______________________________________________<br>
erlang-questions mailing list<br>
<a moz-do-not-send="true" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a moz-do-not-send="true" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a></p>
</blockquote>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
erlang-questions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</blockquote>
<br>
</div>
</blockquote></div><br></div></body></html>