Bug 1536230
| Summary: | Review Request: rmd - User-space daemon for resource management (RMD) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Krish Raghuram <krishnan.raghuram> |
| Component: | Package Review | Assignee: | Donghai Qiao <dqiao> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | alexander.beregalov, apevec, extras-orphan, kcarcia, krishnan.raghuram, lin.a.yang, liyong.qiao, nhorman, package-review, plai, pragyansri.pathi, sunku.ranganath |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-04-22 12:20:49 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1531160 | ||
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'. New technical contacts from Intel are: Lin Yang - lin.a.yang Sunku Ranganath - sunku.ranganath This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. If you want to add a new package to Fedora, please follow https://fedoraproject.org/wiki/Join_the_package_collection_maintainers I'll re-purpose this BZ as the package review, in case krishnan.raghuram is still going to be the package owner. If not, actual owner will need to open a new BZ https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_Your_Review_Request To proceed with the package review here, please upload spec and SRPM files somewhere and link to them in a comment here with the following format : Spec URL: <spec info here> SRPM URL: <srpm info here> Description: <description here> Fedora Account System Username: This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32. ping, waiting for the spec and srpm files here ping, still waiting on the srpm and spec files ping, its been another week, will the srpm and spec files be getting posted here? Neil - Let me update when we have the srpm available. Thanks We are currently gated by clearance from our open source legal team. *** This bug has been marked as a duplicate of bug 1826621 *** The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
Description of feature: Resource Management Daemon (RMD) is a host-based software that Intel open-sourced in Nov’17, that interfaces with Intel RDT to gather host cache details and publicize it to OpenStack Nova through the Traits API (can similarly publicize to other orchestrators like Kubernetes in the future). It also interfaces with Nova to get the workload policy or flavor information and then enforces the policy through Intel RDT. Discussions have been initiated with the Nova community about the addition of these traits, policies and flavors with a goal of intercepting the Rocky release. Intel would like to work closely with Red Hat to refine, review, test and merge the software into RHEL 8 release Version-Release number of selected component (if applicable): RHEL 8 2. Business Justification: a) Why is this feature needed? As organizations seek to get good ROI on their cloud infrastructure by deploying multiple workloads on shared resources, latency and jitter become issues affecting end-user satisfaction and the business itself. Rather than falling back on inefficient mechanisms for partitioning the infrastructure, opportunity now exists to take advantage of platform enhancements like Intel Resource Director Technology (Intel RDT) to allocate cache appropriately for example to each workload and avoid “noisy neighbors” that hog the cache. Workload usage of cache can be monitored and enforced through the use of this technology, interfacing with orchestration software like OpenStack b) What hardware does this enable? Intel platforms starting with Haswell generation c) Is this hardware on-board in a system (eg, LOM) or an add-on card? On-chip d) Business impact? CSPs can offer premium service for some workloads to eliminate latency and jitter (ie. no noisy neighbors). Private cloud deployments can avoid costly workarounds e) Other business drivers: N/A 3. Primary contact at Partner, email, phone (chat) liyong.qiao 4. Expected results: - A user (or orchestration SW) sets workload policy - RMD publishes host cache & memory availability details to the Traits API - Nova schedules workload onto appropriate host using Traits info, and Nova Compute talks to RMD to enforce policy - RMD initiates remedial action to Nova if needed to enforce policy (migrate noisy neighbors) Additional info: Open sourced at https://github.com/intel/rmd