Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: helloway <simple_hlw at 163.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Integrate OpenStack/Cyborg into SPDK Architecture
Date: Sat, 28 Sep 2019 02:06:05 +0000	[thread overview]
Message-ID: <a176929.425.163f684f996.Coremail.simple_hlw@163.com> (raw)
In-Reply-To: 82C9F782B054C94B9FC04A331649C77AAD46D4AA@FMSMSX108.amr.corp.intel.com

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

Hi Paul,
Thank you for your response, I have submitted a trello [0] titled  “Integrate OpenStack/Cyborg into SPDK Architecture”. I am trying to answer your questions from this trello, do I make sense? I really hope to receive your feedback.


[0]https://trello.com/c/QfSAkLSS/121-integrate-openstack-cyborg-into-spdk-architecture 


Thx,
Helloway
On 06/12/2018 08:16,Luse, Paul E<paul.e.luse(a)intel.com> wrote:

Hi Helloway,

 

I was actually just wondering what had happened with this.  Looking at the OpenStack patch it looks like it’s close to landing. Somewhere out there we have a Cinder driver that’s also getting fairly close I believe so for sure integration with OpenStack is interesting to many in the community.

 

Would you be able to summarize more specifically how your patch would work once it lands? I of course see your high level description below that some questions that I have, I’m assuming others as well, include:

 

- what else is required to be pushed into OpenStack for this to work

- is anything required in the SPDK repo for this to work

- how will the necessary SPDK components be associated with the VM in question and subsequently configured

 

Thanks for continuing to work on this!

 

-Paul

 

From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of helloway
Sent: Monday, June 11, 2018 1:35 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] Integrate OpenStack/Cyborg into SPDK Architecture

 

Hi Jim and all,

 

Do you know OpenStack/Cyborg? It is OpenStack acceleration service which provides a management framework for accelerator devices (e.g. FPGA, GPU, NVMe SSD). There is a strong demand for OpenStack to support hardware accelerated devices in a dynamic model(mentioned in OpenStack Summit Vancouver 2018 [0]). 

 

For this reason, we can use Cyborg to interactive with nvmf_tgt to realize the management of the user space accelerator NVMe SSD device, which can badly promote the efficiency. It is worth mentioning that the Cyborg_SPDK_Driver I summitted has been merged into the OpenStack version Q [1]. The driver can report the detailed information of the device to the Cyborg agent. When user requests a vm with a user space NVMe SSD, Cyborg agent will update the Nova/Placement inventory on available NVMe devices. This is a complete process to describe the connection of Cyborg and SPDK.

 

I wonder whether you guys are interested in integrating OpenStack/Cyborg into SPDK architecture? Do I make sense? Please let me know what your thoughts.

 

[0]https://www.openstack.org/videos/vancouver-2018/optimized-hpcai-cloud-with-openstack-acceleration-service-and-composable-hardware

[1]https://review.openstack.org/#/c/538164/

 

 

Thx,

Helloway

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 9452 bytes --]

             reply	other threads:[~2019-09-28  2:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-28  2:06 helloway [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-28  2:06 [SPDK] Integrate OpenStack/Cyborg into SPDK Architecture helloway
2019-09-28  2:06 helloway
2018-06-21  0:41 Zhipeng Huang
2018-06-20 15:43 Harris, James R
2018-06-20  6:48 Bob Chen
2018-06-20  4:53 Zhipeng Huang
2018-06-19 16:42 Walker, Benjamin
2018-06-17  0:20 Zhipeng Huang
2018-06-16 15:15 Luse, Paul E
2018-06-16  1:27 Zhipeng Huang
2018-06-15 14:28 Szwed, Maciej
2018-06-14  3:26 Luse, Paul E
2018-06-13 14:46 Luse, Paul E
2018-06-12  0:16 Luse, Paul E

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=a176929.425.163f684f996.Coremail.simple_hlw@163.com \
    --to=spdk@lists.01.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox