From nobody Mon Feb 9 03:47:39 2026 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 --- 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.

--=20 2.35.1