On 01/06/12 10:46 AM, "Chiradeep Vittal" <chiradeep.vit...@citrix.com> wrote:
>A third way is to split the agent api into 2 commands: CreateVm and >StartVm. CloudStack already has two separate agent api commands for creating(CreateCommand) and starting (StartCommand) VM operations. Not sure if any optimization influenced this but, unfortunately VM creation operations are spread across both CreateCommand and StartCommand implementations. So volumes for the VM are prepared as part of the CreateCommand and actual VM creation on Hypervisor, nic's for the VM, and ISO etc are created as part of the StartCommand. Also there is no state transition for VM from Created/Creating to Starting. If we have it, a pluggable service can register for state change and act on it.
