A network of LXC containers, managed through libvirt
Go to file
Théophile Bastian abe5fc6972 Ask and drop sudo rights at the right moment 2020-03-19 23:32:19 +01:00
lxc_net Ask and drop sudo rights at the right moment 2020-03-19 23:32:19 +01:00
topologies Add a few topologies 2020-03-12 11:58:10 +01:00
.gitignore Use virtualenv, rename src -> lxc_net 2020-03-09 12:58:57 +01:00
LICENSE Initial commit 2020-03-08 15:12:28 +01:00
README.md Add better README 2020-03-12 11:52:07 +01:00
__init__.py Use virtualenv, rename src -> lxc_net 2020-03-09 12:58:57 +01:00
requirements.txt Add entry point: `parse_network.py` 2020-03-12 11:40:17 +01:00
spawn_network.py Ask and drop sudo rights at the right moment 2020-03-19 23:32:19 +01:00

README.md

lxc-network

A network of LXC containers, managed through libvirt

Dependencies

This script will most probably break on any other system than Linux, and will definitely break on anything non-UNIX.

It relies on libvirt and overlayfs.

Setup

It is recommended to set up lxc-network within a virtualenv:

virtualenv -p python3 venv
source venv/bin/activate
pip install -r requirements.txt

Furthermore, you are expected to set up a system root tree within the directory of your choice, and put its path in lxc_net/settings.py. This can be done eg. in ArchLinux with

pacstrap [your_root_directory] base

or the equivalent debootstrap command on Debian.

This system is expected to use systemd, and to have enabled systemd-networkd to setup its IP addresses.

Usage

You can spawn a network using

./spawn_network.py topology_description.yml

where topology_description.yml is a valid topology description file (see below).

Topology description file

A topology is described in a YAML file looking like this:

---
links:
  - domains: ['a', 'b']
  - domains: ['b', 'c']
domains:
  b:
    enable_v4: false

The links element is mandatory, each link containing a mandatory domains attribute, the list of domains (containers) connected to it. A domain is described by an arbitrary name. Domains will be spawned (and indexed) in alphabetical order.

A domains root element is optional, and may be used to specify domain-specific options.

The valid options are:

  • enable_v4: boolean, specifies whether the domain has an IPv4 address.