NVMf initiator persistent across boots

[Johannes Thumshirn]

On Thu, Mar 08, 2018 at 03:15:42PM +0200, Max Gurtovoy wrote:
> Yes, I got it.
> IMO if you will add:
> -t rdma -a 1.1.1.1 -s 4420 -w 1.1.1.2
> -t rdma -a 1.1.1.1 -s 4420 -w 1.1.1.3
> 
> to the discovery file it should be fine.
> I think we'll need to fix few things in nvmecli and in the driver too.
> I'm checking this.

Hmm interesting. This probably was too obvious for me to try...

> > Good question. I'd be fine with both. The only thing that should be
> > considered as well is, if you already need the nvmf connection in the
> > initrd, you'll have to rebuild the initrd after each change of
> > /etc/nvme/discovery.conf and thus every nvme
> > persist-add/persist-remove (or discover --persistent) call.
> 
> Let's assume that we don't need it for now, otherwise it will be unpleasent
> :)

Given the number of "Boot from SAN failed with XXX" Bugs I have seen
the last years I doubt we won't need it ;-).

But yes we can think about this in step two I guess.

-- 
Johannes Thumshirn                                          Storage
jthumshirn at suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850