Hi Tim,
I'm glad to hear that you're already working on this. I must admit that
sometimes it's easier to ask you to give new features than fixing the
network topology (that grows most of the times without the proper
planning or without knowledge of future requirements), but as other
platforms hand
d Hat, Inc.
Brisbane, Australia
Email: thild...@redhat.com
Internal: 8588287
Mobile: +61 4 666 25242
IRC: thildred
- Original Message -
> From: "Juan Pablo Lorier"
> To: "Lior Vernia"
> Cc: users@ovirt.org
> Sent: Thursday, May 16, 2013 9:24:31 PM
> Subje
Hi Lior,
Thank you very much for your help. I'm sure things are improving and
fast thanks to the great job of the ovirt team. Right now I think that
using VLans is going to be the safest choice to me. I plan to move the
plataform into production before end of month so I'll stick to stable stuff.
I
Hello again Juan Pablo,
We're aware that the networking (among other things) in oVirt isn't
perfect, we're working on it :) As I had mentioned, the 3.2 release did
improve the network functionality, as well as make it much
user-friendlier, so an upgrade is recommended if possible. Also, in the
up-
Hi Lior
I did managed to get the mgmt network tagged so now I can use the same
interface for several networks. The thing now is that I also have two
networks I use for iscsi that I'd like to be able to use in the same
interface (not the mgmt one) in one of the hosts, but as this networks
are in vl
I went over the thread again, do I understand correctly that you've
managed to get ovirtmgmt VLAN-tagged and working? That's the hard part,
once there you should be able to tag all other networks through the
oVirt engine quite easily.
What Moti and I said about a non-VM network living together wit
Hi Lior,
Thanks for the tip. I don't know if I can move to 3.2 as the centos
repos are not there yet and I'm not quite sure of moving (compile 3.2)
to a version without "stable" dependencies for a system almost in
production.
I'm trying to move stuff into vlans so I can share the interfaces.
I'd l
Hello Juan Pablo,
If I'm correctly reading the configuration values in my database, non-VM
(AKA bridgless networks) are only enabled for 3.2 datacenters/clusters
onwards, so if upgrading is an option that should do the trick.
Otherwise, if it's important enough and you're feeling gutsy, it MIGHT
Hi René
It's grayed in both DC edit and cluster assign/unassign, and even when I
create a new network, I can't choose it not to be a VM network.
Regards,
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Hi,
Is VM Network grayed out in "Assign/Unassign Networks" windows in
clusters tab or is it grayed out in "Edit Logical Network" in data
centers tab?
Afaik you have to define vm network for a data center not for a cluster...
Regards,
René
On 05/13/2013 10:22 PM, Juan Pablo Lorier wrote:
H
Hi Itamar,
I've read the doc you pointed (actually I didn't look before in red hat,
just in ovirt world) but in the manual, vm option is not grayed as in my
3.1 management engine.
Do I have to tune something in the config so new networks are not VM
networks by default?
Regards,
__
On 05/13/2013 07:49 PM, Juan Pablo Lorier wrote:
Hi everyone,
Thank you all, you've been very helpfull. I have one more question; How
do I get a network not to be a VM network. If I create a new one, the VM
option is ticked and grayed so I can't untick it. The same thing with an
already created
Hi everyone,
Thank you all, you've been very helpfull. I have one more question; How
do I get a network not to be a VM network. If I create a new one, the VM
option is ticked and grayed so I can't untick it. The same thing with an
already created network.
Sorry for all this questions, but though I
- Original Message -
> From: "Gianluca Cecchi"
> To: "Juan Pablo Lorier"
> Cc: "users"
> Sent: Friday, May 10, 2013 5:21:50 PM
> Subject: Re: [Users] Vlan interface on top of bonding
>
> On Fri, May 10, 2013 at 4:12 PM, Juan Pablo Lo
On 05/09/2013 08:55 AM, Moti Asayag wrote:
- Original Message -
From: "René Koch"
To: "Juan Pablo Lorier"
Cc: users@ovirt.org
Sent: Wednesday, May 8, 2013 11:15:04 PM
Subject: Re: [Users] Vlan interface on top of bonding
Hi,
vlan tagging for ovirtmgmt inter
Hello,
To elaborate on what Gianluca and Moti said: Assuming you're using a
reasonable recent oVirt version (like from the past year), you should be
able to have VLAN networks reside together on the same NIC with ONE
non-VM, non-VLAN network.
By non-VLAN I mean that the VLAN tag checkbox is left
Hi Gianluca,
I have to confess that I didn't dig much more than I needed to get this
working, but in the web admin I was unable to mix untagged networks (I
have a couple to do iscsi on other bonds) with vlan interfaces. I
dragged a vlan network over the interface that already had one of this
untag
On Fri, May 10, 2013 at 4:12 PM, Juan Pablo Lorier wrote:
> Hi,
>
> thank you all for your help. I took a little time to try and test your
> guidelines and I've managed to get ovirmgmt tagged living together with
> other tagged lans over the same physical interface.
> I hope some day it can allow
Hi,
thank you all for your help. I took a little time to try and test your
guidelines and I've managed to get ovirmgmt tagged living together with
other tagged lans over the same physical interface.
I hope some day it can allow untagged and tagged networks over the same
interface.
Regards,
__
- Original Message -
> From: "René Koch"
> To: "Juan Pablo Lorier"
> Cc: users@ovirt.org
> Sent: Wednesday, May 8, 2013 11:15:04 PM
> Subject: Re: [Users] Vlan interface on top of bonding
>
> Hi,
>
> vlan tagging for ovirtmgmt int
On Wed, May 8, 2013 at 10:15 PM, René Koch wrote:
> Hi,
>
> vlan tagging for ovirtmgmt interface is a bit tricky.
>
> Here's how I do it:
> - configure vlan tag on host(s) and switch - imho not necessary to have a
> ovirtmgmt bridge available but vlan tagging configured for your ovirtmgmt
> netwo
om:Juan Pablo Lorier
> Sent: Wednesday 8th May 2013 21:14
> To: René Koch
> Cc: users@ovirt.org
> Subject: Re: [Users] Vlan interface on top of bonding
>
> Hi René,
>
> Tanks for your help. I've tried in the direction you pointed and I was
> able to share the bond among
Hi Gianluca,
Thanks for the help. I've already read those post you pointed but they
don't have the same problem. The key was in the reply of René that I
can't mix untugged and tagged networks (a pitty as it's quite common to
me in regular linux setups).
I'm now trying to get ovirtmgmt to be tagged
Hi René,
Tanks for your help. I've tried in the direction you pointed and I was
able to share the bond among other tagged networks. One of the problems
would be how to edit ovirtmgmt network now that it's created, I just
can't find in the way to do it by the web. I've tried starting a hole
new dat
On Wed, May 8, 2013 at 4:18 PM, Juan Pablo Lorier wrote:
> Hi,
>
> I'm new to ovirt and I'm dealing with network configuration. I have a
> host with a bonding of 4 eths and on top of that I added ovirtmgmt
> interface. I now want my vm to work on vlan 128 so I added the nic to
> ovirtmgmt bridge.
Hi,
first of all welcome to the oVirt project.
Did you configure vlan tagging for your ovirtmgmt network?
If you're using vlan tagging on (bonded) interfaces in oVirt you have to
add a vlan tag to all logical networks - can't mix tagged and untagged
logical networks.
e.g (same for bonds as well)
Hi,
I'm new to ovirt and I'm dealing with network configuration. I have a
host with a bonding of 4 eths and on top of that I added ovirtmgmt
interface. I now want my vm to work on vlan 128 so I added the nic to
ovirtmgmt bridge. I have access to vlan 1 (the bridge to the bond) but
even if I add th
27 matches
Mail list logo
