[pve-devel] [RFC pve-container 0/4] Deal with gateways outside the subnet

Wolfgang Bumiller w.bumiller at proxmox.com
Fri Oct 16 15:57:09 CEST 2015


Unsurprisingly debian was the least convenient distribution to
configure.
For Redhat/Centos the routes are more easy to add, but since it's a
separate file which might be used by the user we need to update rather
than replace it. Which is still simple enough.
systemd-networkd wins the medal of convenience with this one, or maybe
hotplugging does, which currently doesn't delete old gateways btw
because of the required atomicity, though we could simply append that
to the end I suppose?

Wolfgang Bumiller (4):
  debian: deal with gateways in external subnets
  centos: deal with gateways outside the subnet
  systemd: deal with gateways outside the subnet
  hotplug: deal with gateways outside the subnet

 src/PVE/LXC.pm                                     | 10 ++-
 src/PVE/LXC/Setup/Base.pm                          | 14 ++++
 src/PVE/LXC/Setup/Debian.pm                        | 74 +++++++++++++++++++++-
 src/PVE/LXC/Setup/Redhat.pm                        | 30 +++++++++
 src/test/test-debian-012/config                    |  2 +
 src/test/test-debian-012/etc/debian_version        |  1 +
 src/test/test-debian-012/etc/network/interfaces    |  2 +
 .../test-debian-012/etc/network/interfaces.exp     | 21 ++++++
 8 files changed, 150 insertions(+), 4 deletions(-)
 create mode 100644 src/test/test-debian-012/config
 create mode 100644 src/test/test-debian-012/etc/debian_version
 create mode 100644 src/test/test-debian-012/etc/network/interfaces
 create mode 100644 src/test/test-debian-012/etc/network/interfaces.exp

-- 
2.1.4




More information about the pve-devel mailing list