The idea is that the current deployer of orabuntu-lxc will remain the same and continue to use the 10.207.39.0/24 network. The lxc-copy overlayfs clones can be created and then modified with a new network, while at the same time a new zone file is added to the DNS/DHCP container and new entries added to
/etc/NetworkManager/dnsmasq.d/local
and a new openvswitch crt_ovs_swX.sh added to create the network to allow user to completely configure their additional networks entirely to their own liking.
This way new networks of containers can be added, and the user can name those containers entirely arbitrarily, unlike the base network which is designed so that the DHCP address matches the container name index.
gstanden
commented
3 years ago
The idea is that the current deployer of orabuntu-lxc will remain the same and continue to use the 10.207.39.0/24 network. The lxc-copy overlayfs clones can be created and then modified with a new network, while at the same time a new zone file is added to the DNS/DHCP container and new entries added to
/etc/NetworkManager/dnsmasq.d/local
and a new openvswitch crt_ovs_swX.sh added to create the network to allow user to completely configure their additional networks entirely to their own liking.
This way new networks of containers can be added, and the user can name those containers entirely arbitrarily, unlike the base network which is designed so that the DHCP address matches the container name index.