Re: [ovirt-users] network configuration oVirt 3.5
This is part of the ovirtmgmt logical network configuration in oVirt Engine.
It looks something like this:
Ido
On Tue, Dec 22, 2015 at 11:59 AM, Kristof VAN DEN EYNDEN <
kristof.vandeneyn...@politiewestkust.be> wrote:
> Hey Ido,
>
> But I didn’t set anything to DHCP ? So where does that come from
>
>
>
>
>
>
>
> *Van:* Ido Barkan [mailto:ibar...@redhat.com]
> *Verzonden:* dinsdag 22 december 2015 10:54
>
> *Aan:* Kristof VAN DEN EYNDEN
> *CC:* users@ovirt.org
> *Onderwerp:* Re: [ovirt-users] network configuration oVirt 3.5
>
>
>
> Configuring the management network with DHCP causes VDSM to try and
> configure
>
> the NIC that with a bridge on top of it with DHCP.
> This has failed and VDSM automatically reverted the NIC configuration to
> its original
> static IP configuration.
>
> The installation of VDSM went OK, but the configuration of the management
> network
>
> have failed because the assignment of a DHCP address failed.
>
> Ido
>
>
>
> On Tue, Dec 22, 2015 at 11:46 AM, Kristof VAN DEN EYNDEN <
> kristof.vandeneyn...@politiewestkust.be> wrote:
>
> Before installing the oVirt Node I set the ifcfg-enp3s0 to a static
> address (no dhcp server availaible on this network).
>
>
>
> After installing the Node through the oVirt interface I was still able to
> connect to the server using that address.
>
> After reboot the IP was still active. After connecting the ovirtmgmt to
> that interface I saw that is was set to DHCP (but the static IP was filled
> in the grayed out boxes) so probably something has gone wrong during the
> install of the VDSM package?
>
>
>
>
>
> *Van:* Ido Barkan [mailto:ibar...@redhat.com]
> *Verzonden:* dinsdag 22 december 2015 10:32
> *Aan:* Kristof VAN DEN EYNDEN
>
> *CC:* users@ovirt.org
> *Onderwerp:* Re: [ovirt-users] network configuration oVirt 3.5
>
>
>
> Hi Kristof.
>
> By inspecting the logs (supervdsm.log) I see the following:
> Adding the management network on the host started here:
>
> MainProcess|jsonrpc.Executor/4::DEBUG::2015-12-21
> 15:40:04,620::supervdsmServer::114::SuperVdsm.ServerCallback::(wrapper)
> call setupNetworks with ({u'ovirtmgmt': {u'nic': u'enp3s0', u'mtu':
> u'1500', u'bootproto': u'dhcp', u'STP': u'no', u'bridged': u'true',
> u'defaultRoute': True}}, {}, {u'connectivityCheck': u'true',
> u'connectivityTimeout': 120}) {}
>
> as part of the network configuration vdsm tries to call `ifup` on the
> bridge named ovirtmgmt:
>
> ifup-waiting-on-dhcp::DEBUG::2015-12-21
> 15:40:04,854::utils::669::root::(execCmd) /usr/bin/systemd-run --scope
> --unit=8bcdacee-4849-453d-a68f-2251e168d466 --slice=vdsm-dhclient
> /usr/sbin/ifup ovirtmgmt (cwd None)
>
> This fails after ~1 minute:
>
> ifup-waiting-on-dhcp::DEBUG::2015-12-21
> 15:41:08,184::utils::687::root::(execCmd) FAILED: = 'Running as unit
> 8bcdacee-4849-453d-a68f-2251e168d466.scope.\n'; = 1
>
> and then the vdsm gives up after 2 minuets (see the parameter:
> u'connectivityTimeout': 120) when it no longer hears the keepalive ping
> from the engine.
>
> I guess that somehow the DHCP process on your network is not operating
> properly.
>
> To work around this (until you sort out the DHCP issues)- configure
> ovirtmgmt management to have a static IP.
>
> Ido
>
>
>
>
>
> On Mon, Dec 21, 2015 at 4:04 PM, Kristof VAN DEN EYNDEN <
> kristof.vandeneyn...@politiewestkust.be> wrote:
>
> Hey Dan,
>
> I reïnstalled the 3.6 on CentOS 7 (this was the issue as vdsm is no longre
> build for 6.7).
> It's a fresh install of CentOs, only configured the adapter for a static
> IP and then the install of the oVirt Node.
> Installation goes well until following errors popup:
>
>
> Dec 21, 2015 3:42:45 PM
> Host KVM1 installation failed. Failed to configure management network on
> the host.
>
> Dec 21, 2015 3:42:45 PM
> Failed to configure management network on host KVM1 due to setup networks
> failure.
>
> Dec 21, 2015 3:42:45 PM
> VDSM KVM1 command failed: connectivity check failed
>
> I included both vdsm.log & supervdsm.log
>
> ---
>
> I did a reboot, the ovirtmgmt was not linked to the adapter (enp3s0).
> Tried to link it manually which worked without hassle...
>
> So now everything seems OK. I'll test further with the 3.6 now and hope it
> all goes like this now
>
> -Oorspronkelijk bericht-
> Van: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Namens
> Kristof VAN DEN EYNDEN
> Verzonden: maandag 21 december 2015 11:41
> Aan: 'users@ovirt.org'
>
> Onderwerp: Re: [ovirt-users] network configuration oVirt 3.5
>
> Hey Dan,
>
> Thanks f
Re: [ovirt-users] network configuration oVirt 3.5
Configuring the management network with DHCP causes VDSM to try and
configure
the NIC that with a bridge on top of it with DHCP.
This has failed and VDSM automatically reverted the NIC configuration to
its original
static IP configuration.
The installation of VDSM went OK, but the configuration of the management
network
have failed because the assignment of a DHCP address failed.
Ido
On Tue, Dec 22, 2015 at 11:46 AM, Kristof VAN DEN EYNDEN <
kristof.vandeneyn...@politiewestkust.be> wrote:
> Before installing the oVirt Node I set the ifcfg-enp3s0 to a static
> address (no dhcp server availaible on this network).
>
>
>
> After installing the Node through the oVirt interface I was still able to
> connect to the server using that address.
>
> After reboot the IP was still active. After connecting the ovirtmgmt to
> that interface I saw that is was set to DHCP (but the static IP was filled
> in the grayed out boxes) so probably something has gone wrong during the
> install of the VDSM package?
>
>
>
>
>
> *Van:* Ido Barkan [mailto:ibar...@redhat.com]
> *Verzonden:* dinsdag 22 december 2015 10:32
> *Aan:* Kristof VAN DEN EYNDEN
> *CC:* users@ovirt.org
> *Onderwerp:* Re: [ovirt-users] network configuration oVirt 3.5
>
>
>
> Hi Kristof.
>
> By inspecting the logs (supervdsm.log) I see the following:
> Adding the management network on the host started here:
>
> MainProcess|jsonrpc.Executor/4::DEBUG::2015-12-21
> 15:40:04,620::supervdsmServer::114::SuperVdsm.ServerCallback::(wrapper)
> call setupNetworks with ({u'ovirtmgmt': {u'nic': u'enp3s0', u'mtu':
> u'1500', u'bootproto': u'dhcp', u'STP': u'no', u'bridged': u'true',
> u'defaultRoute': True}}, {}, {u'connectivityCheck': u'true',
> u'connectivityTimeout': 120}) {}
>
> as part of the network configuration vdsm tries to call `ifup` on the
> bridge named ovirtmgmt:
>
> ifup-waiting-on-dhcp::DEBUG::2015-12-21
> 15:40:04,854::utils::669::root::(execCmd) /usr/bin/systemd-run --scope
> --unit=8bcdacee-4849-453d-a68f-2251e168d466 --slice=vdsm-dhclient
> /usr/sbin/ifup ovirtmgmt (cwd None)
>
> This fails after ~1 minute:
>
> ifup-waiting-on-dhcp::DEBUG::2015-12-21
> 15:41:08,184::utils::687::root::(execCmd) FAILED: = 'Running as unit
> 8bcdacee-4849-453d-a68f-2251e168d466.scope.\n'; = 1
>
> and then the vdsm gives up after 2 minuets (see the parameter:
> u'connectivityTimeout': 120) when it no longer hears the keepalive ping
> from the engine.
>
> I guess that somehow the DHCP process on your network is not operating
> properly.
>
> To work around this (until you sort out the DHCP issues)- configure
> ovirtmgmt management to have a static IP.
>
> Ido
>
>
>
>
>
> On Mon, Dec 21, 2015 at 4:04 PM, Kristof VAN DEN EYNDEN <
> kristof.vandeneyn...@politiewestkust.be> wrote:
>
> Hey Dan,
>
> I reïnstalled the 3.6 on CentOS 7 (this was the issue as vdsm is no longre
> build for 6.7).
> It's a fresh install of CentOs, only configured the adapter for a static
> IP and then the install of the oVirt Node.
> Installation goes well until following errors popup:
>
>
> Dec 21, 2015 3:42:45 PM
> Host KVM1 installation failed. Failed to configure management network on
> the host.
>
> Dec 21, 2015 3:42:45 PM
> Failed to configure management network on host KVM1 due to setup networks
> failure.
>
> Dec 21, 2015 3:42:45 PM
> VDSM KVM1 command failed: connectivity check failed
>
> I included both vdsm.log & supervdsm.log
>
> ---
>
> I did a reboot, the ovirtmgmt was not linked to the adapter (enp3s0).
> Tried to link it manually which worked without hassle...
>
> So now everything seems OK. I'll test further with the 3.6 now and hope it
> all goes like this now
>
> -Oorspronkelijk bericht-
> Van: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Namens
> Kristof VAN DEN EYNDEN
> Verzonden: maandag 21 december 2015 11:41
> Aan: 'users@ovirt.org'
>
> Onderwerp: Re: [ovirt-users] network configuration oVirt 3.5
>
> Hey Dan,
>
> Thanks for your response.
>
> VDSM was the first problem when installing oVirt 3.6 on CentOS, it
> couldn't find the package and while browsing through the repos I couldn't
> find it either. So that was the first issue.. I tried compiling vdsm myself
> which didn't work either and I ended up using the VDSM package under the
> 3.5 release. Any idea how to tackle this?
>
> If I have the time I'll try to reinstall 3.6 and note all the issues I
> find on the way. Can't recover those files as the server is complete messed
> up after my previous efforts
>
> Kind regards !
> Kristof
>
>
>
>
> -Oorspronkelijk bericht-
> Van: Dan Kenigsberg [mailto:da
Re: [ovirt-users] network configuration oVirt 3.5
's connections...)
> > ->not assigning an IP is no option as I can only select static /dhcp
> > ->for ovirtmgmt
>
>
> ovirtmgmt should have been automatically added on top of the interface
> that has the IP used to add the host to Engine.
>
> Could you share your engine.log and {super,}vdsm.log from that time to
> understand why did it happen?
>
> Similarly, please share your ifcfg files prior to adding ovirtmgmt, and
> the supervdsm logs that end up with disconnection.
>
> Regards,
> Dan.
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
--
Thanks,
Ido Barkan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] changing the mtu on bridge devices
Hi Gary. First, In oVirt 3.6 we will enable editing a few network attributes while there vms attached to it. The reason this is forbidden is that until v3.6, by default, vdsm will recreate the network for every network edition and this can seriously disturb the network for the running vms. Second, if you want to tweak the MTU you should use 'ip link set dev mtu 9000' for each device in the network (Bridge, Vlan device, Bond, physical NIC). Then, you should edit vdsm persistence json files under both /var/run/vdsm/netconf// and /var/lib/vdsm/persistence/netconf//. You should find a file for each network/bond under those paths. On the engine DB you should find the proper row in the 'network' table and update the 'mtu' attribute. Good luck, Ido On Thu, Nov 12, 2015 at 4:45 PM, Gary Lloyd <g.ll...@keele.ac.uk> wrote: > Hi we have upgraded to ovirt 3.5.5 and it seems to have gone well. However > when we initially configured one of our clusters (back in the day of ovirt > 3.2) we forgot to adjust two of our vm guest bridges that we use for iscsi > traffic to an mtu of 9000. > > We have around 50 or so vms using these bridges and we cant change the mtu > on the data center screen due to the vms being attached to the bridges (This > message comes up trying to change it). > > We were able to easily override the settings on the hosts in prior versions > of ovirt (but I don't remember where we did it). Our current 3.4 cluster is > fine, but I am now setting up a 3.5 cluster with new servers. > I don't see how changing it to 9000 will cause us any problems due to the > fact that our older clusters are running those bridges at 9000 anyway. > > Also has anyone experienced the new ui not being as responsive when showing > the state of vm migrations (doesn't seem to refresh very well on the hosts > screen). > > Does anyone know if there a way I can force the value to mtu 9000 in the > database somewhere without blowing it up ? > > Cheers > > Gary Lloyd > > I.T. Systems:Keele University > Finance & IT Directorate > Keele:Staffs:IC1 Building:ST5 5NB:UK > +44 1782 733063 > > > _______ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- Thanks, Ido Barkan ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Host In Peril?
On Fri, Oct 30, 2015 at 12:04 AM, Duckworth, Douglas C <du...@tulane.edu>
wrote:
> Doug
Hi Doug,
You haven't sated your vdsm/oVirt version so I my answers might be somewhat
generic.
1) once a network configuration (net-conf) is given by the engine, and is
configured by vdsm,
vdsm stores it under /var/run/vdsm/netconf/{nets,bonds}. This is used
as an intermediate
place fro this configuration, and allows the user to verify that his
requested net-conf
indeed serves his goals.
If the worst has happen, and all communication is now broken, and since
this path does
not survive a reboot, it leaves the user with the emergency ultimate
option of rebooting
the host and let it restooe the last knownworking net-conf (see2).
2) once engine calls setSafeNetworkConfig API verb, this info is copied
into /var/lib/vdsm/persistence/netconf/
in an atomic operation. Since this path survives a host reboot, the
host will restore
all networks from that place.
If I am not mistaking, the engine defaults to call this API immediately
after each netwrok
setup (it can be toggled in a checkbox in the UI).
In general, the ultimate knoledge about the required networks sits in the
administrator mind,
and hopefully, in the engine database. So the best options you guys have is
adding the required netwroks
one by one from the engine, and call setSafeNetworkConfig after each
verified successful state.
This will ensure a proper state+backup on your host.
--
Thanks,
Ido Barkan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Issue with kernel 2.6.32-573.3.1.el6.x86_64?
It might help to tcpdump at different points (devices: bridge, vlan device, physical nic or bond) in order to isolate the evil dropper. Ido Thanks, Ido On Oct 22, 2015 12:06 AM, "Michael Kleinpaste" < michael.kleinpa...@sharperlending.com> wrote: > VMs are on different VLANs and use a central Vyos VM as the firewall and > default gateway. The only indication I had that the packets were getting > dropped or being sent out of order was by tshark'ing the traffic. Tons and > tons of resends. > > The problem was definitely resolved after I dropped back to the prior > kernel (2.6.32-504.12.2.el6.x86_64). > > On Tue, Oct 20, 2015 at 11:51 PM Ido Barkan <ibar...@redhat.com> wrote: > >> Hi Michael, >> Can you describe your network architecture for this vm (inside the host). >> Do you know where are the packets get dropped? >> Ido >> >> On Tue, Sep 22, 2015 at 1:19 AM, Michael Kleinpaste >> <michael.kleinpa...@sharperlending.com> wrote: >> > Nobody's seen this? >> > >> > On Wed, Sep 16, 2015 at 9:08 AM Michael Kleinpaste >> > <michael.kleinpa...@sharperlending.com> wrote: >> >> >> >> So I patched my vhosts and updated the kernel to >> >> 2.6.32-573.3.1.el6.x86_64. Afterwards the networking became unstable >> for my >> >> vyatta firewall vm. Lots of packet loss and out of order packets >> (based on >> >> my tshark at the time). >> >> >> >> Has anybody else experienced this? >> >> -- >> >> Michael Kleinpaste >> >> Senior Systems Administrator >> >> SharperLending, LLC. >> >> www.SharperLending.com >> >> michael.kleinpa...@sharperlending.com >> >> (509) 324-1230 Fax: (509) 324-1234 >> > >> > -- >> > Michael Kleinpaste >> > Senior Systems Administrator >> > SharperLending, LLC. >> > www.SharperLending.com >> > michael.kleinpa...@sharperlending.com >> > (509) 324-1230 Fax: (509) 324-1234 >> > >> > ___ >> > Users mailing list >> > Users@ovirt.org >> > http://lists.ovirt.org/mailman/listinfo/users >> > >> >> >> >> -- >> Thanks, >> Ido Barkan >> > -- > *Michael Kleinpaste* > Senior Systems Administrator > SharperLending, LLC. > www.SharperLending.com > michael.kleinpa...@sharperlending.com > (509) 324-1230 Fax: (509) 324-1234 > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Issue with kernel 2.6.32-573.3.1.el6.x86_64?
Hi Michael, Can you describe your network architecture for this vm (inside the host). Do you know where are the packets get dropped? Ido On Tue, Sep 22, 2015 at 1:19 AM, Michael Kleinpaste <michael.kleinpa...@sharperlending.com> wrote: > Nobody's seen this? > > On Wed, Sep 16, 2015 at 9:08 AM Michael Kleinpaste > <michael.kleinpa...@sharperlending.com> wrote: >> >> So I patched my vhosts and updated the kernel to >> 2.6.32-573.3.1.el6.x86_64. Afterwards the networking became unstable for my >> vyatta firewall vm. Lots of packet loss and out of order packets (based on >> my tshark at the time). >> >> Has anybody else experienced this? >> -- >> Michael Kleinpaste >> Senior Systems Administrator >> SharperLending, LLC. >> www.SharperLending.com >> michael.kleinpa...@sharperlending.com >> (509) 324-1230 Fax: (509) 324-1234 > > -- > Michael Kleinpaste > Senior Systems Administrator > SharperLending, LLC. > www.SharperLending.com > michael.kleinpa...@sharperlending.com > (509) 324-1230 Fax: (509) 324-1234 > > ___________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- Thanks, Ido Barkan ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway
gt; >>> This the case >>> >>> With No IP in the VLAN, and IP in the Virtual Machine, From the Virtual >>> Machine can ping myself (192.168.50.8) but I can't reach the gateway, can't >>> reach the host, can't reach Internet. >>> >>> Any help is appreciated >>> >>> Thanks Friends of oVirt >>> >>> >>> >>> >>> >>> >>> >>> >>> 2015-07-06 7:51 GMT-05:00 Soeren Malchow <soeren.malc...@mcon.net>: >>> >>>> Hi, >>>> >>>> To make it easier to understand what the situation is, it would help to >>>> see your bridging configuration and your interface configration. >>>> >>>> Something like: >>>> >>>> #> ip addr >>>> >>>> And >>>> >>>> #> brctl show >>>> >>>> Regards >>>> Soeren >>>> >>>> On 06/07/15 13:30, "users-boun...@ovirt.org on behalf of Dan >>>> Kenigsberg" >>>> <users-boun...@ovirt.org on behalf of dan...@redhat.com> wrote: >>>> >>>> >On Tue, Jun 30, 2015 at 03:48:49PM -0500, Julián Tete wrote: >>>> >> Hi Friends of oVirt >>>> >> >>>> >> I'm trying to migrate my company from VMware to oVirt. >>>> > >>>> >We'd like to help you do this! >>>> > >>>> >> In my final tests, I set up 2 more VLANs in oVirt, (VM VLANs) >>>> >> The Virtual Machines in these VLANs, can be reached from the external >>>> >>IPs >>>> >> from the net range, >>>> >> but from the Virtual machines only can ping the Host with the Bridge >>>> and >>>> >> itself, can't reach the gateway. ¿? >>>> >> >>>> >> I configured a IP Forwarding in the Host with the virtual machine, >>>> and >>>> >> nothing changes... >>>> >> >>>> >> Any idea ? This is the last duty before embrace oVirt in the company. >>>> >> >>>> >> Look to the VLAN 100 configuration (My desired VM Network): >>>> >> >>>> >> http://postimg.org/image/7hrog0a2n/ >>>> >> >>>> >> http://postimg.org/image/68b40i1vr/ >>>> >> >>>> >> http://postimg.org/image/lu6mlshgp/ >>>> > >>>> >I must admit that I don't understand your problem yet. When you ping >>>> >from inside your guest, where are your packets dropped? >>>> > >>>> >I'd like to point that your "Hosting" network, as most VM networks, is >>>> >better off left without an IP address. The benefit of this is better >>>> >security (host TCP stack is not accessible from VMs) and less chances >>>> of >>>> >routing collisions from the host. >>>> > >>>> >So unless you need to use the same network for something other than VM >>>> >communication, try to clear its address. >>>> > >>>> >Regards, >>>> >Dan. >>>> >___ >>>> >Users mailing list >>>> >Users@ovirt.org >>>> >http://lists.ovirt.org/mailman/listinfo/users >>>> >>>> >>> >> > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > -- Thanks, Ido Barkan ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Problem with network VM
Hi Rocha, This depends on the network configuration on you host, which can be configured from the engine. Can you please attach the contents of /var/lib/vdsm/persistence/netconf ? (it is a soft link for a directory tree of json files. Thanks, Ido On Wed, Sep 9, 2015 at 8:56 PM, Rocha Neto <em...@rochaneto.net> wrote: > Hello friends, okay with you? I hope you are well. > > I've tried to get in some mailing lists and could not. Did you could get me > a question, or send me somewhere that I can study about? > > I rode an environment with oVirt. I have the engine running on the IP > xx.xx.xx.45 and Host with the IP xx.xx.xx.46. > > Everything works fine, datacenter, cluster, host, storage (iSCSI). But when > I create a VM, install CentOS for example. I can not access the network. I > can not ping any address out. What should I do? Is there some setting I need > to change? > > The host has two interfaces eth0 and ovirtmgmt, all working perfectly well. > > Could someone give me a light? > > Thanks in advance! > > > Update: > > I have /27 (Netmask 255.255.255.224) > xx.xx.xx.45 engine > xx.xx.xx.46 host (vdsm) ovirtmgmt bridge > xx.xx.xx.33 is my gateway > > Network of VM is: > xx.xx.xx.52 > xx.xx.xx.33 gw > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- Thanks, Ido Barkan ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] oVirt 3.5.3 and Network Unified Persistence issues?
Hi Simon. In the meantime (until 3.5.4 is out) you can run "vdsm-tool restore-nets --force" to solve this after "service network restart". Vdsm will skip restoration if this was done since last boot. The --force flags will skip this check. Ido On Tue, Aug 25, 2015 at 7:45 PM, Michael Burman <mbur...@redhat.com> wrote: > Hi Simon, > > This issue will be fixed on 3.5.4 > see - https://bugzilla.redhat.com/show_bug.cgi?id=1203422 > > On 3.5.3, vdsm generating all ifcfg-* files to ONBOOT=NO by default, except > the management network and the interface it is attached to. In your case bond > (bond0,bond.108 and the slaves). > - You can configure your ifcfg-* files manually to ONBOOT=yes and restart > network service as a workaround for now. > > Kind regards, > Michael B > > - Original Message - > From: "Simon Barrett" <simon.barr...@tradingscreen.com> > To: users@ovirt.org > Sent: Monday, August 24, 2015 5:01:45 PM > Subject: [ovirt-users] oVirt 3.5.3 and Network Unified Persistence issues? > > > > I’m running into a problem with my upgrades to oVirt 3.5.3 and wanted to > check if the following is a known issue. > > > > I have multiple vlan tagged interfaces configured. The files are being > generated as expected by vdsm. The vlan 108 interface below is used by the > ovirtmgmt bridge. The uatdev_ben, bond0.192, dev_office, bond0.124 interface > definitions all have ONBOOT=no. > > > > root@host> grep -i onboot ifcfg* | grep -v bak > > ifcfg-bond0:ONBOOT=yes > > ifcfg-bond0.108:ONBOOT=yes > > ifcfg-bond0.124:ONBOOT=no > > ifcfg-bond0.192:ONBOOT=no > > ifcfg-dev_office:ONBOOT=no > > ifcfg-eth0:ONBOOT=yes > > ifcfg-eth1:ONBOOT=yes > > ifcfg-eth2:ONBOOT=no > > ifcfg-eth3:ONBOOT=no > > ifcfg-lo:ONBOOT=yes > > ifcfg-ovirtmgmt:ONBOOT=yes > > ifcfg-uatdev_ben:ONBOOT=no > > > > The persistence configuration files are where they should be (I think): > > > > root@host> ls -l /var/lib/vdsm/persistence/netconf/nets/ > > total 12 > > -rw-r--r-- 1 root root 121 Aug 24 22:44 dev_office > > -rw-r--r-- 1 root root 173 Aug 24 22:44 ovirtmgmt > > -rw-r--r-- 1 root root 121 Aug 24 22:44 uatdev_ben > > > > If I were to do a “service network restart” on the node, the uatdev_ben, > dev_office, bond0.124 & bond0.192 are removed and then not restored as the > “ONBOOT=no”. I assumed that vdsmd would re-create the dev_office and > uatdev_ben interfaces so restarted vdsmd but they were not restored. I tried > a “vdsm-tool restore-nets” to see if that would restore the interfaces but no > joy. > > > > Am I missing something? Is there another method I should use to recover the > missing interfaces? Should the ifcfg files all be configured with > “ONBOOT=yes” just in case someone does run a “service network restart”? > > > > My oVirt nodes are CentOS 6.5, I’m not using the node iso. > > > > Many thanks in advance for any assistance. > > > > Regards, > > > > Simon Barrett > > ___________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > -- > Michael Burman > RedHat Israel, RHEV-M QE Network Team > > Mobile: 054-5355725 > IRC: mburman > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users -- Thanks, Ido Barkan ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] oVirt 3.5.3 Host Network Interfaces
Hi Michael, Just to let you know. In the next version (3.6) Ovirt will support Editing networks (in most cases) while there are VMs attached to them. This might make situations like your a bit easier. Thanks, Ido - Original Message - From: Prof. Dr. Michael Schefczyk mich...@schefczyk.net To: Soeren Malchow soeren.malc...@mcon.net, users@ovirt.org Sent: Tuesday, July 7, 2015 1:46:15 PM Subject: Re: [ovirt-users] oVirt 3.5.3 Host Network Interfaces Dear Soeren, Thank you very much for your feedback. I think that the issue is that bonding mode balance-alb (with no special switch configuration) does work while 802.3ad (with appropriate switch configuration) does not. With correct switch configuration, 802.3ad does connect the server to the LAN but it does prevent oVirt/VDSM from working, I think. As the hosted engine, does not even start, it is then not possible to further change the configuration. This is surprising to me, as I prefer standardized solutions making use of available hardware capabilities (i.e., 802.3ad). As a result, I will explore oVirt further based on balance-alb NIC bonding. Regards, Michael -Ursprüngliche Nachricht- Von: Soeren Malchow [mailto:soeren.malc...@mcon.net] Gesendet: Dienstag, 7. Juli 2015 10:54 An: Prof. Dr. Michael Schefczyk; users@ovirt.org Betreff: Re: AW: [ovirt-users] oVirt 3.5.3 Host Network Interfaces Dear Michael, The network scripts look exactly as we did that, and then during setting up the host network we also got the already enslaved message which did not cause a problem since it actually was enslaved, afterwards there were proper vdsm generated interface files. Though we have the difference, that the ovirt already showed the bond even when it was not managed by ovirt yet. You can still change the one bonded interface in ovirt and add one additional interface, just drag and drop, put the bridge in and configured the Ips, however, if you want 802.3ad you need to change the switch ports to do 802.3ad as well a little bit after you applied the change, to avoid having to do the switch configuration use custom and mode=5 or mode=6 Regards Soeren On 07/07/15 01:14, Prof. Dr. Michael Schefczyk mich...@schefczyk.net wrote: Dear Soeren, dear all, Thank you very much. I did try the steps on an installed system. The result was that after manipulating the network scripts, the server would communicate well with the rest of the LAN - as many other servers on which I use NIC bonds. However, my hosted-engine refused to start: hosted-engine --vm-start results in Connection to localhost:54321 refused. Needless to say, it is not possible to revert the maintenance mode then. ABRT points out what the problem is (but not the solution): api.py:119:objectivizeNetwork:ConfigNetworkError: (24, u'nic enp0s20f1 already enslaved to bond0') This shows that oVirt cannot start after the manipulation of network scripts as it does expect enp0s20f1 no not be a slave of a bond. Naming of the devices becomes clear from the following paragraph. After multiple failed experiments to set up the server with bonded NIC (each implying configuring the server from scratch), I took the following approach this time: - The server has two LAN facing NICs enp0s20f0, enp0s20f1. The other two NICs point to the other server in the intended gluster cluster - creating a bond for them is not problematical. - Setting up Centos 7, I just used enp0s20f0 with no bond and bridge. - Deploying oVirt one gets asked for an unused NIC, so I selected enp0s20f1. Then the network was only resting on enp0s20f1 with a working setup of oVirt - just without bonding two NICs. I am still surprised that this HA network issue is so difficult to manage in a software that is largely about high availability. Can anyone please indicate how to proceed towards NIC bonding? Regards, Michael Network Scripts as set manually: DEVICE=enp0s20f0 TYPE=Ethernet USERCTL=no SLAVE=yes MASTER=bond0 BOOTPROTO=none HWADDR=00:25:90:F5:18:9A NM_CONTROLLED=no DEVICE=enp0s20f1 TYPE=Ethernet USERCTL=no SLAVE=yes MASTER=bond0 BOOTPROTO=none HWADDR=00:25:90:F5:18:9B NM_CONTROLLED=no DEVICE=bond0 ONBOOT=yes BONDING_OPTS='mode=802.3ad miimon=100' BRIDGE=ovirtmgmt NM_CONTROLLED=no DEVICE=ovirtmgmt ONBOOT=yes TYPE=Bridge IPADDR=192.168.12.40 NETMASK=255.255.255.0 GATEWAY=192.168.12.1 DNS=192.168.12.1 NM_CONTROLLED=no -Ursprüngliche Nachricht- Von: Soeren Malchow [mailto:soeren.malc...@mcon.net] Gesendet: Montag, 6. Juli 2015 15:01 An: Prof. Dr. Michael Schefczyk; users@ovirt.org Betreff: Re: [ovirt-users] oVirt 3.5.3 Host Network Interfaces Dear Michael We actually created the ovirtmgmt and the bond manually upfront and then in the ³Setup Hosts Network² we basically did this again (including setting the IP address), regarding the bonding in the gluster network we did not have a problem, you just drag one interface onto the other and then select the bonding mode, where you can
Re: [ovirt-users] vlan-tagging on non-tagged network
Hey Felix. IIUC your frames are dropped by the bridge. Ovirt uses Linux Bridges To connect virtual machines to 'networks'. The guest connects to the bridge using a tap device which usually is called 'vnetnumber'. So, just to verify, can you please tcpdump both on the bridge device and on the tap device? The bridge can be quite noisy so I suggest filtering traffic using the guest's MAC address. So I am not sure what protocol you use for tunneling but applying a filter similar to this one should do the job: tcpdump -n -i vnet0 -vvv -s 1500 'udp[38:4]=0x001a4aaeec8e' My guess is that you will observe traffic on the tap device, but not on the bridge. You didn't specify which centOS version you use but I do remember seeing people complaining about Linux bridges discarding their tagged frames. You can -maybe- also observe the 'dropped' counter increases on the bridge by running: 'ip -s link show dev trunk' There were a few bugs on rhel6/7 about this, specifically I remember https://bugzilla.redhat.com/show_bug.cgi?id=1174291 and https://bugzilla.redhat.com/show_bug.cgi?id=1200275#c20 Also, is the vlan module loaded on your host? 'lsmod |grep 8021q' Thanks, Ido - Original Message - From: Felix Pepinghege pepingh...@ira.uka.de To: Users@ovirt.org Sent: Monday, June 15, 2015 11:33:39 AM Subject: [ovirt-users] vlan-tagging on non-tagged network Hi everybody! I am experiencing a behaviour of ovirt, of which I don't know whether it is expected or not. My setup is as follows: A virtual machine has a logical network attached to it, which is configured without vlan-tagging and listens to the name 'trunk'. The VM is running an openvpn server. It is a patched openvpn version, including vlan-tagging. That is, openvpn clients get a vlan tag. This should not really be an issue but should satisfy the why do you want to do it in the first place-questions. Anyhow, effectively, the VM simply puts vlan-tagged ethernet-frames on the virtual network. These frames, however, never make it to the host's network bridge, which represents the logical network. My observations are: According to tcpdump, the vlan-tagged packages arrive at the eth1-interface inside the VM (which *is* the correct interface). Again, according to tcpdump, these packages never arrive at the corresponding network-bridge (i.e., the interface 'trunk') on the host. I know that the setup itself is feasible with KVM---I have it working on a proxmox-machine. Therefore, my conclusion is, that ovirt doesn't like vlan-tagged ethernet-frames on non-tagged logical networks, and somehow filters them out, though I don't really see on what level that would happen (Handling the ethernet frames should be a concern of KVM/QEMU/Linux only, once ovirt has started the VM). So this problem could be a CentOS issue, but I really don't see why CentOS should act differently than debian does (proxmox is debian-based). Is this a known/wanted/expected behaviour of ovirt, and can I somehow prevent or elude it? Any help is much appreciated! Of course I am happy to provide more information if that helps helping me :) Regards, Felix ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] [ACTION REQUIRED] oVirt 3.5.2 and 3.5.3 status
1187244 - 2, 3 work weeks I assume. we aim for 3.5.1. - Original Message - From: Adam Litke ali...@redhat.com To: Sandro Bonazzola sbona...@redhat.com Cc: Amit Aviram aavi...@redhat.com, Yedidyah Bar David d...@redhat.com, Ido Barkan ibar...@redhat.com, Martin Perina mper...@redhat.com, Tal Nisan tni...@redhat.com, Maor Lipchuk mlipc...@redhat.com, Eyal Edri ee...@redhat.com, Users@ovirt.org, de...@ovirt.org Sent: Wednesday, March 11, 2015 3:09:43 PM Subject: Re: [ACTION REQUIRED] oVirt 3.5.2 and 3.5.3 status On 11/03/15 13:33 +0100, Sandro Bonazzola wrote: Hi, We still have 8 open blockers for 3.5.2[1]: Bug ID Whiteboard Status Summary 1177220storage ASSIGNED[BLOCKED] Failed to Delete First NFS snapshot with live merge Eric Blake is creating a workaround for libvirt. I just pinged him in the blocking bug https://bugzilla.redhat.com/show_bug.cgi?id=1199182 to check on his progress. -- Adam Litke ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] OVIRT-3.5-TEST-DAY-3: Network Custom Properties
Hi,
Following is a summery of testing the Network custom properties feature as
detailed the link at the bottom.
setUp:
==
engine: F19
Hosts:
F20 (virtual)
REHL 6.5 (physical)
- in separate clusters
Network custom properties:
==
1. I have defined a custom property entry via 'engine-config' cli and verified
it consisted.
* The property was defined with a validation regular expression
* note that this requires an engine restart.
2. Added a new network to the DC and set the new property with the new
drop-down value of 'custom properties'.
- verified that violating the regular expression validation fails the network
set up (client side validation).
- verified that a legal value is passed to the server using a custom hook at
before_network_setup stage.
[hook code attached]
3. removed the value from the DB
-- verified it is no longer available in the set up networks custom properties
drop down.
bridge options:
===
1. changed the bridge options at the OS level (via editing
/sys/class/net/bridge/bridge/options)
2. defined overrides in the logical level using the bridge_opts drop down value
(key=value comma separated list)
--verified that the values are changed after setting up network
3. removed the logical level settings
-- verified that the values are set back to the original ones
ethtool options:
* note- testing this on a virtual host, or on a virtual NIC on a physical host
is pretty useless. For the NIC driver
to be capable of actually allowing NIC changes you need a bare metal NIC.
1. installed the vdsm-hook-ethtool-options hook on a physical host
2. set up network with the following ethtool command line arguments added: -s
eth1 speed 100 autoneg off
-- verified using ethtool that changes took place
3. set up network with the following ethtool command line arguments added: -s
eth1 autoneg on
-- verified using ethtool that changes took place
feature page: http://www.ovirt.org/Features/Network_Custom_Properties
Thanks,
Ido
#!/usr/bin/python
import os
import hooking
def main():
setup_nets_config = hooking.read_json()
hooking.log('keys:'+ str(setup_nets_config.keys()))
for network, attrs in setup_nets_config['request']['networks'].items():
if 'custom' in attrs and 'hostonly' in attrs['custom']:
value = attrs['custom']['hostonly']
else:
value = 'not found'
hooking.log('TESTING: {0}'.format(value))
if __name__ == '__main__':
main()___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
