[SPDK] NVMeF online namespace management

[SPDK] NVMeF online namespace management

[shahar.salzman]

[-- Attachment #1: Type: text/plain, Size: 680 bytes --]

Hi guys!

New to this mailing list, awesome project!

We have been integrating the NVMeF target into our appliance. In our 
appliance, the user can add/remove volumes on the fly, these volumes 
need to be exposed to the NVMeF target.

We are looking for a way to avoid the static configuration file 
namespace allocation, I noticed that there is an RPC mechanism which 
does this for iSCSI LUNs, but for NVMeF seems to only create a subsystem 
with a fixed # of namespaces.

The RPC is ideal for integration into our management as it is python, 
would this be the correct place to add namespaces to a subsystem on the fly?

Thanks for any help,
Shahar Salzman

Re: [SPDK] NVMeF online namespace management

[Marushak, Nathan]

[-- Attachment #1: Type: text/plain, Size: 2556 bytes --]

Adding to Cunyin's response a bit, the community is planning to transition more (as much as sensible) of the configuration to RPC. So, there will be active changes in this area over the next couple of releases.

The changes would definitely benefit from your participation in the development process in this area.


> -----Original Message-----
> From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Chang, Cunyin
> Sent: Thursday, November 09, 2017 4:56 PM
> To: Storage Performance Development Kit <spdk(a)lists.01.org>
> Cc: Eran Mann <eran.mann(a)kaminario.com>; Yael Shavit
> <yael.shavit(a)kaminario.com>; open-source-contrib(a)kaminario.com; Ilan
> Steinberg <ilan.steinberg(a)kaminario.com>
> Subject: Re: [SPDK] NVMeF online namespace management
> 
> Hi,
> 
> Please see my embedded comment:
> 
> > -----Original Message-----
> > From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of
> > shahar.salzman
> > Sent: Thursday, November 9, 2017 6:16 PM
> > To: spdk(a)lists.01.org
> > Cc: Yael Shavit <yael.shavit(a)kaminario.com>; Eran Mann
> > <eran.mann(a)kaminario.com>; open-source-contrib(a)kaminario.com; Ilan
> > Steinberg <ilan.steinberg(a)kaminario.com>
> > Subject: [SPDK] NVMeF online namespace management
> >
> > Hi guys!
> >
> > New to this mailing list, awesome project!
> >
> > We have been integrating the NVMeF target into our appliance. In our
> > appliance, the user can add/remove volumes on the fly, these volumes
> > need to be exposed to the NVMeF target.
> >
> > We are looking for a way to avoid the static configuration file
> > namespace allocation, I noticed that there is an RPC mechanism which
> > does this for iSCSI LUNs, but for NVMeF seems to only create a
> > subsystem with a fixed # of namespaces.
> >
> > The RPC is ideal for integration into our management as it is python,
> > would this be the correct place to add namespaces to a subsystem on the
> fly?
> 
> RPC method is the correct interface to start the process, but the detail
> work should be done by nvmf library, For example we need attach the bdev to
> NS accordingly, update the identify information of the controller and
> namespace.
> 
> >
> > Thanks for any help,
> > Shahar Salzman
> >
> > _______________________________________________
> > SPDK mailing list
> > SPDK(a)lists.01.org
> > https://lists.01.org/mailman/listinfo/spdk
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk

Re: [SPDK] NVMeF online namespace management

[Chang, Cunyin]

[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]

Hi,

Please see my embedded comment:

> -----Original Message-----
> From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of shahar.salzman
> Sent: Thursday, November 9, 2017 6:16 PM
> To: spdk(a)lists.01.org
> Cc: Yael Shavit <yael.shavit(a)kaminario.com>; Eran Mann
> <eran.mann(a)kaminario.com>; open-source-contrib(a)kaminario.com; Ilan
> Steinberg <ilan.steinberg(a)kaminario.com>
> Subject: [SPDK] NVMeF online namespace management
> 
> Hi guys!
> 
> New to this mailing list, awesome project!
> 
> We have been integrating the NVMeF target into our appliance. In our
> appliance, the user can add/remove volumes on the fly, these volumes need
> to be exposed to the NVMeF target.
> 
> We are looking for a way to avoid the static configuration file namespace
> allocation, I noticed that there is an RPC mechanism which does this for iSCSI
> LUNs, but for NVMeF seems to only create a subsystem with a fixed # of
> namespaces.
> 
> The RPC is ideal for integration into our management as it is python, would
> this be the correct place to add namespaces to a subsystem on the fly?

RPC method is the correct interface to start the process, but the detail work should be done by nvmf library,
For example we need attach the bdev to NS accordingly, update the identify information of the controller and 
namespace.

> 
> Thanks for any help,
> Shahar Salzman
> 
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk