[Ovirt-devel] [PATCH ovirt-node] Adds automatic non-interactive configuration for the standalone node.

Daniel P. Berrange berrange at redhat.com
Mon Nov 17 12:14:21 UTC 2008

On Mon, Nov 17, 2008 at 01:08:50PM +0100, Alan Pevec wrote:
> From: Darryl L. Pierce <dpierce at redhat.com>
> NOTE: rebased to apply after:
>     Moved network configuration work files to a temporary directory.
>     Adds a "Save" option to save the configuration.
> If ovirt-config-network is called as follows:
> ovirt-config-network AUTO  [NIC] [IP NETMASK GATEWAY BROADCAST]
> where NIC is the management interface to be configured.
> If the IP details are provided then they are used to configure the device.
> Otherwise DHCP will be used.
> The kernel arguments are:
>  * OVIRT_MGMT_IFACE:   the management network interface name

This should really expect the MAC address rather than the interface
name. An admin deploying a piece of hardware has no clue what name
each NIC will be given by Linux. They do, however, know exactly what
MAC address is associated with each NIC and which they have plugged 
into which LAN. So we should either use MAC exclusively or allow 
either a MAC or name here.

>  * OVIRT_IP_ADDRESS:   the IP address
>  * OVIRT_IP_NETMASK:   the netmask
>  * OVIRT_IP_GATEWAY:   the network gateway
>  * OVIRT_IP_BROADCAST: the network broadcast address

This latter BROADCAST address can be calculated from the ADDRESS+NETMASK.

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