[workspace-dev] Plugin development/Integration with OpenNebula

[Kate Keahey]

William,

I am delighted to hear that you want to work on integration with
openNebula, it seems like a very project.

I am not sure what you are asking though: do you want us to add an ANY
parameter or do you want to experiment with optional parameters
(possibly including ANY) yourself? If the latter, the answer is go right 
on ahead, the project is open source :-) .

Adding ANY parameter, as I am sure you realize, is a very controversial
thing to do. We do have plans to accommodate diverse lease terms but
more a-la WS-Agreement where there is some structure to it. Before we do 
that though, we plan to expose more extensibility plugins on the 
backend. All this won't happen immediately of course and while you can 
look for the new plugins in the next release sometime in August, the new 
lease structure will probably happen after your summer project has 
finished.

William Voorsluys wrote:
> Hello,
> 
> We (as part of Google Summer of Code) are working in the integration
> between the Workspace Service and OpenNebula (ONE).
> The next step will be adding a plugin to the VWS that will access
> ONE's through its XMLRPC API.
> 
> So, I'm following the suggestion from the WS website ("To develop new
> plugins, contact the workspace-dev mailing list").
> 
> We will need to add some extra information in the XML metadata (mainly
> in the request metadata) to include support for market-based resource
> allocation and also advanced reservations. Our main enquiry right now
> is whether we need to modify the XML schema in order to support
> addition of new parameters. We've noticed that some "Optional
> Parameters" are supported but my understanding so far is the we still
> need to patch/extend the schema in order to add support for additional
> parameters. Is there any way of including ANY additional parameter
> that would be simply passed to be handled by a certain plugin?
> 
> Cheers,
> 
> William.

-- 

Kate Keahey,
Mathematics & CS Division, Argonne National Laboratory
Computation Institute, University of Chicago