5:02 a.m.
Hello Alan,
Please check
https://www.ovirt.org/documentation/how-to/hosted-engine/#migrate-hosts-f...
to understand how to perform your upgrade from EL6 & RHEV3.5, quoting:
"In 3.6, el6 is not supported anymore for hosted-engine hosts. Existing 3.5
el6 hosts should be first migrated to el7, then upgraded to 3.6. More
details in Hosted Engine host operating system upgrade Howto
<https://www.ovirt.org/documentation/how-to/hosted-engine/hosted-engine-ho...
."
It is up to the Engine (RHEVM) to be aware of the networks on your hosts
(and to configure them through running VDSM daemons), so if you want the
tagged networks the way you configured them manually on your hosts, you
need to define the cluster networks in web GUI correspondingly.
I don't think it is possible to leave network setup to manual configuration
by standard means (that is, by having VDSM running to take care of all but
networking chores, but have it patched or use hooks to implement your
configuration).
I, too, don't exactly understand your existing setup. Can you describe it
in more detail? Since you want to learn how to perform an upgrade, you
should try to mimic your production system, which is necessarily managed by
VDSM daemons running on all hosts.
If you are having a trouble reproducing your production environment in your
lab, please describe the steps you took. Perhaps it is reasonable to
install the Engine first with no complicated network setup, and only then
configure networks step by step.
Thank you,
Ondra
On Sun, Apr 9, 2017 at 10:33 AM, Dan Kenigsberg <danken(a)redhat.com> wrote:
On Fri, Apr 7, 2017 at 4:24 PM, Alan Cowles
<alan.cowles(a)gmail.com> wrote:
> Hey guys,
>
> I'm in a lab setup currently with 2 hosts, running RHEV-3.5, with a
> self-hosted engine on RHEL 6.9 servers. I am doing this in order to plot
out
> a production upgrade I am planning going forward to 4.0, and I'm a bit
stuck
> and I'm hoping it's ok to ask questions here concerning this product and
> version.
>
> In my lab, I have many vlans trunked on my switchports, so I have to
create
> individual vlan interfaces on my RHEL install. During the install, I am
able
> to pick my ifcfg-eth0.502 interface for rhevm, and ifcfg-eth1.504
interface
> for NFS, access the storage and create my self-hosted engine. The issue
I am
> running into is that I get into RHEV-M, and I am continuing to set the
hosts
> up or add other hosts, when I go to move my NFS network to host2 it only
> allows me to select the base eth1 adapter, and not the VLAN tagged
version.
> I am able to tag the VLAN in the RHEV-M configured network itself, but
this
> has the unfortunate side effect of tagging a network on top of the
already
> tagged interface on host1, taking down NFS and the self hosted engine.
>
> I am able to access the console of host1, and I configure the ifcfg
files,
> vlan files, and bridge files to be on the correct interfaces, and I get
my
> host back up, and my RHEV-M back up. However when I try to make these
manual
> changes to host2 and get it up, the changes to these files are completely
> overwritten the moment the host reboots connected to vdsmd start-up.
If that was your only issue, I would have recommended you to read
https://www.ovirt.org/blog/2016/05/modify-ifcfg-files/ and implement a
hook that would leave the configuration as you wanted it.
>
> Right now, I have vdsmd disabled, and I have host2 configured the way I
need
> it to be with the rhevm bridge on eth0.502, the NFS bridge on eth1.504,
and
> my VMNet "guest" bridge on eth1.500, however that leaves me with a
useless
> host from RHEV standards.
>
> I've checked several different conf files to see where vdsmd is pulling
it's
> configuration from but I can't find it, or find a way to modify it to
fit my
> needs.
>
> Any advice or pointers here would be greatly appreciated. Thank you all
in
> advance.
Pardon me for not clearly understanding the problem at hand.
Could you specify your Engine-defined network names and vlan IDs? Can
you specify the ifcfgs that you'd like to see on your hosts, and the
ones re-generated on reboot?
Dan.