Skip to content
This repository has been archived by the owner on Feb 9, 2022. It is now read-only.

in iscsi deployment we need to use only he_iscsi_portal_addr and not he_storage_domain_addr #158

Closed
kobihk opened this issue Mar 27, 2019 · 1 comment
Closed

in iscsi deployment we need to use only he_iscsi_portal_addr and not he_storage_domain_addr #158

kobihk opened this issue Mar 27, 2019 · 1 comment

Comments

@kobihk
Copy link
Contributor

kobihk commented Mar 27, 2019

in iscsi deployment, we have 2 different variables that are the same:

  • he_iscsi_portal_addr
  • he_storage_domain_addr

I think that we need to use:

  • he_storage_domain_addr in case of nfs and glusterfs deployment
  • he_iscsi_portal_addr in case of iscsi deployment
@tiraboschi
Copy link
Contributor

he_iscsi_portal_addr appears just in tasks/iscsi_discover.yml and tasks/iscsi_getdevices.yml which are helpers tasks files for the the interactive iSCSI discovery via CLI and cockpit.
For the deployment only he_storage_domain_addr is relevant.

tiraboschi added a commit to tiraboschi/ovirt-ansible-hosted-engine-setup that referenced this issue Mar 27, 2019
@tiraboschi
Explain the difference between he_iscsi_portal_addr and he_storage_do…
b95e3f0 
…main_addr

Fixes: oVirt#158
@tiraboschi tiraboschi mentioned this issue Mar 27, 2019
Merged
tiraboschi added a commit that referenced this issue Apr 5, 2019
@tiraboschi
Explain the difference between he_iscsi_portal_addr and he_storage_do…
dc811d0 
…main_addr

Fixes: #158
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kobihk @tiraboschi