aboutsummaryrefslogtreecommitdiff
blob: 059f0b7921beb252930014b39cfd4890bacb6d74 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
<html>
  <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>