Description of feature: Metrics related to Power/Thermal consumption and performance metric such as bandwidth, frequency, latency and throttling are available OOB through RedFish API in Intel’s latest (Purley) platform. The appropriate RedHat OSP modules should be able to pull these metrics for RSD resources and make them available to OpenStack components via in-band mechanisms Version-Release number of selected component (if applicable): OpenStack Nova version (or other projects as appropriate) in OpenStack Queens release 2. Business Justification: a) Why is this feature needed? RSD is a new architecture that realizes an agile infrastructure where the hardware resources can be pooled according to application needs. It also enables a more easily scaled infrastructure, so CPU, memory, network and storage resources can be added as needed, without the need to do complete replacements of nodes b) What hardware does this enable? New platforms based on RSD architecture c) Is this hardware on-board in a system (eg, LOM) or an add-on card? RSD nodes are disaggregated (CPU, memory, storage, accelerators etc.) d) Business impact? N/A e) Other business drivers: N/A 3. Primary contact at Partner, email, phone (chat) Priyank Durugkar - priyank.durugkar 4. Expected results: - DC admin subscribes to required performance metrics - Openstack then receives the metrics and propagates to other OpenStack components (eg. Nova, Ironic, Cinder) for action Additional info:
Will Intel be driving these upstream and are there specific blueprint etc. links related to this submission?
(In reply to Stephen Gordon from comment #1) > Will Intel be driving these upstream and are there specific blueprint etc. > links related to this submission? Hey Stephen, I am OpenStack developer from Intel, and will work on this item. Will submit the BP soon.
(In reply to Lin Yang from comment #5) > (In reply to Stephen Gordon from comment #1) > > Will Intel be driving these upstream and are there specific blueprint etc. > > links related to this submission? > > Hey Stephen, I am OpenStack developer from Intel, and will work on this > item. Will submit the BP soon. Thanks, as soon as you have a URL please let us know even if it is a draft specification. Joe/Krish the other aspect I need help understanding is who owns testing the overall RSD solution.
(In reply to Stephen Gordon from comment #6) > (In reply to Lin Yang from comment #5) > > (In reply to Stephen Gordon from comment #1) > > > Will Intel be driving these upstream and are there specific blueprint etc. > > > links related to this submission? > > > > Hey Stephen, I am OpenStack developer from Intel, and will work on this > > item. Will submit the BP soon. > > Thanks, as soon as you have a URL please let us know even if it is a draft > specification. > > Joe/Krish the other aspect I need help understanding is who owns testing the > overall RSD solution. Stephen, we will test all our upstream submissions, and also set up a CI/CD environment linked to gerrit for any changes we make to Openstack modules. However, we expect Red Hat to do end-to-end testing (discover-compose-provision-deploy-release-decompose) on RSD hardware, and we can help bring OEMs to the table to provide the hardware
Updates have been tested and posted into the rsd-lib repo at https://github.com/openstack/rsd-lib/tree/master/rsd_lib
This RFE is a priority for RSD and OSP 14. The updates are incremental changes to the work done for RFE #1466874 - addition additional attributes or entities.
Paul, could you add to this BZ the spec(s) and upstream patches related to this effort if/when available? Many thanks.
Ramon, these patches to pull RSD 2.2 telemetry info in rsd-lib have been merged. I list them as two major part: 1. Pull metrics for RSD resources, like System, Processor, Memory. https://review.openstack.org/#/c/543779/ https://review.openstack.org/#/c/543803/ https://review.openstack.org/#/c/544173/ https://review.openstack.org/#/c/544128/ 2. Support new /TelemetryService uri in RSD 2.2 https://review.openstack.org/#/c/543813/ https://review.openstack.org/#/c/544757/ https://review.openstack.org/#/c/549069/
Lin's comment 14 answers Ramons comment 13.
Approving for OSP 14. Paul, Ling, please, once you are able to test it with OSP 14 post the tests and the test results here. Also, as far as I understand this will be included with rsd-lib OSP package, so no new packages are necessary.
As all changes per comment 14 have landed, moving to POST.
This will need QA from your team Krish. Please update the BZ when the QA is done. once you are able to test it with OSP 14 post the tests and the test results here. Thanks, Sean
(In reply to Sean Merrow from comment #20) > This will need QA from your team Krish. Please update the BZ when the QA is > done. once you are able to test it with OSP 14 post the tests and the test > results here. > > Thanks, > Sean Sean, let's have a conversation on this at the weekly meeting on 9/6. I'll ask Mike Brennan to attend, as he's made it very clear to us that the Intel dev team doesn't need to be testing RH OSP Krish
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0045
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days