Re: [pve-devel] Network configuration
On Wed, 22 Jul 2015 01:25:14 +0200
Michael Rasmussen m...@datanom.net wrote:
Hi all,
I have installed a proxmox 4.0 to test openvswitch and IMHO the current
network GUI config is not suited for the task since every time you need
to create or delete an OVSint Port a reboot of the node is required. I
will therefore propose a change in the GUI which allows creating or
deleting of OVSint Port without the need for a reboot of the node.
Creating OVS Bonds and OVS Bridges IMHO should still require a reboot
of the node since changes here is something rarely done after initial
configuration and changing configuration of this will break basic
networking on the node.
For the above I have decided on the following implementation:
OVS:
eval {
ovs-vsctl add-port $bridge vlan$port tag=$port -- set interface
vlan$port type=internal
};
die vlan$port: Could not add to bridge $bridge if ($@);
eval {
if ($ip and $mask) ? ifconfig vlan$port $ip netmask $mask up :
ifconfig vlan$port $ip up;
};
if ($@) {
ovs-vsctl del-port $bridge $port;
die vlan$port: Could not bring up interface;
}
eval {
update /etc/network/interfaces
};
if ($@) {
ifconfig vlan$port down;
ovs-vsctl del-port $bridge $port;
die vlan$port: Could not update network config;
};
Something missing above?
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael at rasmussen dot cc
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD3C9A00E
mir at datanom dot net
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE501F51C
mir at miras dot org
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE3E80917
--
/usr/games/fortune -es says:
He hath eaten me out of house and home.
-- William Shakespeare, Henry IV
pgpdAA6F09ZsO.pgp
Description: OpenPGP digital signature
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
eval {
ovs-vsctl add-port $bridge vlan$port tag=$port -- set interface
vlan$port type=internal
};
internal interface can have a random name.
also, we need to manage update. (ip modification for example).
we could do down, up . But it's not optimal.
- Mail original -
De: datanom.net m...@datanom.net
À: pve-devel pve-devel@pve.proxmox.com
Envoyé: Lundi 27 Juillet 2015 19:46:23
Objet: Re: [pve-devel] Network configuration
On Wed, 22 Jul 2015 01:25:14 +0200
Michael Rasmussen m...@datanom.net wrote:
Hi all,
I have installed a proxmox 4.0 to test openvswitch and IMHO the current
network GUI config is not suited for the task since every time you need
to create or delete an OVSint Port a reboot of the node is required. I
will therefore propose a change in the GUI which allows creating or
deleting of OVSint Port without the need for a reboot of the node.
Creating OVS Bonds and OVS Bridges IMHO should still require a reboot
of the node since changes here is something rarely done after initial
configuration and changing configuration of this will break basic
networking on the node.
For the above I have decided on the following implementation:
OVS:
eval {
ovs-vsctl add-port $bridge vlan$port tag=$port -- set interface
vlan$port type=internal
};
die vlan$port: Could not add to bridge $bridge if ($@);
eval {
if ($ip and $mask) ? ifconfig vlan$port $ip netmask $mask up :
ifconfig vlan$port $ip up;
};
if ($@) {
ovs-vsctl del-port $bridge $port;
die vlan$port: Could not bring up interface;
}
eval {
update /etc/network/interfaces
};
if ($@) {
ifconfig vlan$port down;
ovs-vsctl del-port $bridge $port;
die vlan$port: Could not update network config;
};
Something missing above?
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael at rasmussen dot cc
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD3C9A00E
mir at datanom dot net
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE501F51C
mir at miras dot org
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE3E80917
--
/usr/games/fortune -es says:
He hath eaten me out of house and home.
-- William Shakespeare, Henry IV
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
On Mon, 27 Jul 2015 20:08:24 +0200 (CEST)
Alexandre DERUMIER aderum...@odiso.com wrote:
eval {
ovs-vsctl add-port $bridge vlan$port tag=$port -- set interface
vlan$port type=internal
};
internal interface can have a random name.
I know, but to keep it simple and IMHO more intuitive use a descriptive
name.
also, we need to manage update. (ip modification for example).
we could do down, up . But it's not optimal.
How would you do it otherwise? The only way to change IP on an
interface which is up is to bring it down first, change IP, and then
bring it up again.
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael at rasmussen dot cc
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD3C9A00E
mir at datanom dot net
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE501F51C
mir at miras dot org
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE3E80917
--
/usr/games/fortune -es says:
He hated being thought of as one of those people that wore stupid
ornamental armour. It was gilt by association.
-- Terry Pratchett, Night Watch
pgpoS_SDgFqE7.pgp
Description: OpenPGP digital signature
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
we have done it for lxc container.
https://git.proxmox.com/?p=pve-container.git;a=blob_plain;f=src/PVE/LXC.pm;hb=HEAD
sub update_ipconfig {}
What I would like to do, is when in gui we have done the new config in
/etc/network/interfaces.new,
then apply it online.
So manage dependencies between ethX-bondX-vmbrX-tapX (and also ovs).
and manage in correct order remove/add of devices. (and maybe value update)
The main problem is ip change on bridge directly, because we can't shutdown it
if vms tap are plugged on it.
So we need to do it online.
We the ip is on an admin interface, it's not a problem to shutdown it.
- Mail original -
De: Martin Waschbüsch serv...@waschbuesch.it
À: datanom.net m...@datanom.net
Cc: aderumier aderum...@odiso.com, pve-devel pve-devel@pve.proxmox.com
Envoyé: Mardi 28 Juillet 2015 06:12:09
Objet: Re: [pve-devel] Network configuration
Am 27.07.2015 um 20:27 schrieb Michael Rasmussen m...@datanom.net:
On Mon, 27 Jul 2015 20:08:24 +0200 (CEST)
Alexandre DERUMIER aderum...@odiso.com wrote:
eval {
ovs-vsctl add-port $bridge vlan$port tag=$port -- set interface
vlan$port type=internal
};
internal interface can have a random name.
I know, but to keep it simple and IMHO more intuitive use a descriptive
name.
also, we need to manage update. (ip modification for example).
we could do down, up . But it's not optimal.
How would you do it otherwise? The only way to change IP on an
interface which is up is to bring it down first, change IP, and then
bring it up again.
Is it?
I thought you can do
ip addr del 192.168.1.1/32 dev eth0
to remove one IPv4
or
ip addr flush dev eth0
to remove all IPs?
This way, at least, the interface is not physically down, as you only modify a
single layer 3 protocol's properties.
Martin
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
Am 27.07.2015 um 20:27 schrieb Michael Rasmussen m...@datanom.net:
On Mon, 27 Jul 2015 20:08:24 +0200 (CEST)
Alexandre DERUMIER aderum...@odiso.com wrote:
eval {
ovs-vsctl add-port $bridge vlan$port tag=$port -- set interface
vlan$port type=internal
};
internal interface can have a random name.
I know, but to keep it simple and IMHO more intuitive use a descriptive
name.
also, we need to manage update. (ip modification for example).
we could do down, up . But it's not optimal.
How would you do it otherwise? The only way to change IP on an
interface which is up is to bring it down first, change IP, and then
bring it up again.
Is it?
I thought you can do
ip addr del 192.168.1.1/32 dev eth0
to remove one IPv4
or
ip addr flush dev eth0
to remove all IPs?
This way, at least, the interface is not physically down, as you only modify a
single layer 3 protocol's properties.
Martin
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
Many feature are not implemented in OVS (multicast snooping/querier, connection tracking, limited bond modes, iptables, ...), so why is OVS far superior? I would prefer to have missing bits implemented with linux bridge code. According to Alexandre's post much of this is coming in ovs 2.4 which should be available at the time of the release of Proxmox 4.0. really? i.e. can we use iptables with ovs? IMHO ovs is superior for two reasons: 1) vlans are linked to ports and not to bridges 2) it more closely resembles the physical world which means simpler to grasp PS. what is limited bond modes? Most standard linux bond modes are missing? And I never found a good documentation about the implemented bond modes - do you know any docs? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
What is your opinion to this suggestion? Can we implement that reliable? Second. If the above is implemented then in my opinion using openvswitch is far superior to Linux Bridge/Bond and gives greater flexibility while at the same time is more logical and simple in use in which case I propose that the installer change default network configuration to use openvswitch in proxmox 4.0. What is your opinion to this suggestion? I still prefer linux bridge, because it works without additional daemons. Many feature are not implemented in OVS (multicast snooping/querier, connection tracking, limited bond modes, iptables, ...), so why is OVS far superior? I would prefer to have missing bits implemented with linux bridge code. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
On Wed, 22 Jul 2015 17:17:58 +0200 (CEST) Dietmar Maurer diet...@proxmox.com wrote: Can we implement that reliable? I am positive. I guess the same applies to Linux bridge based vlans. I am willing to give it a try. I still prefer linux bridge, because it works without additional daemons. Many feature are not implemented in OVS (multicast snooping/querier, connection tracking, limited bond modes, iptables, ...), so why is OVS far superior? I would prefer to have missing bits implemented with linux bridge code. According to Alexandre's post much of this is coming in ovs 2.4 which should be available at the time of the release of Proxmox 4.0. IMHO ovs is superior for two reasons: 1) vlans are linked to ports and not to bridges 2) it more closely resembles the physical world which means simpler to grasp PS. what is limited bond modes? -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael at rasmussen dot cc http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD3C9A00E mir at datanom dot net http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE501F51C mir at miras dot org http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE3E80917 -- /usr/games/fortune -es says: Everybody is talking about the weather but nobody does anything about it. -- Mark Twain pgpxUsGryiBpR.pgp Description: OpenPGP digital signature ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
since kernel 3.10, it's possible to tag vlan by port on linux bridge too. I had sent patches last year. Maybe can I have a look with kernel 3.19,to see if it's still working fine ? Yes, please. This would simplify our setup. superior feature of ovs will be dpdk and vhost-user https://software.intel.com/en-us/blogs/2015/06/09/building-vhost-user-for-ovs-today-using-dpdk-200 So you would also prefer OVS by default? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
On Wed, 22 Jul 2015 18:14:07 +0200 (CEST) Dietmar Maurer diet...@proxmox.com wrote: really? i.e. can we use iptables with ovs? In 2.4 something similar are implemented: http://openvswitch.org/support/ovscon2014/17/1030-conntrack_nat.pdf Most standard linux bond modes are missing? And I never found a good documentation about the implemented bond modes - do you know any docs? Bonding Configuration: A port that has more than one interface is a ``bonded port.’’ Bonding allows for load balancing and fail-over. The following types of bonding will work with any kind of upstream switch. On the upstream switch, do not configure the interfaces as a bond: balance-slb Balances flows among slaves based on source MAC address and output VLAN, with periodic rebalancing as traffic patterns change. active-backup Assigns all flows to one slave, failing over to a backup slave when the active slave is disabled. This is the only bonding mode in which interfaces may be plugged into different upstream switches. The following modes require the upstream switch to support 802.3ad with successful LACP negotiation. If LACP negotiation fails and other-con‐ fig:lacp-fallback-ab is true, then active-backup mode is used: balance-tcp Balances flows among slaves based on L2, L3, and L4 pro‐ tocol information such as destination MAC address, IP address, and TCP port. http://openvswitch.org/support/dist-docs/ovs-vswitchd.conf.db.5.txt balance-slb ~≃ balance-tlb (mode 5) active-backup = active-backup (mode 1) balance-tcp ~= 802.3ad (mode 4) What more modes do you miss? -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael at rasmussen dot cc http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD3C9A00E mir at datanom dot net http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE501F51C mir at miras dot org http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE3E80917 -- /usr/games/fortune -es says: Journalism is literature in a hurry. -- Matthew Arnold pgp6wNMZBNMX2.pgp Description: OpenPGP digital signature ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
On Wed, 22 Jul 2015 19:06:52 +0200 Michael Rasmussen m...@datanom.net wrote: balance-slb ~≃ balance-tlb (mode 5) active-backup = active-backup (mode 1) balance-tcp ~= 802.3ad (mode 4) What more modes do you miss? Forgot to mention I have made an example available on the wiki using bond + balance-slb which imitates the default setup by the proxmox installer: https://pve.proxmox.com/wiki/Open_vSwitch#Example_3:_Bond_.2B_Bridge_.2B_Internal_Ports_.2B_Untagged_traffic_.2B_No_LACP -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael at rasmussen dot cc http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD3C9A00E mir at datanom dot net http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE501F51C mir at miras dot org http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE3E80917 -- /usr/games/fortune -es says: If it's Tuesday, this must be someone else's fortune. pgp7NeyN6fCng.pgp Description: OpenPGP digital signature ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
really? i.e. can we use iptables with ovs? In 2.4 something similar are implemented: http://openvswitch.org/support/ovscon2014/17/1030-conntrack_nat.pdf That is just an interface to the conntrack module - not really related to iptables? We need iptables for our firewall implementation. http://openvswitch.org/support/dist-docs/ovs-vswitchd.conf.db.5.txt balance-slb ~≃ balance-tlb (mode 5) active-backup = active-backup (mode 1) balance-tcp ~= 802.3ad (mode 4) Linux has a few more modes. But you are right, above modes are most commonly used. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
IMHO ovs is superior for two reasons: 1) vlans are linked to ports and not to bridges 2) it more closely resembles the physical world which means simpler to grasp since kernel 3.10, it's possible to tag vlan by port on linux bridge too. I had sent patches last year. Maybe can I have a look with kernel 3.19,to see if it's still working fine ? superior feature of ovs will be dpdk and vhost-user https://software.intel.com/en-us/blogs/2015/06/09/building-vhost-user-for-ovs-today-using-dpdk-200 - Mail original - De: datanom.net m...@datanom.net À: dietmar diet...@proxmox.com, pve-devel pve-devel@pve.proxmox.com Envoyé: Mercredi 22 Juillet 2015 17:52:11 Objet: Re: [pve-devel] Network configuration On Wed, 22 Jul 2015 17:17:58 +0200 (CEST) Dietmar Maurer diet...@proxmox.com wrote: Can we implement that reliable? I am positive. I guess the same applies to Linux bridge based vlans. I am willing to give it a try. I still prefer linux bridge, because it works without additional daemons. Many feature are not implemented in OVS (multicast snooping/querier, connection tracking, limited bond modes, iptables, ...), so why is OVS far superior? I would prefer to have missing bits implemented with linux bridge code. According to Alexandre's post much of this is coming in ovs 2.4 which should be available at the time of the release of Proxmox 4.0. IMHO ovs is superior for two reasons: 1) vlans are linked to ports and not to bridges 2) it more closely resembles the physical world which means simpler to grasp PS. what is limited bond modes? -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael at rasmussen dot cc http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD3C9A00E mir at datanom dot net http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE501F51C mir at miras dot org http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE3E80917 -- /usr/games/fortune -es says: Everybody is talking about the weather but nobody does anything about it. -- Mark Twain ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
Forgot to mention I have made an example available on the wiki using bond + balance-slb which imitates the default setup by the proxmox installer: https://pve.proxmox.com/wiki/Open_vSwitch#Example_3:_Bond_.2B_Bridge_.2B_Internal_Ports_.2B_Untagged_traffic_.2B_No_LACP Thanks. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
I don't have any objection. (now that everybody will use a recent kernel, it should work fine). But maybe wait for ovs 2.4 (should come very soon) http://openvswitch.org/pipermail/announce/2015-June/74.html - Native Linux kernel STT support - Geneve tunneling - DPDK vhost and tunneling - OpenFlow 1.4 bundles (flow transactions) - Bash command completion - RSTP - Multicast snooping - Support for Linux kernels up to 4.0.x multicast snooping, DPDK vhost and tunneling are 2 good features. - Mail original - De: aderumier aderum...@odiso.com À: datanom.net m...@datanom.net Cc: pve-devel pve-devel@pve.proxmox.com Envoyé: Mercredi 22 Juillet 2015 10:26:49 Objet: Re: [pve-devel] Network configuration Hi all, I have installed a proxmox 4.0 to test openvswitch and IMHO the current network GUI config is not suited for the task since every time you need to create or delete an OVSint Port a reboot of the node is required. I will therefore propose a change in the GUI which allows creating or deleting of OVSint Port without the need for a reboot of the node. Creating OVS Bonds and OVS Bridges IMHO should still require a reboot of the node since changes here is something rarely done after initial configuration and changing configuration of this will break basic networking on the node. What is your opinion to this suggestion? I Agree that GUI could be improve to change network online (if possible), both for ovs and linux bridge. I have had a lot of requests about it during my trainings. Second. If the above is implemented then in my opinion using openvswitch is far superior to Linux Bridge/Bond and gives greater flexibility while at the same time is more logical and simple in use in which case I propose that the installer change default network configuration to use openvswitch in proxmox 4.0. What is your opinion to this suggestion? I don't have any objection. (now that everybody will use a recent kernel, it should work fine). Having bonding and vlan setup in installer could be a big improvement too ! - Mail original - De: datanom.net m...@datanom.net À: pve-devel pve-devel@pve.proxmox.com Envoyé: Mercredi 22 Juillet 2015 01:25:14 Objet: [pve-devel] Network configuration Hi all, I have installed a proxmox 4.0 to test openvswitch and IMHO the current network GUI config is not suited for the task since every time you need to create or delete an OVSint Port a reboot of the node is required. I will therefore propose a change in the GUI which allows creating or deleting of OVSint Port without the need for a reboot of the node. Creating OVS Bonds and OVS Bridges IMHO should still require a reboot of the node since changes here is something rarely done after initial configuration and changing configuration of this will break basic networking on the node. What is your opinion to this suggestion? Second. If the above is implemented then in my opinion using openvswitch is far superior to Linux Bridge/Bond and gives greater flexibility while at the same time is more logical and simple in use in which case I propose that the installer change default network configuration to use openvswitch in proxmox 4.0. What is your opinion to this suggestion? -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael at rasmussen dot cc http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD3C9A00E mir at datanom dot net http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE501F51C mir at miras dot org http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE3E80917 -- /usr/games/fortune -es says: You are here: *** *** * *** * *** * But you're not all there. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
Hi all, I have installed a proxmox 4.0 to test openvswitch and IMHO the current network GUI config is not suited for the task since every time you need to create or delete an OVSint Port a reboot of the node is required. I will therefore propose a change in the GUI which allows creating or deleting of OVSint Port without the need for a reboot of the node. Creating OVS Bonds and OVS Bridges IMHO should still require a reboot of the node since changes here is something rarely done after initial configuration and changing configuration of this will break basic networking on the node. What is your opinion to this suggestion? I Agree that GUI could be improve to change network online (if possible), both for ovs and linux bridge. I have had a lot of requests about it during my trainings. Second. If the above is implemented then in my opinion using openvswitch is far superior to Linux Bridge/Bond and gives greater flexibility while at the same time is more logical and simple in use in which case I propose that the installer change default network configuration to use openvswitch in proxmox 4.0. What is your opinion to this suggestion? I don't have any objection. (now that everybody will use a recent kernel, it should work fine). Having bonding and vlan setup in installer could be a big improvement too ! - Mail original - De: datanom.net m...@datanom.net À: pve-devel pve-devel@pve.proxmox.com Envoyé: Mercredi 22 Juillet 2015 01:25:14 Objet: [pve-devel] Network configuration Hi all, I have installed a proxmox 4.0 to test openvswitch and IMHO the current network GUI config is not suited for the task since every time you need to create or delete an OVSint Port a reboot of the node is required. I will therefore propose a change in the GUI which allows creating or deleting of OVSint Port without the need for a reboot of the node. Creating OVS Bonds and OVS Bridges IMHO should still require a reboot of the node since changes here is something rarely done after initial configuration and changing configuration of this will break basic networking on the node. What is your opinion to this suggestion? Second. If the above is implemented then in my opinion using openvswitch is far superior to Linux Bridge/Bond and gives greater flexibility while at the same time is more logical and simple in use in which case I propose that the installer change default network configuration to use openvswitch in proxmox 4.0. What is your opinion to this suggestion? -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael at rasmussen dot cc http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD3C9A00E mir at datanom dot net http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE501F51C mir at miras dot org http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE3E80917 -- /usr/games/fortune -es says: You are here: *** *** * *** * *** * But you're not all there. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
在 2015年7月22日，下午4:26，Alexandre DERUMIER aderum...@odiso.com 写道： Having bonding and vlan setup in installer could be a big improvement too ! this will be great! ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Network configuration
I had problems with DRBD 8.4.5 using dedicated NICs in linux-bridge (NIC-to-NIC) and in mode balance-rr and OVS IntPort for the LAN communication, and DRBD don't work correctly. I have not tried DRBD if OVS is configured for the LAN without OVS IntPort, simply i changed the LAN communication from OVS to linux-bridge, and DRBD worked out as expected. - Original Message - From: Michael Rasmussen m...@datanom.net To: pve-devel@pve.proxmox.com Sent: Tuesday, July 21, 2015 7:25 PM Subject: [pve-devel] Network configuration Second. If the above is implemented then in my opinion using openvswitch is far superior to Linux Bridge/Bond and gives greater flexibility while at the same time is more logical and simple in use in which case I propose that the installer change default network configuration to use openvswitch in proxmox 4.0. What is your opinion to this suggestion? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
