a) when cloud is out of public ip adresses we do not see clear message of this in cloudmesh
b) when secgroups are duplicated it does not allow us to upload a new secgroup with the same name (e.g. secgroup was already there)
we need a better way to fix this
c) when we delete the db the counter starts at one. however we need to have some way to find out whats the maximum counter in the names of the vm and reset it to that value +1?
d) when we delete the vms with vm delete gvonlasz-, we had to execute that comamnd twice before the vms got removed. The vms were actually in active state, but shoudl have shown up as termnated. however the termination was so fast that the db sync to cloudmesh could not find it, so we need to possibly introduce a new state “NOTFOUND” that updates all
gvonlasz- vms that are no longer found in the cloud and add this state to the db.
than when we delete it explicitly it will be removed.
e) we need a “manual” that deals with these issues
a) when cloud is out of public ip adresses we do not see clear message of this in cloudmesh b) when secgroups are duplicated it does not allow us to upload a new secgroup with the same name (e.g. secgroup was already there) we need a better way to fix this c) when we delete the db the counter starts at one. however we need to have some way to find out whats the maximum counter in the names of the vm and reset it to that value +1? d) when we delete the vms with vm delete gvonlasz-, we had to execute that comamnd twice before the vms got removed. The vms were actually in active state, but shoudl have shown up as termnated. however the termination was so fast that the db sync to cloudmesh could not find it, so we need to possibly introduce a new state “NOTFOUND” that updates all gvonlasz- vms that are no longer found in the cloud and add this state to the db. than when we delete it explicitly it will be removed.
e) we need a “manual” that deals with these issues