[SPDK] Re: About SMA + IPU

--===============7923352404974005756==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Hi Yibo,

The sequence you've listed is pretty close to how I understand it, except f=
or this part:

> - IPU sends SPDK-RPC commands to some storage node through http proxy,
> to create bdev, export NVMe-oF target

I don't think IPU is responsible for configuring the target side. That shou=
ld be done by some other external orchestrator prior to sending the CreateD=
evice/AttachVolume commands.

Konrad

> -----Original Message-----
> From: Yibo Cai <yibo.cai(a)arm.com>
> Sent: Friday, June 24, 2022 10:21 AM
> To: spdk(a)lists.01.org
> Subject: [SPDK] About SMA + IPU
> =

> Hi,
> =

> I'm struggling in understand use cases of SMA(Storage Management Agent)
> and IPU(Infrastructure Processing Unit). Would like to seek for help.
> =

> Assume a host with IPU, connected to a remote storage node running SPDK
> service.
> =

> If an app on host CPU needs storage resource, in my understanding, below
> steps will happen:
> - app (or orchestrator) sends SMA CreateDevice/AttachVolume commands to
> the SPDK service running on IPU
> - IPU sends SPDK-RPC commands to some storage node through http proxy,
> to create bdev, export NVMe-oF target
> - IPU runs NVMe initiator to connect to remote NVMe-oF target
> - IPU exposes the NVMe-oF target as a local NVMe device to host OS, so the
> app (or orchestrator) can make use of it
> =

> Is that correct?
> =

> Yibo
> _______________________________________________
> SPDK mailing list -- spdk(a)lists.01.org
> To unsubscribe send an email to spdk-leave(a)lists.01.org
--===============7923352404974005756==--