trim the trailing
whitespace on save, since most of good editors have such ability…
--
Cheers,
Roman Dobosz
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.o
as the interface, and provide a
vim plugin (which could be written in python) for review activities.
Although it may be unsuitable for other editor users.
--
Cheers,
Roman Dobosz
__
OpenStack Development Mailing List (not for us
ce providers spec proposal.
Great, thank you!
> The only thing I'd say is that I was envisioning the dynamic resource
> classes for FPGAs to be the resource context to an already-flashed
> algorithm, not to the FPGA root device (or a region even). But, who
> knows, p
e number of region/slot.
> Inside FPGA, there can be some self-scheduling logic to schedule
> accelerators on regions by using the fast partial reconfiguration.
> It is not new, there are lots of such design in FPGA academic.
Right, but not all devices have such functiona
allocation.
OTOH if we need to store the information which VF is passed to which
VM, than probably we need this level, or store VF addresses in
inventory/allocation in some new filed.
--
Cheers,
Roman Dobosz
__
OpenSt
p; pre-divided into a fixed number of slots and simply
> deal with this. This is similar to how we dealt with PCI SR-IOV initially
> where we assumed the dev is in VF-mode only. Only later did we start to
> add cleverness around switching VF vs PF mode. For FPGA I think any kind
> of
going to have the host program the
> > FPGA and then make the resources available then the scheduler
> > doesn't need to know about whole FPGAs.
>
> That was where we left the discussion in Austin, so that was my
> assumption.
… as the first step, isn't it? No one is pushing
tarted. Now
we have resource tree HostA FPGA->slot->AX1 and HostB FPGA.
Next, user requests another VM with AY accelerator, scheduler now
should know, that the only available option is HostB, so again magic
is happening, and there is a resource tree:
HostA FPGA
+- slot1
+- AX1
H
ply brought up by external entity (assumed
library or service) which will take care about burden for preparing
such IP accelerator/IP on free slot, and takes care about updating
information of allocations and dynamic resources.
Thoughts?
--
Cheers,
Roman Dobosz
#x27;t be).
It is similar, but not the same. Using RabbitMQ/pika alone it is fairly
easy to accomplish the goal for using messaging system to wait for the
result. Difference is, there is no external queue involved.
--
Cheers,
Roman Dobosz
;
> Thoughts from others?
Option #4
(Which might be obvious) Directly use RabbitMQ driver, like
pika/kombu, which can expose all the message queue features to the
project.
Issues raised: Pushback from the community due not using
oslo.messaging and potential necessity for implementing it for o
.
>
> You are more than welcomed to join the conversation : )
Thanks! I'll try to attend.
Nevertheless, I've briefly looked at page of project Nomad, and don't
quite get it, how this might be related to cases described in this
thread - i.e. prov
> I think you shouldn't look at the FPGAs as being like CPU resource, but
> rather look at them as a generalization of PCI device asignment.
CPU in this context was only an example of "easy" resource, which
doesn't need any preparation before VM can use it :)
--
Chee
tel.com/content/dam/doc/white-paper/quickassist-technology-aal-white-paper.pdf
--
Cheers,
Roman Dobosz
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subj
ion of vms from the
host (so it is kind of bulk) but the loop is implemented in nova-client
- it could be one of the options to implement something similar,
although it's not best approach, IMHO.
--
Cheers,
Roman Dobosz
__
ch problem (long running tasks) could be resolved
in OpenStack?
[1] http://blog.russellbryant.net/2014/10/15/openstack-instance-ha-proposal/
[2] https://github.com/dawiddeja/evacuationd
--
Cheers,
Roman Dobosz
__
OpenStack D
so serialization
might also be done on such layer.
Hope that clear your doubts.
--
Cheers,
Roman Dobosz
__
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
On Wed, 3 Dec 2014 08:44:57 +0100
Roman Dobosz wrote:
> I've just started to work on the topic of detection if host is alive or
> not: https://blueprints.launchpad.net/nova/+spec/host-health-monitoring
>
> I'll appreciate any comments :)
I've submitted another
Hi,
I've just started to work on the topic of detection if host is alive or
not: https://blueprints.launchpad.net/nova/+spec/host-health-monitoring
I'll appreciate any comments :)
--
Kind regards
Roman
___
OpenStack-dev mailing list
OpenStack-dev@lis
19 matches
Mail list logo
