(Please excuse the top-posting)

The other possibility is that the Cyborg managed devices are plumbed in via
IP in guest network space. Then "attach" isn't so much a Nova problem as a
Neutron one - probably similar to Manila.
Has the Cyborg team considered a RESTful-API proxy driver, i.e., something
that wraps a vendor-specific accelerator service and makes it friendly to a
multi-tenant OpenStack cloud? Quantum co-processors might be a compelling
example which fit this model.

Cheers,

On Sun., 20 May 2018, 23:28 Chris Friesen, <chris.frie...@windriver.com>
wrote:

> On 05/19/2018 05:58 PM, Blair Bethwaite wrote:
> > G'day Jay,
> >
> > On 20 May 2018 at 08:37, Jay Pipes <jaypi...@gmail.com> wrote:
> >> If it's not the VM or baremetal machine that is using the accelerator,
> what
> >> is?
> >
> > It will be a VM or BM, but I don't think accelerators should be tied
> > to the life of a single instance if that isn't technically necessary
> > (i.e., they are hot-pluggable devices). I can see plenty of scope for
> > use-cases where Cyborg is managing devices that are accessible to
> > compute infrastructure via network/fabric (e.g. rCUDA or dedicated
> > PCIe fabric). And even in the simple pci passthrough case (vfio or
> > mdev) it isn't hard to imagine use-cases for workloads that only need
> > an accelerator sometimes.
>
> Currently nova only supports attach/detach of volumes and network
> interfaces.
> Is Cyborg looking to implement new Compute API operations to support hot
> attach/detach of various types of accelerators?
>
> Chris
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to