[pve-devel] OpenVSwitch GUI

[Alexandre DERUMIER]

Ok, I found the problem, my openvswitch daemon started in S03 and not S01.
(Don't have checked that updating the packages don't have updated the start order).

So, all is working fine now !



----- Mail original ----- 

De: "Alexandre DERUMIER" <aderumier at odiso.com> 
À: "Dietmar Maurer" <dietmar at proxmox.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Dimanche 29 Décembre 2013 17:33:56 
Objet: Re: [pve-devel] OpenVSwitch GUI 

>>I need to test that again - I thought it works here (why is 'auto' not working?) 

This is strange, if I do after boot: 

#ifup vmbr10 

I have 
ifup: interface bond1 already configured 

(but I can't see any bond1 anywhere) 

then 

#ifdown vmbr10 
#ifup vmbr10 

and now it's ok ... 




----- Mail original ----- 

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Dimanche 29 Décembre 2013 16:17:39 
Objet: RE: OpenVSwitch GUI 

> >>That attribute is not needed, so I removed it. It only causes problems 
> >>because ovs-switchd tries to start that interface at wrong time when booting. 
> 
> How/when does it start ? (because the bridge don't start on my test server with 
> "auto vmbrxx" ) 

I need to test that again - I thought it works here (why is 'auto' not working?) 

> About tagging the default internal port, I found how to do it, we can just use 
> OVS_EXTRA, to execute ovs-vsctl extra commands) 
> 
> 
> here my test config, with non-starting bridge with auto 
> 
> auto vmbr10 
> iface vmbr10 inet static 
> address 10.7.0.40 
> netmask 255.255.255.0 
> broadcast 10.7.0.255 
> ovs_type OVSBridge 
> ovs_ports bond1 
> ovs_extra set port vmbr10 tag=100 

Ah - i see. 
_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel