Re: frontend API for block reservations (VCL-78)

Would it make sense to break this into two functions? Have this function XMLRPCblockAllocation with only two parameters blockrequestid and blockTimeid. The second function would be to create the Block Allocation - XMLRPCcreateBlockAllocation. Aaron --On February 4, 2009 4:39:30 PM -0500 Jo

Re: VCL developer call Thurs (2/5) from 1-3 PM

Kevan, Matt, Thanks for the feedback. Your comments do highlight the potential problems if such a call is not handled properly. I think we'll try it this time to see what happens it may or may not work out, but we'll see. I'll step up and volunteer to record this call and then post it back

Re: frontend API for block reservations (VCL-78)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 For the frontend, one function works as well as two would. However, I can see how it would simplify code on the backend to just pass a blockTimes id since it wouldn't have to determine all of the other information (blockTimes entries include blockr

Re: frontend API for block reservations (VCL-78)

Another suggestion. Can you look at staggering the reload start times based on the load of the management node? A problem that currently exist on the backend method is that the block allocation process inserts multiple reloads at a time, which can quickly overload a management node. For exam

Re: frontend API for block reservations (VCL-78)

That would work. But now you loose the ability to create new block allocations through the API. Previously it created one if there was not an existing entry. So I guess we need to ask is this a desired/separate feature, the ability create block reservations through the API. --On February

Re: frontend API for block reservations (VCL-78)

never mind this response I overlooked the part about keeping the first function which provides the ability to create a block reservation through the API. Aaron --On February 5, 2009 10:33:40 AM -0500 Aaron Peeler wrote: That would work. But now you loose the ability to create new block

Re: frontend API for block reservations (VCL-78)

This is just semantics for now but it might be better to think of the number of things being allocated as requests rather than machines. This will allow for block requests of cluster images. Regarding the return code... it might be useful to return the number of requests that haven't been suc

Re: VCL developer call Thurs (2/5) from 1-3 PM

All, The notes from the conf call are posted on the wiki. Please note - these minutes are not approved and likely need corrections. For the members in attendance - review the notes and make any corrections as needed. Th