Project

General

Profile

Actions

Feature #1711

closed

Need an option to choose whether a Libvirt-based VM should have a VNC password set or not

Added by Andreas Ntaflos over 11 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Category:
Compute resources
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

We use Libvirt-based compute resources and are all in all very happy with the way Foreman supports provisioning of virtual machines (still needing to work around issue #1639 though). And the web-based VNC console is just awesome.

But we dearly need an option at provisioning time to enable or disable the VNC password. Firstly, the password is nowhere noted, except in the VM's XML definition (virsh edit foo). It is not very practical to get it out of there. Secondly, to remove the password the VM needs to be shut down, which also very impractical and sometimes not even possible. All of this interferes pretty heavily with the idea of no-hands provisioning of machines. And since Foreman is not yet able to fully replace virt-manager and all its features (and I don't know that it ever should), I don't think it is a good idea to impede virt-manager's function by effectively disabling the VNC console.

Kinda related to this is issue #1644 which is the reason we can't even really use the web-based console. The default keymap that gets set is entirely wrong.


Related issues 2 (0 open2 closed)

Related to Foreman - Feature #1740: VNC password should be optional on hypervisorsDuplicate07/10/2012Actions
Has duplicate Foreman - Feature #2742: VNC/Spice password creation should be optionalDuplicateGreg Sutcliffe07/03/2013Actions
Actions #1

Updated by Dominic Cleal over 10 years ago

  • Has duplicate Feature #2742: VNC/Spice password creation should be optional added
Actions #2

Updated by Dominic Cleal over 10 years ago

  • Assignee set to Greg Sutcliffe
  • Target version set to 1.3.0
  • Description updated (diff)
  • Category set to Compute resources
  • Status changed from New to Ready For Testing
Actions #3

Updated by Greg Sutcliffe over 10 years ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF