File: archstorage.html.in

package info (click to toggle)
libvirt 1.2.9-9%2Bdeb8u5
  • links: PTS, VCS
  • area: main
  • in suites: jessie
  • size: 174,832 kB
  • sloc: ansic: 463,173; xml: 68,283; sh: 16,393; makefile: 4,580; python: 3,705; perl: 3,675; ml: 470; sed: 16
file content (32 lines) | stat: -rw-r--r-- 1,118 bytes parent folder | download | duplicates (5)
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
31
32
<?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>