Files
nova-specs/specs/juno/implemented/hyper-v-console-log.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

2.2 KiB

Hyper-V serial console log

https://blueprints.launchpad.net/nova/+spec/hyper-v-console-log

This blueprint introduces serial console log in the Nova Hyper-V driver.

Problem description

The Hyper-V driver is currently not providing a serial console log unlike other compute drivers (e.g. libvirt). This feature is particularly useful for the troubleshooting of both Linux and Windows instances.

Proposed change

Console log support in the Hyper-V nova driver will be obtained by implementing the "get_console_output" method inherited from nova.virt.driver.ComputeDriver.

Hyper-V supports virtual serial ports in the guests, which can be redirected to a dedicated named pipe on the host.

The driver will setup and connect the pipe upon starting or resuming a VM and closing it when stopping, suspending or live migrating.

Data read from the pipe will be written in a file placed in the instance directory, capped to a maximum size.

In case of live migration the console file must be moved to the destination server.

A call to "get_console_output" for a given instance will return the content of the file.

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:

petrutlucian94

Other contributors:

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