Bug #3774
EC2 driver - poweroff in opennebula terminates the vm in the amazon cloud
| Status: | Closed | Start date: | 04/24/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Tino Vázquez | % Done: | 100% | |
| Category: | Drivers - VM | |||
| Target version: | Release 4.14 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.10 |
Description
Hello,
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.
Best regards,
Tom
Associated revisions
Bug #3774: Change poweroff behaviour for hybrids
History
#1
Updated by Ruben S. Montero about 6 years ago
- Category changed from 20 to Drivers - VM
- Status changed from Pending to New
- Target version set to Release 4.14
Totally, it should be the same behavior as for local resources.
#2
Updated by Ruben S. Montero almost 6 years ago
- Assignee set to Tino Vázquez
#3
Updated by OpenNebula Systems Support Team almost 6 years ago
Fixed for EC2 and Azure. Not closing until SoftLayer checked properly
#4
Updated by Ruben S. Montero almost 6 years ago
There is no need to call to OpenNebula, the core sends a VMM_DRIVER_ACTION document that includes the the VM information as an XML document, with the state included.
#5
Updated by Tino Vázquez almost 6 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
- Resolution set to fixed
SoftLayer checked.
The vmm_exec.rb driver modification will likely impact other drivers, opening a ticket for 5.0 to look into it:
http://dev.opennebula.org/issues/3940