[Ovirt-devel] [PATCH node] generalized configuration persistence for oVirt Node

Perry N. Myers pmyers at redhat.com
Sun Sep 21 06:10:39 UTC 2008

Perry N. Myers wrote:
> Alan Pevec wrote:
>> If local OVIRT partition is available, persist selected configuration 
>> files,
>> for now: Kerberos config, libvirt keytab and SSH host key.
>> To initialize OVIRT partition, boot oVirt Node with ovirt_init=scsi 
>> parameter,
>> this will format the first disk and create the partition.
>> For more details see http://ovirt.org/page/Local_Disk_Usage
> Tested this and seems to work so ACK.  Fixed one minor typo below...

Noticed something that should be mentioned for developers...

If you create appliances for testing often, each time you create a new 
appliance you need to wipe out the local disk installations of oVirt that 
you have.  For the fake nodes this means just deleting and recreating the 
node.img files in /var/lib/libvirt/images on the host.  For physical nodes 
you need to delete the OVIRT partition on the box's hard disk.

The reason for this is that the Node will cache the keytab and if you 
switch out to a new appliance that keytab will no longer be valid.

We probably need a way to tell the node to 'reinitialize' the stored 
config.  Maybe a kernel boot opt called ovirt_clean or something that 
wipes out the OVIRT partition.  If ovirt_clean and ovirt_init=[scsi|usb] 
are passed at the same time the partition would be wiped and then 
recreated with the newest information (new keytab, etc...)

That way if in real environments you have cause to wipe out your kerberos 
configuration for some reason you can re-initialize your nodes easily.


More information about the ovirt-devel mailing list