Files
nova-specs/specs/juno/implemented/hyper-v-soft-reboot.rst
Michael Still f0b8204072 Re-organize juno specs
As discussed at our nova meetings, reorganize the juno specs into
three directories:

 - proposed: things proposed which weren't approved
 - approved: things we approved but didn't implement
 - implemented: things approved and implemented

The first I suspect is the most controversial. I've done this
because I worry about the case where a future developer wants to
pick up something dropped by a previous developer, but has trouble
finding previous proposed specifications on the topic. Note that
the actual proposed specs for Juno are adding in a later commit.

Change-Id: Idcf55ca37a83d7098dcb7c2971240c4e8fd23dc8
2014-10-07 07:49:59 +11:00

1.9 KiB

Hyper-V soft reboot

https://blueprints.launchpad.net/nova/+spec/hyper-v-soft-reboot

This blueprint introduces soft reboot support in the Nova Hyper-V driver.

Problem description

Currently both "nova reboot" and "nova reboot --hard" cause a hard reset on Hyper-V instances. The driver needs to perform a soft reboot in the former case for consistency with the API specifications.

Proposed change

This feature can be implemented by invoking the "InitiateShutdown" method of the "Msvm_ShutdownComponent" class, waiting for the VM to reach a powered off status and powering it on again.

For consistency with the libvirt driver, if a soft reboot fails then a hard reboot is attempted.

Hyper-V provides an API to execute a soft shutdown but not a direct API to execute a soft reboot, hence the need to wait for the shutdown to be completed.

Alternatives

None

Data model impact

None

REST API impact

None

Security impact

None

Notifications impact

None

Other end user impact

None

Performance Impact

None

Other deployer impact

None

Developer impact

None

Implementation

Assignee(s)

Primary assignee:

alexpilotti

Work Items

  • Hyper-V Nova driver feature implementation
  • Unit tests

Dependencies

None

Testing

  • Unit tests
  • Additional Tempest tests can be evaluated

Documentation Impact

None

References