On Tue, Jun 11, 2019 at 4:24 PM Wesley Dillingham <wdillingham@xxxxxxxxxxx> wrote:
(running 14.2.0 and ceph-iscsi-3.0-57.g4ae4444)
and configuring the dash as follows:
ceph dashboard set-iscsi-api-ssl-verification false
ceph dashboard iscsi-gateway-add http://admin:admin@${MY_HOSTNAME}:5000systemctl restart ceph-mgr@${MY_HOSTNAME_SHORT}.service
in the dash block/iscsi/target shows:
Unsupported `ceph-iscsi` config version. Expected 8 but found 9.
Thanks again.
this means your ceph-iscsi version is too new.
There isn't an officially supported way to downgrade it, though, so the best way is to wait for this version to be supported in the dashboard.
(Or well, the config version 9 change is rather trivial, you can undo it manually in gateway.conf: https://github.com/ceph/ceph-iscsi/commit/2d2f26ac54149a0c0d598e0640bcfd75adb69432 )
Paul
_______________________________________________
From: Jason Dillaman <jdillama@xxxxxxxxxx>
Sent: Tuesday, June 11, 2019 9:37 AM
To: Wesley Dillingham
Cc: ceph-users@xxxxxxxxxxxxxx
Subject: Re: limitations to using iscsi rbd-target-api directly in lieu of gwcliNotice: This email is from an external sender.
On Tue, Jun 11, 2019 at 9:29 AM Wesley Dillingham
<wdillingham@xxxxxxxxxxx> wrote:
>
> Hello,
>
> I am hoping to expose a REST API to a remote client group who would like to do things like:
>
>
> Create, List, and Delete RBDs and map them to gateway (make a LUN)
> Create snapshots, list, delete, and rollback
> Determine Owner / Active gateway of a given lun
It currently doesn't have any RBAC style security so I would be weary
about exposing the current REST API to arbitrary users since you would
give them full access to do anything. The Ceph dashboard in Nautilus
(and also improved in the master branch) has lots of hooks to
configure LUNs via the rbd-target-api REST API as another alternative
to look at.
> I would run 2-4 nodes running rbd-target-gw and rbd-target-api however client wishes to not use multi-path, wants to connect directly and only to active gateway for that lun
The current rbd-target-api doesn't really support single path LUNs.
> In order to prevent re-inventing the wheel I was hoping to simply expose the rbd-target-api directly to client but am wondering if this is appropriate.
>
> My concern is that I am taking gwcli out off the picture by using rbd-target-api directly and am wondering if the rbd-target-api on its own is able to propagate changes in the config up to the RADOS configuration object and thus keep all the gateways in sync.
gwcli just uses rbd-target-api to do the work, and rbd-target-api is
responsible for keeping the gateways in-sync with each other.
> My other thought was to build a simple and limited in scope api which on the backend runs gwcli commands.
>
> Thank you for clarification on the functionality and appropriate use.
>
> Respectfully,
>
> Wes Dillingham
> wdillingham@xxxxxxxxxxx
> Site Reliability Engineer IV - Platform Storage / Ceph
>
> _______________________________________________
> ceph-users mailing list
> ceph-users@xxxxxxxxxxxxxx
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
--
Jason
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
