[lxc-devel] [lxd/master] Document container launch algorithm on cluster

[dnegreira on Github]

A non-text attachment was scrubbed...
Name: not available
Type: text/x-mailbox
Size: 465 bytes
Desc: not available
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20191128/775114d9/attachment.bin>
-------------- next part --------------
From bb107ea0847bd4cec6f328420ab95dbc2b1c8b53 Mon Sep 17 00:00:00 2001
From: David Negreira <david.negreira at 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.negreira at 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