Ovirt devel - Aug 2008 - Default configuration for a new managed node...

In working on the managed node configuration generator, I came across a
simple case that's going to come up every time.

Basically, when a new managed node comes up, it's not going to have a
configuration in the database. As things stand now, in that case the node
would boot and have no active interfaces on the virtual network. Until/unless
we introduce the ability to configure in real-time the node's interfaces,
we'll always have to configure the node and then restart it to bring those
up.

So I'm considering having a default interface configuration that gets
applied
whenever a node comes up. It would be defined in a YML file,
config/default_nic.yml, and would be applied. 

Either that, or we could have some configurable actions for undefined (in the
DB) nics such as to turn on DHCP and set it to use ovirtbr0 as a bridge. 

Thoughts?

-- 
Darryl L. Pierce, Sr. Software Engineer
Red Hat, Inc. - http://www.redhat.com/
oVirt - Virtual Machine Management - http://www.ovirt.org/
"What do you care what other people think, Mr. Feynman?"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
<http://listman.redhat.com/archives/ovirt-devel/attachments/20080827/9340bd7b/attachment.sig>

Darryl L. Pierce wrote:
> In working on the managed node configuration generator, I came across a
> simple case that's going to come up every time.
> 
> Basically, when a new managed node comes up, it's not going to have a
> configuration in the database. As things stand now, in that case the node
> would boot and have no active interfaces on the virtual network.
Until/unless
> we introduce the ability to configure in real-time the node's
interfaces,
> we'll always have to configure the node and then restart it to bring
those
> up.
> 
> So I'm considering having a default interface configuration that gets
applied
> whenever a node comes up. It would be defined in a YML file,
> config/default_nic.yml, and would be applied. 
> 
> Either that, or we could have some configurable actions for undefined (in
the
> DB) nics such as to turn on DHCP and set it to use ovirtbr0 as a bridge. 
Hm, Alan is the expert here, but I thought we already did that.  There was
something like "defaultdb" or something that was set up for this, and
it already
pulled the default configuration down.  Maybe I'm misunderstanding what you
mean, though.

Chris Lalancette