Open Stack

I like the idea of having a generic consumable resource on the hypervisor.
You could use things other than PCI passthrough to pass disks or graphics
cards to the host.

Is there anything beyond extraspecs and the current resource allocator
logic that is required here?

Not sure about using it for resources you can over provision though, like
CPU or Memory though. That seems to be a separate class of thing already
handled quite well. Also leaving memory and CPU a special primary resource
in the flavor seems good from an interop point of view.

John
On May 30, 2013 12:01 PM, "Kaarle Ritvanen" <kaarle.ritvanen at nsn.com> wrote:

> Hello,
>
> I have an improvement proposal for this blueprint detailing how to
> allocate PCI devices to instances:
>
> https://blueprints.launchpad.**net/nova/+spec/pci-**passthrough-base<https://blueprints.launchpad.net/nova/+spec/pci-passthrough-base>
>
> The blueprint proposes mechanisms to declare what kind of PCI devices are
> required in flavor definition, making scheduling decisions based on device
> availability, and attaching the device to the instance at hypervisor level.
>
> I feel this pattern is not specific to PCI devices in any way. In a
> generalized version, the flavor declares the instance requires X units of
> resources of type Y. The host would advertise to the scheduler how much of
> Y it currently has available, and use a hypervisor-specific mechanism to
> actually allocate X units of Y to the instance if deployed there. Y could
> be memory, CPU time, network bandwidth (to a given Quantum network),
> storage capacity or bandwith, PCI device or virtual function etc. In case
> of KVM, the hypervisor-specific mechanism could be based e.g. on cgroups or
> tc.
>
> I think we should consider making the API generic enough to cover all
> these use cases. We could also clean up the current flavor definitions by
> consolidating the memory and disk requirements under this generic API.
>
> BR,
> Kaarle
>
> ______________________________**_________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.**org <OpenStack-dev at lists.openstack.org>
> http://lists.openstack.org/**cgi-bin/mailman/listinfo/**openstack-dev<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130607/f6c12b04/attachment.html>