[pve-devel] [PATCH 2/3] vznetaddbr perl version
Alexandre DERUMIER
aderumier at odiso.com
Tue Jun 3 10:22:53 CEST 2014
>>I guess we should have a cleanup method in PVE::Tools which does the same job:
>>sub cleanup_vm_network {
>>my $vmid = shift;
>># should read /proc/net/dev to get a list of devices ...
>>}
>>What do you think?
this patch do tap_plug|tap_unplug , but not bridge cleanup.
So I need to read openvz config file
----- Mail original -----
De: "Dietmar Maurer" <dietmar at proxmox.com>
À: "Alexandre Derumier" <aderumier at odiso.com>, pve-devel at pve.proxmox.com
Envoyé: Mardi 3 Juin 2014 08:47:28
Objet: RE: [pve-devel] [PATCH 2/3] vznetaddbr perl version
Applied, although this introduces a dependency bug, because it depends on pve-manager.
I guess we should have a cleanup method in PVE::Tools which does the same job:
sub cleanup_vm_network {
my $vmid = shift;
# should read /proc/net/dev to get a list of devices ...
}
What do you think?
> diff --git a/debian/vznetaddbr b/debian/vznetaddbr new file mode 100755 index
> 0000000..7c394a2
> --- /dev/null
> +++ b/debian/vznetaddbr
> @@ -0,0 +1,69 @@
> +#!/usr/bin/perl
> +use strict;
> +use warnings;
# PVE::OpenVZ is part of pve-manager
> +use PVE::OpenVZ;
> +use PVE::Tools qw(run_command);
> +use PVE::Network;
> +use PVE::ProcFSTools;
More information about the pve-devel
mailing list