Interesting!
Seem also that debian will do low maintenance on ifupdown package
https://lists.debian.org/debian-devel/2015/05/msg00574.html
(So, I think that mean that they never will implement vlan-aware bridge or
vxlan. both are already implemented in ifupdown2)
Thanks for that link.
I need to do more test to see how it's works.
Interesting!
Seem also that debian will do low maintenance on ifupdown package
https://lists.debian.org/debian-devel/2015/05/msg00574.html
(So, I think that mean that they never will implement vlan-aware bridge or
vxlan. both are already
The vlan range feature in from kernel 4.0, it's only 3 small patches, I would
like to add them to current 3.19 kernel.
Any objection ?
No, that is OK for me.
Seem that cumulus guys are trying to push ifupdown2 as default for next debian
version.
It's backward compatible with current
My feeling is that the number of packages we need to maintain gets far too
high.
So if we go that way, we need to make sure that debian people will integrate
those changes.
I just tried iproute2 (4.0) package from debian stretch repository, it's
working fine.
The vlan range feature in from
Seem that they completly replace ifupdown by their own implementation in
python
https://github.com/CumulusNetworks/ifupdown2
so, I think I'll just take ideas from syntax, et reimplemented them in bash.
BTW, It could be wonderfull if we upgrade iproute2 to match the kernel version
Hi,
I have done test again with vlan aware bridges with my old patches, they seem
to works fine.
As debian don't provide yet /etc/network/interfaces syntax,
I have found that cumulus network linux have implemented it. (this is a distrib
for physical network switches)
Seem that they completly replace ifupdown by their own implementation in python
https://github.com/CumulusNetworks/ifupdown2
so, I think I'll just take ideas from syntax, et reimplemented them in bash.
BTW, It could be wonderfull if we upgrade iproute2 to match the kernel version
we used
Catch the error, if the dataset doesn't exists.
If it will not catched, you can't remove a VM.
---
PVE/Storage/ZFSPoolPlugin.pm | 3 +++
1 file changed, 3 insertions(+)
diff --git a/PVE/Storage/ZFSPoolPlugin.pm b/PVE/Storage/ZFSPoolPlugin.pm
index 6b095f1..d3bb0fd 100644
---
On Wed, 22 Jul 2015 09:08:05 +0200
Michael Rasmussen m...@datanom.net wrote:
Hi all,
Yesterday I created a VM which was assigned an ID that was reused from
a previous VM (the algorithm in proxmox). I added this new VM to a pool
and this morning I received this mail from the cron.daily.
On Thu, 23 Jul 2015 18:34:37 +0200 (CEST)
Dietmar Maurer diet...@proxmox.com wrote:
What is the content of /etc/pve/user.cfg ?
pool:test::124,127,142,129,107,119,136,106,105,133,126,120,134,146,108,135,140::
As you can see no 101 in the above.
--
Hilsen/Regards
Michael Rasmussen
Get my
On Wed, 22 Jul 2015 17:09:07 +0200 (CEST)
Dietmar Maurer diet...@proxmox.com wrote:
If so, this is a bug. Are you able to reproduce it?
This is very strange. I keep getting error mails regarding the
duplicate resource in pool test but displaying the pool in the gui
shows no sign of the
Oh, you want to implement it with openflow?
yes
Would be quite interesting tocompare firewall performance (openflow vs.
iptables) ...
the presentation said that it's scaling with number of rules :).
(I would like to compare with nftables too).
I think I'll have time to test this is some
+ my $cores = POSIX::sysconf(84);
I wonder if we should add the constant name _SC_NPROCESSORS_ONLN
somewhere in pve-common, though, instead of using the literal 84.
Though I guess as long as it's only used once...
(A comment stating that it actually is _SC_NPROCESSORS_ONLN would be
good
On Wed, Jul 22, 2015 at 04:54:51PM +0200, Dietmar Maurer wrote:
A minority of users requested that feature. So I guess we do not want to
'depend' on pigz.
Does debian have optional-dependencies? Anything that isn't default or
required at load-time would be better off there.
(In Arch I can
On 07/23/2015 09:10 AM, Wolfgang Bumiller wrote:
On Wed, Jul 22, 2015 at 04:54:51PM +0200, Dietmar Maurer wrote:
A minority of users requested that feature. So I guess we do not want to
'depend' on pigz.
Does debian have optional-dependencies? Anything that isn't default or
required at
On Wed, Jul 22, 2015 at 04:54:51PM +0200, Dietmar Maurer wrote:
A minority of users requested that feature. So I guess we do not want to
'depend' on pigz.
Does debian have optional-dependencies? Anything that isn't default or
required at load-time would be better off there.
Yes, it is
16 matches
Mail list logo
