----- Original Message -----
From: "Anil Dhingra" <anildhingra25@gmail.com> To: "Fabian Deutsch" <fabiand@redhat.com> Cc: users@ovirt.org Sent: Wednesday, October 2, 2013 6:07:26 PM Subject: Re: [Users] ovirt-node post-reboot no persistent networks config .. !!! urgent update req for POC coming weekend
Hey Fabian Thanks you so much .. abv mentioned iso draft for el6 works like a charm config is persistent now ..only issue I faced is after configuring first interface "eth0" when it starts VDSM & other service it hangs at <close> & hard reboot was required but after that no issue tried multiple reboots different n/w configs ..looks perfect. just wanted to ask some n/w related q to clear my doubts .. may be its not a right group to ask such question Please find attached image for below 1- ovirt-node creates Bridged network only when "vm network" option is selected ... ? correct me if I am wrong
The engine directs vdsm how to create the network on the host. If the logical network definition is 'vm network', the network will be created as a bridge which is the current vm network implementation.
2- is it recommended or best practice to select ovirtmgmt for VM n/w ? so that it make a Bridged n/w
It depends on you h/w capabilities. If you have a single nic per host, it would be better defining it as a non-vm network, so you will be able to attach additional tagged networks to that nic, so you can support multiple private networks (you'll have to specify a specific vlan-id for each additional network). If you have multiple nics, it would be better to define the ovirtmgmt as a non-vm network, and not use it as a migration network. (traffic considerations).
3- for Migration/Display network whats the best practice do we need to create manual bridge setup ?
There is no need for that. You must have a network with IP configured and obtained by the engine (on the host nics sub-tab you should see the engine reports the ip of the network you wish to use as a display network and/or a migration network).
Thanks again for prompt response really appreciate yours help .. Anil
On Wed, Oct 2, 2013 at 5:16 PM, Fabian Deutsch < fabiand@redhat.com > wrote:
Am Dienstag, den 01.10.2013, 15:05 +0000 schrieb Sven Kieske:
Hi,
we encountered the same problem as Anil.
We wanted to give this nightly iso a try: http://jenkins.ovirt.org/job/node-devel/825/distro=centos64/artifact/ovirt-n...
but it seems it doesn't contain the required vdsm-plugin?
True. The plugin is missing.
I've prepared two isos (but untested) which address this bug: http://fedorapeople.org/~fabiand/node/ovirt-node-iso-3.0.1-1.0.201310020841d... http://fedorapeople.org/~fabiand/node/ovirt-node-iso-3.1.0-0.999.20131002084...
They are basically the base iso (found in jenkins) plus an edit-node run: /edit-node --repo edit-node-el6.repo --install ovirt-node-plugin-vdsm ovirt-node-iso-3.0.1-1.0.201310020841draft.el6.iso
Please let me know if they fix the problem.
Greetings fabian
So any help on this topic would be appreciated.
Greetings
Sven
On 30/09/13 20:52, Fabian Deutsch wrote:
Hey Anil,
you were doing the right thing to persist the network cfg files. It might have been node that was to greedy when reconfiguring DNS :)
You might take a look at this fix: http://gerrit.ovirt.org/19705 It is untested but at least I could reproduce the behavior you were seeing and prepared the patch based on that findings. An ISO containing that fix will sooner or later land here: http://jenkins.ovirt.org/job/node-devel/
(The queue is currently quite long, which can take a day until the patch above is turned into an ISO).
Long story short, please check if this patch fixes your problem, I'll also try to take a look at it when an iso is ready.
And file a bug if you want to track the state of this issue.
Greetings fabian
_______________________________________________ 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