ah I just noticed Islam replied too ... well, the content is different :)
On 12/04/11 14:58, Farrel Lifson wrote:
I am in the process of spec'ing out a new ruote project. The idea is to
have a daemon-kit based ruote engine running which is then managed by a
workerless ruote-kit (with some extensions) admin console. Both the
engine and admin console will be running off the same FS storage.
Initially I was going to define all the participants and processes in
the engine however that is causing a bit of a snag as the admin console
would then not have any knowledge of the process definition so that the
process may be launched dynamically.
One strategy I thought was to define all participants in the engine but
define the processes in the admin console. Another was to save all the
process definitions as class constants and package them up as a gem.
Is there any best practise in the Ruote community about persistently
storing/loading process definitions?
You may want to take a look at the work we've been doing for MeeGo; it's not
pure Ruby and is more aimed at people who want a natively packaged solution.
It's called BOSS but it is very much an integration project around ruote. It's
at the point where 'apt-get install' works and it runs fine.
We run a single ruote engine/worker with amqp.
Then multiple (python only for now) participants are started and managed by
skynet. These can run as different users on different machines.
It handles the wrapping of the business logic in an amqp participant so writing
participants is trivial - and, I hope, updating them when the boilerplate
changes should be easy. It also supports dynamic registration of participants.
The boss-viewer is currently just packaging to run a ruote-kit instance and
allow us to monitor what's happening. Currently FS but Redis looks good.
We use daemontools to do the daemon management which has a few advantages
(especially when doing setuid).
We wanted to use native packaging so we have Debian 6 and Suse 11.3/4 rpms.
Installation docs are here:
http://wiki.meego.com/Release_Infrastructure/BOSS/Installation
We're missing a human/ruote interaction (bpm-rails?) solution.
Certainly it's useful to get a quick feel for an amqp based ruote install.
HTH
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
--
you received this message because you are subscribed to the "ruote users" group.
to post : send email to [email protected]
to unsubscribe : send email to [email protected]
more options : http://groups.google.com/group/openwferu-users?hl=en
