Redesigned Network Configuration
Configuring network information via oVirt
The networking configuration interface can be broken down into a few major components.
'Networks' are general settings for groupings of network devices describing various attributes such as how they are assigned IP addresses (statically, DHCP) and other information such as name and vlan number. They can be accessed and edited via the dashboard, by anyone who has modify permissions on the default pool in the system.
A user can also add/edit/remove ip addresses associated with a network, these containing information such as broadcast, netmask, prefix, etc as needed. Subclasses to Network include PhysicalNetwork and Vlan, which may only be assigned to Nics and Bondings respecively.
'Nics' and 'Bondings' belong to hosts and must be associated with one or more networks. They can be accessed by any user who has modify permissions on the corresponding host, by selecting that host on the hosts tabs of it's parent hardware pool and clicking on 'Edit Network Information' in the details pane.
Bondings can be created / updated / deleted as needed by a user with sufficient permissions, where as nics may be only edited via the wui, as instances are created and destroyed by backend components when they are physically added / removed from machines. A Bonding may be associated with one or more nics, where as a nic may only be associated with one bonding. Finally both may be associated with one or more ip addresses, and must have at least one if assigned to static network.
Finally, while all of the interface is wired up, most of the managed-node-conf and host-browser backend configuring the database on recieving node network information, and performing the reverse, configuring nodes on network changes has not been sufficiently updates to fully use the new network model.
Views
Personal tools
Toolbox
