[Ovirt-devel] [PATCH]: Fix ovirt-identify-node to work at boot time

[Daniel P. Berrange]

On Wed, Jun 04, 2008 at 04:19:30PM -0400, Darryl Pierce wrote:
> Perry N. Myers wrote:
> >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. Bad design...
> >
> >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
> >
> >Thoughts?
> 
> In my last email, WRT the indentify process, I was under the impression 
> we wanted to have the hardware information submitted when the node 
> identified itself. Is that incorrect in my understanding?

Ideally the keytab fetching will be a onetime process, persisted on the
machine once fetched. Hardware info will want to be re-submitted on every
boot because admin may have altered the hardware across reboots. So these
should be considered separate submission steps.

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 :|