On Wed, Jun 20, 2012 at 02:52:19PM -0400, Mike Kolesnik wrote:
Thanks for the response, see responses inline.
You're welcome, responses inline.
On Wed, Jun 20, 2012 at 2:54 AM, Mike Kolesnik <mkolesni@redhat.com> wrote:
Hi,
Please see reply in-line.
In ovirt-engine-3.1 I'm attempting to setup the base logical networks and have run into 2 major issues.
Are you using cluster version 3.0 or 3.1?
I have been using 3.1 as it's the default. Is the different just the API updates? All I could really find related to 3.0 vs 3.1 pertaining to networking was this document http://www.ovirt.org/wiki/Features/Design/Network/SetupNetworks
As Itamar replied, there are a few more network features in 3.1 other than this one.
For a Host which is in a 3.1 cluster there should be a "Setup Networks" button which indeed enables the functionality described in that wiki. This is a new feature for 3.1 & up which allows to do several network changes in an atomic manner, with an improved UI experience.
However, from the logs it looks like you're using the old commands to edit the networks on the Host, so if you have this button (you should) then you can try using it.
<SNIP>
Unfortunately, oVirt supports setting only the default gateway of the Host (This is the field you saw in the management network).
We could theoretically use initscripts' static routing files, but that is left for future development.
So for now, is it then easier to just run all public interfaces through the same subnet/gateway? The main reason to run management via 100Mbps and everything else 1Gbps was that our campus is out of IPs so we're attempting to conserve on the usage of gigabit IPs.
Yes, currently the only gateway you can specify is the default one which is set on the management network.
However it is worth mentioning that VM networks should generally not have an IP address (or gateway) of their own. At best, they serve as layer-2-only entities. Putting the management network in one subnet and VMs on a different one, makes a lot of sense.
<SNIP>
<snap>
So in the host interface eth5 I set the following via web interface
Network: private1 Boot Protocol: Static IP: 10.20.1.241 Subnet Mask: 255.0.0.0 Check: Save network configuration
After the save the node's ifcfg-eth5 is touched (based on modified date in ls -la) but this is all it contains DEVICE=eth5 ONBOOT=yes BOOTPROTO=none HWADDR=00:1b:21:1d:33:f1 NM_CONTROLLED=no MTU=9000
As far as I can tell the only setting from ovirt-engine that made it to that file was the MTU setting defined when creating the logical network for the cluster.
Is my process somehow wrong or am I missing a step? I've done this with the node being in both "Up" status and "Maintenance", same results.
No, it looks like a bug that should be taken care of.
And a serious one, that hinders the usability of non-VM networks, and which I consider an oVirt-3.1 release blocker Bug 834281 - [vdsm][bridgeless] BOOTPROTO/IPADDR/NETMASK options are not set on interface Thanks for reporting it. Dan.