They can be used like loopback, but not limited to only 1 interface.
It's needed for bgp with multipath/ecmp to have a unique src ip
Signed-off-by: Alexandre Derumier
---
src/PVE/INotify.pm | 4
1 file changed, 4 insertions(+)
diff --git a/src/PVE/INotify.pm b/src/PVE/INotify.pm
index bd2b
On 09.11.20 09:26, Alexandre Derumier wrote:
> "slaves" is deprecated (not even used in official debian docs),
> and ifupdown don't support it
> ---
> pve-network.adoc | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
>
applied, thanks!
___
On 08.11.20 15:19, Alexandre Derumier wrote:
> This patch series add basic subnets managements.
This did not apply, seems like the "add subnet plugin" stuff missed in general.
But, I had the previous version v10 somewhat cleaned up here (reduced to 25
patches)
from a month ago or so, so I pushed
On 18.11.20 11:04, Fabian Ebner wrote:
> Follow-up to/finishing up the partially-applied series:
> https://lists.proxmox.com/pipermail/pve-devel/2020-November/045929.html
>
> The first two patches extend the cluster resources API call to include the
> content types of a storage, and avoid dynamic
On 18.11.20 11:04, Fabian Ebner wrote:
> adapted from PBS. Main differences are:
> * loading of the prune-backups options from the storage configuration if
> configured
> * API has GET/DELETE distinction instead of 'dry-run'
> * API expects a single property string for the prune o
On 19.11.20 11:29, Fabian Ebner wrote:
> When using the path to request properties, and no ZFS file system is mounted
> at that path, ZFS will fall back to the parent filesystem:
>
>> # zfs unmount myzpool/subvol-172-disk-0
>> # zfs get mounted /myzpool/subvol-172-disk-0
>> NAME PROPERTY VALU
On 20.11.20 15:12, Dominik Csapak wrote:
> Adds the typical sectionconfig api entry points, as well as a basic
> CRUD ui under Datacenter -> Metric Server
>
> the next step is to adapt the documentation to no refer to editing the
> config anymore, adding some more useful information, as well
> as
Hi,
On 21.11.20 14:08, Pablo Ruiz wrote:
> Hi,
>
> I've just made a little custom storage plugin which basically
> overrides/extends ZFSPoolPluging so the pool name instead of being fixed,
> can be 'dynamically' guessed on each cluster node.
>
> While adding some new nodes to one of our current
Why not just rename the ZFS-dataset on the old server with "zfs rename"? Seems
to be much easier than implementing a separate feature.
-Ursprüngliche Nachricht-
Von: pve-devel [mailto:pve-devel-boun...@lists.proxmox.com] Im Auftrag von
Thomas Lamprecht
Gesendet: Montag, 23. November 2020
