Open Stack

On Thu, 21 Jul 2016 08:44:21 +0800
Fei K Chen <uchen at cn.ibm.com> wrote:

> > 4. It might be also necessary to track every VF individually, although
> >    I didn't assumed it will be needed, nevertheless with nested
> >    resources it should be easy to handle it.
> You need. For example you have 4 region and 8 VF. Some region is 
> configured with an accelerator so it can be shared to multi-VM (each 
> consume a VF). But some other region is configured with private 
> exclusive accelerator so it can only be bind to one VF. That's why 
> we need to track both region and VF.

Well, it depends. If there is no difference between the VF (all 
provides the same functionality) and we don't really care about the 
placement (external entity would take care of this) than we don't need 
this level. All the information will be hold by resource inventory and 
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