I took a little review of the vm command and i think its not properly implemented in some aspects
a) certainly when we want to boot a vm we take defaults so that seems ok
b) however when we ask for the status or add things to the vm we have to
1) cycle through the vms that we have as parameters
2) identify the cloud on which the vm is
3) use the provider for that cloud to do things while use int the appropriate methods
4) make sure the status update does the following
gather first all clouds,
issue a status request for either the specific vm or all of the vms
store the result in the db
retrieve the status from the db
So we need to clarify all of the vm command if this is the case and fix it
At the same time we can implement than wait functions and timeouts, so this may be a bigger task and we MUST make this our top priority.
In parallel tests coudl be developed and modified once new features and fixes have been done.
P:6
I took a little review of the vm command and i think its not properly implemented in some aspects
a) certainly when we want to boot a vm we take defaults so that seems ok
b) however when we ask for the status or add things to the vm we have to
So we need to clarify all of the vm command if this is the case and fix it
At the same time we can implement than wait functions and timeouts, so this may be a bigger task and we MUST make this our top priority.
In parallel tests coudl be developed and modified once new features and fixes have been done.
Gregor