[Libstoragemgmt-devel] About Volume/LUN Masking

[Gris Ge]

Hi Tony,

I have some concerns about lsm.MaskInfo since we discussed in previous IRC
meeting.

1. If we have 'search_key' support for property, why we just merge the
volumes_accessible_by_access_group
into
volumes(search_key='access_group_id')
It could simply the user library.

2. I still want to introduce lsm.MaskInfo class:
a. To query access_type(RW, RO) but we support define it
when masking.
b. You mentioned the client requirements for LUN ID(HLU).
c. Once we introduced target port class, MaskInfo would also
hold the target ports information. Some array(like EMC VMAX)
support masking LUN to dedicate front-end ports.

Thank you in advance.
Best regards.

[Tony Asleson]

Discussed on IRC, outcome listed here for others.

Post by Gris Ge
I have some concerns about lsm.MaskInfo since we discussed in previous IRC
meeting.
1. If we have 'search_key' support for property, why we just merge the
volumes_accessible_by_access_group
into
volumes(search_key='access_group_id')
It could simply the user library.

No

Post by Gris Ge
a. To query access_type(RW, RO) but we support define it
when masking.

Removing access type, RO never used

Post by Gris Ge
b. You mentioned the client requirements for LUN ID(HLU).

Not needed with vpd 0x83

Post by Gris Ge
c. Once we introduced target port class, MaskInfo would also
hold the target ports information. Some array(like EMC VMAX)
support masking LUN to dedicate front-end ports.

Yes we want this, but will add later.

Regards,
Tony