From nobody Sat May 18 09:48:26 2024
Delivered-To: importer@patchew.org
Received-SPF: pass (zohomail.com: domain of redhat.com designates
170.10.133.124 as permitted sender) client-ip=170.10.133.124;
envelope-from=libvir-list-bounces@redhat.com;
helo=us-smtp-delivery-124.mimecast.com;
Authentication-Results: mx.zohomail.com;
dkim=pass;
spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as
permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com;
dmarc=pass(p=none dis=none) header.from=redhat.com
ARC-Seal: i=1; a=rsa-sha256; t=1650630225; cv=none;
d=zohomail.com; s=zohoarc;
b=G5uZbKZIU7UIOK3wX6b3r0GGJuVvVgjMxBOp3M9xtbeNHtA+fMUx5vJB8eYexz/ORUdNyUIrmQKSh7PCNLJB6bA1Sgw4eLKRCtFDOVn1hOCV13cDvAzlLBN8FahrDVRKUjtNteewr6LCJR5VuW+HJR7GH8pPxFxgqEq5aGIHnIg=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com;
s=zohoarc;
t=1650630225;
h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To;
bh=yhgqUL6wXqdxys0HKyxUGSltO7efi1uxxrPlyP2H8b4=;
b=QIsZDqDjSJEbqlcmMEOjjXsCL5ooSPEDDdmDvScbNaIrW5Xr/s2cI4vzLvMnZEa4SeuCiANju4Lv4e/xic3jjvveMHQo0bSV851EJZVxoi0VMciy/xDOe7bwG8a0Ypo7an6YdfT5tMyurxF1Pm+Z6tOy9Bg/wQBlj+ymYNmVSYw=
ARC-Authentication-Results: i=1; mx.zohomail.com;
dkim=pass;
spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as
permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com;
dmarc=pass header.from= (p=none dis=none)
Return-Path:
Received: from us-smtp-delivery-124.mimecast.com
(us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.zohomail.com
with SMTPS id 1650630225244512.9138525558816;
Fri, 22 Apr 2022 05:23:45 -0700 (PDT)
Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com
[66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS
(version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
us-mta-88-dmyzAMPcOhi5kv5ys_bE3g-1; Fri, 22 Apr 2022 08:23:41 -0400
Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com
[10.11.54.1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 853E71014A68;
Fri, 22 Apr 2022 12:23:37 +0000 (UTC)
Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com
(mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100])
by smtp.corp.redhat.com (Postfix) with ESMTP id 6D5414087D96;
Fri, 22 Apr 2022 12:23:37 +0000 (UTC)
Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com
(localhost [IPv6:::1])
by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with
ESMTP id 1D1671940360;
Fri, 22 Apr 2022 12:23:35 +0000 (UTC)
Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com
[10.11.54.10])
by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with
ESMTP id DBE0A1940355 for ;
Fri, 22 Apr 2022 12:23:33 +0000 (UTC)
Received: by smtp.corp.redhat.com (Postfix)
id CB1B1416361; Fri, 22 Apr 2022 12:23:33 +0000 (UTC)
Received: from speedmetal.lan (unknown [10.40.208.36])
by smtp.corp.redhat.com (Postfix) with ESMTP id 4C113416171
for ; Fri, 22 Apr 2022 12:23:33 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
s=mimecast20190719; t=1650630224;
h=from:from:sender:sender:reply-to:subject:subject:date:date:
message-id:message-id:to:to:cc:mime-version:mime-version:
content-type:content-type:
content-transfer-encoding:content-transfer-encoding:
in-reply-to:in-reply-to:references:references:list-id:list-help:
list-unsubscribe:list-subscribe:list-post;
bh=yhgqUL6wXqdxys0HKyxUGSltO7efi1uxxrPlyP2H8b4=;
b=VUOPSB5JhaRC6x6/dsSwC4SSHGrYIcUj8a9SgzGrYeFOS7AwZqkr879MDZaa33j2jtCDdy
3yWqt6J7PSLVLO0bkVeR7sQU1srlQqVl3Uy3nHLADl4j/7ybWqhM9TB3rOAsj+aYR5qEP4
M+R1Z9pJjsOLYsnzSQTYqRNee4Yc9ZU=
X-MC-Unique: dmyzAMPcOhi5kv5ys_bE3g-1
X-Original-To: libvir-list@listman.corp.redhat.com
From: Peter Krempa
To: libvir-list@redhat.com
Subject: [PATCH 01/15] docs: formatsecret: Correct link to storage volume XML
definition
Date: Fri, 22 Apr 2022 14:23:17 +0200
Message-Id:
<2dd194c5c62091abd884a2960645554793e6cf8b.1650629879.git.pkrempa@redhat.com>
In-Reply-To:
References:
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.85 on 10.11.54.10
X-BeenThere: libvir-list@redhat.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Development discussions about the libvirt library & tools
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: libvir-list-bounces@redhat.com
Sender: "libvir-list"
X-Scanned-By: MIMEDefang 2.84 on 10.11.54.1
Authentication-Results: relay.mimecast.com;
auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Transfer-Encoding: quoted-printable
X-ZohoMail-DKIM: pass (identity @redhat.com)
X-ZM-MESSAGEID: 1650630225912100001
Content-Type: text/plain; charset="utf-8"
The anchor name was not fixed when the 'formatstorage' document was
converted to rst.
Signed-off-by: Peter Krempa
Reviewed-by: Michal Privoznik
---
docs/formatsecret.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/formatsecret.rst b/docs/formatsecret.rst
index bb2217041a..03c2836843 100644
--- a/docs/formatsecret.rst
+++ b/docs/formatsecret.rst
@@ -63,10 +63,10 @@ See `Setting secret values in virsh`_ on how to set the=
value of the secret
using ``virsh secret-set-value``.
The volume type secret can be supplied either in volume XML during creatio=
n of a
-`storage volume `__ in order to provide the
-passphrase to encrypt the volume or in domain XML `disk
-device `__ in order to provide the passph=
rase
-to decrypt the volume, :since:`since 2.1.0` . An example follows:
+`storage volume `__ in order to pro=
vide
+the passphrase to encrypt the volume or in domain XML
+`disk device `__ in order to provide the
+passphrase to decrypt the volume, :since:`since 2.1.0` . An example follow=
s:
::
--=20
2.35.1
From nobody Sat May 18 09:48:26 2024
Delivered-To: importer@patchew.org
Received-SPF: pass (zohomail.com: domain of redhat.com designates
170.10.129.124 as permitted sender) client-ip=170.10.129.124;
envelope-from=libvir-list-bounces@redhat.com;
helo=us-smtp-delivery-124.mimecast.com;
Authentication-Results: mx.zohomail.com;
dkim=pass;
spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as
permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com;
dmarc=pass(p=none dis=none) header.from=redhat.com
ARC-Seal: i=1; a=rsa-sha256; t=1650630227; cv=none;
d=zohomail.com; s=zohoarc;
b=LGcL7IA/GK+a+uGWGOsuktyg4nB0M94n2Oko/nV4UpoOdsFshou6eKaTlwT1biQ9/3//TX2D9fxDl7NTKnEWYSITUMX7aN2IAlWje6v56+ISutDTbVg7TFTx+2c2XCKF305KygPuCH16hKNWyQ4C24Lji+7aQ+D7sJbJcjpl+DI=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com;
s=zohoarc;
t=1650630227;
h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To;
bh=8l0OT+Xy/2uoYRiVgrM5u6gj/5mj2Sv/DsuHuTTuGgM=;
b=c77owuLCiWIssVSqQaixC5HwQ263MBjz2il0gPkAWTra9WrrHsBKxQDvMJqV5egUAkVuJuGCO2SpCfciSNru2+8irD6kuDtEZRWWKvcVCrk/zs9yPwNv2clMTR+VolRaxGkOKV0Wb9sf8JDiOhm4Rm/7l3tPGtsD/6LDC4Y4GTk=
ARC-Authentication-Results: i=1; mx.zohomail.com;
dkim=pass;
spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as
permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com;
dmarc=pass header.from= (p=none dis=none)
Return-Path:
Received: from us-smtp-delivery-124.mimecast.com
(us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.zohomail.com
with SMTPS id 1650630227670746.9588840495728;
Fri, 22 Apr 2022 05:23:47 -0700 (PDT)
Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com
[66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS
(version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
us-mta-15-7tpskncPNSSjJtoUFVqqfg-1; Fri, 22 Apr 2022 08:23:42 -0400
Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com
[10.11.54.9])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 3147283395E;
Fri, 22 Apr 2022 12:23:38 +0000 (UTC)
Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com
(mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100])
by smtp.corp.redhat.com (Postfix) with ESMTP id 191B354CE44;
Fri, 22 Apr 2022 12:23:38 +0000 (UTC)
Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com
(localhost [IPv6:::1])
by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with
ESMTP id F059C194036E;
Fri, 22 Apr 2022 12:23:35 +0000 (UTC)
Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com
[10.11.54.10])
by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with
ESMTP id E7599194035F for ;
Fri, 22 Apr 2022 12:23:34 +0000 (UTC)
Received: by smtp.corp.redhat.com (Postfix)
id B911E416361; Fri, 22 Apr 2022 12:23:34 +0000 (UTC)
Received: from speedmetal.lan (unknown [10.40.208.36])
by smtp.corp.redhat.com (Postfix) with ESMTP id 3395D416171
for ; Fri, 22 Apr 2022 12:23:34 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
s=mimecast20190719; t=1650630226;
h=from:from:sender:sender:reply-to:subject:subject:date:date:
message-id:message-id:to:to:cc:mime-version:mime-version:
content-type:content-type:
content-transfer-encoding:content-transfer-encoding:
in-reply-to:in-reply-to:references:references:list-id:list-help:
list-unsubscribe:list-subscribe:list-post;
bh=8l0OT+Xy/2uoYRiVgrM5u6gj/5mj2Sv/DsuHuTTuGgM=;
b=NveISr0dAZ41i7MoBuAlwRxq9CHRbmq2Jrt0OcEYhK7JSDUVrvzou0sbndT7+DKCDCanOT
u6uNgWeayOqIYz2EgNoxxj7VxY8XU26DIjxcgW15E7wNRORodJMlUjY1hTD7WWZJ2KWDRR
g9D0ffDLgEe/FzlOO0aNdPl87JioJJ0=
X-MC-Unique: 7tpskncPNSSjJtoUFVqqfg-1
X-Original-To: libvir-list@listman.corp.redhat.com
From: Peter Krempa
To: libvir-list@redhat.com
Subject: [PATCH 02/15] Correct links to TLS certificate setup page
Date: Fri, 22 Apr 2022 14:23:18 +0200
Message-Id:
<49708a910a2ef44d2691dbe17320444403c23da0.1650629879.git.pkrempa@redhat.com>
In-Reply-To:
References:
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.85 on 10.11.54.10
X-BeenThere: libvir-list@redhat.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Development discussions about the libvirt library & tools
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: libvir-list-bounces@redhat.com
Sender: "libvir-list"
X-Scanned-By: MIMEDefang 2.85 on 10.11.54.9
Authentication-Results: relay.mimecast.com;
auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Transfer-Encoding: quoted-printable
X-ZohoMail-DKIM: pass (identity @redhat.com)
X-ZM-MESSAGEID: 1650630227897100004
Content-Type: text/plain; charset="utf-8"
When the setup of TLS certs was originally split out of
'docs/remote.html' ( df99aa311a33e87d4 ) links refering to it were not
fixed.
Adjust them to point to the correct document.
Signed-off-by: Peter Krempa
Reviewed-by: Michal Privoznik
---
docs/drvesx.rst | 5 ++---
tools/virt-pki-validate.in | 10 +++++-----
2 files changed, 7 insertions(+), 8 deletions(-)
diff --git a/docs/drvesx.rst b/docs/drvesx.rst
index 9ef6b74161..81625d6f10 100644
--- a/docs/drvesx.rst
+++ b/docs/drvesx.rst
@@ -231,9 +231,8 @@ There are also other causes for connection problems tha=
n those related to
error: Cannot access CA certificate '/etc/pki/CA/cacert.pem': No suc=
h file or directory
Don't let this error message confuse you. Setting up certificates as
- described on the `remote transport
- mechanism `__ page does not help, as t=
his is
- not a certificate related problem.
+ described on the `tls certificates `__ page does n=
ot
+ help, as this is not a certificate related problem.
To fix this problem you need to update your libvirt to 0.7.0 or newer. =
You
may also see this error when you use a libvirt version that contains th=
e ESX
diff --git a/tools/virt-pki-validate.in b/tools/virt-pki-validate.in
index 2f7404bd94..7100eafb63 100644
--- a/tools/virt-pki-validate.in
+++ b/tools/virt-pki-validate.in
@@ -2,7 +2,7 @@
#
# This shell script checks the TLS certificates and options needed
# for the secure client/server support of libvirt as documented at
-# https://libvirt.org/remote.html#Remote_certificates
+# https://libvirt.org/kbase/tlscerts.html
#
# Copyright (C) 2009-2013 Red Hat, Inc.
#
@@ -166,7 +166,7 @@ if [ ! -f "$CA/cacert.pem" ]
then
echo the CA certificate $CA/cacert.pem is missing while it
echo should be installed on both client and servers
- echo "see https://libvirt.org/remote.html#Remote_TLS_CA"
+ echo "see https://libvirt.org/kbase/tlscerts.html#setting-up-a-certifi=
cate-authority-ca"
echo on how to install it
exit 1
fi
@@ -186,7 +186,7 @@ if [ "$ORG" =3D "" ]
then
echo the CA certificate $CA/cacert.pem does not define the organization
echo it should probably regenerated
- echo "see https://libvirt.org/remote.html#Remote_TLS_CA"
+ echo "see https://libvirt.org/kbase/tlscerts.html#setting-up-a-certifi=
cate-authority-ca"
echo on how to regenerate it
exit 1
fi
@@ -234,7 +234,7 @@ then
else
echo Did not find "$LIBVIRT/clientcert.pem" client certificate
echo The machine cannot act as a client
- echo "see https://libvirt.org/remote.html#Remote_TLS_client_certificat=
es"
+ echo "see https://libvirt.org/kbase/tlscerts.html#issuing-client-certi=
ficates"
echo on how to regenerate it
CLIENT=3D0
fi
@@ -287,7 +287,7 @@ then
else
echo Did not find $LIBVIRT/servercert.pem server certificate
echo The machine cannot act as a server
- echo "see https://libvirt.org/remote.html#Remote_TLS_server_certificat=
es"
+ echo "see https://libvirt.org/kbase/tlscerts.html#issuing-server-certi=
ficates"
echo on how to regenerate it
SERVER=3D0
fi
--=20
2.35.1
From nobody Sat May 18 09:48:26 2024
Delivered-To: importer@patchew.org
Received-SPF: pass (zohomail.com: domain of redhat.com designates
170.10.129.124 as permitted sender) client-ip=170.10.129.124;
envelope-from=libvir-list-bounces@redhat.com;
helo=us-smtp-delivery-124.mimecast.com;
Authentication-Results: mx.zohomail.com;
dkim=pass;
spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as
permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com;
dmarc=pass(p=none dis=none) header.from=redhat.com
ARC-Seal: i=1; a=rsa-sha256; t=1650630246; cv=none;
d=zohomail.com; s=zohoarc;
b=b+ddoXLszlvBQbyNZ5X5ZSIWSDpY7dbLMg7cZA/NNTrFjGiyTUDboKg15/Fzhkb+TJghEPDm4u4tEb1LM8DjtMYCslwthtlBZMaIjS8xScJ6dCLzlLoNFCqQuPAEjCA8pTe6+gLwVQkIoV35+Djlc9zCSN1k9RLu10dDpsBP61U=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com;
s=zohoarc;
t=1650630246;
h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To;
bh=/I6Jfm6DjPAknqpBhurQdiadzBYQqwOu1Wihnayn/Ds=;
b=kld5x0S5p44TorHNWjiBZ3jpjv4Su1wHegXQpmpx8Spd4WWrgX9RRPDeIzLLlFpITLGJnF1u9dFrWXRFj67B7CtfIP9ZRujRwXs4x2vbWm323WvcKYNEuoJbzsB9ybJ7LvQlTCG4rBzJx4mEHfS4yOMPOjSuijcg62hfvekYiqE=
ARC-Authentication-Results: i=1; mx.zohomail.com;
dkim=pass;
spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as
permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com;
dmarc=pass header.from= (p=none dis=none)
Return-Path:
Received: from us-smtp-delivery-124.mimecast.com
(us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.zohomail.com
with SMTPS id 165063024639769.73681246981721;
Fri, 22 Apr 2022 05:24:06 -0700 (PDT)
Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com
[66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS
(version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
us-mta-15-9xezwRdNMI6HgmjR-MiCGw-1; Fri, 22 Apr 2022 08:23:44 -0400
Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com
[10.11.54.7])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by mimecast-mx02.redhat.com (Postfix) with ESMTPS id D0FC31801DB0;
Fri, 22 Apr 2022 12:23:38 +0000 (UTC)
Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com
(mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100])
by smtp.corp.redhat.com (Postfix) with ESMTP id 881BA15230A2;
Fri, 22 Apr 2022 12:23:38 +0000 (UTC)
Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com
(localhost [IPv6:::1])
by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with
ESMTP id 47D631940356;
Fri, 22 Apr 2022 12:23:37 +0000 (UTC)
Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com
[10.11.54.10])
by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with
ESMTP id D3FA2194036D for ;
Fri, 22 Apr 2022 12:23:35 +0000 (UTC)
Received: by smtp.corp.redhat.com (Postfix)
id B110841617F; Fri, 22 Apr 2022 12:23:35 +0000 (UTC)
Received: from speedmetal.lan (unknown [10.40.208.36])
by smtp.corp.redhat.com (Postfix) with ESMTP id 245D4572328
for ; Fri, 22 Apr 2022 12:23:34 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
s=mimecast20190719; t=1650630245;
h=from:from:sender:sender:reply-to:subject:subject:date:date:
message-id:message-id:to:to:cc:mime-version:mime-version:
content-type:content-type:
content-transfer-encoding:content-transfer-encoding:
in-reply-to:in-reply-to:references:references:list-id:list-help:
list-unsubscribe:list-subscribe:list-post;
bh=/I6Jfm6DjPAknqpBhurQdiadzBYQqwOu1Wihnayn/Ds=;
b=SHOjqrxVuYcE8Wl05bVlOUTbK02QS9e94oWhZgt0Ofi5+Jk7ud3eQINfSz8aiiLYnQ+p2n
dM1HLagoAa4TTqiS3B4EXZMd11b//TTQRSTpiLtxArqvvFwXojkgmNXPKIMeUTTaOVy9gT
OD1jPSz7Pdyj5xaaMA7Uh95SR+2DdoY=
X-MC-Unique: 9xezwRdNMI6HgmjR-MiCGw-1
X-Original-To: libvir-list@listman.corp.redhat.com
From: Peter Krempa
To: libvir-list@redhat.com
Subject: [PATCH 03/15] docs: storage: rename headers to remove duplicate names
Date: Fri, 22 Apr 2022 14:23:19 +0200
Message-Id:
<962f4d6a4c43902ffba2b72407b38a89b167af5c.1650629879.git.pkrempa@redhat.com>
In-Reply-To:
References:
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.85 on 10.11.54.10
X-BeenThere: libvir-list@redhat.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Development discussions about the libvirt library & tools
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: libvir-list-bounces@redhat.com
Sender: "libvir-list"
X-Scanned-By: MIMEDefang 2.85 on 10.11.54.7
Authentication-Results: relay.mimecast.com;
auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Transfer-Encoding: quoted-printable
X-ZohoMail-DKIM: pass (identity @redhat.com)
X-ZM-MESSAGEID: 1650630248032100005
Content-Type: text/plain; charset="utf-8"
From: Pavel Hrdina
Signed-off-by: Pavel Hrdina
Signed-off-by: Peter Krempa
Reviewed-by: Michal Privoznik
---
docs/storage.html.in | 96 ++++++++++++++++++++++----------------------
1 file changed, 48 insertions(+), 48 deletions(-)
diff --git a/docs/storage.html.in b/docs/storage.html.in
index b2cf343933..8fb2cec9bd 100644
--- a/docs/storage.html.in
+++ b/docs/storage.html.in
@@ -96,7 +96,7 @@
operation can be used to create it.
- Example pool input definition
+ Example directory pool input definition
<pool type=3D"dir">
<name>virtimages</name>
@@ -105,12 +105,12 @@
</target>
</pool>
- Valid pool format types
+ Valid directory pool format types
The directory pool does not use the pool format type element.
- Valid volume format types
+ Valid directory volume format types
One of the following options:
@@ -148,7 +148,7 @@
required.
- Example pool input
+ Example filesystem pool input
<pool type=3D"fs">
<name>virtimages</name>
@@ -160,7 +160,7 @@
</target>
</pool>
- Valid pool format types
+ Valid filesystem pool format types
The filesystem pool supports the following formats:
@@ -207,7 +207,7 @@
- Valid volume format types
+ Valid filesystem volume format types
The valid volume types are the same as for the directory
pool type.
@@ -224,7 +224,7 @@
protocol, which generally tries a mount via NFS first.
- Example pool input
+ Example network filesystem pool input
<pool type=3D"netfs">
<name>virtimages</name>
@@ -238,7 +238,7 @@
</target>
</pool>
- Valid pool format types
+ Valid network filesystem pool format types
The network filesystem pool supports the following formats:
@@ -261,7 +261,7 @@
- Valid volume format types
+ Valid network filesystem volume format types
The valid volume types are the same as for the directory
pool type.
@@ -278,7 +278,7 @@
of storage from the volume group.
- Example pool input
+ Example logical pool input
<pool type=3D"logical">
<name>HostVG</name>
@@ -292,14 +292,14 @@
</target>
</pool>
- Valid pool format types
+ Valid logical pool format types
The logical volume pool supports only the lvm2
format,
although not supplying a format value will result in automatic
selection of thelvm2
format.
- Valid volume format types
+ Valid logical volume format types
The logical volume pool does not use the volume format type element.
@@ -315,7 +315,7 @@
It will default to using dos
as the pool source format.
- Example pool input
+ Example disk pool input
<pool type=3D"disk">
<name>sda</name>
@@ -327,7 +327,7 @@
</target>
</pool>
- Valid pool format types
+ Valid disk pool format types
The disk volume pool accepts the following pool format types, repres=
enting
the common partition table types:
@@ -374,7 +374,7 @@
in parted
.
- Valid volume format types
+ Valid disk volume format types
The disk volume pool accepts the following volume format types, repr=
esenting
the common partition entry types:
@@ -423,7 +423,7 @@
on the same host will fail the duplicate source pool checks.
- Example pool input
+ Example iSCSI pool input
<pool type=3D"iscsi">
<name>virtimages</name>
@@ -436,12 +436,12 @@
</target>
</pool>
- Valid pool format types
+ Valid iSCSI pool format types
The iSCSI volume pool does not use the pool format type element.
- Valid volume format types
+ Valid iSCSI volume format types
The iSCSI volume pool does not use the volume format type element.
@@ -453,7 +453,7 @@
It requires a host, a path which is the target IQN, and an initiator=
IQN.
- Example pool input
+ Example iSCSI direct pool input
<pool type=3D"iscsi-direct">
<name>virtimages</name>
@@ -466,12 +466,12 @@
</source>
</pool>
- Valid pool format types
+ Valid iSCSI direct pool format types
The iSCSI direct volume pool does not use the pool format type eleme=
nt.
- Valid volume format types
+ Valid iSCSI direct volume format types
The iSCSI direct volume pool does not use the volume format type ele=
ment.
@@ -486,7 +486,7 @@
Since 0.6.2
- Example pool input
+ Example SCSI pool input
<pool type=3D"scsi">
<name>virtimages</name>
@@ -498,12 +498,12 @@
</target>
</pool>
- Valid pool format types
+ Valid SCSI pool format types
The SCSI volume pool does not use the pool format type element.
- Valid volume format types
+ Valid SCSI volume format types
The SCSI volume pool does not use the volume format type element.
@@ -522,7 +522,7 @@
Since 0.7.1
- Example pool input
+ Example multipath pool input
<pool type=3D"mpath">
<name>virtimages</name>
@@ -531,12 +531,12 @@
</target>
</pool>
- Valid pool format types
+ Valid multipath pool format types
The Multipath volume pool does not use the pool format type element.
- Valid volume format types
+ Valid multipath volume format types
The Multipath volume pool does not use the volume format type elemen=
t.
@@ -562,7 +562,7 @@
Since 0.9.13
- Example pool input
+ Example RBD pool input
<pool type=3D"rbd">
<name>myrbdpool</name>
@@ -577,7 +577,7 @@
</source>
</pool>
- Example volume output
+ Example RBD volume output
<volume>
<name>myvol</name>
@@ -597,19 +597,19 @@
</target>
</volume>
- Example disk attachment
+ Example RBD disk attachment
RBD images can be attached to QEMU guests when QEMU is built
with RBD support. Information about attaching a RBD image to a
guest can be found
at format domain
page.
- Valid pool format types
+ Valid RBD pool format types
The RBD pool does not use the pool format type element.
- Valid volume format types
+ Valid RBD volume format types
Only raw volumes are supported.
@@ -626,7 +626,7 @@
Since 0.9.13
- Example pool input
+ Example Sheepdog pool input
<pool type=3D"sheepdog">
<name>mysheeppool</name>
@@ -636,7 +636,7 @@
</source>
</pool>
- Example volume output
+ Example Sheepdog volume output
<volume>
<name>myvol</name>
@@ -656,19 +656,19 @@
</target>
</volume>
- Example disk attachment
+ Example Sheepdog disk attachment
Sheepdog images can be attached to QEMU guests.
Information about attaching a Sheepdog image to a
guest can be found
at the format domain
page.
- Valid pool format types
+ Valid Sheepdog pool format types
The Sheepdog pool does not use the pool format type element.
- Valid volume format types
+ Valid Sheepdog volume format types
The Sheepdog pool does not use the volume format type element.
@@ -696,7 +696,7 @@
Since 1.2.0
- Example pool input
+ Example Gluster pool input
A gluster volume corresponds to a libvirt storage pool. If a
gluster volume could be mounted as mount -t glusterfs
localhost:/volname /some/path
, then the following example
@@ -722,7 +722,7 @@
</source>
</pool>
-
Example volume output
+ Example Gluster volume output
Libvirt storage volumes associated with a gluster pool
correspond to the files that can be found when mounting the
gluster volume. The name
is the path relative to
@@ -741,19 +741,19 @@
<allocation unit=3D'bytes'>53687091200</allocation>
</volume>
-
Example disk attachment
+ Example Gluster disk attachment
Files within a gluster volume can be attached to QEMU guests.
Information about attaching a Gluster image to a
guest can be found
at the format domain
page.
- Valid pool format types
+ Valid Gluster pool format types
The Gluster pool does not use the pool format type element.
- Valid volume format types
+ Valid Gluster volume format types
The valid volume types are the same as for the directory
pool type.
@@ -777,7 +777,7 @@
Since 1.2.8
.
- Example pool input
+ Example ZFS pool input
<pool type=3D"zfs">
<name>myzfspool</name>
@@ -788,12 +788,12 @@
</source>
</pool>
- Valid pool format types
+ Valid ZFS pool format types
The ZFS volume pool does not use the pool format type element.
- Valid volume format types
+ Valid ZFS volume format types
The ZFS volume pool does not use the volume format type element.
@@ -808,7 +808,7 @@
Please refer to the Virtuozzo Storage documentation for details
on storage management and usage.
- Example pool input
+ Example vstorage pool input
In order to create storage pool with Virtuozzo Storage backend you
have to provide cluster name and be authorized within the cluster.
@@ -822,12 +822,12 @@
</target>
</pool>
- Valid pool format types
+ Valid vstorage pool format types
The Vstorage volume pool does not use the pool format type element.
- Valid volume format types
+ Valid vstorage volume format types
The valid volume types are the same as for the directory pool.