iSCSI LUN ID cannot exceed 256 characters
Bug #2069270 reported by
Adam Karwasz
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
New
|
Undecided
|
Saravanan Manickam | ||
Bug Description
iSCSI LUN ID presented to OpenStack that cannot exceed 256
OpenStack doesn’t support SAM-4, but SAM-2 and SAM-3 addressing only.
* SAM:
- 64bit address
* SAM-2:
- Peripheral device addressing method (Code 00b)
+ Single level
+ Multi level
- Flat space addressing method (Code 01b)
- Logical unit addressing mode (Code 10b)
- Extended logical unit addressing method (Code 11b)
* SAM-3: Mostly same as SAM-2 but with some differences,
like supporting addressing LUNs < 256 with flat address space.
For NetApp driver, enable the driver to support SAM-4 to get LUN ids > 256 to go through and discovered properly. Is there any workaround from Netapp storage to present the iSCSI LUN ID with SAM-4 01b method ?
| Changed in cinder: | |
| assignee: | nobody → Saravanan Manickam (msaravan) |
Revision history for this message
| Vida Haririan (vhariria) wrote | #1 |
| no longer affects: | manila |
To post a comment you must log in.
The bug suggests we should name LUNs according to a different standard; the netapp driver in manila doesn't create any LUNs
See additional triage information at https:/