mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-07-06 18:05:45 +00:00
f2f9742d4d
The rule generating the HTML docs passing the --html flag to xsltproc. This makes it use the legacy HTML parser, which either ignores or tries to fix all sorts of broken XML tags. There's no reason why we should be writing broken XML in the first place, so removing --html and adding the XHTML doctype to all files forces us to create good XML. This adds the XHTML doc type and fixes many, many XML tag problems it exposes. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
33 lines
1.1 KiB
XML
33 lines
1.1 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml">
|
|
<body>
|
|
<h1>Storage management architecture</h1>
|
|
|
|
<p>
|
|
The storage management APIs are based around 2 core concepts
|
|
</p>
|
|
<ol>
|
|
<li>
|
|
<strong>Volume</strong> - a single storage volume which can
|
|
be assigned to a guest, or used for creating further pools. A
|
|
volume is either a block device, a raw file, or a special format
|
|
file.
|
|
</li>
|
|
<li>
|
|
<strong>Pool</strong> - provides a means for taking a chunk
|
|
of storage and carving it up into volumes. A pool can be used to
|
|
manage things such as a physical disk, a NFS server, a iSCSI target,
|
|
a host adapter, an LVM group.
|
|
</li>
|
|
</ol>
|
|
|
|
<p>
|
|
These two concepts are mapped through to two libvirt objects, a
|
|
<code>virStorageVolPtr</code> and a <code>virStoragePoolPtr</code>,
|
|
each with a collection of APIs for their management.
|
|
</p>
|
|
|
|
</body>
|
|
</html>
|