Apply after my others ipv6 patches
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
We need to check also the ipversion of venet0,
to avoid to try to create ipv4 rules in ip6tables
Signed-off-by: Alexandre Derumier
---
src/PVE/Firewall.pm |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/PVE/Firewall.pm b/src/PVE/Firewall.pm
index 8325b25..a58f815 1
Hi,
here the ebtables patches, details are in commits.
Please comment, feel free to change and adapt them.
(I'm going to holiday Friday, so I'll don't have too much time to improve them
this week)
___
pve-devel mailing list
pve-devel@pve.proxmox.com
need ebtables-save && ebtables-restore, ebtables debian package don't include
them.
ebtables-restore need to restore the full ruleset (atomicaly),
so we can't update only 1 chain
Signed-off-by: Alexandre Derumier
---
src/PVE/Firewall.pm | 103 +
-A FORWARD -j PVEFW-FORWARD
-A PVEFW-FORWARD -p IPv4 -j ACCEPT #filter mac in iptables for ipv4, so we
can speedup rules with conntrack established
-A PVEFW-FORWARD -p IPv6 -j ACCEPT
-A PVEFW-FORWARD -o fwln+ -j PVEFW-FWBR-OUT
-A PVEFW-FWBR-OUT -i tap110i0 -j tap110i0-OUT
Corosync with sheepdog has 2 major problem :
- corosync is limited to a "small" numbers of nodes ( technically not a
problem, on "small" clusters )
- under heavy load, network fragmentation will appear
The problems and the descriptions are on the sheepdog mailing lists.
Thanks for the hard wor
> That's fine. The reason it would not apply to 2.6.32 is that I only made the
> changes to the 3.10 kernel because I suspected that changes to
> 2.6.32 of this kind was not appropriate due to the near end of life for kernel
> 2.6.32.
Ah, I see. Just applied the patch to 3.10.0.
_
applied, thanks!
> -Original Message-
> From: pve-devel [mailto:pve-devel-boun...@pve.proxmox.com] On Behalf
> Of Alexandre Derumier
> Sent: Montag, 30. Juni 2014 05:50
> To: pve-devel@pve.proxmox.com
> Subject: [pve-devel] pve-sheepdog : bump to 0.8.2
>
> bump to 0.8.2 and add zookeeper
On Mon, 14 Jul 2014 11:05:57 +
Dietmar Maurer wrote:
> Your patch does not apply to current version in git. So I simply extracted
> your changes and applied it myself - hope that is OK for you?
>
That's fine. The reason it would not apply to 2.6.32 is that I only made
the changes to the 3.1
Your patch does not apply to current version in git. So I simply extracted your
changes and applied it myself - hope that is OK for you?
see
https://git.proxmox.com/?p=pve-kernel-2.6.32.git;a=commitdiff;h=fb3948c5044b6af685050325630f3540ab24b57c
> diff --git a/Makefile b/Makefile
> index 3e2c1b
>> also add zookeeper support
>>I wonder why we need that? I found this at
>>https://github.com/sheepdog/sheepdog/wiki/Cluster-Management-Backends-and-dual-NIC:
>>
I just add support to zooker because some user request it. (So, it they want to
manually enable it, they can, without need to rec
> also add zookeeper support
I wonder why we need that? I found this at
https://github.com/sheepdog/sheepdog/wiki/Cluster-Management-Backends-and-dual-NIC:
>> Corosync is not recommended for production use as the method used for
>> synchronization is susceptible to packet loss under load. For r
> After an immense work of translation and proofreading, I have revised the
> "es.po" file and is ready. Please tell me how i will can give you the "es.po"
> file.
Simply post the file to this list.
> Also, i suggest that you do some changes of structure.
>
> 1- In the Tag "Options" of any VM, i
13 matches
Mail list logo
