[kolla-ansible][yoga] how to configure cinder to connect to iscsi target?

wodel youchi wodel.youchi at gmail.com
Tue Apr 11 12:15:00 UTC 2023


Hi,

What do you mean by controller status?

After some digging I found that, when using
cinder.volume.drivers.lvm.LVMVolumeDriver, it seems that cinder searches
for the VG, and the VG must exist.
Seeing some examples like this [1], it's like the configuration is made to
expose a local disk as an iscsi LUN.

The VG was created on a local disk, then it was exposed as LUN. So just to
be sure, is cinder.volume.drivers.lvm.LVMVolumeDriver with target_protocol
= iscsi, intended to expose a local VG on compute nodes as iscsi LUNs?

My other question is : Can I configure cinder with  Tagetcli as external
iscsi storage?


[1] :
https://www.server-world.info/en/note?os=CentOS_Stream_8&p=openstack_yoga2&f=12

Regards.

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, Apr 10, 2023, 06:33 Nguyễn Hữu Khôi <nguyenhuukhoinw at gmail.com>
wrote:

> what is your controller status?
> Nguyen Huu Khoi
>
>
> On Sun, Apr 9, 2023 at 10:36 PM wodel youchi <wodel.youchi at gmail.com>
> wrote:
>
>> Hi,
>> I am trying to configure cinder to connect to an iscsi target. I am using
>> targetcli as my target server.
>>
>> I have tested the connection from the node using iscsiadm and it works
>> from the OS.
>>
>> Now I am trying to use the iscsid container to do the job.
>>
>> I added this to my globals.yml
>> enable_iscsid: "yes"
>> enable_cinder_backend_iscsi: "yes"
>> enable_cinder_backend_lvm: "no"
>>
>> And I created the cinder.conf file like this
>> [DEFAULT]
>> enabled_backends = rbd1,nfs-1,*lvmtnas *
>>
>> # add follows to the end
>> [lvmtnas]
>> target_helper = lioadm
>> target_protocol = iscsi
>> target_ip_address = 20.1.0.32 (my target server)
>> volume_backend_name = lvmtnas
>> # volume group name created
>> volume_group = *vg_volume01 *
>> volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver
>> use_chap_auth = false
>>
>> I did create the vg_volume01 on the LUN prior to the test.
>>
>> I did a deploy, the container has been created, but nothing happened,
>> it's like I am missing something.
>>
>> docker logs iscsid fome one the compute nodes
>> + sudo -E kolla_set_configs
>> INFO:__main__:Loading config file at
>> /var/lib/kolla/config_files/config.json
>> INFO:__main__:Validating config file
>> INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
>> INFO:__main__:Copying service configuration files
>> INFO:__main__:Writing out command to execute
>> ++ cat /run_command
>> + CMD='iscsid -d 8 -f'
>> + ARGS=
>> + sudo kolla_copy_cacerts
>> + [[ ! -n '' ]]
>> + . kolla_extend_start
>> ++ [[ ! -f /etc/iscsi/initiatorname.iscsi ]]
>> + echo 'Running command: '\''iscsid -d 8 -f'\'''
>> + exec iscsid -d 8 -f
>> Running command: 'iscsid -d 8 -f'
>> iscsid: sysfs_init: sysfs_path='/sys'
>> iscsid: in ctldev_open
>> iscsid: created NETLINK_ISCSI socket...
>> iscsid: InitiatorName=iqn.1994-05.com.redhat:2a318909ad8
>> iscsid: InitiatorName=iqn.1994-05.com.redhat:2a318909ad8
>> iscsid: InitiatorAlias=computehci01
>> iscsid: Max file limits 1048576 1048576
>> iscsid: current time 258465
>> iscsid: nothing on pend_list, deactivating alarm
>>
>>
>> Any idea?
>>
>> Regards.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230411/44f4f7f3/attachment.htm>


More information about the openstack-discuss mailing list