All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Cc: Keith Busch <kbusch@kernel.org>, Hannes Reinecke <hare@suse.de>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [RFC PATCH 0/5] nvmetcli: REST API for remote configuration
Date: Tue, 5 Dec 2023 05:58:04 +0000	[thread overview]
Message-ID: <e72f68dc-455c-47dc-ac1e-e5e7bb009ddc@nvidia.com> (raw)
In-Reply-To: <2c945f01-2b57-4b89-99c5-5cecdbb697c5@nvidia.com>

On 11/13/23 20:20, Chaitanya Kulkarni wrote:
> On 11/13/2023 7:27 AM, Hannes Reinecke wrote:
>> Hi all,
>>
>> here's an attempt to allow remote configuration via a JSON REST API.
>> It's basically using the configfs paths as the web URI, and using
>> http 'GET', 'PUT', and 'PATCH' to retrieve, create, or modify the
>> nvmet configuration.
>> I've also included a REST API responder based on flask to handle API
>> calls.
>> To test it out just do:
>>
>> # python nvmetapi
>>
>> and on another console:
>>
>> # export NVMET_URI=http://127.0.0.1:5000/
>> # python ./nvmetcli ls
>>
>> and you should be seeing the same output as you would when running
>> local (albeit with a 'small' delay as it fetches the data via the network).
>>
>> As usual, comments and reviews are welcome.
>
> I'm at LPC, I'll give it a try once I'm back.
>
> -ck
>
>
>

I did take a quick look into this series, overall I like this idea of 
allowing
remote configuration, Sagi/Christoph do you guys have any objections ?

-ck



      reply	other threads:[~2023-12-05  5:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231113152709.30894-1-hare@suse.de>
2023-11-14  4:20 ` [RFC PATCH 0/5] nvmetcli: REST API for remote configuration Chaitanya Kulkarni
2023-12-05  5:58   ` Chaitanya Kulkarni [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e72f68dc-455c-47dc-ac1e-e5e7bb009ddc@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.