The following pull request was submitted through Github.
It can be accessed and reviewed at: https://github.com/lxc/linuxcontainers.org/pull/430

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) ===
…to storage description.

Signed-off-by: Tobias Gerold <tob...@g3ro.eu>

Related to https://github.com/lxc/lxd/issues/7491 and https://github.com/lxc/lxd/commit/180c611d2045e434c19a8782c07fb07564ea98f0
From 1a8ceac673e7480b304d32ea83d336eb7a49b191 Mon Sep 17 00:00:00 2001
From: Tobias Gerold <tob...@g3ro.eu>
Date: Wed, 10 Jun 2020 22:47:10 +0200
Subject: [PATCH] content/lxd/getting-started-cli.md - added the word "empty" &
 a link to storage description.

Signed-off-by: Tobias Gerold <tob...@g3ro.eu>
---
 content/lxd/getting-started-cli.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/lxd/getting-started-cli.md 
b/content/lxd/getting-started-cli.md
index c999187..7f553ab 100644
--- a/content/lxd/getting-started-cli.md
+++ b/content/lxd/getting-started-cli.md
@@ -143,7 +143,7 @@ Run the following as root:
 | Clustering | A Cluster combines several LXD-servers. They share the same 
distributed database and can be managed uniformly using the LXD-client (lxc) or 
the REST API. | default=`no`; <br> If set to `yes`, you can either connect to 
an existing cluster or create a new one. | LXD-documentation: <br> 
[[clustering]] |
 | MAAS server | "MAAS is an open-source tool that lets you build a data centre 
from bare-metal servers." | default=`no`; <br> If set to `yes`, you can connect 
to an existing MAAS-server and specify the `name`, `URL` and `API key`. | - 
[maas.io](https://maas.io/) <br> - [maas - install with 
lxd](https://maas.io/docs/install-with-lxd) |
 | Network bridge | Provides network access for the instances. | You can either 
use an existing bridge (or interface) or let LXD create a new bridge 
(recommended option). <br> You can also create additional bridges and assign 
them to instances later. | LXD-documentation: <br> - [[networks]] <br> - 
[Network 
interface](https://linuxcontainers.org/lxd/docs/master/instances#type-nic) |
-| Storage pools | Instances etc. are stored in storage pools. | For testing 
purposes you can create a loop-backed storage pool. <br> But for production use 
it is recommended to use a partition (or full disk) instead of loop-backed 
storages (Reasons include: loop-backed pools are slower and their size can't be 
reduced). <br> The recommended backends are `ZFS` and `btrfs`. <br> You can 
also create additional storage pools later. | LXD-documentation: <br> - 
[[storage]] <br> - [Backend Comparison 
Chart](https://linuxcontainers.org/lxd/docs/master/storage#feature-comparison) |
+| Storage pools | Instances etc. are stored in storage pools. | For testing 
purposes you can create a loop-backed storage pool. <br> But for production use 
it is recommended to use an empty partition (or full disk) instead of 
loop-backed storages (Reasons include: loop-backed pools are slower and their 
size can't be reduced). <br> The recommended backends are `ZFS` and `btrfs`. 
<br> You can also create additional storage pools later. | LXD-documentation: 
<br> - [[storage]] <br> - [Comparison of 
methods](https://linuxcontainers.org/lxd/docs/master/storage.html#where-to-store-lxd-data)
 <br> - [Backend Comparison 
Chart](https://linuxcontainers.org/lxd/docs/master/storage#feature-comparison) |
 | Network Access | Allows access to the server over network. |  default=`no`; 
<br> If set to `yes`, you can connect to the server over network. <br> You can 
set a `password` or accept the client certificate manually. | - |
 | Automatic Image Update | You can download Images from Image servers, in this 
case images can be updated automatically. | default=`yes`; <br> If set to 
`yes`, LXD will update the downloaded images regularly. | LXD-documentation: 
<br> [[image-handling]] |
 | "YAML lxd init preseed" | Will display a summary of your chosen 
configuration options in the terminal. | default=`no` | - |
_______________________________________________
lxc-devel mailing list
lxc-devel@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-devel

Reply via email to