Issue with adding iSCSI disk to new VMware host
neiltorda
98 Posts
October 27, 2020, 2:14 pmQuote from neiltorda on October 27, 2020, 2:14 pmOur VMware vSphere environment is getting ready to add new host boxes and I need to be able to present the same iscsi disks we have shared from Petasan to these new hosts.
The web interface requires shutting down the iscsi disk in order to edit the list of available IQN's. This would force me to take about 50 vm's offline to add a new host box.
Is there a way to add IQN's to currently configured iSCSI disks without taking them offline first.
Our VMware vSphere environment is getting ready to add new host boxes and I need to be able to present the same iscsi disks we have shared from Petasan to these new hosts.
The web interface requires shutting down the iscsi disk in order to edit the list of available IQN's. This would force me to take about 50 vm's offline to add a new host box.
Is there a way to add IQN's to currently configured iSCSI disks without taking them offline first.
admin
2,930 Posts
October 27, 2020, 3:07 pmQuote from admin on October 27, 2020, 3:07 pmIn version 2.7 we support editing disk data for running iSCSI disks, in 2.6 you need to stop it first in the ui.
in 2.6 you can change the data manually on running iSCSI disks via the utility: /opt/petasan/scripts/util/disk_meta.py
disk_meta.py read --image image-##### --pool rbd > diskdata.json
disk_meta.py write --image image-##### --pool rbd --file diskdata.json
you need to edit the json config file and add the client acl under the "acl" field, it is comma separated string.
In version 2.7 we support editing disk data for running iSCSI disks, in 2.6 you need to stop it first in the ui.
in 2.6 you can change the data manually on running iSCSI disks via the utility: /opt/petasan/scripts/util/disk_meta.py
disk_meta.py read --image image-##### --pool rbd > diskdata.json
disk_meta.py write --image image-##### --pool rbd --file diskdata.json
you need to edit the json config file and add the client acl under the "acl" field, it is comma separated string.
Last edited on October 27, 2020, 3:08 pm by admin · #2
neiltorda
98 Posts
October 27, 2020, 4:12 pmQuote from neiltorda on October 27, 2020, 4:12 pmSo I read the config using the disk_meta.py read… and this will write data out to a file called diskdata.json
I then edit that file with the new iqn, etc, and load it using the second version of the command..
But I am not sure what you mean with the image-####
How do I find this info?
Thanks,
Neil
So I read the config using the disk_meta.py read… and this will write data out to a file called diskdata.json
I then edit that file with the new iqn, etc, and load it using the second version of the command..
But I am not sure what you mean with the image-####
How do I find this info?
Thanks,
Neil
Last edited on October 27, 2020, 4:17 pm by neiltorda · #3
admin
2,930 Posts
October 27, 2020, 6:56 pmQuote from admin on October 27, 2020, 6:56 pmthis is the rbd image name, for disk 00001 the image name is image-00001
this is the rbd image name, for disk 00001 the image name is image-00001
neiltorda
98 Posts
October 27, 2020, 8:05 pmQuote from neiltorda on October 27, 2020, 8:05 pmThanks! That makes sense.
Neil
Thanks! That makes sense.
Neil
neiltorda
98 Posts
October 27, 2020, 8:50 pmQuote from neiltorda on October 27, 2020, 8:50 pmEdited - It finished….but i think i had a mistake in my command..
it lost information about the disk and it says it is detached.
Going to try with another test disk..
Edited - It finished….but i think i had a mistake in my command..
it lost information about the disk and it says it is detached.
Going to try with another test disk..
Last edited on October 27, 2020, 9:08 pm by neiltorda · #6
neiltorda
98 Posts
October 27, 2020, 9:40 pmQuote from neiltorda on October 27, 2020, 9:40 pmyeah… so it is important to not put a typo in the file you are reading in.. it just overwrote the disk info with nothing…
And then i accidentally overwrote the file with blank data by running the first command again.
Luckily I had made a copy of the original export and was able to re-write the disk meta info by running the command again with the correct file.
The test disk seems to be working just fine, so I appreciate your assistance in outlining the steps.
For anyone else trying to do this from the command line before the GUI is released, make sure you are very careful with the commands. Double check them before you run them!
yeah… so it is important to not put a typo in the file you are reading in.. it just overwrote the disk info with nothing…
And then i accidentally overwrote the file with blank data by running the first command again.
Luckily I had made a copy of the original export and was able to re-write the disk meta info by running the command again with the correct file.
The test disk seems to be working just fine, so I appreciate your assistance in outlining the steps.
For anyone else trying to do this from the command line before the GUI is released, make sure you are very careful with the commands. Double check them before you run them!
Issue with adding iSCSI disk to new VMware host
neiltorda
98 Posts
Quote from neiltorda on October 27, 2020, 2:14 pmOur VMware vSphere environment is getting ready to add new host boxes and I need to be able to present the same iscsi disks we have shared from Petasan to these new hosts.
The web interface requires shutting down the iscsi disk in order to edit the list of available IQN's. This would force me to take about 50 vm's offline to add a new host box.
Is there a way to add IQN's to currently configured iSCSI disks without taking them offline first.
Our VMware vSphere environment is getting ready to add new host boxes and I need to be able to present the same iscsi disks we have shared from Petasan to these new hosts.
The web interface requires shutting down the iscsi disk in order to edit the list of available IQN's. This would force me to take about 50 vm's offline to add a new host box.
Is there a way to add IQN's to currently configured iSCSI disks without taking them offline first.
admin
2,930 Posts
Quote from admin on October 27, 2020, 3:07 pmIn version 2.7 we support editing disk data for running iSCSI disks, in 2.6 you need to stop it first in the ui.
in 2.6 you can change the data manually on running iSCSI disks via the utility: /opt/petasan/scripts/util/disk_meta.py
disk_meta.py read --image image-##### --pool rbd > diskdata.json
disk_meta.py write --image image-##### --pool rbd --file diskdata.jsonyou need to edit the json config file and add the client acl under the "acl" field, it is comma separated string.
In version 2.7 we support editing disk data for running iSCSI disks, in 2.6 you need to stop it first in the ui.
in 2.6 you can change the data manually on running iSCSI disks via the utility: /opt/petasan/scripts/util/disk_meta.py
disk_meta.py read --image image-##### --pool rbd > diskdata.json
disk_meta.py write --image image-##### --pool rbd --file diskdata.json
you need to edit the json config file and add the client acl under the "acl" field, it is comma separated string.
neiltorda
98 Posts
Quote from neiltorda on October 27, 2020, 4:12 pmSo I read the config using the disk_meta.py read… and this will write data out to a file called diskdata.json
I then edit that file with the new iqn, etc, and load it using the second version of the command..
But I am not sure what you mean with the image-####How do I find this info?
Thanks,
Neil
So I read the config using the disk_meta.py read… and this will write data out to a file called diskdata.json
I then edit that file with the new iqn, etc, and load it using the second version of the command..
But I am not sure what you mean with the image-####
How do I find this info?
Thanks,
Neil
admin
2,930 Posts
Quote from admin on October 27, 2020, 6:56 pmthis is the rbd image name, for disk 00001 the image name is image-00001
this is the rbd image name, for disk 00001 the image name is image-00001
neiltorda
98 Posts
Quote from neiltorda on October 27, 2020, 8:05 pmThanks! That makes sense.
Neil
Thanks! That makes sense.
Neil
neiltorda
98 Posts
Quote from neiltorda on October 27, 2020, 8:50 pmEdited - It finished….but i think i had a mistake in my command..
it lost information about the disk and it says it is detached.
Going to try with another test disk..
Edited - It finished….but i think i had a mistake in my command..
it lost information about the disk and it says it is detached.
Going to try with another test disk..
neiltorda
98 Posts
Quote from neiltorda on October 27, 2020, 9:40 pmyeah… so it is important to not put a typo in the file you are reading in.. it just overwrote the disk info with nothing…
And then i accidentally overwrote the file with blank data by running the first command again.
Luckily I had made a copy of the original export and was able to re-write the disk meta info by running the command again with the correct file.
The test disk seems to be working just fine, so I appreciate your assistance in outlining the steps.
For anyone else trying to do this from the command line before the GUI is released, make sure you are very careful with the commands. Double check them before you run them!
yeah… so it is important to not put a typo in the file you are reading in.. it just overwrote the disk info with nothing…
And then i accidentally overwrote the file with blank data by running the first command again.
Luckily I had made a copy of the original export and was able to re-write the disk meta info by running the command again with the correct file.
The test disk seems to be working just fine, so I appreciate your assistance in outlining the steps.
For anyone else trying to do this from the command line before the GUI is released, make sure you are very careful with the commands. Double check them before you run them!