Update docs for serial console support

There are two changes here:

1. The serial_console config option group help text is
   updated to point out that hyper-v also supports serial
   console access. This is based on virt drivers that
   implement the 'get_serial_console' method.

2. The hypervisor feature matrix is updated to point out
   that the vmware driver does not support getting serial
   console output. This is based on virt drivers that
   implement the 'get_console_output' method.

Closes-Bug: #1632135

Change-Id: Ibf7f865e2b768e5ea3d7a7ec7cbf77bd8997c50f
This commit is contained in:
Matt Riedemann 2016-10-18 08:47:20 -04:00
parent 413da8528d
commit a5bd35f899
2 changed files with 3 additions and 3 deletions

View File

@ -781,7 +781,7 @@ driver-impl-libvirt-kvm-s390x=complete
driver-impl-libvirt-qemu-x86=complete
driver-impl-libvirt-lxc=missing
driver-impl-libvirt-xen=complete
driver-impl-vmware=complete
driver-impl-vmware=missing
driver-impl-hyperv=complete
driver-impl-ironic=missing
driver-impl-libvirt-vz-vm=missing

View File

@ -27,8 +27,8 @@ serial_opt_group = cfg.OptGroup("serial_console",
title="The serial console feature",
help="""
The serial console feature allows you to connect to a guest in case a
graphical console like VNC, RDP or SPICE is not available. This is
supported for the libvirt and Ironic driver.""")
graphical console like VNC, RDP or SPICE is not available. This is only
currently supported for the libvirt, Ironic and hyper-v drivers.""")
enabled_opt = cfg.BoolOpt('enabled',
default=False,