Re: tcmu iscsi (failover not supported)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks for the response.
I am using gwcli for configuration. We are not using ansible.

I built the following from from git releases because centos mirrors are far behind.

[root@dc1srviscsi02 ~]# rpm -qa | egrep "ceph|rbd|kernel-ml"
python-rbd-13.2.2-0.el7.x86_64
ceph-mds-13.2.2-0.el7.x86_64
ceph-mgr-13.2.2-0.el7.x86_64
ceph-release-1-1.el7.noarch
ceph-common-13.2.2-0.el7.x86_64
ceph-mon-13.2.2-0.el7.x86_64
ceph-13.2.2-0.el7.x86_64
libcephfs2-13.2.2-0.el7.x86_64
ceph-base-13.2.2-0.el7.x86_64
ceph-osd-13.2.2-0.el7.x86_64
ceph-radosgw-13.2.2-0.el7.x86_64
kernel-ml-4.18.12-1.el7.elrepo.x86_64
python-cephfs-13.2.2-0.el7.x86_64
librbd1-13.2.2-0.el7.x86_64
ceph-selinux-13.2.2-0.el7.x86_64
librbd-devel-13.2.2-0.el7.x86_64

[root@dc1srviscsi02 ~]# getenforce 
Disabled

[root@dc1srviscsi02 ~]# gwcli 
/> ls
o- / ......................................................................................................................... [...]
  o- clusters ........................................................................................................ [Clusters: 1]
  | o- ceph ............................................................................................................ [HEALTH_OK]
  |   o- pools ......................................................................................................... [Pools: 12]
  |   | o- cephfs_data ................................................................. [(x3), Commit: 0b/77.0T (0%), Used: 366.4T]
  |   | o- cephfs_metadata ............................................................... [(x3), Commit: 0b/77.0T (0%), Used: 256M]
  |   | o- iscsi-primary ................................................................ [(x3), Commit: 0b/77.0T (0%), Used: 11.2T]
  |   | o- iscsi-secondary ............................................................... [(x3), Commit: 0b/77.0T (0%), Used: 7.9T]
  |   | o- it_share .................................................................... [(9+1), Commit: 0b/26.5T (0%), Used: 84.2T]
  |   | o- nvme ........................................................................... [(x3), Commit: 0b/5.0T (0%), Used: 1.0T]
  |   | o- one ........................................................................... [(x3), Commit: 0b/77.0T (0%), Used: 765G]
  |   | o- rbd ......................................................................... [(x3), Commit: 2.1T/77.0T (2%), Used: 112G]
  |   | o- vmware_rep ................................................................... [(x3), Commit: 0b/77.0T (0%), Used: 10.3T]
  |   | o- vmware_ssd ................................................................... [(4+1), Commit: 0b/11.1T (0%), Used: 515G]
  |   | o- vmware_ssd_2_1 ................................................................ [(3+0), Commit: 0b/12.4T (0%), Used: 19b]
  |   | o- vmware_ssd_metadata ............................................................ [(x3), Commit: 0b/77.0T (0%), Used: 36b]
  |   o- topology .............................................................................................. [OSDs: 404,MONs: 3]
  o- disks ........................................................................................................ [2.1T, Disks: 3]
  | o- rbd.EyeTracker1_0 .................................................................................... [EyeTracker1_0 (2.0T)]
  | o- rbd.EyeTracker1_1 ..................................................................................... [EyeTracker1_1 (60G)]
  o- iscsi-target ..................................................................................................... [Targets: 1]
    o- iqn.2003-01.com.redhat.iscsi-gw:iscsi-igw ..................................................................... [Gateways: 2]
      o- gateways ............................................................................................ [Up: 2/2, Portals: 2]
      | o- dc1srviscsi01 ..................................................................................... [10.124.103.109 (UP)]
      | o- dc1srviscsi02 ..................................................................................... [10.124.103.110 (UP)]
      o- host-groups .................................................................................................. [Groups : 1]
      o- hosts .......................................................................................................... [Hosts: 4]
        o- iqn.1991-05.com.microsoft:eyetracker1 ...................................................... [Auth: None, Disks: 2(2.1T)]
        | o- lun 0 ................................................................. [rbd.EyeTracker1_0(2.0T), Owner: dc1srviscsi02]
        | o- lun 1 .................................................................. [rbd.EyeTracker1_1(60G), Owner: dc1srviscsi01]


On Wed, Oct 10, 2018 at 1:01 PM Mike Christie <mchristi@xxxxxxxxxx> wrote:
On 10/10/2018 12:40 PM, Mike Christie wrote:
> On 10/09/2018 05:09 PM, Brady Deetz wrote:
>> I'm trying to replace my old single point of failure iscsi gateway with
>> the shiny new tcmu-runner implementation. I've been fighting a Windows
>> initiator all day. I haven't tested any other initiators, as Windows is
>> currently all we use iscsi for.
>>
>> One issue I've considered is our Ceph cluster is running 12.2.8 but I
>> built my iscsi gateways against 13.2.2 since we will be moving to mimic
>> within the next month or so.
>>
>> I compiled tcmu-runner with default options against 13.2.2 on a fresh
>> fully updated version of centos 7.5.1804 with elrepo kernel 4.18.12-1.
>>
>> syslog:
>> Oct  9 16:55:31 dc1srviscsi01 tcmu-runner: tcmu_get_alua_grp:225
>> rbd/rbd.test_0: Unsupported alua_access_type: Implicit and Explicit
>> failover not supported.
>
> We do not yet support explicit failover. Did you use targetcli directly
> to set this up or did you use the ceph-iscsi tools?
>
> If you are using targetlci then you need to set alua_access_type to 1.
> In the rc releases for 1.4.0 we had explicit enabled but there were too
> many bugs and never got to fully QA it so for the final release it was
> disabled.
>
> If you used the ceph-iscsi tools did you use ansible or gwcli and what
> versions of ceph-iscsi-config and ceph-iscsi-cli or ceph-ansible?

Ignore that. ceph-iscsi-config 2.6 enabled explicit alua in anticipation
for the tcmu-runner support. We are about to release 2.7 which matches
tcmu-runner 1.4.0.
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux