On Wed, 2011-03-16 at 20:23 +0100, Michal Fojtik wrote:
Actually we was thinking about using Sinatra app which talks to Condor and translate queries for Deltacloud API to handle this IP managment.
To make sure I get this right: the flow then is
* client -> deltacloud-core server -> new sinatra app -> condor
Which raises the same question I asked yesterday about vSphere: why does the interface marked with (*) need to be REST ? Wouldn't it make more sense to collapse all that into the deltacloud-falcon driver so that the interface (*) is just normal in-process calls within the driver ?
I am all for abstracting the deltacloud driver/condor interaction a little bit, but that can also be done by putting that code into a separate gem or similar.
David