[ceph-users] Re: iSCSI Gateway reboots and permanent loss

2019-12-03 Thread Jason Dillaman
If I recall correctly, the recent ceph-iscsi release supports the removal of a gateway via the "gwcli". I think the Ceph dashboard can do that as well. On Tue, Dec 3, 2019 at 1:59 PM Wesley Dillingham wrote: > > We utilize 4 iSCSI gateways in a cluster and have noticed the following > during pat

[ceph-users] Re: iSCSI Gateway reboots and permanent loss

2019-12-03 Thread Paul Emmerich
Gateway removal is indeed supported since ceph-iscsi 3.0 (or was it 2.7?) and it works while it is offline :) Paul -- Paul Emmerich Looking for help with your Ceph cluster? Contact us at https://croit.io croit GmbH Freseniusstr. 31h 81247 München www.croit.io Tel: +49 89 1896585 90 On Tue, De

[ceph-users] Re: iSCSI Gateway reboots and permanent loss

2019-12-03 Thread Mike Christie
I do not think it's going to do what you want when the node you want to delete is down. It looks like we only temporarily stop the gw from being exported. It does not update the gateway.cfg, because we do the config removal call on the node we want to delete. So gwcli would report success and the

[ceph-users] Re: iSCSI Gateway reboots and permanent loss

2019-12-03 Thread Wesley Dillingham
Thanks. If I am reading this correctly the ability to remove an iSCSI gateway would allow the remaining iSCSI gateways to take over for the removed gateway's LUN's as of > 3.0. Thats good, we run 3.2. However, because the actual update of the central config object happens from the to-be-deleted iSC

[ceph-users] Re: iSCSI Gateway reboots and permanent loss

2019-12-03 Thread Mike Christie
On 12/03/2019 04:19 PM, Wesley Dillingham wrote: > Thanks. If I am reading this correctly the ability to remove an iSCSI > gateway would allow the remaining iSCSI gateways to take over for the > removed gateway's LUN's as of > 3.0. Thats good, we run 3.2. However, > because the actual update of the

[ceph-users] Re: iSCSI Gateway reboots and permanent loss

2019-12-04 Thread Gesiel Galvão Bernardes
Hi, Em qua., 4 de dez. de 2019 às 00:31, Mike Christie escreveu: > On 12/03/2019 04:19 PM, Wesley Dillingham wrote: > > Thanks. If I am reading this correctly the ability to remove an iSCSI > > gateway would allow the remaining iSCSI gateways to take over for the > > removed gateway's LUN's as o

[ceph-users] Re: iSCSI Gateway reboots and permanent loss

2019-12-04 Thread Jason Dillaman
On Wed, Dec 4, 2019 at 9:27 AM Gesiel Galvão Bernardes wrote: > > Hi, > > Em qua., 4 de dez. de 2019 às 00:31, Mike Christie > escreveu: >> >> On 12/03/2019 04:19 PM, Wesley Dillingham wrote: >> > Thanks. If I am reading this correctly the ability to remove an iSCSI >> > gateway would allow the

[ceph-users] Re: iSCSI Gateway reboots and permanent loss

2019-12-04 Thread Mike Christie
On 12/04/2019 08:26 AM, Gesiel Galvão Bernardes wrote: > Hi, > > Em qua., 4 de dez. de 2019 às 00:31, Mike Christie > escreveu: > > On 12/03/2019 04:19 PM, Wesley Dillingham wrote: > > Thanks. If I am reading this correctly the ability to remove an iSCSI >

[ceph-users] Re: iSCSI Gateway reboots and permanent loss

2019-12-04 Thread Wesley Dillingham
I have never had a permanent loss of a gateway but I'm a believer in Murphy's law and want to have a plan. Glad to hear that there is a solution in-the-works, curious when might that be available in a release? If sooner than later I'll plan to upgrade then immediately, otherwise, if far down the qu

[ceph-users] Re: iSCSI Gateway reboots and permanent loss

2019-12-05 Thread Mike Christie
On 12/04/2019 02:34 PM, Wesley Dillingham wrote: > I have never had a permanent loss of a gateway but I'm a believer in > Murphy's law and want to have a plan. Glad to hear that there is a > solution in-the-works, curious when might that be available in a > release? If sooner than later I'll plan t

[ceph-users] Re: iSCSI Gateway reboots and permanent loss

2019-12-05 Thread Wesley Dillingham
Thats great thank you so much. I will try and get this patch in my test env asap but will likely wait for official release cut for prod. I really appreciate you adding this in to the product. Respectfully, *Wes Dillingham* w...@wesdillingham.com LinkedIn