Re: [openstack-dev] [Nova] FPGA as a resource

2016-04-06 Thread Fei K Chen
Teng <teng...@linux.vnet.ibm.com> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Cc: Fei K Chen/China/IBM@IBMCN, Yong Hua Lin/China/IBM@IBMCN Date: 2016/04/06 12:25 Subject: Re: [openstac

Re: [openstack-dev] [Nova] FPGA as a resource

2016-04-06 Thread Rayson Ho
On Wed, Apr 6, 2016 at 6:37 AM, Daniel P. Berrange wrote: > Most of the > work to support FPGA will be internal to nova, to deal with modelling > of assignable devices and their scheduling / allocation. I think the EPA blueprint already covers some of the FPGA device

Re: [openstack-dev] [Nova] FPGA as a resource

2016-04-06 Thread Zhipeng Huang
Yes the project is quite new, we are still developing requirements at the OPNFV side. We will update with full description after the summit when we got all the inputs. Look forward to have a chat with you at the summit :) I think you are right that Nomad does not solve the problem per se in this

Re: [openstack-dev] [Nova] FPGA as a resource

2016-04-06 Thread Daniel P. Berrange
On Wed, Apr 06, 2016 at 12:28:02PM +0200, Roman Dobosz wrote: > On Wed, 6 Apr 2016 16:12:16 +0800 > Zhipeng Huang wrote: > > > You are actually touching on something we have been working on. There is a > > team in OPNFV DPACC project has been working acceleration related

Re: [openstack-dev] [Nova] FPGA as a resource

2016-04-06 Thread Roman Dobosz
On Wed, 6 Apr 2016 16:12:16 +0800 Zhipeng Huang wrote: > You are actually touching on something we have been working on. There is a > team in OPNFV DPACC project has been working acceleration related topics, > including folks from CMCC, Intel, ARM, Freescale, Huawei. We

Re: [openstack-dev] [Nova] FPGA as a resource

2016-04-06 Thread Daniel P. Berrange
On Wed, Apr 06, 2016 at 07:34:46AM +0200, Roman Dobosz wrote: > On Tue, 5 Apr 2016 13:58:44 +0100 > "Daniel P. Berrange" wrote: > > > Along similar lines we have proposals to add vGPU support to Nova, > > where the vGPUs may or may not be exposed using SR-IOV. We also want >

Re: [openstack-dev] [Nova] FPGA as a resource

2016-04-06 Thread Zhipeng Huang
Hi Roman, You are actually touching on something we have been working on. There is a team in OPNFV DPACC project has been working acceleration related topics, including folks from CMCC, Intel, ARM, Freescale, Huawei. We found out that in order to have acceleration working under NFV scenrios,

Re: [openstack-dev] [Nova] FPGA as a resource

2016-04-05 Thread Roman Dobosz
On Tue, 5 Apr 2016 13:58:44 +0100 "Daniel P. Berrange" wrote: > Along similar lines we have proposals to add vGPU support to Nova, > where the vGPUs may or may not be exposed using SR-IOV. We also want > to be able to on the fly decide whether any physical GPU is assigned >

Re: [openstack-dev] [Nova] FPGA as a resource

2016-04-05 Thread Gerard Braad
Hi, On Tue, Apr 5, 2016 at 8:58 PM, Daniel P. Berrange wrote: >> As you can see, it seems not complicated at this point, however it >> become more complex due to following things we also have to take into >> consideration: I agree with this. Many kinds of resources could be

Re: [openstack-dev] [Nova] FPGA as a resource

2016-04-05 Thread Qiming Teng
Emm... finally this is brought up. We from IBM have already done some work on FPGA/GPU resource management [1]. Let me bring the SMEs into this discussion and see if we together can work out a concrete roadmap to land this upstream. Fei and Yonghua, this is indeed very interesting a topic for us.

Re: [openstack-dev] [Nova] FPGA as a resource

2016-04-05 Thread Daniel P. Berrange
On Tue, Apr 05, 2016 at 02:27:30PM +0200, Roman Dobosz wrote: > Hey all, > > On yesterday's scheduler meeting I was raised the idea of bringing up > the FPGA to the OpenStack as the resource, which than might be exposed > to the VMs. > > The use cases for motivations, why one want do this, are

[openstack-dev] [Nova] FPGA as a resource

2016-04-05 Thread Roman Dobosz
Hey all, On yesterday's scheduler meeting I was raised the idea of bringing up the FPGA to the OpenStack as the resource, which than might be exposed to the VMs. The use cases for motivations, why one want do this, are pretty broad - having such chip ready on the computes might be beneficial