EC2 driver - poweroff in opennebula terminates the vm in the amazon cloud
|Assignee:||Tino Vázquez||% Done:|
|Category:||Drivers - VM|
|Target version:||Release 4.14|
|Affected Versions:||OpenNebula 4.10|
I created an Opennebula Cluster with Amazon as public cloud backend. I was able to create and stop vms on the amazon cloud via Opennebula. That works fine for me.
But I got problems when I used the poweroff function for a vm located in the amazon cloud. The vm was terminated in the amazon cloud instead of just stopping it. In addition to that Opennebula was still "thinking" that the vm was only powered off and kept the vm in the vm list. A resume command failed of course. I had to delete the vm in Opennebula manually.
I work with a hybrid cloud and my user shouldn't care where the vm is running. So I forced them to use stop instead of poweroff. But using stop on an Opennebula host is not what I really was looking for. But I have no other choice for now.
Therefore I think the poweroff command should send a stop command to amazon instead of a terminate command.
#5 Updated by Tino Vázquez about 5 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
- Resolution set to fixed
The vmm_exec.rb driver modification will likely impact other drivers, opening a ticket for 5.0 to look into it: