9045a8e24c
With these changes, a container can have more then one veth-pair. This allows for example to have LAN and DMZ as bridges on the host and add dedicated containers for proxies, ipv4-firewall and ipv6-firewall. Or to have a bridge for normal WAN, one bridge for administration and one bridge for customer-internal communication. So that web-server containers can be reached from outside per http, from the management via ssh and can talk to their database via the customer network. The scripts to set up the containers are now rendered several times instead of just one template. The scripts now contain per-container code to configure the extra veth interfaces. The default template without support for extra-veths is still rendered for the imperative containers. Also a test is there to see if extra veths can be placed into host-bridges or can be reached via routing. |
||
|---|---|---|
| .. | ||
| amazon-grow-partition.nix | ||
| amazon-image.nix | ||
| amazon-init.nix | ||
| amazon-options.nix | ||
| azure-agent-entropy.patch | ||
| azure-agent.nix | ||
| azure-common.nix | ||
| azure-config-user.nix | ||
| azure-config.nix | ||
| azure-image.nix | ||
| azure-qemu-220-no-etc-install.patch | ||
| brightbox-config.nix | ||
| brightbox-image.nix | ||
| container-config.nix | ||
| containers.nix | ||
| docker-image.nix | ||
| docker.nix | ||
| ec2-amis.nix | ||
| ec2-data.nix | ||
| google-compute-config.nix | ||
| google-compute-image.nix | ||
| libvirtd.nix | ||
| lxc-container.nix | ||
| lxc.nix | ||
| lxd.nix | ||
| nova-image.nix | ||
| nova.nix | ||
| openvswitch.nix | ||
| parallels-guest.nix | ||
| qemu-opts | ||
| qemu-vm.nix | ||
| rkt.nix | ||
| virtualbox-guest.nix | ||
| virtualbox-host.nix | ||
| virtualbox-image.nix | ||
| vmware-guest.nix | ||
| xe-guest-utilities.nix | ||
| xen-dom0.nix | ||
| xen-domU.nix | ||