The following pull request was submitted through Github. It can be accessed and reviewed at: https://github.com/lxc/lxd/pull/6524
This e-mail was sent by the LXC bot, direct replies will not reach the author unless they happen to be subscribed to this list. === Description (from pull-request) === Clarify what happens when one does not define a target when launching a container in a LXD cluster. Signed-off-by: David Negreira <david.negre...@canonical.com>
From bb107ea0847bd4cec6f328420ab95dbc2b1c8b53 Mon Sep 17 00:00:00 2001 From: David Negreira <david.negre...@canonical.com> Date: Thu, 28 Nov 2019 16:10:26 +0100 Subject: [PATCH] Document container launch algorithm on cluster Clarify what happens when one does not define a target when launching a container in a LXD cluster. Signed-off-by: David Negreira <david.negre...@canonical.com> --- doc/clustering.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/clustering.md b/doc/clustering.md index d1cdcbd628..905da70a24 100644 --- a/doc/clustering.md +++ b/doc/clustering.md @@ -231,6 +231,11 @@ lxc launch --target node2 ubuntu:16.04 xenial will launch an Ubuntu 16.04 container on node2. +When you launch a container without defining a target, the container will be +launched on the server which has the lowest number of containers. +If all the servers have the same amount of containers, it will choose one +at random. + You can list all containers in the cluster with: ```bash
_______________________________________________ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel
