Feature #3654
Implement extra VM state transitions
Status: | Closed | Start date: | 03/06/2015 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Core & System | |||
Target version: | Release 4.14 | |||
Resolution: | fixed | Pull request: |
Description
- suspended -> stopped
- poweroff -> undeployed
- migrate VMs in poweroff/suspend
- deploy VMs from undeployed/stopped
Related issues
Associated revisions
Feature #3654: Add new transtions to recover failed VM boot
Feature #3654: Transtions to recover failed VM boot in oca & sunstone
Feature #3654: Fix after merge
Feature #3654: Transitions to recover a failed prolog migrate
(cherry picked from commit a14a143b6a05c78f29099aa8958ac5cbb5511e83)
feature #3654: Recover PROLOG_MIGRATE_FAILURE with retries and recover (boot) action
feature #3654 Add comment on onevm boot action, and allow to boot from PROLOG_MIGRATE_FAILURE
feature #3654: Recover through retry
Feature #3654: Transitions to recover a failed prolog
(cherry picked from commit 00aec5067ce3961e5e3a2e42ed69314d4735e26e)
feature #3654: Merge back recover actions for new failure states
Feature #3654: Transitions to recover a failed epilog
(cherry picked from commit 75a275d0115390dd2cc2dab4dbb8d83bd3c3d32d)
feature #3654: Recover EPILOG states with retry
feature #3654: Add new states to deploy a vm to onevm command help
Feature #3654: Add boot_failure to vcenter driver
(cherry picked from commit 03b93f0b02be461b68ff7fd38126f938ffcf97c1)
Feature #3654: Add new failure states to oneflow
(cherry picked from commit bd056779949df7929f7d5549d65e1bc9a5ff742c)
feature #3654: Add retry option to the recover API calls and onevm command
Feature #3654: Transitions to migrate VMs in poweroff
(cherry picked from commit 783775471eae90759b9ca74431415551b2b83495)
(cherry picked from commit 07015c349ffe6ca2d6d0afa08c2f4091f7b23513)
feature #3654: Recover lcm_state_to_str interface
(cherry picked from commit c328fc076d23c26d436c8280b4822b778691a893)
feature #3654: Retry PROLOG_MIGRATE_POWEROFF
(cherry picked from commit b36fe966801fe65a35f62eea86fb6fcaae13ba93)
feature #3654: Add reason to ERROR after a failed resume from POWEROFF or SUSPEND
feature #3654: Add action to history records on resume failure
Feature #3654: Transitions to migrate suspended VMs
(cherry picked from commit ee7bccf48a6852117091ae3051d219cd93addd3d)
feature #3654: Retry failures on PROLOG_MIGRATE_SUSPEND
feature #3654: Adjust migrate history actions and reasons, fix transition
Feature #3654: Transition from suspended to stopped
(cherry picked from commit 9f56a2445748d7b07592b551f42ef06d1b81dcde)
(cherry picked from commit 0d157414579ef0e79b9613f5f1ce17d91a868874)
Feature #3654: Transition from poweroff to undeployed
(cherry picked from commit b69a0e649f24df69eb7e3ff394b5db889fb45277)
(cherry picked from commit df6d271a9b6e40c69c45fff9e4bf4c11c7590f64)
feature #3654: Add missing change after merges
Feature #3654: Allow graceful shutdown from suspended and poweroff
(cherry picked from commit 004c2cb1411c4bf99fe16db5cfa312d28e603807)
Feature #3654: Refactor VM state change log
(cherry picked from commit 329f0ef0fd099c46b2c5b30c61093c421d961e2b)
feature #3654: remove restart states added after merge
feature #3654: Remove missing "New VM state is..." messages
Feature #3654: Refactor LCM::cancel
(cherry picked from commit 7e3869be0aac24e267cc796f79afc472d6098099)
Feature #3654: Update vm recover action in sunstone
Feature #3654: Show the complete lcm state name in sunstone
Feature #3654: Allow to run a poweroff/undeploy again from shutdown_poweroff/undeploy
Feature #3654: Merge the cancel and shutdown states
Feature #3654: Allow to run a shutdown again from shutdown state
Feature #3654: Merge Dispatch Manager reset with reboot
Feature #3654: Refactor LCM to init pointers to managers only once
feature #3654: Retry PROLOGs, EPILOGs, SHUTDOWNs and BOOTs through recover. Remove restart action from oned, removed shutdown retries through shutdown
feature #3214: Redo saveas check.
Revert "Feature #3654: Allow to run a shutdown again from shutdown state". This reverts 36afa9c864
Revert "Feature #3654: Allow to run a poweroff/undeploy again from shutdown_poweroff/undeploy". This reverts 9be8b151bcd
Feature #3654: Refactor DM to init pointers to managers only once
feature #3654: Fix wrong name in state check
Feature #3654: Remove boot action from oca, cli & sunstone
Feature #3654: Remove boot action from oneflow
feature #3654: Add BOOT_UNDEPLOY_FAILURE and BOOT_STOPPED_FAILURE. Get rid of map<string, string> empty declarations.
feature #3654: Update states diagram
Feature #3654: LCM updates the VM life cycle with the poll info
Feature #3654: Manage failure states in flow recover action
feature #3654: PROLOG_RESUME_FAILURE & PROLOG_UNDEPLOY_FAILURE states
Feature #3654: Fix error state management in oneflow
History
#1 Updated by Carlos Martín over 6 years ago
- Related to Backlog #2042: Support graceful VM deletion from UNDEPLOY added
#2 Updated by Carlos Martín over 6 years ago
- Related to Backlog #1769: Decouple deploy and poweron actions added
#3 Updated by Carlos Martín over 6 years ago
- Related to Feature #2095: Allow Deploy for VM in UNDEPLOYED state added
#4 Updated by EOLE Team over 6 years ago
+1
With shared system datastore, this will permit to boot VM in POWEROFF
assigned to a host in ERROR
.
#5 Updated by Carlos Martín over 6 years ago
- Related to Feature #1610: Include information about available operations in error messages added
#6 Updated by Carlos Martín over 6 years ago
- Related to Backlog #2985: Allow administrators to force the VM status added
#7 Updated by Carlos Martín over 6 years ago
TODO: update vcenter_driver.rb to take care of new states, if needed.
#8 Updated by Carlos Martín over 6 years ago
- Related to Bug #2488: A failed resume action will destroy and recreate the VM on the next resume added
#9 Updated by Carlos Martín over 6 years ago
- Related to Bug #3235: Delete --recreate coming from Stop state should not attempt a resume added
#10 Updated by Carlos Martín about 6 years ago
- Related to Bug #3775: deleted VMs are canceled asynchronously, host/ip resources already shown as freed before releasing them added
#11 Updated by Ruben S. Montero about 6 years ago
- Status changed from New to Closed
- Resolution set to fixed