10 Posts
0
1666
When using Unity CSI, is there a way to specify iSCSI Interfaces of Unity?
When I try to use an iSCSI-based PV, the iSCSI sessions are connected through all iSCSI interfaces of Unity.
If I want to use specific interfaces, is there any options for using a specific interface?
For example, if I have 4 interfaces for iSCSI on Unity, is it possible to use only 2 interfaces are used for Kubernetes?
The other 2 interfaces are used for different purpose, not for kubernetes.
- All iSCSI Interfaces on Unity : spa_eth0, spa_eth1, spa_eth0, spb_eth1
- for kubernetes : spa_eth0, spb_eth0
- for other service : spa_eth1, spb_eth1
1. Operating System and its version
=> CentOS 7.9 (3.10.0-1160.24.1)
2. Orchestrator type and its version (e.g., Kubernetes v1.19.4 or OpenShift 4.7)
=> Kubernetes v1.20.2
3. Driver Version (e.g., CSI-PowerScale 1.7)
=> Unity CSI v1.6.0
4. Installer Type (Helm or Operator); In case of Operator, its version
=> Helm
5. Storage array version
=> 5.0
Flo_csI
2 Intern
2 Intern
•
166 Posts
0
September 13th, 2021 01:00
Hi,
I do confirm an enhancement request for the feature has been created.
Send me PM so I can share my email address and give you more details on the roadmap.
Rgds
ankur.patel
286 Posts
0
August 12th, 2021 06:00
hi! when you register your K8S/Centos OS with the unity you do it by logging into the unity from the host via the iscsi initiator. If you only log into just spa_eth0 and spb_eth0 thats all it will use. The installer will register those imitators in unity. The others will be untouched.
chesed82
10 Posts
0
August 12th, 2021 16:00
Hi ankur.patel
First of all, thank you for your answer.
I tested it as you guided me. I logged into Unity for spa_eth0 and spb_eth0 via the iSCSI initiator on K8S/CentOS. But when I deployed Unity CSI, node plugin of Unity CSI logs into all iSCSI Interfaces (spa_eth0, spa_eth1, spb_eth0, spb_eth1). As a result, all iSCSI interfaces in Unity will be used.
What should I do?
ankur.patel
286 Posts
0
August 12th, 2021 18:00
ah interesting. Let me ping some people. I imagine you could manually unregister the initiators you dont want to use on the unity side. I dont see why that would be an issue. Ill get back to you!
chesed82
10 Posts
0
August 18th, 2021 23:00
Hi ankur.patel,
Do you have any updates?
I checked logs of CSI Node Plugin and Go library for unity.
Even if I unregistered the initiators that I don't want to use manually, node plugin connects volume using all iSCSI interfaces on Unity when the pod with pvc is deployed.
In the code of gounity library, function "ListIscsiIPInterfaces" returned all iSCSI interfaces.
So it seems that all iSCSI interfaces on Unity are used, not specified interfaces.
ankur.patel
286 Posts
0
August 19th, 2021 06:00
I thought I could simply unregister the initiator in unity and everything would be fine. I realized that upon rebooting the node it simply logs back in. I tried to delete the initiator record from the centos OS which did make it so it didnt log back in after reboot, but then i realized my k8s environment was broke the whole time Trying to get it back together to try it again. I will pass your note to the development team. Sorry its taking so long!
chesed82
10 Posts
0
August 22nd, 2021 23:00
Thank you for your help.
Can this issue be applied as a feature improvement in the future version?
It was an issue that occurred during the PoC with customer, but it can be good results only when this issue is resolved.
How could I do to check the progress?