You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

98 lines
2.4KB

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