protocol6v
85 Posts
Quote from protocol6v on April 3, 2018, 5:46 pm
Hello,
Would like to be able to modify security parameters and possibly even disk size for live running iSCSI targets. For instance, I limit access to iSCSI targets by IQN, and when adding additional hosts to a Hyper-V cluster, I need to add the IQN to the iSCSI disk without having to "stop" the disk.
Thanks!
Hello,
Would like to be able to modify security parameters and possibly even disk size for live running iSCSI targets. For instance, I limit access to iSCSI targets by IQN, and when adding additional hosts to a Hyper-V cluster, I need to add the IQN to the iSCSI disk without having to "stop" the disk.
Thanks!
admin
2,921 Posts
Quote from admin on April 3, 2018, 8:51 pm
Thanks for your post. I am not sure if it is safe to resize a disk while it is running, like can the os perform io while the disk geometry/number of sectors is being changed ? If this is allowed from the os side we can probably support it.
Thanks for your post. I am not sure if it is safe to resize a disk while it is running, like can the os perform io while the disk geometry/number of sectors is being changed ? If this is allowed from the os side we can probably support it.
protocol6v
85 Posts
Quote from protocol6v on April 4, 2018, 12:23 pm
Resize is much less important than being able to dynamically add or remove IQNs. I believe you can resize with iscsiadm but it may be destructive, not sure.
But really just need to be able to add IQNs on the fly.
Resize is much less important than being able to dynamically add or remove IQNs. I believe you can resize with iscsiadm but it may be destructive, not sure.
But really just need to be able to add IQNs on the fly.
Andoni
7 Posts
Quote from Andoni on September 18, 2019, 1:01 pm
Hi.
I think is a good idea that Petasan can add/remove iqn "on the fly", is not a good idea stop disk to add/remove new iqn because all data on disk are innacessible during operation.
The best option is create "security groups" to add/remove iqn, and we can attach/link this "security group" to a specific disk.
Best
Hi.
I think is a good idea that Petasan can add/remove iqn "on the fly", is not a good idea stop disk to add/remove new iqn because all data on disk are innacessible during operation.
The best option is create "security groups" to add/remove iqn, and we can attach/link this "security group" to a specific disk.
Best
admin
2,921 Posts
Quote from admin on September 18, 2019, 2:52 pm
Hi. Can you clarify adding iqn on the fly. If there is no iqn, the is no iSCSI disk/lun, so the disk is not connected or accessible from iSCSI to begin with and no io, so we are not stopping io when adding an iqn. Similarly to delete an iqn, you will make the iSCSI disk not accessible to client by definition. i think i am missing something.
Hi. Can you clarify adding iqn on the fly. If there is no iqn, the is no iSCSI disk/lun, so the disk is not connected or accessible from iSCSI to begin with and no io, so we are not stopping io when adding an iqn. Similarly to delete an iqn, you will make the iSCSI disk not accessible to client by definition. i think i am missing something.
protocol6v
85 Posts
Quote from protocol6v on September 18, 2019, 2:54 pm
I too, would like this feature.
He's referring to the client IQN access control list. When I add new nodes to a hyper-v cluster for instance, and want to grant new nodes access to a PetaSAN iSCSI LUN, it would be extremely helpful to not have to stop the lun to add the additional client IQN to the ACL.
I too, would like this feature.
He's referring to the client IQN access control list. When I add new nodes to a hyper-v cluster for instance, and want to grant new nodes access to a PetaSAN iSCSI LUN, it would be extremely helpful to not have to stop the lun to add the additional client IQN to the ACL.
admin
2,921 Posts
Quote from admin on September 18, 2019, 3:16 pm
ahh ok this makes sense now 🙂
ahh ok this makes sense now 🙂
admin
2,921 Posts
Quote from admin on September 18, 2019, 8:14 pm
If you do not mind scripting, you can use the following utility to write and read iSCSI metadata to Ceph rbd image,
/opt/petasan/scripts/util/disk_meta.py
it uses json format, you can change the client iqns on the fly this way.
If you do not mind scripting, you can use the following utility to write and read iSCSI metadata to Ceph rbd image,
/opt/petasan/scripts/util/disk_meta.py
it uses json format, you can change the client iqns on the fly this way.
Andoni
7 Posts
Quote from Andoni on September 19, 2019, 5:36 am
Hi,
The problem is that we can't edit disk on "Started" status 
, we need to Stop, and after that, we can edit it to add new iqn, etc 
. As you can imagine all path to Stopped disk will be down.
Please, this feature is a very good idea to implement.
Best
Hi,
The problem is that we can't edit disk on "Started" status , we need to Stop, and after that, we can edit it to add new iqn, etc . As you can imagine all path to Stopped disk will be down.
Please, this feature is a very good idea to implement.
Best
Andoni
7 Posts
Quote from Andoni on December 13, 2019, 7:54 am
Hi @admin,
I updated to 2.4 and this feature still missing, do you has a plan to improve that?
Kind Regards
Hi @admin,
I updated to 2.4 and this feature still missing, do you has a plan to improve that?
Kind Regards
