[netcf-devel] [Matahari] Updating oVirt Server to the latest Matahari 0.4.0 schema

Adam Stokes ajs at redhat.com
Tue Nov 16 19:28:09 UTC 2010


> > But there's more to it since, netcf can also configure interfaces
> > (not yet in Matahari schema, but it is planned). Currently,
> > ovirt-server provides network configuration which is downloaded by
> > the Node on boot and applied (via augeas). Question is should
> > ovirt-server switch fully to netcf (via Matahari)? I'm not sure how
> > does netcf handle unstable interface names, seems that it relies on
> > them being stable which is not the case in the stateless
> > environment like oVirt Node.

If the device is accessible via /files/sys/class/net/<interface> then netcf will capture anything made available through that file structure.

For example, the mac address can be pulled through reading:

/sys/class/net/<intername>/address

HTH
Adam


More information about the netcf-devel mailing list