[kepler-dev] question about kepler
dejw at man.poznan.pl
Thu Jul 17 22:49:05 PDT 2008
thanks for replay, we are now in the phase of requirements gathering and
later we will work on desired architecture. I can't say at the moment if
we are going to use web services at all. We have now quite nice frame
work with all kind of services (http://vinetoolkit.org/) and we will
think add another service to it.
Our target is possibility to run quite complicated kepler workflows on
different grids below and use different data storage management systems
to store all generated data, we need also very detailed info about every
step of execution of it.
If we have such service (we use spring for our services) then it is no
problem to make a web service from it later. So it would be actually
straight way to do it :) At the moment we have to get known the kepler
much better and gain some experience in it. So I think we will be in
I saw the code of your replacement classes for some actors in python.
Would it be possible for you to write shortly about them in few
sentences? What every of it changes vs the original actors? I would be
grateful. (it's always good to hear such thing from the author of code ;)
Tristan King wrote:
> Hi Dawid,
> Hydrant was developed with python purely for prototyping reasons. It
> would be maybe 2 weeks work to translate all the python backend code
> into java, and I would be happy to collaborate with you to do this.
> The only problem would be the interface. You would have to write a new
> one using your java web-framework of choice.
> However, I don't plan to build any more on top of Hydrant in it's
> current state. What I want to do is separate the backend execution out
> from Hydrant and have it run as it's own service. This service could
> then be accessed using some form of web services (i.e. SOAP) by
> Hydrant or any other front-end portal. I hope to get the community
> involved in building something like this, as there seems to be a lot
> of people interested in it, and there has already been a lot of work
> done in separate instances towards such technology, it would be great
> if we can work together to build something that everyone can use
> rather then a whole number of different solutions. Unfortunately there
> has not been a lot of response to my initial attempts to get such a
> project going, and i've since been distracted working on the other
> various things i want to see put into ptolemy/kepler.
> I will try and get back onto this next week and perhaps get some
> requirements and such up on the wiki.
> 2008/7/17 dejw <dejw at man.poznan.pl <mailto:dejw at man.poznan.pl>>:
> Hi Jianwu again,
> I want to ask more about this below:
>>> 3. Actor repository - I understand that it is possible to have
>>> one common actor repository for some organization? Kepler uses
>>> LDAP for it? Are there some access rights for actors or
>>> something like this? Is it possible to grant some roles to users
>>> when LDAP authentication is used? Is it possible to require
>>> login while starting Kepler?
>> You can find the current actor repository at
>> http://library.kepler-project.org/kepler/. Yet it is not widely
>> used currently. We are trying implement more comprehensive actor
>> repository mechanism.
> 1. So you use LDAP server to store actors? or something else?
> 2. How about access rights and user roles as regard access to
> actors in such repository?
> 3. I understand I can deploy such repository inside some
> organization and configure kepler to use it?
> 4. Can I set kepler to require login before start editor? to
> recognize user somehow?
> Kepler-users mailing list
> Kepler-users at ecoinformatics.org
> <mailto:Kepler-users at ecoinformatics.org>
> Tristan King
> Research Officer,
> eResearch Centre
> James Cook University, Townsville Qld 4811
> Phone: +61747816902
> E-mail: tristan.king at jcu.edu.au <mailto:tristan.king at jcu.edu.au> www:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Kepler-dev