Revision 5b18ff3b doc/design-2.1.rst

b/doc/design-2.1.rst
81 81
not ready for 2.1) with the AddNode and SetNodeParams LUs (so that the relevant
82 82
files will be automatically shipped to new master candidates as they are set).
83 83

  
84
VNC Console Password
85
~~~~~~~~~~~~~~~~~~~~
86

  
87
Current State and shortcomings
88
++++++++++++++++++++++++++++++
89

  
90
Currently just the xen-hvm hypervisor supports setting a password to connect
91
the the instances' VNC console, and has one common password stored in a file.
92

  
93
This doesn't allow different passwords for different instances/groups of
94
instances, and makes it necessary to remember to copy the file around the
95
cluster when the password changes.
96

  
97
Proposed changes
98
++++++++++++++++
99

  
100
We'll change the VNC password file to a vnc_password_file hypervisor parameter.
101
This way it can have a cluster default, but also a different value for each
102
instance. The VNC enabled hypervisors (xen and kvm) will publish all the
103
password files in use through the cluster so that a redistribute-config will
104
ship them to all nodes (see the Redistribute Config proposed changes above).
105

  
106
The current VNC_PASSWORD_FILE constant will be removed, but its value will be
107
used as the default HV_VNC_PASSWORD_FILE value, thus retaining backwards
108
compatibility with 2.0.
109

  
110
The code to export the list of VNC password files from the hypervisors to
111
RedistributeConfig will be shared between the KVM and xen-hvm hypervisors.
112

  
84 113
External interface changes
85 114
--------------------------
86 115

  

Also available in: Unified diff