Konrad Sztyber e1068a862c sma: configure crypto when attaching volumes ... Crypto parameters are now checked and crypto is configured when a volume is attached. Since configuring crypto can lead to creating new bdevs on top of the attached volume, each device manager will also need to be changed to retrieve the bdev through the CryptoEngine.get_crypto_bdev() interface. This will be done in subsequent patches. Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: Idb5f804cf88aa5e34bbee6817acdb8f3a42a2320 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/13870 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: <sebastian.brzezinka@intel.com>		2022-09-19 19:43:35 +00:00
..
device	sma: nvmf/vfiouser device manager implementation	2022-08-01 08:45:58 +00:00
proto	sma: volume crypto interface	2022-09-19 19:43:35 +00:00
volume	sma: configure crypto when attaching volumes	2022-09-19 19:43:35 +00:00
__init__.py	sma: initial crypto definitions	2022-09-19 19:43:35 +00:00
common.py	sma: initial Storage Management Agent structures	2022-05-18 07:24:06 +00:00
qmp.py	sma: QMP base definitions created	2022-05-20 09:16:54 +00:00
sma.py	sma: initial crypto definitions	2022-09-19 19:43:35 +00:00