You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Thomas Lamprecht e41f20af64 d/control: bump version dependency to ha-manager 1 day ago
debian d/control: bump version dependency to ha-manager 1 day ago
src Use crm-command stop to allow shutdown with timeout and hard stop for HA 1 day ago
Makefile buildsys: switch upload dist over to buster 5 months ago
README update README for new configuration format 4 years ago


= Info for developers =

== Command Line Tool ==


# pct create 200 debian-7.0-standard_7.0-2_i386.tar.gz
# pct start 200
# pct enter 200
# pct stop 200
# pct destroy 200

You can get detailed help with:

# pct help -v

== Container names ==

We use integers values for container names (and do not allow to use
arbitrary names for containers).

== LXC Configuration ==

We store LXC container configurations on the cluster file system:


There is a symbolic link for the local node at

/etc/pve/lxc => /etc/pve/nodes/<localhost>/lxc

see man pct.conf for syntax details.

== CRIU ==

CRIU (1.5.2) does not work well with kernel 3.10.0, so checkpoint/restore
and live migration does not work.

= FAQ =

* Why not LXD

- LXD uses a local database to store configuration files, which simply
does not work with our distributed configuration file system

- We want to use our existing libraries (i.e. Storage). Also see:
where they write: "Lxd will not be as flexible as lxc in many ways,
including with respect to backing stores."

We have a different goal, and want to support many new storage technologies
like zfs, ceph, ...

- It is a wrapper around LXC, and only provides a REST API and new CLI
tool. But Proxmox VE already provides a full featured API, and CLI tools
are automatically generated from that API.