[Ovirt-devel] [PATCH]: Fix ovirt-identify-node to work at boot time
Daniel P. Berrange
berrange at redhat.com
Wed Jun 4 20:19:21 UTC 2008
On Wed, Jun 04, 2008 at 04:16:17PM -0400, Perry N. Myers wrote:
> Daniel P. Berrange wrote:
> >On Wed, Jun 04, 2008 at 09:47:08PM +0200, Chris Lalancette wrote:
> >>Problem: ovirt-identify-node was calling libvirt functions. However,
> >>libvirtd
> >>isn't running at this point in boot, so calling these functions fails.
> >
> >Surely libvirtd should be set to run before any oVirt services on the
> >host start. There's a clear line of dependancy from oVirt to libvirt
> >so the startup should reflect that.
>
> Catch-22 problem.... if you have suggestions let me know.
>
> libvirt requires a keytab to work properly. The code that is executing is
> code to GET the keytab. Therefore this must execute prior to libvirt.
Ok that makes sense now.
> Bad design...
Indeed :-)
> We're probably going to change the startup sequence to be like this
> instead (but this will have to happen after summit)
>
> 1. ovirt init script starts so keytab could get retrieved
> 2. libvirt start
> 3. another ovirt initscript starts to give hardware info to ovirt server
That plan gets my vote. The first step will go away if the host has a
persistent storage capability for the keys (tpm/flash/usbkey etc), so
having it independant of step 3 is a good idea.
Regards,
Dan.
--
|: 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
mailing list