[Ovirt-devel] oVirt console (again!)
Daniel P. Berrange
berrange at redhat.com
Fri Nov 7 09:33:02 UTC 2008
On Thu, Nov 06, 2008 at 10:02:37PM +0100, Gerd Hoffmann wrote:
> > (3) Running virt-viewer or viagre as separate, standalone programs.
> > This works, but requires the user to type in some very long
> > and complicated command line by hand, and there are unresolved
> > authentication problems.
> Authentication problems? Which authentication problems?
> /me uses virt-manager for the guest consoles. Authenticates just fine
> via kerberos, using the same ticket I need for the ovirt wui anyway.
Yes & no. We've actually got two authentication problems. In the
virt-viewer case, you've got the libvirt auth, but in every case
you've got VNC auth.
> Not the most elegant solution as I'll have to add each node manually to
> virt-manager. Not a big issue either with my two-node-test-setup ;)
> For a larger-scale setup you'll probably want build some dedicated app
> (say ovirt-viewer) which gets a list of vms from ovirt, the node they
> are running on and then goes talk to libvirt on the nodes for the vnc
> display. The kerberos ticket should open all doors needed.
Yes, that's the new plan. We still have to solve the VNC auth problem
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
More information about the ovirt-devel