Bug 1299678 - Nova support for Intel Cache Allocation Technology
Summary: Nova support for Intel Cache Allocation Technology
Keywords:
Status: CLOSED DUPLICATE of bug 1411864
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Eoghan Glynn
QA Contact: nlevinki
URL:
Whiteboard:
Depends On: 1288964 1289368 1547015
Blocks: 1412215
TreeView+ depends on / blocked
 
Reported: 2016-01-19 00:36 UTC by Karen Noel
Modified: 2019-09-09 13:46 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1289368
Environment:
Last Closed: 2017-07-25 14:31:23 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Karen Noel 2016-01-19 00:36:40 UTC
+++ This bug was initially created as a clone of Bug #1289368 +++

Kernel support for CAT requires libvirt support:

Bug 1288964 - [Intel 7.3 FEAT] Enable Cache Allocation Technology (CAT)

Comment 2 Sahid Ferdjaoui 2016-01-19 15:58:48 UTC
A spec will have to be addressed, after a first look this feature needs some work in several components of Nova to maintain/schedule/consume host's cache. I can work on that spec and implementation it when libvirt will provides information about cache and feature to use it for guests.

Comment 5 Kashyap Chamarthy 2017-01-06 15:03:02 UTC
After having a quick chat with the Real Time folks Rik van Riel, and 
Luiz Capitulino, A quick summary of current status.  There are a couple
of things at play here.

 - Kernel. The Kernel infrastructure is ready and merged upstream.  And
   there's work in-progress to get these patches into RHEL
 
 - Integration into virtualization stack -- libvirt to provide an API.

 - Once libvirt provides the API to configure cache reservation, then it
   can be exposed in OpenStack Nova.


About the feature itself:
https://software.intel.com/en-us/articles/introduction-to-cache-allocation-technology

Comment 6 Stephen Gordon 2017-07-25 14:31:23 UTC

*** This bug has been marked as a duplicate of bug 1411864 ***


Note You need to log in before you can comment on or make changes to this bug.