[ANN] CloudI 0.2.0rc2 Released

[Michael Truog]

Download 0.2.0rc2 from http://sourceforge.net/projects/cloudi/files/latest/download

CloudI (http://cloudi.org) release 0.2.0rc2 is a bugfix release. Testing is ongoing and the FAQ will be updated to reflect the new features in 0.2.0. After sufficient testing, the 0.2.0 release will become 1.0.0 to begin semantic versioning (http://semver.org). Summary of changes:
* many bugfixes
* messaging test is now implemented in Erlang, C++, Ruby, Java, and Python
* added alternative function pointer parameters for C++ CloudI API usage
so that there is no need to create std::string objects

Anyone with questions, comments, ideas, suggestions, criticisms, or concerns is welcome to send email.

Thanks,
Michael

[osiris]

Building this release on Ubuntu 12.04 and starting cloudi has been
very straightforward; no issues at all. What appears to be missing for
a newbie to Cloudi is how to setup and run a simple example like the
hexpi application. A few tips will be welcome.

On Apr 14, 5:15 pm, Michael Truog <mjtr...@gmail.com> wrote:
> Download 0.2.0rc2 fromhttp://sourceforge.net/projects/cloudi/files/latest/download

[Michael Truog]

The default configuration runs the following tests:
hexpi
http
http_req
zeromq
msg_size
messaging
(as shown here: https://github.com/okeuday/CloudI/blob/master/src/cloudi.conf.in)

That is why the CPU usage will go up when starting CloudI with the default configuration. The default hexpi parameters only compute upto the 65536th hexadecimal digit of pi (see the configuration for the cloudi_job_hexpi Erlang service arguments, on line 185).

The other tests are doing a few other things: "http" and "http_req" both respond to HTTP requests in the supported languages for testing the HTTP functionality and the latency/throughput, "zeromq" tests the ZeroMQ integration, "msg_size" tests the forwarding of large messages within the supported languages, and "messaging" tests complex usage of the CloudI API. The "flood" test is commented out within the configuration file, since it attempts to saturate the CloudI internal messaging, but is rather dull otherwise.

When CloudI is installed, the configuration exists in PREFIX/etc/cloudi/cloudi.conf (where PREFIX is /usr/local by default). The progress of hexpi can be seen within the CloudI logfile which exists in PREFIX/var/log/cloudi/cloudi.log (as long as CloudI starts successfully... otherwise you would need to check PREFIX/var/log/cloudi/erlang.log.1 and/or PREFIX/var/log/cloudi/sasl.log to see what went wrong).

If you are only interested in the hexpi test, you can remove the rest from you configuration file within the configuration file's jobs list (the services are ran as jobs, so with an explicit order, despite the fact these jobs (i.e., longer running services) do not exit). Please keep in mind that the hexpi test is two CloudI services, one in C++ and one in Erlang (so, there are two jobs list entries within the configuration file... one internal and one external).

Please tell me if you have more questions. I updated the FAQ tonight so that it has more information that is relevant to the last release, but I know more documentation is necessary (an API doc, tutorials, etc.). I am working on more documentation besides the FAQ, so any suggestions or ideas are appreciated.

[osiris]

This is very good feedback. I now understand how to interact with
Cloudi. Thank you very much.