Bug 1294854

Summary: [RFE] [downstream clone] Report fibre channel initiator and target world wide names
Product: Red Hat Enterprise Virtualization Manager Reporter: Kumar Mashalkar <kmashalk>
Component: RFEsAssignee: Rob Young <royoung>
Status: CLOSED DEFERRED QA Contact: Lukas Svaty <lsvaty>
Severity: high Docs Contact:
Priority: high    
Version: 3.5.0CC: ahoness, bugs, fgarciad, juan.hernandez, kmashalk, lsurette, mkalinin, pdwyer, srevivo
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: lsvaty: testing_plan_complete-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1264053 Environment:
Last Closed: 2020-04-01 14:48:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1264053    
Bug Blocks: 1523346    

Description Kumar Mashalkar 2015-12-30 17:24:50 UTC
+++ This bug was initially created as a clone of Bug #1264053 +++

Currently the engine (via the RESTAPI) doesn't report the WWN (world wide names) of the SCSI initiators and targets for fiber channel storage domains. For example:

  <logical_unit id="3600014400000001070605fc6b86f0000">
    <serial>myserial</serial>
    <vendor_id>myvendor</vendor_id>
    <product_id>myuproduct</product_id>
    <lun_mapping>0</lun_mapping>
    <size>53687091200</size>
    <paths>4</paths>
    <status>used</status>
  </logical_unit>

This information doesn't include the WWN of the initiator or the target.

For iSCSI the target is reported, in the form of a iSCSI IQN, but the initiator WWN is also missing:

  <logical_unit id="3600a09803752706c3224462d72794500">
    <port>3260</port>
    <target>iqn.2015-09.com.example:mytarget</target>
    <portal>...</portal>
    <address>...</address>
    <serial>...</serial>
    <vendor_id>myvendor</vendor_id>
    <product_id>myproduct</product_id>
    <lun_mapping>0</lun_mapping>
    <size>107374182400</size>
    <paths>0</paths>
    <volume_group_id>...</volume_group_id>
    <storage_domain_id>...</storage_domain_id>
  <logical_unit>

This RFE is about reporting the initiator and target WWN in all cases, for example:

  <logical_unit id="3600014400000001070605fc6b86f0000">
    <initiator>
      <wwn>myinitiatorwwn</wwn>
    </initiator>
    <target>
      <wwn>mytargetwwn</wwn>
    </target>
    ...
  </logical_unit>

As the initiators are more related to the host than to a specific LU it may be better to create a new "/hosts/{host:id}/scsiinitiators" collection:

  GET /hosts/{host:id}/scsiinitiators
  <scsi_initiators>
    <scsi_initiator id="..." href="...">
      <wwn>myinitiator1wwwn</wwn>
    </scsi_initiator>
    <scsi_initiator id="..." hef="...">
      <wwn>myinitiator2wwwn</wwn>
    </scsi_initiator>
    ...
  </scsi_initiators>

Same for the targets. The LU can then report them using links:

  <logical_unit ...>
    <initiator id="..." href="/hosts/{host:id}/scsiinitiators/..."/>
    <target id="..." href="/hosts/{host:id}/scsitargets/..."/>
  </logical_unit>

Comment 4 Kumar Mashalkar 2016-04-21 09:21:25 UTC
Hello,

Any further updates on this? Is it planned for any release?

Comment 5 Kumar Mashalkar 2016-06-20 08:43:09 UTC
Hello Team, Any plans for this feature?

Comment 17 Michal Skrivanek 2020-03-18 15:47:06 UTC
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 18 Michal Skrivanek 2020-03-18 15:51:52 UTC
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 19 Michal Skrivanek 2020-04-01 14:48:04 UTC
ok, closing. Please reopen if still relevant/you want to work on it.

Comment 20 Michal Skrivanek 2020-04-01 14:51:22 UTC
ok, closing. Please reopen if still relevant/you want to work on it.

Comment 23 Red Hat Bugzilla 2023-09-14 23:58:50 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days