[pve-devel] [PATCH v1 series 0/5] limit out and inrate of network device

[Hannes Laimer]

'rate' is split into 'outrate' and 'inrate', so the upload and download
limit can be set individually. Old configs containing just 'rate' are
mapped to out/inrate. After opening the edit dialog in the gui 'rate'
will be removed from the config and out/inrate are added. In the WebUI
the field Rate is also replace with the two new fields.
Since we can only set rules for the tap-device in the host system, we
are only able to limit the downloadrate of the VM accuratelly(egress of
tap). Setting an uploadrate limit is neither precise nor consistent due
to the nature of ingress traffic shaping(ingress of tap/outrate of VM)

pve-common: Hannes Laimer (2):
  replace rate with out/in-rate in setup_tc_rate_limit and
    tap_rate_limit
  add out/in-rate parameter to tap_plug sub, keep version with just rate
    param

 src/PVE/Network.pm | 43 +++++++++++++++++++++++++++----------------
 1 file changed, 27 insertions(+), 16 deletions(-)


pve-network: Hannes Laimer (1):
  add out/in-rate parameter to tap_plug sub, keep version with just rate
    param

 PVE/Network/SDN/Zones.pm | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)


qemu-server: Hannes Laimer (1):
  add fields inrate and outrate to net_fmt, map rate of old configs to
    out/inrate

 PVE/QemuServer.pm             | 35 +++++++++++++++++++++++++++++------
 vm-network-scripts/pve-bridge |  9 ++++++---
 2 files changed, 35 insertions(+), 9 deletions(-)


pve-manager: Hannes Laimer (1):
  out/in-rate in network edit, keep rate to still be able to open old
    configs

 www/manager6/Parser.js           | 18 ++++++++++++++++++
 www/manager6/qemu/NetworkEdit.js | 27 ++++++++++++++++++++++++---
 2 files changed, 42 insertions(+), 3 deletions(-)

-- 
2.20.1