]> git.proxmox.com Git - pve-docs.git/blame_incremental - pve-storage-iscsi.adoc
scan-adoc-refs: improve title parser, store doctype
[pve-docs.git] / pve-storage-iscsi.adoc
... / ...
CommitLineData
1http://www.open-iscsi.org/[Open-iSCSI] initiator
2------------------------------------------------
3include::attributes.txt[]
4
5ifdef::wiki[]
6:pve-toplevel:
7endif::wiki[]
8
9Storage pool type: `iscsi`
10
11iSCSI is a widely employed technology used to connect to storage
12servers. Almost all storage vendors support iSCSI. There are also open
13source iSCSI target solutions available,
14e.g. http://www.openmediavault.org/[OpenMediaVault], which is based on
15Debian.
16
17To use this backend, you need to install the `open-iscsi`
18package. This is a standard Debian package, but it is not installed by
19default to save resources.
20
21 # apt-get install open-iscsi
22
23Low-level iscsi management task can be done using the `iscsiadm` tool.
24
25
26Configuration
27~~~~~~~~~~~~~
28
29The backend supports the common storage properties `content`, `nodes`,
30`disable`, and the following iSCSI specific properties:
31
32portal::
33
34iSCSI portal (IP or DNS name with optional port).
35
36target::
37
38iSCSI target.
39
40
41.Configuration Example (`/etc/pve/storage.cfg`)
42----
43iscsi: mynas
44 portal 10.10.10.1
45 target iqn.2006-01.openfiler.com:tsn.dcb5aaaddd
46 content none
47----
48
49TIP: If you want to use LVM on top of iSCSI, it make sense to set
50`content none`. That way it is not possible to create VMs using iSCSI
51LUNs directly.
52
53
54File naming conventions
55~~~~~~~~~~~~~~~~~~~~~~~
56
57The iSCSI protocol does not define an interface to allocate or delete
58data. Instead, that needs to be done on the target side and is vendor
59specific. The target simply exports them as numbered LUNs. So {pve}
60iSCSI volume names just encodes some information about the LUN as seen
61by the linux kernel.
62
63
64Storage Features
65~~~~~~~~~~~~~~~~
66
67iSCSI is a block level type storage, and provides no management
68interface. So it is usually best to export one big LUN, and setup LVM
69on top of that LUN. You can then use the LVM plugin to manage the
70storage on that iSCSI LUN.
71
72.Storage features for backend `iscsi`
73[width="100%",cols="m,m,3*d",options="header"]
74|==============================================================================
75|Content types |Image formats |Shared |Snapshots |Clones
76|images none |raw |yes |no |no
77|==============================================================================
78
79
80Examples
81~~~~~~~~
82
83Scan a remote iSCSI portal, and returns a list of possible targets:
84
85 pvesm iscsiscan -portal <HOST[:PORT]>
86
87ifdef::wiki[]
88
89See Also
90~~~~~~~~
91
92* link:/wiki/Storage[Storage]
93
94endif::wiki[]
95
96