Re: [ovirt-users] NetworkManager with oVirt version 4.2.0

2018-02-05 Thread Edward Haas
On Sun, Feb 4, 2018 at 10:01 PM, Vincent Royer 
wrote:

> I had these types of issues as well my first time around, and after a
> failed engine install I haven't been able to get things cleaned up, so I
> will have to start over. I created a bonded interface on the host before
> the engine setup. but once I created my first VM and assigned bond0 to it,
> the engine became inaccessible the moment the VM got an IP from the
> router.
>

Please clarify what does it mean to "assign bond0 to it".  A vnic can be
defined on a network (using vnic profiles).
If your Engine is inaccessible, try to understand what changed in the
network, perhaps something collided (duplicate IP/s, routes, mac/s etc).


> What is the preferred way to setup bonded interfaces?  In Cockpit or nmcli
> before hosted engine setup?  Or proceed with only one interface then add
> the other in engine?
>

All should work.


>
> Is it possible, for example, to setup bonded interfaces with a static
> management IP on vlan 50 to access the engine, and let the other VMs grab
> DHCP IPs on vlan 10?
>

Sure it is, one is the management (vlan 50) network and the other a VM
network (vlan 10).


>
>
> On Feb 3, 2018 11:31 PM, "Edward Haas"  wrote:
>
>
>
> On Sat, Feb 3, 2018 at 9:06 AM, maoz zadok  wrote:
>
>> Hello All,
>> I'm new to oVirt, I'm trying with no success to set up the networking on
>> an oVirt 4.2.0 node, and I think I'm missing something.
>>
>> background:
>> interfaces em1-4 is bonded to bond0
>> VLAN configured on bond0.1
>> and bridged to ovirtmgmt for the management interface.
>>
>> I'm not sure its updated to version 4.2.0 but I followed this post:
>> https://www.ovirt.org/documentation/how-to/networking/bondin
>> g-vlan-bridge/
>>
>
> It looks like an old howto, we will need to update or remove it.
>
>
>>
>> with this setting, the NetworkManager keep starting up on reboot,
>> and the interfaces are not managed by oVirt (and the nice traffic graphs
>> are not shown).
>>
>
> For the interfaces to be owned by oVirt, you will need to add the host to
> Engine.
> So I would just configure everything up to the VLAN (slaves, bond, VLAN)
> with NetworkManager prior to adding it to Engine. The bridge should be
> created when you add the host.
> (assuming the VLAN you mentioned is your management interface and its ip
> is the one used by Engine)
>
>
>>
>>
>>
>>
>> my question:
>> Is  NetworkManager need to be disabled as in the above post?
>>
>
> No (for 4.1 and 4.2)
>
> Do I need to manage the networking using (nmtui) NetworkManager?
>>
>
> You better use cockpit or nmcli to configure the node before you add it to
> Engine.
>
>
>>
>> Thanks!
>> Maoz
>>
>>
>>
>>
>>
>> ___
>> 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
>
>
>
> ___
> 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] NetworkManager with oVirt version 4.2.0

2018-02-04 Thread Vincent Royer
I had these types of issues as well my first time around, and after a
failed engine install I haven't been able to get things cleaned up, so I
will have to start over. I created a bonded interface on the host before
the engine setup. but once I created my first VM and assigned bond0 to it,
the engine became inaccessible the moment the VM got an IP from the
router.

What is the preferred way to setup bonded interfaces?  In Cockpit or nmcli
before hosted engine setup?  Or proceed with only one interface then add
the other in engine?

Is it possible, for example, to setup bonded interfaces with a static
management IP on vlan 50 to access the engine, and let the other VMs grab
DHCP IPs on vlan 10?


On Feb 3, 2018 11:31 PM, "Edward Haas"  wrote:



On Sat, Feb 3, 2018 at 9:06 AM, maoz zadok  wrote:

> Hello All,
> I'm new to oVirt, I'm trying with no success to set up the networking on
> an oVirt 4.2.0 node, and I think I'm missing something.
>
> background:
> interfaces em1-4 is bonded to bond0
> VLAN configured on bond0.1
> and bridged to ovirtmgmt for the management interface.
>
> I'm not sure its updated to version 4.2.0 but I followed this post:
> https://www.ovirt.org/documentation/how-to/networking/bonding-vlan-bridge/
>

It looks like an old howto, we will need to update or remove it.


>
> with this setting, the NetworkManager keep starting up on reboot,
> and the interfaces are not managed by oVirt (and the nice traffic graphs
> are not shown).
>

For the interfaces to be owned by oVirt, you will need to add the host to
Engine.
So I would just configure everything up to the VLAN (slaves, bond, VLAN)
with NetworkManager prior to adding it to Engine. The bridge should be
created when you add the host.
(assuming the VLAN you mentioned is your management interface and its ip is
the one used by Engine)


>
>
>
>
> my question:
> Is  NetworkManager need to be disabled as in the above post?
>

No (for 4.1 and 4.2)

Do I need to manage the networking using (nmtui) NetworkManager?
>

You better use cockpit or nmcli to configure the node before you add it to
Engine.


>
> Thanks!
> Maoz
>
>
>
>
>
> ___
> 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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] NetworkManager with oVirt version 4.2.0

2018-02-04 Thread maoz zadok
I think that I find a quick workaround to resolve this issue, I remove all
the logical interfaces from NM and from sysconfig/network-scripts and
restart the server,
the VDSM service generates the new file and configuration and everything
works as cream.

1. delete all the ifcfg-* files from /etc/sysconfig/network-scripts (except
for the ifcfg-lo )
2. delete the interfaces from NetworkManager as follow:
nmcli d delete ovirtmgmt
nmcli d delete bond0
nmcli d delete bond0.1

👍



On Sun, Feb 4, 2018 at 10:42 AM, Edward Haas  wrote:

> You may be encountering this problem: https://bugzilla.redhat.com/
> show_bug.cgi?id=1523661
> If this is it, you have two options:
> - Upgrade VDSM to latest 4.2.1.
> - Define first the VLAN on one of the slaves, add the host to Engine and
> then modify the network attachment by creating a bond through Engine.
>
> Thanks,
> Edy.
>
> On Sun, Feb 4, 2018 at 9:30 AM, Edward Haas  wrote:
>
>>
>>
>> On Sat, Feb 3, 2018 at 9:06 AM, maoz zadok  wrote:
>>
>>> Hello All,
>>> I'm new to oVirt, I'm trying with no success to set up the networking on
>>> an oVirt 4.2.0 node, and I think I'm missing something.
>>>
>>> background:
>>> interfaces em1-4 is bonded to bond0
>>> VLAN configured on bond0.1
>>> and bridged to ovirtmgmt for the management interface.
>>>
>>> I'm not sure its updated to version 4.2.0 but I followed this post:
>>> https://www.ovirt.org/documentation/how-to/networking/bondin
>>> g-vlan-bridge/
>>>
>>
>> It looks like an old howto, we will need to update or remove it.
>>
>>
>>>
>>> with this setting, the NetworkManager keep starting up on reboot,
>>> and the interfaces are not managed by oVirt (and the nice traffic graphs
>>> are not shown).
>>>
>>
>> For the interfaces to be owned by oVirt, you will need to add the host to
>> Engine.
>> So I would just configure everything up to the VLAN (slaves, bond, VLAN)
>> with NetworkManager prior to adding it to Engine. The bridge should be
>> created when you add the host.
>> (assuming the VLAN you mentioned is your management interface and its ip
>> is the one used by Engine)
>>
>>
>>>
>>>
>>>
>>>
>>> my question:
>>> Is  NetworkManager need to be disabled as in the above post?
>>>
>>
>> No (for 4.1 and 4.2)
>>
>> Do I need to manage the networking using (nmtui) NetworkManager?
>>>
>>
>> You better use cockpit or nmcli to configure the node before you add it
>> to Engine.
>>
>>
>>>
>>> Thanks!
>>> Maoz
>>>
>>>
>>>
>>>
>>>
>>> ___
>>> 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] NetworkManager with oVirt version 4.2.0

2018-02-04 Thread Edward Haas
You may be encountering this problem:
https://bugzilla.redhat.com/show_bug.cgi?id=1523661
If this is it, you have two options:
- Upgrade VDSM to latest 4.2.1.
- Define first the VLAN on one of the slaves, add the host to Engine and
then modify the network attachment by creating a bond through Engine.

Thanks,
Edy.

On Sun, Feb 4, 2018 at 9:30 AM, Edward Haas  wrote:

>
>
> On Sat, Feb 3, 2018 at 9:06 AM, maoz zadok  wrote:
>
>> Hello All,
>> I'm new to oVirt, I'm trying with no success to set up the networking on
>> an oVirt 4.2.0 node, and I think I'm missing something.
>>
>> background:
>> interfaces em1-4 is bonded to bond0
>> VLAN configured on bond0.1
>> and bridged to ovirtmgmt for the management interface.
>>
>> I'm not sure its updated to version 4.2.0 but I followed this post:
>> https://www.ovirt.org/documentation/how-to/networking/
>> bonding-vlan-bridge/
>>
>
> It looks like an old howto, we will need to update or remove it.
>
>
>>
>> with this setting, the NetworkManager keep starting up on reboot,
>> and the interfaces are not managed by oVirt (and the nice traffic graphs
>> are not shown).
>>
>
> For the interfaces to be owned by oVirt, you will need to add the host to
> Engine.
> So I would just configure everything up to the VLAN (slaves, bond, VLAN)
> with NetworkManager prior to adding it to Engine. The bridge should be
> created when you add the host.
> (assuming the VLAN you mentioned is your management interface and its ip
> is the one used by Engine)
>
>
>>
>>
>>
>>
>> my question:
>> Is  NetworkManager need to be disabled as in the above post?
>>
>
> No (for 4.1 and 4.2)
>
> Do I need to manage the networking using (nmtui) NetworkManager?
>>
>
> You better use cockpit or nmcli to configure the node before you add it to
> Engine.
>
>
>>
>> Thanks!
>> Maoz
>>
>>
>>
>>
>>
>> ___
>> 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] NetworkManager with oVirt version 4.2.0

2018-02-03 Thread Edward Haas
On Sat, Feb 3, 2018 at 9:06 AM, maoz zadok  wrote:

> Hello All,
> I'm new to oVirt, I'm trying with no success to set up the networking on
> an oVirt 4.2.0 node, and I think I'm missing something.
>
> background:
> interfaces em1-4 is bonded to bond0
> VLAN configured on bond0.1
> and bridged to ovirtmgmt for the management interface.
>
> I'm not sure its updated to version 4.2.0 but I followed this post:
> https://www.ovirt.org/documentation/how-to/networking/bonding-vlan-bridge/
>

It looks like an old howto, we will need to update or remove it.


>
> with this setting, the NetworkManager keep starting up on reboot,
> and the interfaces are not managed by oVirt (and the nice traffic graphs
> are not shown).
>

For the interfaces to be owned by oVirt, you will need to add the host to
Engine.
So I would just configure everything up to the VLAN (slaves, bond, VLAN)
with NetworkManager prior to adding it to Engine. The bridge should be
created when you add the host.
(assuming the VLAN you mentioned is your management interface and its ip is
the one used by Engine)


>
>
>
>
> my question:
> Is  NetworkManager need to be disabled as in the above post?
>

No (for 4.1 and 4.2)

Do I need to manage the networking using (nmtui) NetworkManager?
>

You better use cockpit or nmcli to configure the node before you add it to
Engine.


>
> Thanks!
> Maoz
>
>
>
>
>
> ___
> 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


[ovirt-users] NetworkManager with oVirt version 4.2.0

2018-02-02 Thread maoz zadok
Hello All,
I'm new to oVirt, I'm trying with no success to set up the networking on an
oVirt 4.2.0 node, and I think I'm missing something.

background:
interfaces em1-4 is bonded to bond0
VLAN configured on bond0.1
and bridged to ovirtmgmt for the management interface.

I'm not sure its updated to version 4.2.0 but I followed this post:
https://www.ovirt.org/documentation/how-to/networking/bonding-vlan-bridge/
with this setting, the NetworkManager keep starting up on reboot,
and the interfaces are not managed by oVirt (and the nice traffic graphs
are not shown).



my question:
Is  NetworkManager need to be disabled as in the above post?
Do I need to manage the networking using (nmtui) NetworkManager?

Thanks!
Maoz
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users