alena
|
6f55c4dd7e
|
bug 8270: Synchronize on 1) ipAddress object when create/delete ipForwarding/portForwardingRule and vpn service 2) on networkId when assignTo/removeFrom/deleteLoadBalancer
status 8270: resolved fixed
|
2011-02-03 18:45:49 -08:00 |
will
|
c67d26cec4
|
bug 6969: First step of now displaying pending async jobs for listXXXCommands. There is a lot more cleanup and fixing to do but all commands acting against VirtualMachines now work.
|
2010-11-30 19:12:09 -08:00 |
Alex Huang
|
d38f7fd56d
|
Moved DAO to server
|
2010-11-22 07:40:41 -08:00 |
|
Alex Huang
|
1e44925564
|
api refactoring
|
2010-11-21 12:00:21 -08:00 |
|
will
|
05ab3bf673
|
bug 7063: AsyncJobResult should now return the correct success and error tags upon the completion of a async job. It should now follow either the format ... jobresult.success or jobresult.errorcode and jobresult.errortext
- Fixed a lot of other Async related packaging issues. It's not all done but will continue to refactor this later.
|
2010-11-05 17:30:03 -07:00 |
Kris McQueen
|
848ce60097
|
Merging master into 2.1.refactor, resolve the merge conflicts as best I can. New commands related to extracting template/iso/volume and related to instance groups were refactored to the new API framework.
|
2010-09-28 15:47:14 -07:00 |
|
Kris McQueen
|
4a73639d67
|
Fix up setting the response object correctly after dispatching the api method call. Begin working on the serialization of the responses which don't include the command name just yet, that's coming.
|
2010-09-17 14:56:55 -07:00 |
|
Kris McQueen
|
3f6a438d92
|
Refactoring the AsyncJobManager to queue jobs appropriately if there is a need to synchronize execution on an object, e.g. a router. API developers can now call command.synchronizeCommand(String, Long) to force the command to be synchronized on a particular object type [the string arg] with a particular id [the long arg]. When synchronizeCommand() is invoked, an exception maybe thrown by the framework (AsyncCommandQueued exception) to force the business logic to abort. The command will then be queued and invoked at the appropriate time. The synchronizeCommand() is re-entrant and will be a no-op if the command has already been queued and is now ready for execution.
|
2010-09-16 19:05:06 -07:00 |
|
Alex Huang
|
327924a9ad
|
More changes for refactoring
|
2010-09-15 18:00:54 -07:00 |
Manuel Amador (Rudd-O)
|
05c020e1f6
|
Source code committed
|
2010-08-11 09:13:29 -07:00 |