Hi Mike,
I'd like to say that though setting ovirtmgmt as non vm as a default
should be nice, it won't be enough as it won't allow to use mixed
traffic in other interfaces either, so the way I see it, the fix should
be to add this ability to ovirt. I can't make my mind to think what a
big
On 26/01/14 15:40, Mike Kolesnik wrote:
- Original Message -
On 01/23/2014 08:34 PM, Juan Pablo Lorier wrote:
Hi Itamar,
I don't know if I get your post right, but to me, it seems that if so
many users hit the same rock, it should mean that this should be
documented somewhere
On 23/01/14 18:35, Itamar Heim wrote:
On 01/23/2014 05:59 PM, Assaf Muller wrote:
If you enable VLAN tagging on the management network, which is configured
on eth0 (Which also provides internet access from my understanding) then
you will connectivity as (I assume) your physical switches
- Original Message -
On 01/23/2014 08:34 PM, Juan Pablo Lorier wrote:
Hi Itamar,
I don't know if I get your post right, but to me, it seems that if so
many users hit the same rock, it should mean that this should be
documented somewhere visible and in my opinion, push on getting
If you enable VLAN tagging on the management network, which is configured
on eth0 (Which also provides internet access from my understanding) then
you will connectivity as (I assume) your physical switches aren't configured
for VLANs.
For an all-in-one, what I would suggest is the following
On Thu, 23 Jan 2014 10:59:57 -0500 (EST) Assaf wrote:
AM If you enable VLAN tagging on the management network, which is
AM configured on eth0 (Which also provides internet access from my
AM understanding) then you will connectivity as (I assume) your physical
AM switches aren't configured for
Hi Robert,
You can use mgmt untagged but if it's a non-vm network. If you tag mgmt
network, ovirt will configure a vlan interface and add it to ovirtmgmt,
so you'll get a disruption when network gets restarted to take the changes.
Regards,
___
Users
Hi Itamar,
I don't know if I get your post right, but to me, it seems that if so
many users hit the same rock, it should mean that this should be
documented somewhere visible and in my opinion, push on getting bug
1049476 https://bugzilla.redhat.com/show_bug.cgi?id=1049476 solved asap.
Regards,
Sorry, privY on eth1.
Assaf Muller, Cloud Networking Engineer
Red Hat
- Original Message -
From: Robert Story rst...@tislabs.com
To: Assaf Muller amul...@redhat.com
Cc: users users@ovirt.org
Sent: Thursday, January 23, 2014 7:11:50 PM
Subject: Re: [Users] networking: basic vlan help
What is the purpose of PubY on eth1?
Assaf Muller, Cloud Networking Engineer
Red Hat
- Original Message -
From: Robert Story rst...@tislabs.com
To: Assaf Muller amul...@redhat.com
Cc: users users@ovirt.org
Sent: Thursday, January 23, 2014 7:11:50 PM
Subject: Re: [Users] networking
On Thu, 23 Jan 2014 13:33:07 -0500 (EST) Assaf wrote:
AM Sorry, privY on eth1.
For VM to VM communication that doesn't need to go over the public net..
Robert
--
Senior Software Engineer @ Parsons
signature.asc
Description: PGP signature
___
Users
once you've decided to do so.
Assaf Muller, Cloud Networking Engineer
Red Hat
- Original Message -
From: Robert Story rst...@tislabs.com
To: Assaf Muller amul...@redhat.com
Cc: users users@ovirt.org
Sent: Thursday, January 23, 2014 8:41:43 PM
Subject: Re: [Users] networking: basic vlan
Hi Robert,
As I said before, you'll have network disruptions everytime you change
network topology and that's not because of ovirt but because you need to
restart network to set the new interfaces, routing tables and addresses,
etc.
This does not mean that you loose access to your hosts, if
On 01/23/2014 08:34 PM, Juan Pablo Lorier wrote:
Hi Itamar,
I don't know if I get your post right, but to me, it seems that if so
many users hit the same rock, it should mean that this should be
documented somewhere visible and in my opinion, push on getting bug
1049476
14 matches
Mail list logo
