Re: [PVE-User] VLAN and 4.2 upgrade

2016-05-09 Thread Laurent CARON 

My bad.

I forgot to:

dpkg --purge vzctl

After running it, it works wonderfully.

/etc/network/if-up.d/vzifup-post was the culpirt.

Sorry for the noise.

On 06/05/2016 17:05, Dietmar Maurer wrote:

The corresponding if-up/if-down scripts are here:

/etc/network/if-post-down.d/vlan
/etc/network/if-pre-up.d/vlan



On May 6, 2016 at 1:35 PM Laurent CARON  wrote:


On 06/05/2016 12:50, Dietmar Maurer wrote:

Is there really no way we can re-introduce the native debian VLAN config ?


AFAIK VLAN still works as before (we just not use the deprecated vconfig
package).



Unfortunately not

The following stanzas in :/etc/network/interfaces:

auto vlan136
iface vlan136 inet manual
 vlan-raw-device eth1


auto vmbr136
iface vmbr136 inet manual
 bridge_ports vlan136
 bridge_stp off
 bridge_fd 0

# ifup vlan136 results in:
Failed to bring up vlan136

Is there a way you could not have a conflict between pve-manager and vlan ?

Thanks




!DSPAM:572cb2e334831305710144!



___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] VLAN and 4.2 upgrade

2016-05-06 Thread Adam Thompson 



On 16-05-06 02:30 PM, Adam Thompson wrote:

On 16-05-06 10:03 AM, Michael Rasmussen wrote:

On Fri, 6 May 2016 09:22:56 -0500
Adam Thompson  wrote:

Has this bug 
(http://openvswitch.org/pipermail/discuss/2015-July/018242.html) 
ever been found & fixed?
If not, using OVS in this scenario will still break your cluster 
horribly.

It causes no problem whatsoever with a single non-clustered host.
Also, AFAIK, OVS *still* doesn't implement an IGMP querier, so if 
you were relying on the Linux Bridge IGMP querier (like I am), 
you're screwed there, too.  (My switches support IGMP snooping, but 
my router doesn't have an IGMP querier.)



What kind of switch do you have?


A pair of NetGear GS752TXS switches.
They do have an IGMP querier feature, but AFAIK it is only active when 
you've configured them as the router (layer 3 functions), and I'm only 
using them as layer 2 devices because the L3 implementation is, um, 
not useful.  IGMP snooping works properly in L2 mode regardless.


The router/firewall is pfSense, which does IGMP proxying, but 
apparently not querying... or at least not correctly :-/.


-Adam



Well, as usual, I figured out how to make the switch act as a querier 
and NOT a router about 60 seconds after I hit send.

Aaargh.  So that's a non-issue now.

On the other hand, I still have concerns about the way OVS was handling 
multicast packet checksums incorrectly, which was causing cluster failures.


-Adam
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] VLAN and 4.2 upgrade

2016-05-06 Thread Adam Thompson 

On 16-05-06 10:03 AM, Michael Rasmussen wrote:

On Fri, 6 May 2016 09:22:56 -0500
Adam Thompson  wrote:


Has this bug (http://openvswitch.org/pipermail/discuss/2015-July/018242.html) ever 
been found & fixed?
If not, using OVS in this scenario will still break your cluster horribly.
It causes no problem whatsoever with a single non-clustered host.
Also, AFAIK, OVS *still* doesn't implement an IGMP querier, so if you were 
relying on the Linux Bridge IGMP querier (like I am), you're screwed there, 
too.  (My switches support IGMP snooping, but my router doesn't have an IGMP 
querier.)


What kind of switch do you have?


A pair of NetGear GS752TXS switches.
They do have an IGMP querier feature, but AFAIK it is only active when 
you've configured them as the router (layer 3 functions), and I'm only 
using them as layer 2 devices because the L3 implementation is, um, not 
useful.  IGMP snooping works properly in L2 mode regardless.


The router/firewall is pfSense, which does IGMP proxying, but apparently 
not querying... or at least not correctly :-/.


-Adam

___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] VLAN and 4.2 upgrade

2016-05-06 Thread Michael Rasmussen 
On Fri, 6 May 2016 09:22:56 -0500
Adam Thompson  wrote:

> Has this bug (http://openvswitch.org/pipermail/discuss/2015-July/018242.html) 
> ever been found & fixed?
> If not, using OVS in this scenario will still break your cluster horribly.
> It causes no problem whatsoever with a single non-clustered host.
> Also, AFAIK, OVS *still* doesn't implement an IGMP querier, so if you were 
> relying on the Linux Bridge IGMP querier (like I am), you're screwed there, 
> too.  (My switches support IGMP snooping, but my router doesn't have an IGMP 
> querier.)
> 
What kind of switch do you have?


-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
--
/usr/games/fortune -es says:
Sigh.  I like to think it's just the Linux people who want to be on
the "leading edge" so bad they walk right off the precipice.
(Craig E. Groeschel)


pgppVD8pSzVlq.pgp
Description: OpenPGP digital signature
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] VLAN and 4.2 upgrade

2016-05-06 Thread Dietmar Maurer 
The corresponding if-up/if-down scripts are here:

/etc/network/if-post-down.d/vlan
/etc/network/if-pre-up.d/vlan


> On May 6, 2016 at 1:35 PM Laurent CARON  wrote:
> 
> 
> On 06/05/2016 12:50, Dietmar Maurer wrote:
> >> Is there really no way we can re-introduce the native debian VLAN config ?
> >
> > AFAIK VLAN still works as before (we just not use the deprecated vconfig
> > package).
> >
> 
> Unfortunately not
> 
> The following stanzas in :/etc/network/interfaces:
> 
> auto vlan136
> iface vlan136 inet manual
>  vlan-raw-device eth1
> 
> 
> auto vmbr136
> iface vmbr136 inet manual
>  bridge_ports vlan136
>  bridge_stp off
>  bridge_fd 0
> 
> # ifup vlan136 results in:
> Failed to bring up vlan136
> 
> Is there a way you could not have a conflict between pve-manager and vlan ?
> 
> Thanks
> 

___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] VLAN and 4.2 upgrade

2016-05-06 Thread Dietmar Maurer 
> # ifup vlan136 results in:
> Failed to bring up vlan136

works for me...

___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] VLAN and 4.2 upgrade

2016-05-06 Thread Adam Thompson 
Has this bug 
(http://openvswitch.org/pipermail/discuss/2015-July/018242.html) ever 
been found & fixed?

If not, using OVS in this scenario will still break your cluster horribly.
It causes no problem whatsoever with a single non-clustered host.
Also, AFAIK, OVS *still* doesn't implement an IGMP querier, so if you 
were relying on the Linux Bridge IGMP querier (like I am), you're 
screwed there, too.  (My switches support IGMP snooping, but my router 
doesn't have an IGMP querier.)


I guess I'm not upgrading to 4.x anytime soon :-(.

-Adam


On 16-05-06 04:21 AM, lyt_yudi wrote:

hi

recommend you use this mode:

http://pve.proxmox.com/wiki/Open_vSwitch 


Example 2: Bond + Bridge + Internal Ports



在 2016年5月6日，下午4:59，Laurent CARON  写道：

Hi,

I'm running a 3.4 cluster and am planning the upgrade.

It seem the vlan package will be removed upon upgrade (vlan is in conflict with 
pve-manager).

I've got the following /etc/network/interfaces config (on proxmox hosts):

auto bond1
iface bond1 inet manual
slaves eth8 eth9
bond-miimon 100
bond-downdelay 200
bond-updelay 200
bond-mode 802.3ad

auto vlan34
iface vlan34 inet manual
vlan-raw-device bond1

auto vmbr34
iface vmbr34 inet manual
bridge_ports vlan34
bridge_stp off
bridge_fd 0

The ports on the switch are trunk ports carrying all VLANs used by my VMs.

I'm then using vmbr34 interface as a network interface on my hosts.

Will it be supported with proxmox 4 (since the vlan package will be removed) ?

Thanks
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user


___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] VLAN and 4.2 upgrade

2016-05-06 Thread Laurent CARON 

On 06/05/2016 12:50, Dietmar Maurer wrote:

Is there really no way we can re-introduce the native debian VLAN config ?


AFAIK VLAN still works as before (we just not use the deprecated vconfig
package).



Unfortunately not

The following stanzas in :/etc/network/interfaces:

auto vlan136
iface vlan136 inet manual
vlan-raw-device eth1


auto vmbr136
iface vmbr136 inet manual
bridge_ports vlan136
bridge_stp off
bridge_fd 0

# ifup vlan136 results in:
Failed to bring up vlan136

Is there a way you could not have a conflict between pve-manager and vlan ?

Thanks
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] VLAN and 4.2 upgrade

2016-05-06 Thread Dietmar Maurer 
> Is there really no way we can re-introduce the native debian VLAN config ?

AFAIK VLAN still works as before (we just not use the deprecated vconfig
package).

___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] VLAN and 4.2 upgrade

2016-05-06 Thread Laurent CARON 

On 06/05/2016 11:21, lyt_yudi wrote:

hi

recommend you use this mode:

http://pve.proxmox.com/wiki/Open_vSwitch 



This is quite a nightmare to have to use a v-switch to simply use VLANs.

Is there really no way we can re-introduce the native debian VLAN config ?

Thanks

___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] VLAN and 4.2 upgrade

2016-05-06 Thread lyt_yudi 
hi

recommend you use this mode:

http://pve.proxmox.com/wiki/Open_vSwitch 


Example 2: Bond + Bridge + Internal Ports


> 在 2016年5月6日，下午4:59，Laurent CARON  写道：
> 
> Hi,
> 
> I'm running a 3.4 cluster and am planning the upgrade.
> 
> It seem the vlan package will be removed upon upgrade (vlan is in conflict 
> with pve-manager).
> 
> I've got the following /etc/network/interfaces config (on proxmox hosts):
> 
> auto bond1
> iface bond1 inet manual
>slaves eth8 eth9
>bond-miimon 100
>bond-downdelay 200
>bond-updelay 200
>bond-mode 802.3ad
> 
> auto vlan34
> iface vlan34 inet manual
>vlan-raw-device bond1
> 
> auto vmbr34
> iface vmbr34 inet manual
>bridge_ports vlan34
>bridge_stp off
>bridge_fd 0
> 
> The ports on the switch are trunk ports carrying all VLANs used by my VMs.
> 
> I'm then using vmbr34 interface as a network interface on my hosts.
> 
> Will it be supported with proxmox 4 (since the vlan package will be removed) ?
> 
> Thanks
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

[PVE-User] VLAN and 4.2 upgrade

2016-05-06 Thread Laurent CARON 

Hi,

I'm running a 3.4 cluster and am planning the upgrade.

It seem the vlan package will be removed upon upgrade (vlan is in 
conflict with pve-manager).


I've got the following /etc/network/interfaces config (on proxmox hosts):

auto bond1
iface bond1 inet manual
slaves eth8 eth9
bond-miimon 100
bond-downdelay 200
bond-updelay 200
bond-mode 802.3ad

auto vlan34
iface vlan34 inet manual
vlan-raw-device bond1

auto vmbr34
iface vmbr34 inet manual
bridge_ports vlan34
bridge_stp off
bridge_fd 0

The ports on the switch are trunk ports carrying all VLANs used by my VMs.

I'm then using vmbr34 interface as a network interface on my hosts.

Will it be supported with proxmox 4 (since the vlan package will be 
removed) ?


Thanks
___
pve-user mailing list
pve-user@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user