ad323b8064
Previous patches enabled users to configure CHAP secrets dynamically by RPCs. Subsequent patches will enable users to load CHAP secrets from JSON config file. Loading CHAP secret file is done by default and this will conflict to JSON config file. Hence the path to CHAP secret file is required to specify in the config file or JSON RPC set_iscsi_options explicitly after this patch. Users who have used CHAP secret file are expected to specify it explicitly and this will be no harm for them. Besides, CHAP secret file is not oly for discovery sessions but also for login to iSCSI targets. However there were wrong description to make user misunderstand. Hence remove these wrong description in this patch too. Change-Id: Ic4093cabc0c14b87e26baef4bba6b0d292e40c06 Signed-off-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-on: https://review.gerrithub.io/421467 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| app.py | ||
| bdev.py | ||
| client.py | ||
| ioat.py | ||
| iscsi.py | ||
| log.py | ||
| lvol.py | ||
| nbd.py | ||
| net.py | ||
| nvmf.py | ||
| pmem.py | ||
| subsystem.py | ||
| vhost.py | ||