A scheduling and resource management system for using a farm of servers running VMware virtualisation products as a computing cloud. Currently, only the VMware VIM 1.4 proxy is considered 'working'. Out of active development for the moment.
Be the first to post a text review of VirtualCloud. Rate and review a project by clicking thumbs up or thumbs down in the right column.
New features and capabilities: * Logging to file can be set up easily in PowerShell, with [Vim]::InitialiseLog([string]filename, [bool]append). Bug fixes: * #1826746 'Updates are not being applied properly' is fixed. * #1826693 'Reconnection mechanism is still broken' is fixed. * #1826946 'Tasks that expire during disconnection are not relinked' is believed fixed; such tasks will be treated as having failed. * Miscellaneous reliability issues dealt with. Known Issues: * #1827408 'Operating against VIM on localhost crashes webservice'. For best results, do not use this assembly on the machine hosting VirtualCenter. * Multiple datastores with the same name ('local') will not be updated properly. This is unfixable. * Each Vim instance in an appdomain will have its own message pump. Multiple message pumps talking to the same server can potentially cause problems.
New features and capabilities: * Logging to file can be set up easily in PowerShell, with [Vim]::InitialiseLog([string]filename, [bool]append). Bug fixes: * #1826746 'Updates are not being applied properly' is fixed. * #1826693 'Reconnection mechanism is still broken' is fixed. * #1826946 'Tasks that expire during disconnection are not relinked' is believed fixed; such tasks will be treated as having failed. * Miscellaneous reliability issues dealt with. Known Issues: * #1827408 'Operating against VIM on localhost crashes webservice'. For best results, do not use this assembly on the machine hosting VirtualCenter. * Multiple datastores with the same name ('local') will not be updated properly. This is unfixable. * Each Vim instance in an appdomain will have its own message pump. Multiple message pumps talking to the same server can potentially cause problems.
New features and capabilities: * Logging to file can be set up easily in PowerShell, with [Vim]::InitialiseLog([string]filename, [bool]append). Bug fixes: * #1826746 'Updates are not being applied properly' is fixed. * #1826693 'Reconnection mechanism is still broken' is fixed. * #1826946 'Tasks that expire during disconnection are not relinked' is believed fixed; such tasks will be treated as having failed. * Miscellaneous reliability issues dealt with. Known Issues: * #1827408 'Operating against VIM on localhost crashes webservice'. For best results, do not use this assembly on the machine hosting VirtualCenter. * Multiple datastores with the same name ('local') will not be updated properly. This is unfixable. * Each Vim instance in an appdomain will have its own message pump. Multiple message pumps talking to the same server can potentially cause problems.
New features and capabilities since the 0.112 beta: * VM network adapter info added. * VMs can now be cloned, renamed, and moved between VM groups. * FarmGroups are supported properly. * The Vim object knows how to re-establish a connection to the webservice in the event that connectivity is lost. Bug fixes: * Fixed an issue where a NullReferenceException would be generated if a VM had no devices of a certain type (Network adapter, optical drive, hard disk). * Disconnection is no longer fatal; the API can re-establish a connection without invalidating objects. * Exceptions in the message pump are now less likely to stop a handle being updated. * Various issues with handle-object linking have been ironed out. * The internals of the update mechanism are marginally less horrible.
New features and capabilities since the 0.112 beta: * VM network adapter info added. * VMs can now be cloned, renamed, and moved between VM groups. * FarmGroups are supported properly. * The Vim object knows how to re-establish a connection to the webservice in the event that connectivity is lost. Bug fixes: * Fixed an issue where a NullReferenceException would be generated if a VM had no devices of a certain type (Network adapter, optical drive, hard disk). * Disconnection is no longer fatal; the API can re-establish a connection without invalidating objects. * Exceptions in the message pump are now less likely to stop a handle being updated. * Various issues with handle-object linking have been ironed out. * The internals of the update mechanism are marginally less horrible.
New features and capabilities since the 0.112 beta: * VM network adapter info added. * VMs can now be cloned, renamed, and moved between VM groups. * FarmGroups are supported properly. * The Vim object knows how to re-establish a connection to the webservice in the event that connectivity is lost. Bug fixes: * Fixed an issue where a NullReferenceException would be generated if a VM had no devices of a certain type (Network adapter, optical drive, hard disk). * Disconnection is no longer fatal; the API can re-establish a connection without invalidating objects. * Exceptions in the message pump are now less likely to stop a handle being updated. * Various issues with handle-object linking have been ironed out. * The internals of the update mechanism are marginally less horrible.
Fixes an issue where VM state is reported as 'On' until the server reports a change. POSSIBLY fixes remaining issues with custom properties.
Fixes an issue where VM state is reported as 'On' until the server reports a change. POSSIBLY fixes remaining issues with custom properties.
Be the first person to add a text review.
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?