Spdk/python/spdk/sma/device/__init__.py

from .device import DeviceException
from .device import DeviceManager
from .nvmf_tcp import NvmfTcpDeviceManager
from .vhost_blk import VhostBlkDeviceManager
sma: initial Storage Management Agent structures Storage Management Agent is a gRPC server that provides an abstraction layer above the SPDK RPC interface. The interface aims to provide a set of methods for managing various protocols (e.g. NVMe, virtio-blk) while hiding the details of a particular transport. The external API is defined by `lib/python/spdk/sma/proto/sma.proto` protobuf file. It defines the generic gRPC service methods and their requests/responses. Device-specific messages are defined in their own files. This patch also defines messages for creating NVMe and NVMe/TCP devices. This patch implements a gRPC service that delegates the work to a specific device type. A DeviceManager is a class that implements some of the methods defined by the service for a given type of devices (e.g. NVMe, virtio-blk, NVMe/TCP, etc.). For now, only the RPC for creating a device is implemented, others are added in subsequent patches. The series implements the generic calls as well as their NVMe/TCP implementation. Support for other devce types could be easily added by creating a new device manager and defining its protobuf parameter definition. Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: I17cde3b31d3514878f1027cfcd112b48848f6123 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/10273 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot 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> 2022-01-05 09:32:09 +00:00			`from .device import DeviceException`
			`from .device import DeviceManager`
			`from .nvmf_tcp import NvmfTcpDeviceManager`
sma: vhost-user sma implementation This patch utilize generic sma implementation by adding vhost-user devices manager. It's allow to expose virtualized block devices to QEMU instances or other arbitrary processes. Max device capacity depend on available `pci-bridge` ``` devices: - name: 'vhost_blk' params: buses: - name: 'pci.spdk.0' count: 32 - name: 'pci.spdk.1' count: 32 qmp_addr: 127.0.0.1 qmp_port: 9090 ``` To attach `pci-bridge` at boot time we need to run qemu with this option ``` device pci-bridge,chassis_nr=1,id=pci.spdk.0 device pci-bridge,chassis_nr=2,id=pci.spdk.1 `` Change-Id: Idbe841b12cf59975ff0e6717f8dc905d38379357 Signed-off-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12207 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by: Artek Koltun <artsiom.koltun@intel.com> 2022-04-08 11:43:28 +00:00			`from .vhost_blk import VhostBlkDeviceManager`